Read site productivity without blaming the wrong crew

State the activity, location, period, unit of output and the work included. Clarify whether the quantity represents installed work, inspected work or accepted work. Identify which crew hours are included: all paid site hours, assigned activity hours or a narrower productive-hours measure.

Use the same boundary for numerator and denominator. Output completed by another crew or outside the measured period should not be credited to the selected hours without an explicit adjustment. Conversely, excluding waiting hours can make an activity appear efficient while hiding the site's actual resource cost.

Keep the source records available. Procore's Daily Log documentation illustrates separate manpower, equipment and productivity records. The important implementation choice is to connect those observations with the project's quantity and acceptance evidence using consistent activity and time definitions.

In this fictional example, a crew records 80 crew-hours during the period and installs 40 metres of pipe. At the reporting cut-off, 35 metres are accepted and five metres require rework that has not yet been performed. Gross installed productivity is 40 divided by 80, or 0.5 metres per crew-hour.

Accepted-output productivity at that cut-off is 35 divided by 80, or 0.4375 metres per crew-hour. The five metres remain installed but unaccepted. Do not count them as new production again when corrected. Additional rework hours must be recorded in the later period or cumulative view under the stated measurement policy.

Neither figure alone explains why rework arose or whether the crew caused it. The technical and quality review may identify design changes, material issues, access conditions, workmanship or another cause. Preserve that investigation separately from the arithmetic.

Suppose some of the 80 hours were spent waiting for access. If you also report productive-hours efficiency, clearly identify the hours excluded and why. Do not replace the all-hours measure with the narrower figure without telling the reader; the two answer different management questions.

A simple time classification can distinguish direct activity, waiting, rework and other approved categories, provided the definitions are practical for site users. Avoid asking supervisors to reconstruct minute-by-minute precision they did not record. A reasoned, acknowledged estimate should be labelled as such.

Review waiting causes with the responsible teams. Access release, materials, equipment and preceding work may sit outside the crew's control. The useful action may be to improve work-front readiness rather than demand a higher hourly rate from the same people under unchanged conditions.

Pipe diameter, material, joint type, elevation, congestion, inspection requirements and work method can materially change the task. The responsible engineering and planning team should determine which characteristics matter for the comparison. A common unit of metres does not make all pipe installation equivalent.

Compare similar packages and periods first. If conditions differ, show the differences and treat the comparison as a prompt for investigation. Do not invent adjustment factors merely to produce a ranking. Any standard or planning norm used should have a defined basis and an owner who can explain its applicability.

Use trends carefully. A crew may improve as repetitive work progresses, while the remaining work becomes more difficult. Changes in the mix can move the average even if performance within each activity is stable. Report the mix alongside the aggregate when it affects the decision.

A planner can use observed rates to review remaining-duration assumptions, but only after assessing whether the remaining scope and conditions are comparable. Keep the estimate range and assumptions visible. A short period of unusually favourable work is a weak basis for a firm completion forecast.

The estimate-to-project handover guide explains why the original productivity basis needs to survive into execution. Compare actual conditions with that basis before labelling a variance as poor performance.

When the team changes the work method or removes a constraint, define what improvement would be observable and over what period. Record the intervention and relevant context. Do not claim that a dashboard caused productivity gains merely because a later number is higher.

A daily register linked to accepted quantities may be sufficient for a focused activity. Integration becomes useful when attendance, work allocation, quantity measurement and quality evidence live in different systems. The challenge is reliable association, not simply more frequent data collection.

Test duplicate quantity entries, a late acceptance decision, a crew split between two fronts and rework in a later period. The system should preserve both the original cut-off view and the corrected or cumulative position. It should not silently restate last week's report without a traceable reason.

Keep reporting at the level needed for planning and improvement. Do not use incomplete activity data to automate adverse decisions about individual workers. Personnel decisions require their own appropriate process, evidence and opportunity to correct errors.

An effective productivity review ends with a specific operating action: verify the quantity boundary, resolve access, improve material readiness or review a method with the qualified team. It does not end with an unexplained red cell beside a crew name.

The pipe example demonstrates why gross output, accepted output and hours should remain visible together. A useful report makes the calculation reproducible and the context available before anyone draws a conclusion.

1. Define one activity's quantity, acceptance and crew-hour boundaries.
2. Recalculate gross and accepted-output rates from the same period's evidence.
3. Review waiting, rework and work-front conditions with the responsible teams.
4. Test a focused improvement and compare like work without turning the metric into an automatic personnel judgement.