Note
Actual vs. Quoted: Where Project Margin Disappears
You quoted the job. You did the job. You closed it. Somewhere between those three points, the actual project cost exceeded what you estimated, and the margin you expected to earn became something smaller.
Most electrical contractors who install systems in factories know this happens. What they rarely know is by how much, on which projects, and why. The quoted margin is easy to see: labor at X technician-days, materials listed, overhead applied. The actual project cost is harder: it only exists after the project closes, and by the time it closes, the next project is already running.
Why Most Contractors Cannot Answer the Profitability Question
After you close a project, can you answer this: did it make money at the margin you expected?
Most contractors answer with something like: “The invoice went out, the customer paid, so yes.” But that answer does not account for whether the labor ran over budget, whether there were return trips not charged back, or whether scope was added and absorbed without a variation order.
The reason is that actual cost lives in the field: which technicians were on site for how many days, whether anyone drove back for missing paperwork, and what got done outside the original scope. That data has to be captured at close. It does not arrive on its own.
Where Does the Actual vs. Quoted Gap Come From?
Three sources account for most of the variance between a quoted project cost and an actual one.
-
Technician-days over budget. A project quoted at six technician-days runs to seven and a half. Site access was restricted during active production. A panel location shifted. Cable routing took an extra pass. Half a day over on three technicians is still one and a half days of labor cost that the quote did not carry. Across a full month of projects, small overruns on individual jobs accumulate into a consistent gap between expected and actual margin.
-
Return trips. A technician leaves site without the signed handover. They go back. A cable run is short from the delivery. A technician drives out again. The site engineer asks for photos of a section that was skipped. Someone makes the trip. Return trips consume full travel and setup overhead for work that is, in most cases, minutes of actual labor. The time disappears into a technician-day already allocated to a closed job with no corresponding revenue.
-
Scope additions that were not billed. During install, the factory asks to add two lighting points. The crew does it because it is easy. Nobody writes a variation order. The materials and labor disappear into the job. This is ordinary. The question is whether it shows up anywhere after the close.
What Does a Return Trip Actually Cost a Project?
Take an eight technician-day project: two technicians, four days each. One return trip happens because the handover document was not completed on the final day. The round trip is 80 kilometers. The technician is on site for 45 minutes, then returns.
The project’s actual labor becomes eight and a half technician-days instead of eight. Now consider the margin impact: if the project was quoted with a 15% gross margin on labor and labor was exactly right at eight days, that half-day addition does not reduce margin proportionally. The revenue figure is fixed; the cost is higher. The proportional impact on gross margin is two to three times the proportional impact on labor days.
Run that arithmetic across five projects in a month, each with at least one return trip, and the drag compounds into something that shows up in the bank account with no obvious explanation.
Can You Fix This Without Tracking Every Hour?
You do not need to track every hour. You need to track the unit that drives your cost: technician-days per project.
At the start of a project: how many technician-days were quoted? At the close: how many technician-days actually ran, and were there any return trips?
That comparison, done at close on every project, gives you the one number that tells you whether the job ran to margin. Over 10 or 20 projects, it shows which site types, which scope items, and which phases of the install tend to slip.
How Does Closing Data Improve the Next Quote?
When you close a project with a signed handover and a job order for every technician on every day, you have the actual labor record: site type, scope, technician-days used, and whether any return trips occurred.
Accumulated across 12 months of projects, that comparison becomes a quoting reference that no industry benchmark can match. You know that LED retrofits in factories with active production run about 10% over quoted labor in your operation. You know that solar installations with restricted rooftop access take an extra crew-day. You know which scope items routinely generate return trips. These are not generic figures: they are specific to your crews, your site types, and your suppliers, and they only exist if the close was clean.
The Feedback Loop That Most Contractors Are Missing
The path from a completed project to a more accurate next quote:
- Job orders capture actual technician-days by site, attributed to the right project and the right date
- The closing gate prevents a job from entering the billing queue until the handover document is signed, which eliminates the return trips caused by missing paperwork
- The site register records what was installed and when, making scope additions visible
- The project-level view shows quoted versus actual labor at close, for anyone who looks
A contractor with this loop running can compare actual against quoted on any closed project in a few minutes. After six months, they can spot the patterns that consistently cost them margin and fix the estimate before the next job starts.
FAQ
Is this only relevant for larger projects?
No. Margin variance from return trips and scope additions happens on small and large jobs alike. On a small job, a single return trip can consume the entire profit on the labor component.
My technicians have been doing this for years. Does comparison data still help?
Experienced estimators are better than new ones. But experience fills in the average. It does not show you which specific site types or scope combinations are consistently over budget in your operation. Closing data shows the exceptions that intuition rounds off, which is where the margin drift usually hides.
Where do I start if I have no comparison data right now?
Pick five recently closed projects. Write down the technician-days quoted and the technician-days that actually ran, including any return trips. If you can answer both from your records in under ten minutes, run the comparison. If you cannot, that is your starting point: close the next project with a signed handover and a job order for every day on site, then compare.
If building a clean close into every project is the part that has not happened yet, that is exactly what we install in 30 days. See how the program works at /program/, or book a call to go through your own numbers.