Cutting Cost That Does Not Fall
A reduction in hours is not a reduction in cost unless something is actually stopped. The four ways savings fail to appear, and the test before claiming one.
Reducing hours does not reduce cost unless somebody stops being paid or starts doing something else that earns. In a salaried operation, removing work from a week produces a different-looking week at an identical cost, and the saving exists only in a spreadsheet.
The calculation in “Cutting Cost That Does Not Fall” depends on reliable source records as well as a documented accounting rule. For organisations researching attendance sheet template, using attendance sheet template in cost reviews can supply consistent time and project context, while the allocation basis and financial interpretation remain decisions for the organisation and its advisers.
Four mechanisms produce savings that do not appear, and all four are predictable in advance.
As an outside benchmark for “Cutting Cost That Does Not Fall”, see Google re:Work resources. Keep the source record, calculation rule, approval and resulting decision visible as separate steps.
One: the freed hours go nowhere
An automation saves three hours a week for eight people. Nobody leaves, nothing new is taken on, and the payroll is unchanged.
- The freed hours go nowhere.
- The saving is spread too thin to remove anybody.
- The work moves to another team rather than stopping.
- The cost was never variable in the first place.
Twenty-four hours a week of real improvement, zero cash saving, and a business case that claimed one.
Two: the saving is spread too thin
Half an hour a week from forty people is twenty hours — half a person. But it is half an hour each, and nobody can be removed from half an hour.
Savings only become cash when they concentrate enough to remove a whole person or a whole shift.
Three: the work moves rather than stops
A task is removed from one team and appears in another, often one that does not record its hours. Total cost is unchanged and the first team's numbers improve.
This is the commonest form of apparent saving in cross-functional change programmes.
Four: the cost was never variable
Cutting hours on a fixed-cost resource — salaried staff, owned equipment, leased premises — does not reduce the cost. It reduces utilisation, which raises the rate.
The saving is negative in the rate and zero in cash.
The test before claiming a saving
What specifically stops being paid, by when, and who decides? If there is no answer, the benefit is capacity, not cost, and it should be described as capacity.
One question, asked before the business case is approved.
Capacity is a real benefit
Freed capacity is worth something: it absorbs growth without recruitment, it reduces overtime, it shortens lead times. Those are genuine and they are not cash savings.
Claiming them as cash is what makes change programmes lose credibility by the third one.
Converting capacity into cash
Deliberately: take on more work with the same people, reduce overtime, stop using agency, or reduce headcount through turnover rather than redundancy.
Each is a decision somebody has to take. None of them happens because hours were saved.
The turnover route
The least painful and the slowest. An operation with ten per cent turnover can absorb a ten per cent capacity gain within a year by not replacing leavers.
It requires the vacancy not to be filled by default, which requires somebody to be watching.
What this does to business cases
It should split them into two lines: hours released, and cash released, with the mechanism and the date for the second.
Most business cases have one line and it is the first labelled as the second.
The rate consequence
Cutting hours without cutting cost raises the rate, because the same pool is spread over fewer chargeable hours.
Which means a successful efficiency programme can make every job look more expensive, and the costing system will report it as a deterioration.
The saving that was already counted
A recurring hazard in change programmes: two initiatives claiming the same hours. The automation frees three hours a week; the process redesign frees two; the person's week has not got five hours longer.
A register of claimed savings by team, with the hours, prevents the double count. Without it the sum of claimed benefits across a programme routinely exceeds the payroll of the teams affected.
Measuring afterwards
Six months later, against the same payroll line that was supposed to fall. One query.
Almost nobody runs it, which is why the same claims recur. A programme that measures its own outturn once builds more credibility than one that promises carefully.
The honest business case
Two columns: hours released, and cash released with a mechanism and a date. Where the second column is empty, the case is still worth making — freed capacity is valuable — but it is a different case with a different approver.
Most rejected business cases are rejected because they claimed the second column and could not support it, which loses the first column too.
Where the saving is real
Overtime reduction, agency reduction, and vacancies not filled. All three are cash, all three are measurable in payroll within a quarter, and all three require somebody to decide not to spend.
Those are the mechanisms worth naming in advance, because they are the only ones that have ever produced a saving without a redundancy.
Saying that in advance
"This will release 900 hours a year. It will not reduce payroll unless we take on more work or do not replace two leavers. The rate will rise by about 3 per cent in the meantime."
Three sentences, stated before rather than discovered after, are the difference between a programme that is trusted and one that is not.