A department submits a proposal to save $500,000 next year.
The presentation looks promising. There are fewer contractors, a new software system, some purchasing efficiencies, and a reassuringly precise number at the bottom.
Finance adds $500,000 to the savings column.
Three months later, expenses haven’t moved.
The problem usually isn’t arithmetic. It’s that the savings were never properly defined.
A department can reduce spending against an inflated budget, avoid a future expense, negotiate a lower unit price, or eliminate an actual recurring cost. Those are different financial outcomes, although they tend to arrive in the budget meeting wearing the same name tag.
For CFOs, the question is whether a proposed initiative will produce a measurable improvement against a credible baseline, after implementation costs, timing differences, and operational consequences.
Before approving a cost reduction, finance should be able to answer seven questions.
1. What Exactly Are We Saving Against?
Every savings calculation starts with a baseline.
And a questionable baseline can make almost any proposal look attractive.
Suppose a department spent $2 million last year and requested $2.3 million for next year.
After negotiations, the department agrees to a $2.1 million budget.
Management announces $200,000 in savings.
But spending is still expected to increase by $100,000.
The department reduced its budget request. That may reflect good financial discipline, but it doesn’t establish a $200,000 reduction in actual costs.
Consider the difference:
| Measure | Amount |
|---|---|
| Prior-year actual expense | $2,000,000 |
| Original budget request | $2,300,000 |
| Approved budget | $2,100,000 |
| Reduction from request | $200,000 |
| Increase over prior-year actuals | $100,000 |
The $200,000 is a reduction against the requested budget.
Whether the company achieved genuine cost avoidance depends on whether the original $2.3 million represented a credible, necessary future expense.
Finance should establish the baseline using relevant actual costs, contractual commitments, expected activity levels, and approved operating assumptions.
The useful question is:
What would the company reasonably spend without this initiative?
If that number cannot be supported, the savings estimate isn’t ready for approval.
2. Are These Actual Cost Savings or Cost Avoidance?
Cost savings and cost avoidance both have value, but they affect financial results differently.
Suppose a company currently spends $400,000 annually on outside contractors.
A process improvement will eliminate $100,000 of that spending.
Assuming the contracts can be reduced as planned, the company has a measurable opportunity to lower an existing expense.
Now suppose a department expects demand to increase and requests two additional contractors.
A process improvement eliminates the need for those future hires.
That may be a valuable decision. But if the contractors were never included in the approved forecast, the initiative won’t necessarily reduce forecast expenses.
It prevents an increase that might otherwise have occurred.
Finance should classify the benefits clearly: