Shared-savings consulting only works when the saving can be proved. A buyer should not pay because a consultant produced a forecast, a dashboard, or a persuasive recommendation. The fee should be triggered only when a cost reduction is real, inside the agreed scope, and validated against evidence both sides accept.
That is the role of savings validation. It connects the commercial promise — no fee unless savings are delivered — to the operating evidence that proves whether the promise has been met.
The short answer
Savings validation is the proof layer in a shared-savings contract. It defines:
- the baseline cost position before work starts
- the eligible cost categories that can count as savings
- the evidence sources used to verify the result
- the exclusions that prevent accidental or unfair fee claims
- the timing for sign-off and payment
- the adjustment rules for volume, scope, seasonality, or service changes
Without that proof layer, “contract savings” becomes a slogan. With it, both sides know when a saving is payable and when it is not.
1. Start with a signed-off baseline
Savings cannot be validated without a starting point. The baseline should describe the current cost of the supplier, workflow, process, site, role group, system, or operating area being improved.
Depending on the opportunity, the baseline may use:
- supplier spend by category or contract
- labour hours, overtime, or exception-handling cost
- unit cost per order, job, shipment, ticket, claim, or transaction
- freight, inventory, stock loss, or rework data
- software licences, duplicated tools, or system-support cost
- service, safety, quality, or customer-impact measures that must not deteriorate
The baseline should be conservative and reproducible. If finance cannot recreate it from source data, it is not a strong enough basis for a shared-savings fee.
2. Define what counts as a saving
A validated saving is not just a lower number on a report. It should be a cost reduction that is inside scope, caused by the engagement, and achieved without pushing damage elsewhere in the business.
Examples that can count, if scoped and evidenced, include:
- lower supplier cost for the same or better service level
- removal of duplicated systems, licences, tasks, or approval steps
- reduced rework, credits, freight leakage, claims, or exception handling
- lower manual effort because a workflow has been redesigned or automated
- better utilisation, scheduling, handoff discipline, or throughput without quality loss
- working-capital or inventory improvements that are real rather than timing noise
The contract should make clear whether one-off and recurring savings are treated differently. Recurring savings usually need a measurement rhythm so both sides can see whether the improvement holds.
3. Write down the exclusions before work begins
Exclusions are not legal decoration. They are the difference between a fair performance fee and a future argument.
Common exclusions include:
- savings already identified or under implementation before TightShip starts
- accounting reclassifications with no operating change
- price increases or revenue growth unrelated to cost reduction
- volume declines that reduce spend but do not improve efficiency
- supplier rebates, credits, or renegotiations already secured
- one-off timing differences that do not reduce ongoing cost
- headcount cuts or service reductions unless explicitly agreed in scope
- savings that create safety, compliance, quality, or customer risk
The principle is simple: the buyer should pay only for operational improvement created inside the agreed focus areas.
4. Use evidence that both sides can audit
Savings validation should be data-led and boring. The evidence does not need to be complex, but it does need to be accepted before the engagement turns contentious.
Useful evidence sources include:
- supplier invoices and purchase orders
- payroll, rostering, and overtime records
- ERP, CRM, WMS, TMS, procurement, or finance-system exports
- management accounts and agreed chart-of-account mappings
- production volumes, job reports, and unit-cost measures
- freight, inventory, credits, claims, and rework records
- before-and-after process metrics
The method should also say how the calculation will adjust for volume changes, seasonality, inflation, input-price movements, acquisitions, divestments, and scope changes. Otherwise, ordinary business movement can be mistaken for consulting impact.
5. Tie payment to verified savings, not activity
In a real shared-savings model, the consultant is not paid for time served. They are paid when savings have been validated.
For TightShip, the commercial principle is deliberately narrow: no upfront fees by default, no day rates, and no fee on benefits outside the signed-off focus areas. Payment should follow verified savings, not recommendations or modelled upside.
That does not mean every contract needs the same percentage or exact mechanism. It does mean the payment trigger must be explicit enough that both sides can answer one question without argument: “Has this saving been proved under the agreed method?”
6. Keep governance simple but real
Validation works best when it is part of the operating rhythm, not a surprise calculation at the end.
A practical governance cadence can include:
- baseline sign-off before implementation starts
- a savings log with each opportunity, owner, evidence source, and status
- monthly or quarterly review of validated savings
- finance sign-off on calculations before payment
- scope-change rules when the business context moves
- a dispute path for contested savings
The goal is not bureaucracy. The goal is to make the commercial model calm, transparent, and hard to game.
What buyers should ask
Before signing a shared-savings engagement, ask:
- What baseline will we use?
- What evidence will prove each saving?
- Which savings are excluded?
- How do we adjust for volume, seasonality, and scope changes?
- Who signs off the savings calculation?
- When does payment become due?
- What happens if a saving reverses or creates operational risk?
A consultant who can answer these questions clearly is more likely to be operating a genuine shared-savings model. A consultant who cannot is asking you to trust the upside before the proof system exists.
Bottom line
Savings validation is what makes shared-savings consulting commercially safe. It protects the buyer from paying for activity, projections, or accidental windfalls. It also protects the consultant by making real operational improvement measurable and payable.
TightShip’s position is simple: find recoverable margin, implement the fix, prove the saving, then share in the verified result.
Related guides
- Contract savings explained: shared savings contract design, validation and fees
- What is a shared savings consulting model?
- Which consultants specialise in shared savings contract design?
- Cost reduction consulting in Australia
Book a margin assessment to pressure-test where savings are likely to be real, measurable, and worth pursuing.
Frequently Asked Questions
What is savings validation in shared-savings consulting?
Savings validation is the agreed process for proving that a cost reduction is real, inside scope, caused by the engagement, and measured against an accepted baseline before any shared-savings fee is paid.
What evidence should validate contract savings?
Useful evidence can include supplier invoices, purchase orders, payroll or rostering data, ERP exports, freight or inventory records, management accounts, unit-cost reports, and before-and-after operating metrics. The evidence should be reproducible by finance, not just asserted by the consultant.
When should a shared-savings fee be paid?
The fee should be paid only after savings are verified against the signed-off baseline and accepted measurement method. Forecast savings, recommendations, accounting reclassifications, or benefits outside the agreed focus areas should not trigger payment.
What savings should be excluded from the fee calculation?
Common exclusions include savings already in flight, one-off timing differences, revenue growth, accounting reclassifications, supplier credits already negotiated, volume reductions mistaken for efficiency, and cuts that damage safety, compliance, service quality, or customer outcomes.
Why does validation matter for contract savings?
Validation turns a performance-fee promise into a measurable operating agreement. It protects the buyer from paying for theoretical savings and protects the consultant by defining what evidence will count when real operational improvement is delivered.
Want to Find Your Hidden Margin?
Book a 30-minute Margin Assessment. We'll identify your biggest operational leaks — no obligation.
Book a Margin Assessment