CIVIL CONTRACTOR UNIT PRICE PRODUCTION TRACKING
Civil contractors bidding unit-price work (per LF of pipe, per CY of dirt, per SF of pavement, per ton of asphalt) win and lose money based on production rate against the bid unit. A bid that assumes 280 LF/day of pipe installation and runs at 215 LF/day burns 23% of the project margin on labor and equipment overrun. Most civil subs don’t track production by bid unit during execution — they track total labor hours by project, total equipment hours by project, and find out at closeout how production actually ran. By then the variance is locked in. Unit-level tracking surfaces the variance within days, not weeks.
Your bid promised 280 LF/day. Your crew is running 215 LF/day. Three weeks into the project, you don’t know that yet — but the margin is already gone.
WHY UNIT-LEVEL PRODUCTION MATTERS
Civil work runs heavily on unit-price contracts — per LF of pipe installed, per CY of earth moved, per SF of subgrade prepared, per ton of asphalt placed, per LF of curb and gutter poured. The bid specifies production rate assumptions for each unit: 320 LF/day of 8" sewer pipe, 1,200 CY/day of mass excavation, 8,500 SF/day of subgrade preparation. The financial outcome of the project depends on actual production matching bid production.
When production runs short of bid, labor cost and equipment cost per unit run high. A bid that priced labor at $8.50/LF for sewer install (based on 280 LF/day at $19/hour crew cost) but executes at 215 LF/day actually costs $11.05/LF in labor — a $2.55/LF overrun, which on a 4,800 LF project is $12,240 of margin compression on that one cost code alone.
Most civil subs don’t see this in real time. Cost reports show labor hours and equipment hours totaled at the project level. Production rate by bid unit isn’t tracked separately. Variance becomes visible at closeout, by which point all the units have been installed at whatever rate the crew managed.
WHY UNIT-LEVEL TRACKING FAILS
BID UNITS NOT MIRRORED IN COST CODING
The bid specifies LF of pipe by size and type. The cost coding tracks “labor — underground” in aggregate. The two don’t connect. Comparison of actual vs. estimated is impossible because the units don’t match. The cost coding has to mirror the bid units for production tracking to work.
DAILY PRODUCTION NOT REPORTED
Crews finish a day’s work without reporting units installed. Total project units roll up at the end. Daily production rate — the thing that surfaces variance early — never gets captured. Crew foreman needs to report daily units against daily hours for the system to function.
EQUIPMENT HOURS NOT TIED TO UNITS
Labor hours sometimes track to projects. Equipment hours typically don’t track to specific phases. The cost per unit math requires both labor and equipment costs allocated to the specific scope. Without equipment-hour allocation, the production rate analysis is incomplete.
VARIANCE DETECTED ONLY AT CLOSEOUT
Project closeout calculates total units installed against total cost. The variance becomes visible — but the project is done. The only fix at that point is updating the next bid. The current project’s margin compression is locked in.
NO FEEDBACK INTO NEXT BID
Even subs that calculate variance at closeout often don’t feed it back into estimating tables. Next quarter’s bids use the same production rate assumptions that produced last quarter’s losses. The variance pattern repeats. Estimating accuracy drifts farther from reality with each project.
HOW UNIT-LEVEL PRODUCTION GETS TRACKED
- Cost coding mirrors bid units. Each unit-priced line in the bid gets its own cost code. Labor and equipment hours allocated to the specific cost code for the specific bid unit.
- Daily production reporting by foreman. Each foreman reports units installed and hours worked daily, by cost code. Five minutes at end of shift. Captures the data while it’s fresh.
- Weekly production rate analysis. Actual production rate (units / hours) calculated weekly by cost code. Compared to bid production rate. Variance surfaces within 7 days of work being performed.
- Mid-project corrective action. Variance detected early enough for corrective action — sequencing changes, crew adjustments, scope clarification, equipment additions. Some of the variance can be recovered if the cause is operational; if the cause is bid assumption, at least the variance gets documented for change order discussion.
- Closeout feedback to estimating. Final project production rates by cost code feed back to the estimating tables. Next quarter’s bids reflect this quarter’s reality. Estimating accuracy compounds across years.
WHAT UNIT-LEVEL DISCIPLINE RECOVERS
A $6M civil sub running average production tracking typically experiences 12–18% variance against bid production rates across the project portfolio. That variance compresses gross margin by 4–8 percentage points. The same business running unit-level tracking and weekly variance analysis typically compresses variance to 5–8%, recovering 2–4 points of gross margin.
On $6M revenue with 22% bid gross margin and 4-point variance compression, the margin recovery is $240K per year. The cost is operational discipline (foreman reporting, weekly analysis cadence) and the cost coding alignment work upfront. No price increases, no new customers, no changed scope.
Civil work is unit-priced. Production tracking needs to be unit-priced too. The bid math and the execution data have to speak the same language.
FREQUENTLY ASKED
