“Verified savings” gets used loosely enough in this category that it’s worth pinning down what the phrase should actually require before trusting a number attached to it. A savings figure that survives scrutiny needs a defined before window, a defined after window, a clear statement of what changed between them, and a plain accounting of what else might have caused the difference. Most numbers presented as verified savings skip at least one of those, and the skipped part is usually the one that would have made the number smaller.
The before and after windows have to be defined, in writing
A savings claim starts with two time periods: before a specific change, after it. That sounds obvious, but the window boundaries are where a lot of savings claims go soft without anyone noticing. A “before” period cherry-picked from an unusually bad stretch inflates the apparent improvement. An “after” period that only includes the best weeks since the change does the same thing from the other direction. A number worth trusting states its exact windows, this many weeks before the fixture change, this many weeks after, and would hold up if someone else picked the same two windows and ran the math independently.
The length of each window matters too. A single good week after a fix proves the fix didn’t immediately break anything. It doesn’t prove the improvement holds. A four to six week after window, long enough to cover normal week-to-week variation and at least one full production cycle, is a more solid basis for a savings claim than a comparison built from a handful of unusually clean days right after a change was made.
Attribution is not causation
A number moving after a change doesn’t prove the change caused the move, and this is the part most savings claims skip entirely. A changeover that dropped from twenty five minutes to eighteen after a fixture fix looks like a clean win, but the same period might have also seen a different operator running that job, a different part mix, a slower month overall that gave everyone more time to do the changeover carefully. Attribution means the claim states what changed and when. Causation means ruling out, or at least naming, the other things that changed at the same time and might explain some or all of the difference.
A savings claim done right doesn’t need to eliminate every other variable. That’s rarely possible on a real production floor. It needs to name the ones that plausibly matter and say something about them. “Same three operators ran this job in both windows, same part number, no other process changes logged” is a claim that’s done real attribution work. “Changeover time dropped 30%” with no context about what else might have shifted is a number, not evidence.
Why a ledger that can show zero is worth more
The single clearest sign a savings claim deserves trust is whether the same measurement process could have shown no improvement, or even a decline, and would have reported it plainly if that happened. A system, or a person, that only ever reports wins has either gotten remarkably lucky on every single change, or is filtering out the ones that didn’t work before anyone sees the report. Ask, for any savings claim, what the same process would have shown if the fix hadn’t worked. If there’s no good answer, the claim was never really measuring anything. It was waiting to publish good news.
This is why a claim tied to a specific, falsifiable prediction beats one presented after the fact. “We expect this fixture change to cut changeover time by at least three minutes, we’ll check in four weeks” is a real test. “Changeover time is down, the fixture change worked” announced only once the number was already known to have moved is a story fit to the data, not a measurement that could have gone either way.
What this looks like on a real floor
Put this into practice with a simple habit: log the prediction before the fix, not after the result. When a fixture gets adjusted, a threshold gets retuned, a changeover procedure gets rewritten, write down what’s expected to happen and by when, before running the after window. Then measure the same defined window on the same defined metric and report whatever it actually shows, including the times it shows nothing. A team that’s logged three fixes that didn’t move the number alongside nine that did has a far more credible ninth win than a team that’s never once reported a fix that failed to help.
This discipline pays off past any single fix, too. A plant with a habit of stating predictions and reporting the plain result, wins and non-wins both, builds a body of evidence that holds up when someone senior asks to see it, an auditor, a new plant manager, a corporate finance review. A plant that’s only ever reported wins has no way to answer “how do we know this actually works” except by pointing at more of the same unverifiable pattern.
A worked example of the difference
Take a changeover fix on one press. The loose version of a savings claim: “We fixed the fixture and changeover time dropped.” No window stated, no comparison to what else might have changed, no mention of whether every changeover improved or just a few. The verified version states the same underlying fact with the missing pieces filled in: five weeks before the fixture change, the same job averaged twenty four minutes a changeover across eleven runs, same two operators, same part number. Five weeks after, the same job averaged eighteen minutes across twelve runs, same two operators, no other process changes logged in that window. The prediction, logged before the after window started, was a reduction to twenty minutes or better. The result beat the prediction, and the claim names exactly what would have counted as the fix not working.
That second version takes longer to write and is less quotable in a hallway conversation. It is also the only one of the two that a skeptical plant manager, or a corporate finance reviewer three years later, could actually check.
Quick recap
- A verified savings claim needs a stated before window and after window, specific enough that someone else could rerun the comparison
- An after window needs to be long enough to cover normal variation, beyond the best few days right after a change
- Attribution states what changed. Causation requires naming the other things that changed at the same time and might explain the difference
- The clearest test of a trustworthy savings process is whether it could have reported zero improvement, and has, at least sometimes
- A prediction logged before the result beats a story told after the number was already known to have moved
- A ledger with some plainly reported non-wins in it is more credible than one that reports a win every single time