One number, tracked in real time, tells you more about a contract’s profitability than any monthly report. Here’s how UK shopfitters use actual vs budget hours to protect margin – and why most firms are still getting it wrong.
Ask most shopfitting MDs how a contract is performing and they will tell you two things: how much they’ve invoiced and how much they’ve spent. What they cannot usually tell you – not in real time, not by contract item, not with any precision – is whether the labour hours are running ahead of or behind the estimate. That gap is where margin disappears.
Actual vs budget hours is not a new concept. Every shopfitter who has ever priced a contract and then tried to reconcile the final labour figures has encountered it. The problem is not understanding the metric. The problem is the lag. By the time most firms know that a contract is over on hours, there is nothing left to do about it. This article explains how to track the number in real time – and what changes when you do.
Every contract item in a shopfitter’s estimate carries a labour budget: the number of hours the estimator believes it will take to fabricate and install that item. The sum of all item-level budgets gives you the total contracted labour allowance.
Actual hours is simply the number of hours your operatives have spent on the contract so far – by item, by trade, by location. The variance between the two is the most predictive leading indicator of job margin available to an operations team.
| Why this metric predicts margin Labour is typically 25–45% of a shopfitter’s total contract cost. It is also the most controllable variable mid-contract. Material costs are largely fixed at order; subcontractor costs are fixed at award. If a contract is going to lose money, the early signal is almost always in the hours. A contract that is 15% over on labour hours by the end of Week 4 will not recover by Week 12 unless something changes. The firms that act on that signal in Week 4 protect their margin. The firms that discover it at final account do not. |
The typical process: factory timesheets are collected at the end of the week, typed into a spreadsheet on Monday, and posted to job costing by Tuesday. The production manager or contracts manager runs a labour analysis report fortnightly or monthly. The report compares hours-to-date against the estimate. This process has three structural problems.
A timesheet written on Friday, typed on Monday, and analysed at the fortnightly review is describing work that happened up to two weeks ago. For a twelve-week contract, that means you are always looking in the rear-view mirror. The variance you’re acting on is history, not signal.
Most labour analysis reports show total hours on a contract against a total budget. They do not show which specific items are running over. Without item-level data, you cannot target your response. ‘Contract 214 is over by 80 hours’ tells you there is a problem. It does not tell you whether the overrun is on the joinery, the fit-out, or three specific bespoke units that were under-estimated. Item-level data turns a management report into an operational instruction.
When a contract item runs over the estimated hours for a legitimate reason – a client change, a scope addition, an unforeseen complexity – you have a variation claim. But that claim requires evidence: which item, how many hours, when. If your labour data is weekly aggregates posted to a spreadsheet, assembling that evidence is a reconstruction exercise. If it is real-time item-level scan data, the evidence already exists.
Contract Controller’s production tracking dashboard shows actual vs budgeted hours by contract item, updated as operatives scan in and out on the factory floor. The production manager’s view at 8am Monday morning is not last week’s figures – it is the current state of every live contract.
| Tracking method | When you see the overrun | Can you recover it? | Variation claim possible? |
| Paper timesheets – weekly review | 10–14 days after it happens | Rarely | Difficult – data is reconstructed |
| Spreadsheet – fortnightly report | 14–21 days after it happens | Unlikely | Very difficult |
| Contract Controller real-time dashboard | Same shift it happens | Yes – operational response possible | Yes – scan data is audit-ready evidence |
One of the less-discussed benefits of real-time actual vs budget tracking is what it does to the next estimate. When your labour actuals are clean and item-level, the estimator for the next contract has access to genuine productivity data: how many hours it actually takes your operatives to produce that unit, in your factory, with your processes.
Most shopfitting estimates are built on intuition and memory, refined over years by experienced estimators who have internalised the patterns. Real-time production data makes that intuition explicit and testable. It also catches the drift that happens when operatives, materials, or processes change without the estimate model being updated.
| Key takeaway Actual vs budget hours is not a reporting metric. It is a management tool. Its value is proportional to how quickly you can act on it. A fortnightly report makes it a post-mortem. A real-time dashboard makes it a margin-protection instrument. If your current system tells you what happened last month, you do not have a production tracking system – you have a history book. |
Contract Controller’s production tracking module is included as standard. Actual vs budget hours by contract item is visible in the production manager dashboard from the moment operatives begin scanning. No configuration, no separate report to run, no spreadsheet to maintain.
To see the production tracking dashboard in action, visit:
