What crew productivity assumption log means in practice
A crew productivity assumption log records how much work an estimator expects a crew to complete in a stated period. It belongs beside the estimate because labor hours can look exact while resting on an unrecorded judgment about crew size, work area, or site conditions. Write down the basis before the rate is used so the reviewer knows what the labor extension assumes.
Use the log with the larger crew build-up review workflow. A crew build-up identifies the workers and equipment in the operation; the productivity log explains the output assigned to that crew. Keeping those records together lets another estimator trace labor hours without reconstructing the original reasoning.
Record the assumption, not merely the resulting unit labor. Note the measured activity, its unit, the crew, expected output, and the condition behind that output. The estimator still has to judge whether the assumption fits the drawings and the planned method of work.
A practical workflow
Begin with the activity as it appears in the takeoff. Give it a plain description and cite the plan, detail, or specification that defines the work. If an addendum changes the assembly or access, update the log entry rather than leaving the old production basis attached to the new scope.
Match the production unit to the estimate. A crew may place work by each, linear foot, square foot, cubic yard, ton, hour, or crew day. When the takeoff and production units differ, show the conversion beside the assumption.
Hidden conversions make it hard to tell whether a labor variance comes from quantity or productivity. Add the condition that makes the rate plausible. Access, phasing, working hours, congestion, repetition, and existing conditions can change what the same crew completes.
A short note such as which area or phase the rate covers is more useful than a bare production number copied throughout the estimate. Before closing the estimate, sort the log by labor value and uncertainty.
Review the assumptions that drive the most hours, then check entries based on incomplete details or unusual project conditions. The log should also identify open questions and who must resolve them.
Common risks to watch
A common failure is copying a familiar rate into a different job without carrying over its conditions. The number may have come from open access, repeated floors, or a particular crew composition. Once that context disappears, the rate looks more dependable than it is.
Another risk is using one rate across unlike areas. A project can contain repetitive work and constrained work under the same cost code. Separate entries preserve that difference and allow the estimate to weight each condition by its own quantity.
The log also fails when exceptions have no owner. Professional estimating guidance from AACE International emphasizes documentation, judgment, and clear practice because estimates become business commitments. An estimator should be able to explain why a production assumption applies and which unresolved condition could change it.
Review checks before final use
Trace the major labor lines from the estimate back to their log entries. Confirm that the quantity, production unit, crew, and conversion produce the labor hours shown in the cost detail. A broken link here can hide both arithmetic errors and an outdated basis.
Compare entries across similar activities. Large differences may be justified by access or phasing, but the reason should appear in the log. Identical rates also deserve scrutiny when the work occurs under visibly different conditions.
Check that addenda, alternates, and exclusions reached the affected assumptions. A deleted area should not leave labor in the base bid, and an alternate should carry the rate intended for its own scope. Document control and productivity review meet at this point.
Finally, hand the estimate and log to someone who did not prepare them. That reviewer should be able to locate the basis for a major labor line and understand any open condition without relying on a private message or the preparer's memory.
| Review area | What to check | Why it matters |
|---|---|---|
| Basis | Current documents and stated assumptions | Sets the comparison baseline |
| Scope | Inclusions, exclusions, and interfaces | Finds coverage gaps |
| Timing | Dates, duration, and validity | Exposes schedule effects |
| Adjustment | Difference and estimate treatment | Keeps totals explainable |
| Closeout | Owner, decision, and approval | Creates accountability |
Where remote estimating support fits
Remote estimating support can maintain the log while takeoff and pricing progress. A support estimator can enter activities, connect source references, check units, and flag missing production bases. This work is easiest to review when the estimate and current bid documents are available in the same controlled workspace.
The lead estimator should still approve the rates and their application. Support staff can prepare the record and surface conflicts, but the contractor decides whether the assumed crew and output fit the planned means, scope, and bid risk. The log also gives reviewers a clean handoff to the labor burden review.
Crew output determines base labor hours, while burden determines the cost applied to those hours. Reviewing the two separately makes it easier to find whether a labor difference comes from production or from the wage and burden build-up.
