How to Compare Quoted Labour Hours With Actual Labour Hours
You quote a job allowing:
24 labour hours.
By the end of day two, the team has already used:
21 hours.
The work is only 60% complete.
That job may already have a margin problem.
But if nobody compares the hours until payroll or month-end reporting, the warning arrives too late.
Your Quote Already Contains a Labour Budget
When pricing work, you normally make some assumption about labour.
For example:
2 technicians × 12 hours = 24 quoted hours
That gives the job a labour budget.
Once work begins, actual time can be measured against it.
The useful number is not simply:
How many hours have we used?
It is:
How many hours have we used compared with what we allowed?
Track Actual Time Against the Job
Technicians may already record:
- start time,
- finish time,
- timesheets,
- job clock-ins,
- travel,
- or site attendance.
That information can feed the job automatically.
For example:
Quoted Labour: 24 hours
Actual Labour: 16.5 hours
Remaining Labour Budget: 7.5 hours
Now operations can see the position while the job is still active.
Add a Percentage
A simple percentage makes the position easier to understand.
For example:
Labour Budget Used: 69%
That becomes much more useful when compared with job progress.
If the job is:
80% complete
and labour is:
69% used
the position may be healthy.
If the job is:
50% complete
and labour is:
90% used
something probably needs attention.
Flag Jobs Before They Exceed Budget
The system can surface exceptions automatically.
For example:
70% of labour used → monitor
90% of labour used → warning
100% of labour used → over budget
Management does not need to inspect every active job.
They only need to see the ones moving outside the expected range.
Understand Why Labour Runs Over
The next question is:
Why?
Common reasons might include:
- underestimated scope,
- return visits,
- missing materials,
- access problems,
- inexperienced technician,
- customer changes,
- rework,
- travel,
- or incorrect quoting assumptions.
Capturing the reason turns an overrun into useful information.
Separate Productive Time From Avoidable Time
Not every extra hour means the job was quoted badly.
A technician may spend two hours waiting because materials were missing.
That is different from needing two extra hours to complete the actual work.
You might track:
Installation Time
Travel
Waiting
Rework
Additional Customer Work
Now the business can see what is actually consuming the labour budget.
Feed the Learning Back Into Quoting
This is where the data becomes valuable.
Suppose the last 20 installations were quoted at:
16 hours
but the average actual labour was:
21 hours
That is not just an operations problem.
It is a pricing signal.
Future quotes may need:
- more labour,
- a different crew assumption,
- different pricing,
- or a change to the process.
Actual job data can improve the next quote.
Include Labour Cost, Not Just Hours
Once the hours are reliable, you can also calculate actual labour cost.
For example:
Quoted Labour Cost: €800
Actual Labour Cost So Far: €720
Remaining Budget: €80
Now the impact on job margin becomes much clearer.
You can combine that with materials and other job costs to build a live profitability view.
Do Not Wait Until the Job Is Finished
Traditional job costing often tells you:
This job lost money.
after the job is already closed.
That is useful for learning.
But it cannot save the job.
Tracking labour while work is still underway gives operations a chance to respond.
Maybe you:
- change the crew,
- investigate the delay,
- approve a variation,
- prevent another visit,
- or adjust the remaining plan.
Start With One Job Type
Choose a type of work you complete regularly.
For the last ten jobs, compare:
Quoted Labour Hours
against:
Actual Labour Hours
Then ask:
- How accurate are your estimates?
- Which jobs ran over?
- Why?
- Is there a repeatable pattern?
At 5M Consulting, we help trade and service businesses connect quoting, timesheets and job costing so operational data can show where margin is disappearing before the job is finished.
You already estimated how long the work should take.
Your systems should tell you when reality starts moving away from that estimate.