Field Job Costing for Electrical Contractors: A Practical Guide

What field job costing means for an electrical contractor

Field job costing is the loop that connects the estimate, the field, and the bill. You bid the work in cost codes with budgeted labor hours; the crew logs actual hours and installed quantities against those same cost codes; and the office compares the two to see which scopes are making money and which are bleeding — by code, by week, while the work is still in front of you.

For an electrical sub specifically, this is the whole game. A 480 V feeder pull, branch device trim, gear setting, and underground all behave differently; a blended job-level number hides the one scope that is eating your crew. Field job costing breaks the job into the pieces you actually manage and tells you which one to go fix.

The three inputs (and where each comes from)

• •Budget hours — from the estimate: budgeted labor units × quantity, per cost code (see our electrical labor units reference).
• •Actual hours — from the daily report or time clock: who worked, how long, against which cost code.
• •Installed quantity — from the field: how much got installed (LF of conduit, devices set, fixtures hung) per cost code.
• •With those three, earned hours (quantity × budget unit) and the performance factor (earned ÷ actual) compute themselves.

The one number to watch: performance factor

Performance Factor (PF) = Earned Hours ÷ Actual Hours. Above 1.0 you are beating the estimate; below 1.0 you are burning labor faster than you are earning it. Track it per cost code, weekly.

Example: code 26-100 (branch conduit) was bid at 0.045 hours per foot for 4,000 LF — an 1,800-hour budget. Three weeks in, the crew has installed 1,400 LF and burned 75 hours. Earned = 1,400 × 0.045 = 63 hours; PF = 63 ÷ 75 = 0.84. That 0.84 says you are running ~19% over on that scope — and at 2,600 LF still to install, that is a problem you can still attack with crew size, sequencing, or prefab, instead of discovering it at closeout.

Setting it up so the field actually does it

The reason most electrical contractors do not job-cost in the field is data entry. The fix is to make the daily report the single capture point and let everything downstream compute:

• •Keep the cost-code list short and recognizable — codes a foreman can pick correctly in the field, mapped to a unit you can measure.
• •Capture hours AND installed quantity in the same daily report, against the same codes the estimate used.
• •Carry the crew forward day to day and allow voice entry so completion does not depend on thumb-typing in a truck.
• •Review PF by cost code weekly, not job totals monthly — monthly is too late to recover a slipping scope.
• •Feed actuals back into your labor units so next bid is calibrated to how your crews really build.

Why generic GC software falls short for this

GC-oriented platforms (Procore and similar) are built to coordinate the whole project — drawings, RFIs, submittals across every trade — not to center one sub's self-perform productivity by cost code. Electrical subs on those platforms usually end up tracking the number that matters most, labor, back in a spreadsheet.

Software built for the self-perform field closes that gap: the same daily report that documents the day also drives the cost codes, the productivity index, and the AIA pay application. That is the design behind Field PM — field operations and job costing built for electrical and specialty-trade contractors, so the hours a foreman captures become the job-cost report without re-keying.