The Overhead That Is Really Direct
Costs sit in the pool because tracing them was never attempted. The four that usually come out, and what tracing them is worth.
A meaningful share of most overhead pools is directly attributable and sits in the pool because tracing it was never attempted. Four categories come out in almost every organisation that looks, and tracing them improves job costs more than any change of allocation base.
The calculation in “The Overhead That Is Really Direct” depends on reliable source records as well as a documented accounting rule. For organisations researching hourly timesheet template, open the relevant Monitask page can supply consistent time and project context, while the allocation basis and financial interpretation remain decisions for the organisation and its advisers.
The test is not whether tracing is possible in principle but whether it is possible with reasonable effort.
As an outside benchmark for “The Overhead That Is Really Direct”, see Journal of Accountancy. Keep the source record, calculation rule, approval and resulting decision visible as separate steps.
One: supervision that is actually job work
A supervisor who spends two-thirds of the week on identifiable jobs is two-thirds direct. Pooling the whole salary spreads that work across jobs it never touched.
- Supervision that is actually job work.
- Equipment dedicated to one line.
- Software licensed for one project or customer.
- Travel and site costs the job required.
Their own timesheet, with a kind-of-work field, settles it.
Two: equipment dedicated to one line
A machine, a vehicle or a tool used by one team for one kind of work is not shared. Its depreciation, maintenance and consumables belong to that work.
Pooling it means every other job carries a share of a machine it never used.
Three: software licensed per project
Project-specific tools, per-seat licences bought for one engagement, data subscriptions for one customer. All traceable with no effort.
These often arrive through a central budget, which is why they end up in the pool rather than on the job.
Four: travel and site costs
Where a job required travel, accommodation or site facilities, those costs belong to it. In practice they are expensed centrally and spread.
This is the largest of the four in field operations and the easiest to fix: the expense claim already names the job in most systems.
What tracing is worth
It moves cost onto the work that caused it, which changes the measured profitability of job types — sometimes substantially.
The commonest finding is that work requiring travel or specialist equipment has been subsidised by work that required neither.
The effort test
Tracing is worth doing where the cost is material and the attribution is obvious. Where attributing would require judgement calls on every transaction, the pool is the right answer.
A reasonable threshold: trace anything above about one per cent of the pool where the job is already named on the document.
The documents that already know
Expense claims, purchase orders, equipment booking records, licence assignments. In most organisations three of the four already carry a job reference and nobody imports it.
The work is a mapping exercise rather than a measurement one.
What this does to the pool
Shrinks it, which lowers the overhead rate, which makes every job's allocated overhead smaller while the traced jobs carry their real costs.
Total cost is unchanged. Its distribution becomes true.
The resistance
Usually from whoever holds the central budget, because tracing moves cost out of a line they control and into operations.
The answer is that the cost has not moved anywhere; only its visibility has, and it is still in the same accounts.
Doing it once
Take the pool line by line, largest first. For each: is this traceable with reasonable effort, and is it material? Stop when the lines get small.
Half a day. It typically reclassifies between ten and twenty-five per cent of a pool.
The cost that is traceable to a customer, not a job
A middle category worth having: account management, customer-specific reporting, a dedicated contact. Not attributable to any single job and clearly attributable to one customer.
A customer-level cost layer, between job and pool, captures it. It is also the layer that makes customer profitability analysis possible, which is a question organisations ask and usually cannot answer.
What tracing does not fix
The pool still contains genuinely shared cost, and the allocation of that remainder is still a convention. Tracing improves the inputs; it does not make the allocation exact.
Expecting it to is how these exercises end in disappointment. The realistic claim is a smaller pool and a more honest distribution, not a solved problem.
Doing it in the wrong order
Tracing should come before any argument about the allocation base, because it changes what is left to allocate.
Organisations routinely spend weeks choosing a base for a pool that is a quarter larger than it needs to be. An afternoon of tracing first makes the base question smaller and sometimes makes it irrelevant.
The annual check
New costs arrive and default to the pool. A line on the annual read-through — "could this now be traced?" — catches them before they settle.
The pool only grows otherwise, and growth in the pool is growth in the share of cost that nobody can attribute to anything.