PRODUCTION RATES VS ESTIMATING ASSUMPTIONS.
Most construction margin leakage starts before the job begins — in the gap between the production rate used in the estimate and the production rate the crew actually delivers in the field. If your estimate assumes a crew installs 400 linear feet of conduit per day and they're consistently delivering 320, every similar bid is 25% under-labored before anyone touches a tool. CFOS closes this gap by reconciling estimated production rates against field actuals every month and adjusting your estimating templates accordingly.
The estimator did their job. The field did their job. The margin still disappeared. That's the production rate gap — and it's the most common source of systematic underbidding in commercial subcontracting. This page covers how it works, where to find it in your job cost data, and how to close it.
THE UNIT THAT DRIVES EVERY LABOR ESTIMATE.
A production rate is the measure of how much work a crew can complete in a unit of time — linear feet of pipe per day, cubic yards of concrete placed per hour, square feet of drywall hung per crew-day. Every labor estimate is built on a production rate assumption, whether the estimator states it explicitly or not.
When an estimator looks at a scope and says "that's an 8-day job for a 4-man crew," they're implicitly using a production rate. The question is where that rate came from: a manual standard, an industry table, the estimator's gut feel, or actual field data from your own crews on your own projects.
The source matters enormously. Industry standards are averages. Your crews are specific. Your field conditions are specific. Your labor burden rate is specific. A production rate from an RSMeans manual is a starting point — not a bid number.
WHY ESTIMATED RATES MISS FIELD REALITY.
Best-Day Assumptions Instead of Average-Day Reality
Estimators naturally anchor on the best they've seen their crews do — a productive stretch on a straightforward project with no coordination issues, good weather, and experienced hands. Field reality includes Mondays after long weekends, crews waiting on inspections, GC coordination delays, material deliveries that arrive late, and the inevitable training drag when a new crew member is being brought up to speed. Average-day production is typically 15–25% slower than best-day production. Estimates built on best-day assumptions get beaten by average-day reality every time.
Busy-Month Utilization Instead of Full-Year Reality
A fiber splicing contractor we worked with was pricing T&M work based on the production rate his crews hit during their busiest months — when every technician was fully deployed and there was no slack in the schedule. But overhead doesn't stop between jobs. In slower months, the same crew's effective production rate (measured against total labor cost including down time) was 30–40% lower than the busy-month rate. Every T&M quote built on the busy-month assumption was underpricing work in any month that wasn't peak utilization. Which was most months.
Stale Rates That Haven't Been Updated for Wage Increases
A labor production rate in dollar terms — not hours — compounds the wage increase problem. If your fully-burdened labor rate went up 8% this year due to prevailing wage adjustments or market competition, and your estimating template still uses last year's dollar rates, every bid is understated by at least 8% on the labor line. Estimating templates that aren't updated with current burden rates after every wage change become increasingly inaccurate over time — quietly eroding margin without anyone noticing the cause.
No Feedback Loop Between Estimates and Field Actuals
The most common version: the estimator builds the bid, the project runs, the PM reviews the cost-to-complete. But the estimator never sees the final variance. The bid assumptions never get tested against what actually happened. So next month's bid for similar work uses the same assumptions that caused last month's overrun. Without a structured feedback loop — estimated production rate vs actual production rate on every closed job, reviewed by the estimator — the gap compounds indefinitely.
ESTIMATED VS ACTUAL: A REAL EXAMPLE.
Underground utility contractor. $420,000 sanitary sewer installation. Labor estimate: 18 crew-days at $6,200/crew-day fully burdened = $111,600. Actual field result from job cost report:
Total LF: 1,710
Crew-days: 18
Burden rate: $6,200/day
Estimated labor: $111,600
Total LF: 1,710
Crew-days: 23.1
Burden rate: $6,400/day (wage increase)
Actual labor: $147,840
Labor variance: $36,240 over — a 32% overrun on a single phase. On a $420,000 job with 22% target gross margin, that variance alone erases 8.6 points of gross margin. The job that was supposed to land at 22% closed at 13.4%.
The estimator wasn't wrong to use 95 LF/crew-day — it's what the crew had historically delivered on similar work in ideal conditions. But this project had two creek crossings, a rocky sub-base on 40% of the run, and a new crew member on the second half. Average-day reality for this specific project was 74 LF/day. Without historical project data sorted by site condition type, there was no way to know the right rate at bid time.
CLOSING THE GAP — HOW CFOS DOES IT.
FREQUENTLY ASKED.
