Cost Savings Register

← All maturity guides

SEF Reference Guide G23  |  Manufacturing OpEx Maturity Assessment

What it is

A cost savings register is one controlled list of every cost reduction initiative in the operation. Each entry records what the cost was before (the baseline), what changed, how the saving is calculated, who owns it, what was forecast, and what finance has confirmed actually hit the books.

The register turns “we saved a lot this year” into a number that the plant manager, the controller, and an outside assessor would all accept. That is what PF-3 measures: validated savings as a percentage of the annual cost base, with 2%, 3.5%, and 5% marking Levels 3, 4, and 5.

This guide sets out SEF’s standard register: the fields, the savings categories, the calculation rules, the status stages, and how finance validates. Use it as written, or adapt the details to your accounting system, but write your rules down before you count anything.

Why it matters

• Credibility. Savings that finance has signed off get believed. Savings that operations reports alone get discounted, and so do the people who report them.
• Profit and cash. A plant with a 3.5% annual savings rate offsets most normal wage and price inflation without raising prices.
• Focus. A visible pipeline shows whether enough ideas are coming forward to reach the target, early enough to do something about it.
• Recognition. A clean record of who delivered what supports the recognition system (see G17).
• Honest planning. Validated savings can go into next year’s budget. Guesses cannot.

Key terms

Term	Meaning
Savings Register	A single, controlled log of every cost savings initiative with its baseline, method of calculation, owner, forecast, and finance-validated actual savings.
Hard savings	A reduction in actual spend against the baseline that shows up in the P&L. Examples: lower price for the same part and volume, less scrap, overtime eliminated, a contract cancelled.
Cost avoidance	Preventing a cost increase that would otherwise have happened. Examples: holding price against a supplier’s requested increase, avoiding a planned hire or a capital purchase. Real value, but spend does not go down.
Soft savings (productivity)	Time or capacity freed but not yet removed from spend. Example: a changeover cut by 30 minutes per shift, with the same crew and hours. Becomes hard only when cost is actually removed or the freed capacity replaces a cost (overtime, a temp, outsourced work).
Baseline	The cost before the change, documented with its source (price history, labor report, scrap report) and period.
Annual cost base	The site’s total annual operating cost used as the denominator for the savings percentage (defined below).
Run rate	The annualized saving once the change is fully in place.
In-year savings	The saving actually realized within the period being measured.
Finance validation	A named finance person confirms the baseline, the method, and the actual result from the books.
One-time cost	Implementation cost (tooling, consulting, qualification). Recorded separately and used for payback, not netted from annual savings.

How to do it

1. Set the rules first

Agree these with the site controller and write them on one page:

What counts toward PF-3. Only finance-validated hard savings, including soft savings that have been converted into removed spend. Cost avoidance and unconverted productivity are tracked in the same register but reported separately.

Baseline rules.

• Purchased items: last price paid before the change, or the average price over the prior 12 months if prices moved often. State which.
• Labor: actual paid hours and loaded rate from payroll for a defined prior period.
• Scrap, rework, energy, freight: the prior 6 to 12 month average from the ledger or the relevant KPI system.
• Always use actual volumes when calculating the saving, not forecast volumes.

Calculation rules.

• Price saving = (baseline unit price minus new unit price) x actual quantity bought.
• Usage saving = (baseline usage per unit minus new usage per unit) x actual output x unit cost.
• Labor saving = hours removed x loaded hourly rate, only when the hours are gone from payroll (overtime, temps, headcount not replaced).
• A saving counts for 12 months from the date it starts. After that it is part of the new baseline.
• Recurring new costs caused by the change (a new consumable, a service fee) are subtracted.

Exclusions. Do not count: lower spend caused by lower volume, currency or commodity index movements you did not negotiate, accounting reclassifications, costs moved to another department or site, or a price reduction on a part whose specification was downgraded without engineering approval.

2. Define the annual cost base

SEF standard: the site’s prior fiscal year actual operating costs that the site can influence. Include purchased materials and services, all labor with benefits, manufacturing overhead, energy, freight, maintenance, and site-controlled SG&A. Exclude depreciation and amortization, corporate allocations the site cannot influence, interest, and taxes. Fix the number at the start of the year and do not change it mid-year.

Savings % = validated hard savings realized in the 12 months assessed / annual cost base x 100

Example: a plant with an annual cost base of $40 million needs validated hard savings above $800,000 for Level 3 (2%), $1.4 million for Level 4 (3.5%), and $2 million for Level 5 (5%).

3. Build the register and the stages

Use one spreadsheet or database for the whole site (see Template). Every entry moves through these stages:

Stage	Name	Gate to enter
S0	Idea	Logged with a description and rough estimate
S1	Assessed	Baseline documented, calculation method agreed, owner named
S2	Approved	Manager approves; any one-time cost approved
S3	Implemented	Change is in place; start date recorded
S4	Validated	Finance confirms actual savings from the books
S5	Closed	12 months complete; saving is now in the baseline

Only S4 and S5 amounts count toward PF-3. S0 to S3 amounts are the pipeline.

4. Validate monthly

The owner enters actual monthly savings with evidence (invoice, PO history, payroll report, scrap report). The finance validator reviews each new S3 item within 30 days and each active S4 item quarterly. Validator’s name and date go in the register.

