Avoided Costs That Count: Turning Demand Reduction Into Defensible Value for Money

“Avoided costs” are among the most contested claims in value-for-money discussions. Commissioners are rightly cautious: it is easy to say an event didn’t happen, and much harder to prove why. Defensible avoided-cost arguments are built on operational controls, comparison logic, and conservative assumptions—not counterfactual storytelling. When done well, they demonstrate how a service reduces demand on high-cost systems without compromising safety or access. This article sits within Return on Investment & Value for Money and complements Cost vs Outcomes by showing how to evidence demand reduction credibly.

Oversight expectations around avoided-cost claims

Expectation 1: Plausible causal link between service activity and reduced demand. Funders expect to see how specific actions plausibly prevent specific events. Generic statements about “support” or “engagement” rarely satisfy scrutiny.

Expectation 2: Conservative assumptions and transparent uncertainty. Avoided-cost estimates are expected to err on the conservative side, with clear acknowledgement of uncertainty and shared attribution.

Why avoided-cost arguments are often rejected

Avoided-cost arguments fail when they rely on hypothetical scenarios (“they would have gone to ED”) without evidence of risk or prior patterns. They also fail when services claim full credit for system-wide trends or ignore quality indicators. Commissioners need to see that avoided events were plausible, proximate, and prevented by identifiable actions.

Operational Example 1: Crisis diversion with documented risk thresholds

What happens in day-to-day delivery
The service defines explicit diversion criteria—clinical, social, and environmental—that indicate when ED or inpatient admission would normally be considered. When staff intervene, they document the presenting risk, the actions taken (assessment, medication adjustment, crisis planning), and the alternative pathway implemented. Each diversion case includes a short rationale explaining why admission was likely and why it was safely avoided.

Why the practice exists (failure mode it addresses)
This practice exists to avoid retrospective guesswork. By documenting risk thresholds at the point of decision, the service creates contemporaneous evidence that an expensive intervention was plausibly avoided.

What goes wrong if it is absent
Without risk documentation, diversion claims rely on memory or assumption. Commissioners may reasonably conclude that admission was never likely, weakening the avoided-cost narrative and undermining trust.

What observable outcome it produces
Clear diversion documentation produces defensible avoided-cost cases. Evidence includes diversion logs, risk assessments, and short-term follow-up outcomes showing stability after diversion.

Operational Example 2: Before-and-after comparison using matched cohorts

What happens in day-to-day delivery
The program compares utilization for individuals before and after intervention, using a defined lookback and follow-up period. Where possible, it matches cohorts on key characteristics (acuity, diagnosis, housing status) to strengthen comparison. Analysts focus on a small number of high-cost events rather than broad utilization counts.

Why the practice exists (failure mode it addresses)
This exists to ground avoided-cost claims in observable change rather than hypothetical futures. Matched comparisons increase confidence that observed reductions are linked to the service.

What goes wrong if it is absent
Without comparison logic, reductions may simply reflect regression to the mean or external factors. Commissioners may discount the entire avoided-cost claim as speculative.

What observable outcome it produces
Matched comparisons produce more credible estimates of demand reduction. Evidence includes cohort definitions, utilization tables, and transparent explanation of matching criteria.

Operational Example 3: Avoided-cost assurance through return-case review

What happens in day-to-day delivery
The service reviews cases where demand reduction did not hold—such as later ED visits or admissions—and analyzes whether earlier diversion actions were appropriate and sufficient. Findings are used to refine diversion criteria and follow-up controls. This learning loop is documented and shared with commissioners.

Why the practice exists (failure mode it addresses)
This exists to show that avoided-cost claims are not one-sided. Acknowledging failures and adjusting practice demonstrates integrity and strengthens long-term credibility.

What goes wrong if it is absent
Without return-case review, avoided-cost claims appear selective. Commissioners may suspect cherry-picking and reduce confidence in reported value.

What observable outcome it produces
Assurance reviews produce improved diversion reliability and stronger commissioner trust. Evidence includes review notes, updated criteria, and trend changes in diversion success rates.

Making avoided costs credible and useful

Avoided-cost claims should support learning, not just funding justification. When services document risk, compare outcomes, and acknowledge uncertainty, avoided costs become a tool for system design rather than a fragile headline number.