Is the saving real? Bottlenecks, and the three ways a number becomes money

Why speeding up a machine usually saves nothing, when a number on a costing sheet turns into cash, and how to tell real cash savings apart from cost avoidance before anyone in finance asks.

Updated 31 August 2026

This guide does not teach costing — the industry guides do that. It answers the question sitting behind every costing sheet: does the saving you just calculated mean the plant actually has that much more money?

Usually the answer is no, and the arithmetic is not at fault. Money only leaves the equation when the plant **stops paying for something real** or **sells more output** — and whether an improvement does either depends entirely on where it sits in the flow.

The example every plant has seen

You improve an operation and cycle time drops from six minutes to four. The sheet multiplies two minutes by the machine hour rate by annual volume and produces a satisfying number.

But if that operation was never the constraint — if it already waited on the operation upstream, or waited on orders — then after the improvement the plant ships exactly as much as before, pays the same wages, and draws the same power. The only thing that increased is **idle time**.

That improvement is not worthless. It created spare capacity, and spare capacity can become money later. It is not money yet, and presenting it as money is the fastest way to lose credibility the first time finance reconciles your figure against the ledger.

The three routes from a number to actual money

There are only three, and you must be able to name at least one:

Headcount or a shift comes out — wages genuinely stop being paid.
You sell more — the freed capacity gets filled by orders that actually exist.
A line item with an invoice gets smaller — less material, less energy, less subcontract spend.

The third route is the most reliable and the easiest to defend, because it leaves a trail on a goods issue note or a supplier invoice. The first two require somebody to make a decision; they do not happen on their own.

If you cannot name one of the three, what you have is **released capacity**, not a saving. Saying so plainly is worth more than the number would have been — experienced readers trust a write-up that draws its own limits.

The constraint sets the output of the whole line

The bottleneck is the slowest operation, and the throughput of the entire line equals its throughput. Every other operation, however fast, ends up waiting on it.

That has two consequences, and the second is the one that gets skipped:

An hour saved AT the constraint is an hour of extra output for the whole plant.
An hour saved anywhere ELSE changes nothing — unless you use the freed time to remove a shift, remove a person, or move work onto that resource from somewhere tighter.

Finding the constraint needs no measurement study: walk the line and look for the operation with **work piled up in front of it and nothing waiting behind it**. Or ask which operation is the one that always runs overtime.

Declare the constraint and let the system check you

Both the labour and machine sections have a field asking whether that line is the constraint. It takes no part in the arithmetic — nothing is added, subtracted or multiplied by it.

Its only job is to trigger a warning: if you mark a line as NOT the constraint and that same line still reports a saving, the system says out loud that the money may just be idle time.

The field has three states, and «not declared» is not the same as «not the constraint». Leave it blank and you get no warning at all — the system will not guess on your behalf. You have to declare it to be checked.

So marking a line as «not the constraint» does not weaken your case. It gets you challenged **before** a reviewer challenges you — and if you can still name one of the three routes above, write that route into the verification section and the case stands.

Cash savings and cost avoidance are not the same claim

Both are legitimate. They are not interchangeable, and the reader needs to know which one you are claiming.

Type	What it means	Example
Cash saving	A cost disappears from the ledger	No more replacement units to buy; less material consumed per part
Cost avoidance	A cost that would have appeared never did	No second machine needed because capacity was enough; no overtime this quarter

Cost avoidance is real, but it rests on an assumption — that the avoided cost was genuinely going to occur. State that assumption in writing rather than leaving the reader to infer it.

When the number looks bad and the change is still right

Some improvements score as a cost INCREASE and are still correct. The clearest case is cutting batch size: more setups per year, so setup cost per part rises.

What you get back — shorter lead time, less work in progress, defects caught sooner — is not something a unit cost sheet can measure, and the system says so directly when it detects that batch size has been reduced.

Do not abandon a good change because the number looks bad here. Do not massage the number either — write into the mechanism section that the benefit lives where the sheet cannot reach.

Five questions before you publish

Is this improvement at the constraint or somewhere else?
If elsewhere: which of the three routes to money can I actually name?
Is this a cash saving or cost avoidance? Have I said which?
If cost avoidance: is the assumption behind it written down?
Is there a benefit the sheet cannot measure? Is it in the mechanism section?

None of these five makes your number smaller. They make it **survive questioning** — and that is what decides whether another plant ever copies your work.

Related guides

Six fields almost nobody fills in, and which way each one bends the cost
Material yield, personal and machine allowances, energy, units per pack and fixed cost per lot: six inputs that are usually left empty, and why five of the six make the cost look cheaper than it is.