Does connecting field production to job costing require new software?

No. A standardized daily field log in the same units as the estimate captures what is needed. Software makes it faster but the methodology works with a well-designed spreadsheet and consistent field discipline.

What is the biggest advantage of cost-per-unit over cost-per-hour?

Cost per hour tells you what was spent. Cost per unit tells you what was accomplished per dollar — which is the efficiency measure the estimate was built on. Cost per hour alone cannot tell you whether a crew was efficient or just fast.

How does production rate feed the cost-to-complete calculation?

Monthly cost-to-complete uses actual production rates from the prior 30 days rather than the original estimate rate. If the job ran 75 yards per hour against an estimated 110, the projection uses 75. The forecast is a real prediction, not a hope.

JOB PROFITABILITY — FIELD OPERATIONS

PRODUCTION WITHOUT COST IS SPEED. COST WITHOUT PRODUCTION IS SPEND.

QUICK ANSWER

Field production tracking and job costing answer different questions. Production tracking tells you what was built — yards poured, feet drilled, square feet framed. Job costing tells you what it cost. Together they tell you whether the cost was efficient. Separately they tell you almost nothing useful. A crew that poured 180 yards in 9 hours spent $2,700 in labor. Was that on track? Depends on the estimate. Without connecting production to cost, that question cannot be answered until the job closes.

COST PER UNIT TELLS YOU MORE THAN EITHER NUMBER ALONE.

BY JOSH LUEBKER Published: June 2026 Updated: June 2026

The Gap Between Field Operations and Financial Reporting

FIELD TRACKS OUTPUT. ACCOUNTING TRACKS INPUT.The foreman logs hours worked. The PM tracks schedule. Nobody connects how much was built to what it cost to build it. The result: accounting knows what labor was paid; the field knows what was installed; nobody knows whether the cost-per-unit is on track with the estimate.

PRODUCTION RATE PROBLEMS SURFACE AT JOB CLOSEWhen job costing has no production context, a labor overrun looks the same whether it came from running 110 hours on a task that needed 80 (productivity problem) or from scope expanding without a CO (billing problem). The interventions are completely different. Without production data, the cost variance alone cannot tell you which one it is.

ESTIMATES ARE BUILT ON PRODUCTION RATES. JOB COSTS SHOULD BE EVALUATED AGAINST THEM.Every estimate contains production rate assumptions — concrete placed per day, pipe installed per hour, square feet framed per week. Those assumptions are the basis for the bid price. If job costing doesn't track against those same units, the estimate and the actuals are speaking different languages and meaningful comparison is impossible.

How CFOS Connects Field Production to Job Costing

DAILY FIELD LOG IN PRODUCTION UNITSCrew logs production daily by phase and unit type — yards, linear feet, square feet, tons. 5 minutes at shift end. The log uses the same unit definitions as the estimate so the comparison is direct: estimated 280 yards this week, installed 220 yards, labor was $4,100 instead of $3,200. Cost per yard: $18.64 actual vs $11.43 estimated. That is an actionable number.

WEEKLY COST-PER-UNIT CALCULATIONBy end of each week: units installed vs plan, labor cost vs plan, cost per unit vs estimated cost per unit. Variance above 10% triggers a review. Is it a crew productivity issue? A soil condition change? An undocumented scope addition? Each cause requires a different response — and the response is only available while the job is still running.

PRODUCTION RATE FEEDS COST-TO-COMPLETEMonthly cost-to-complete uses the actual production rate from the prior 30 days — not the original estimate rate — to project remaining cost. If the job ran 75 yards per hour in month one against an estimated 110, the month-two forecast uses 75. The projection is a real prediction, not a hope based on the original assumption.

PRODUCTION + COST LOOKS DIFFERENT IN EVERY TRADE.

Excavation & Grading

Cubic yards per hour is the master number. The estimate assumed 110 CY/hr; the GPS data says the crew ran 75. Cost per yard just went up 47% and the job is three weeks old. Connect machine telemetry to the cost ledger and the variance shows up Friday — not at closeout.

Concrete

Yards placed per crew-day, by pour type. Slab pours and elevated deck pours have completely different production curves; one blended number hides which pour types are bleeding. The flatwork crew that places 85 yards on grade and 40 on deck isn't slow — the estimate that used one rate for both was wrong.

Masonry & Framing

Units per mason-day, board feet per carpenter-day — tracked by elevation and floor. Production drops predictably with height; the question is whether the bid accounted for it. Floor-by-floor production tracking shows the curve. One labor code for the whole building shows nothing.

Fiber & Telecom

Splices per tech-day against the rate sheet. T&M trades think production tracking doesn't apply to them — it applies more. When the rate is fixed, production is the only margin variable left. A tech running 60% of standard production on a fixed-rate contract is losing money invisibly on every single day.

WHAT CHANGES WHEN THE TWO SYSTEMS CONNECT.

Week 2

When the variance becomes visible. A crew running 36% under estimated production shows up in the first connected weekly report. Without the connection, the same problem surfaces at 60% complete — when the labor budget is spent and the only options are eat the loss or fight for a claim. The entire value of the connection is the timing.

$47K

One job's caught overrun. An excavation contractor's production-to-cost report flagged a cut operation running 28% under rate in week three. Cause: a haul route that doubled cycle time. The fix — a second access point — cost $4K and saved a projected $47K labor overrun. The data didn't fix the job. It made the problem visible while fixing it still mattered.

Every Friday

The cadence that makes it real. Production-to-cost reporting only works on a weekly cycle. Monthly is an autopsy. SPM clients run it Friday afternoon: units in place from the field, labor dollars from payroll, variance by cost code on one page. Fifteen minutes per job. The PMs who have it stop being surprised by their own projects.

Frequently Asked Questions

No. A standardized daily field log — paper or spreadsheet — captures what is needed. SPM builds the log format to use the same units as the estimate so the weekly comparison is direct. Software makes the connection faster and more automated, but the methodology works with a well-designed spreadsheet and consistent field discipline.

The foreman enters the daily field log at shift end — they are on site and know what was actually accomplished. The PM reviews the weekly summary and flags variances. Accounting uses the data for cost-to-complete. The foreman's job is to record accurately. The PM's job is to act on what the data shows.

Cost per hour tells you what was spent. Cost per unit tells you what was accomplished per dollar. A crew running 9 hours at $300 per hour that installed 180 yards has a cost per yard of $15. A crew running 12 hours at $300 per hour that installed 300 yards has a cost per yard of $12. The second crew worked more hours and cost more in total — but was more efficient. Cost per hour alone would flag the second crew as the problem.

Make it lighter than what they already do. Crews resist forms that feel like surveillance and take twenty minutes — they don't resist a foreman texting three numbers at quitting time: yards moved, block laid, feet spliced. The system's job is to make capture nearly invisible: photo of the quantity sheet, voice note, one-line text. SPM builds the capture method around how each crew already communicates. When the foreman sees the Friday report catch a problem that would've landed on him at closeout, resistance usually converts to ownership.

Yes — telemetry is a convenience, not a requirement. Manual quantity reporting (foreman counts, survey shots, load tickets, splice logs) feeds the same weekly variance report. Plenty of SPM clients run the full system on a text message and a spreadsheet the bookkeeper updates Friday morning. The technology question is secondary. The system question — does field output connect to labor cost weekly, by cost code — is the one that determines whether you see problems in week two or at closeout.