Finance and Investment
Cost Savings Tracker Excel Template
Keep every cost-reduction project in one register, log the savings finance validates each month, and see realized savings against plan and the year's target.
Overview
This cost savings tracker is a working Excel register for plant managers, continuous-improvement leads, buyers and controllers who report savings. It ships with a full example for a fictional injection moulding plant: fourteen projects across material, labour, scrap, energy, maintenance and logistics, with monthly savings logged through September, so the Dashboard tells a complete story before you type your own projects.
Each project's net annual saving is its annual cost before the change, minus the cost after, minus any running cost the change adds, at the same volume. The plan spreads that saving evenly over the months that count in the savings year: from the start month, for twelve months by default, so a carry-over project stops counting when its year is up. Only the stages you mark on Setup count in the plan, so an idea never inflates the forecast and no probability is invented.
Every month you log the saving finance actually validated. The register sums it per project, compares it with the plan to date and gives a status in words; the year-end forecast is what has been realized plus the plan for the months still to come. Cost avoidance, a price rise that did not happen, is tracked and shown but never counted against the target, which keeps the reported number defensible.
What this template includes
- Setup for the plant, currency, savings year, report month, months a saving counts from its start, the hard savings target and the realization target
- Category and stage lists, with a Counts in plan column so you decide which stages count in the plan and the forecast
- Project Register: one row per project with type (hard saving or cost avoidance), stage, start month, annual cost before and after, one-time and recurring cost
- Per project: net annual savings, payback in months, the months that count this year, plan for the year, plan to date, realized to date, realization, status and year-end forecast
- Savings Log: one row per project per month with the saving realized and who validated it, linked to the register by project ID
- Check columns that name duplicate IDs, stages not on the list, cost after above baseline and savings logged for a project not in plan
- Dashboard tiles for hard savings to date, realization of plan, year-end forecast against target, the gap still to find, cost avoidance, run rate and one-time cost
- Two charts: cumulative realized savings against plan and the year target by month, and plan versus realized by category
Suggested use case
Use it to run a plant's or a company's savings programme: to keep one honest list of projects, to report realized savings against plan every month, and to see early how much of the year's target is still to find.
How to use it
- On Setup, type your plant name, currency, first month of the savings year, the month you report through and the year's hard savings target; adjust the categories and which stages count in plan.
- On Project Register, add one row per project with its category, type, stage, start month, annual cost before and after, and any one-time or recurring cost.
- Each month, add one Savings Log row per project with the saving finance validated.
- Fix anything the Check columns name, then update the report month on Setup.
- Open the Dashboard: realized against plan, the year-end forecast and the gap to target, by month and by category.
Frequently Asked Questions
- What is the difference between a hard saving and cost avoidance?
- A hard saving makes a cost fall in the accounts: a resin price cut from 980,000 to 921,000 a year is a 59,000 hard saving. Cost avoidance is a rise that did not happen, such as a supplier's announced 4,000 carton increase withdrawn after a tender. The tracker records both but only hard savings count against the target.
- How is the plan to date calculated?
- Net annual savings divided by 12, times the months that count from the project's start (or the start of the year) to the report month. A project saving 36,000 a year that started in July has a plan to date of 3,000 x 3 = 9,000 when you report through September.
- How long does a saving count?
- You set it on Setup: 12 months from the start month by default, the common rule in savings programmes. A project that started in October 2025 counts January to September 2026 in the 2026 year and then stops. Set 0 to count every project to the end of the year.
- How is the year-end forecast worked out?
- For each project in plan it is realized to date plus the monthly plan for every counted month after the report month. A project that has realized 20,000 and still has three counted months at 3,000 a month forecasts 29,000. The forecast is a plan, not a probability: projects at stages you exclude add nothing.
- Why does realization use plan to date and not the full-year plan?
- Because savings arrive month by month. Realization compares like with like: 87,600 realized against a 100,000 plan to date is 87.6%, even if the full-year plan is 240,000. The Dashboard forms it from the totals, not by averaging the projects' percentages.
- Is there a CSV version?
- Yes. The CSV with live formulas holds the Project Register with the example rows, units in every header and the settings the formulas read listed below the data, so it opens in any spreadsheet app. Net savings, payback, the counted months, plan, realization, status and forecast are live formulas; realized to date is a typed value because it sums the Savings Log. The dashboard, charts, dropdowns and self-check are in the .xlsx. Excel in a locale that uses semicolons or non-English function names may need Data > From Text/CSV; the .xlsx works everywhere.