5. Review and drive the pipeline

Review the register monthly in the leadership meeting. Compare the validated year-to-date figure and the weighted pipeline with the annual target. A healthy pipeline holds about two to three times the remaining target, because some ideas will fail or shrink.

What each maturity level looks like

PF-3 Cost Savings (Productivity)

Level	Assessment wording	What it looks like on the floor	How to move up
1	No cost savings activity.	No list of savings exists. Cost reductions happen but nobody records them.	Set up the register, write the rules, and name a finance validator.
2	Cost savings are tracked in a formal savings register.	One register holds all initiatives with owners, baselines, and stages. Finance has started validating.	Calculate the savings % against the defined cost base. Set a target of at least 2% and build a pipeline to reach it.
3	As Level 2, plus validated savings exceed 2% of the annual cost base.	Finance-validated hard savings above 2% for the 12 months assessed. Monthly register review in the leadership meeting.	Widen the idea sources: suppliers, operators (suggestion system), energy, freight, and COPQ projects.
4	As Level 2, plus validated savings exceed 3.5% of the annual cost base.	Savings above 3.5%, coming from many owners across functions, with the pipeline tracked visibly.	Tie improvement projects directly to cost targets. Use value stream and COPQ data to find the larger opportunities.
5	As Level 2, plus validated savings exceed 5% of the annual cost base.	Savings above 5%, validated, repeated year over year. Savings targets are built into the budget.	Sustain the rate. Share methods with other sites and suppliers.

Note that Levels 3, 4, and 5 each build on Level 2 (a formal register) plus a higher validated savings threshold.

Evidence to look for

Document

• Written savings rules (what counts, baseline, calculation, exclusions, cost base definition).
• The register itself, with stages, owners, and validator sign-off.
• Evidence files for a sample of 3 to 5 large savings: baseline source, calculation, and actual results.
• The annual cost base figure and how it was derived.

Observation

• The savings total and pipeline displayed on a leadership board or in the monthly pack.
• A changed process, contract, or layout that matches a register entry.

Statement (questions to ask and who to ask)

• Controller: “Do you sign off the savings? Would you put them in the budget?”
• Project owner: “Walk me through how this saving was calculated. What was the baseline?”
• Plant manager: “What is your savings target this year and how far along are you?”
• Buyer: “How do you separate price savings from cost avoidance?”

Management report

• Monthly savings report: validated year-to-date, forecast, pipeline by stage, and % of cost base.
• Split of hard savings, cost avoidance, and productivity.
• Prior year result to confirm the level is sustained.

Common pitfalls

• Counting cost avoidance as savings. It inflates the number and destroys trust with finance. Track it, but report it separately.
• Forecast volumes in the calculation. Savings based on a forecast that did not happen are not savings.
• Double counting. The same scrap reduction claimed by quality, production, and purchasing. One entry, one owner.
• Counting forever. A saving from three years ago is now the baseline, not this year’s achievement.
• Productivity with no cash. Freed hours that stay on the payroll doing nothing new are not hard savings. Plan how freed capacity will be used.
• Finance joins at the end. Validation at year end turns into an argument. Bring finance in at stage S1.

Template

SEF Savings Register Fields

Field	Notes
ID	Unique number
Title	Short name
Description	What changes
Area / function	Where the saving occurs
Owner	Accountable person
Category	Hard / Cost avoidance / Productivity
Cost element	Material, labor, overhead, energy, freight, scrap and rework, maintenance, services
GL account(s)	Where the saving will show in the books
Baseline value and source	For example, $12.40 per unit, last PO price, Jan 2026
Baseline period	Dates
New value	For example, $11.65 per unit
Calculation method	Formula in words
One-time cost	Tooling, qualification, and similar
Start date	When the saving begins
Run rate (annualized)	Full-year value
Forecast by month	12 columns
Actual by month	12 columns, entered by owner
Stage	S0 to S5
Finance validator	Name
Validation date	Date
Evidence link	Folder or file path
Counts toward PF-3?	Y/N (Y only for validated hard savings)

Summary block

Line	Value
Annual cost base (fixed at start of year)
Validated hard savings, last 12 months
Savings % of cost base
Target %
Cost avoidance, last 12 months (reported separately)
Pipeline S0 to S3, run rate

First 30 days

Week 1: Meet the controller. Agree the savings rules and the annual cost base definition. Name the finance validator.

Week 2: Build the register from the template. Load every current and recent initiative you can find, then assign stages honestly.

Week 3: Validate the largest five items with finance. Calculate the current savings % and the gap to 2%, 3.5%, or 5%.

Week 4: Hold the first monthly register review. Set the annual target. Launch an idea drive to fill the pipeline to two to three times the gap.

Further reading

• Maskell, B., Baggaley, B., and Grasso, L. Practical Lean Accounting, 2nd edition (2011). Measuring the financial effect of improvement.
• Kaplan, R. and Cooper, R. Cost & Effect (1998). Understanding cost structure and what drives it.
• GEP, “Cost Avoidance vs Hard Savings: Measuring Procurement Impact.” https://www.gep.com/white-papers/cost-avoidance-vs-hard-savings-measuring-procurement-impact
• Womack, J. and Jones, D. Lean Thinking (1996). Where operational savings come from.