Establishing Labor Productivity Norms
You can't measure "above" or "below" without a baseline of "normal." A productivity norm is the expected hours-per-unit under defined conditions — where it comes from, and how to adjust it honestly for the job in front of you. Built on AACE 73R-13.
What a productivity norm is
A norm is a reference point, not a law of nature. Its whole value comes from being clearly defined: what work, measured how, under what conditions. A norm of "8 hours per tonne of steel" means nothing until you know it assumes, say, a particular crew, standard access, normal weather, and a specific scope of "installed."
Where norms come from
Norms are built from data, ideally several sources cross-checked against each other. The main sources, roughly best to weakest for your specific work:
- Your own historical data — Productivity actually achieved on your past projects (Lesson 25's measurements). The most relevant source — it reflects your crews, methods, and conditions.
- Published reference data — Industry estimating manuals and databases (e.g., RSMeans-type sources). Broad and convenient, but generic — calibrate to your reality.
- Work/time study — Direct observation and measurement of a specific operation. Precise but effort-intensive; reserved for high-value or repetitive work.
- Expert judgment — Experienced estimators and supervisors. Valuable for filling gaps, but should be sanity-checked against data, not used alone.
Adjusting norms for conditions
A base norm describes "normal" conditions. Real jobs rarely are. You adjust the norm up or down with adjustment factors that reflect the actual conditions of the work in front of you:
Using norms — and keeping them alive
Once established, norms do three jobs across the project lifecycle: they price the estimate, they set durations for the schedule (quantity ÷ crew output, per Lesson 9), and they give you the baseline to measure against for control and claims. The same norm threads through estimating, scheduling, and forensics.
Ten things to remember
- A productivity norm is the expected rate for defined work under defined conditions.
- It's the baseline that gives "better/worse" meaning — the reference for measurement.
- A norm without conditions is meaningless — it must travel with its assumptions.
- Build norms from data — your history first, then published data, study, and judgment.
- Your own historical data is the most relevant — calibrate generic sources to your reality.
- Garbage in, garbage out — clean measurement (Lesson 25) makes trustworthy norms.
- Adjust the base norm for actual conditions — height, congestion, weather, learning curve.
- Document every adjustment factor and its basis — the same vocabulary as disruption claims.
- Norms price estimates, set durations, and baseline control — one rate, three jobs.
- Treat norms as a living asset — feed completed jobs back so each estimate gets sharper.
Glossary
- Adjustment factor
- A multiplier reflecting a condition (height, weather, etc.).
- Applied norm
- The base norm adjusted for a specific job's conditions.
- Base norm
- The rate for "normal"/reference conditions, before adjustment.
- Feedback loop
- Measuring actuals to refine norms for future work.
- Historical data
- Productivity achieved on past projects — the prime source.
- Productivity norm
- An expected productivity rate under defined conditions.
- Published reference data
- Industry estimating databases; generic, needs calibration.
- Work/time study
- Direct observation to measure a specific operation.