A system can look “full” even when demand is partly self-created. Avoidable demand shows up as repeat crisis contacts, ED returns, frequent re-referrals, and “restarts” that consume capacity without improving outcomes. This is a flow problem, not a blame problem: when step-down is unreliable, follow-up is delayed, or handoffs are incomplete, people cycle back into high-intensity services. This article sits within System Capacity & Flow Impact and should be read alongside Cost vs Outcomes because avoidable demand is often the most expensive capacity leak—high unit-cost episodes repeating because the system did not stabilize the pathway around the person.
To manage avoidable demand credibly, commissioners and providers need metrics that isolate repeat utilization tied to operational failures, not just population risk. The goal is to identify what the system can change: timeliness, continuity, and reliability of the “last mile” of support.
Two oversight expectations that shape “avoidable demand” work
Expectation 1: Systems must evidence that repeat crises are being addressed through service design, not just rationing. Oversight scrutiny often increases when services tighten eligibility or shorten lengths of stay without proving that risk and need were managed elsewhere. Avoidable-demand strategies must show documented continuity and safety controls.
Expectation 2: Value-for-money claims require attribution logic. If a system says it reduced ED use or crisis contacts, funders and auditors typically expect clarity on what changed operationally (follow-up standards, step-down reliability, escalation routes) and whether safety indicators moved in the same direction.
Defining avoidable demand in operational terms
“Avoidable demand” is not every repeat contact. It is repeat contact that results from preventable breakdowns: missed follow-up, incomplete handoff information, medication continuity gaps, unclear escalation routes, and mismatch between level of support and acuity. A workable definition usually includes a time window and a “why” code linked to system actions.
Practical measurement starts with three linked indicators:
- Repeat contact rate: proportion of people with 2+ crisis contacts or ED presentations within 30/90 days.
- Failure-mode tagging: reason codes tied to operational breakdowns (missed follow-up, no receiving provider, medication gap, housing disruption, unreachable contact route).
- Stability markers: engagement and continuity indicators (24/72-hour post-transition contact completed; safety plan shared; medication reconciliation confirmed; first appointment attended).
The point is to connect outcomes to controllable process reliability. A reduction in repeats without changes in continuity measures is rarely sustainable.
Operational Example 1: A “72-hour post-transition contact” standard that prevents early destabilization
What happens in day-to-day delivery
Whenever a person transitions from a higher-intensity setting (ED, inpatient, crisis residential, detox, intensive case management) into step-down or community support, the receiving team schedules a structured contact within 72 hours (often within 24–48 for higher acuity). The contact is scripted around key risks: confirm medication access, review safety plan triggers, verify the living situation and contact routes, and schedule the next support action (home visit, clinician appointment, peer check-in). Completion is logged in the care record with time stamps and escalation notes if the person cannot be reached.
Why the practice exists (failure mode it addresses)
This exists to address the predictable early window where re-crisis risk is highest because routines, medication supply, and support structures are not yet stable. Without an early check, deterioration is discovered only when it becomes urgent, pushing the person back to crisis entry points.
What goes wrong if it is absent
If there is no early contact standard, the system “hopes” the transition holds. People miss appointments, medication gaps go unnoticed, and practical barriers (transport, unstable housing, conflict at home) escalate. The failure presents as repeat ED presentations, repeated crisis calls, and re-referrals framed as “non-engagement,” when the underlying problem is unreliable follow-up.
What observable outcome it produces
When implemented with monitoring, systems typically see fewer 7/30-day returns and fewer urgent escalations due to missed follow-up. Evidence includes compliance reports for 72-hour contacts, audit trails showing completed risk checks, reduced early re-presentation rates, and improved engagement indicators in the first month.
Operational Example 2: A shared handoff summary that prevents information loss between teams
What happens in day-to-day delivery
A standardized handoff summary travels with the person across levels of care. It includes current medications and last confirmed fill date, key triggers and early warning signs, safeguarding or safety concerns, contact preferences, crisis plan steps, and clear escalation routes. The sending team completes the template at transition, and the receiving team confirms receipt, clarifies questions, and documents acceptance of risk responsibilities. The summary is stored in a shared system or attached to the referral packet with version control.
Why the practice exists (failure mode it addresses)
This practice exists because transitions routinely fail due to missing or fragmented information—especially around medication changes, risk triggers, and contact constraints. Without a consistent handoff artifact, teams spend time reconstructing context, and important details drop out during busy discharge periods.
What goes wrong if it is absent
Information loss becomes normal: the receiving team doesn’t know what was tried, which risks are active, or how to respond when things deteriorate. People may be re-assessed repeatedly instead of supported. The failure shows up as duplicated work, delayed interventions, medication errors, safeguarding concerns discovered late, and repeated crisis presentations because preventive action wasn’t triggered.
What observable outcome it produces
A shared handoff summary improves timeliness and reduces errors. Evidence includes fewer duplicated assessments, improved medication reconciliation accuracy, better continuity in care plans, reduced incident reports linked to missing information, and improved audit findings on transition documentation.
Operational Example 3: A repeat-crisis review loop that turns “frequent users” into system learning
What happens in day-to-day delivery
On a weekly or biweekly cadence, a small panel reviews cases with repeat crises within a defined period (e.g., 2+ crisis contacts in 30 days or 3+ in 90). The review uses a structured template: timeline of contacts, what actions were taken, which follow-ups were missed or delayed, what transition points occurred, and what barriers were unresolved (housing, medication, benefits, family conflict). Actions are assigned: strengthen step-down criteria, add peer support, adjust contact frequency, expedite care coordination, or modify crisis planning. Findings are logged and themed across cases to identify systemic bottlenecks.
Why the practice exists (failure mode it addresses)
This addresses the failure mode where repeat crises are treated as individual non-compliance rather than a signal that the pathway is not holding. Without a review loop, the same breakdowns repeat—missed contacts, unclear escalation routes, unsupported step-down—creating persistent avoidable demand.
What goes wrong if it is absent
Teams react to each crisis as a new event. Staff become demoralized, people experience repeated disruption, and commissioners see rising cost without clear levers to pull. The failure presents as “high utilizers” lists that grow but do not change system practice, meaning capacity pressure remains chronic.
What observable outcome it produces
Repeat-crisis review produces measurable reductions in repeat contacts for targeted cohorts and improves reliability of follow-up standards. Evidence includes documented action completion, reduced repeat crisis rates within defined windows, improved timeliness metrics for high-risk cases, and clearer attribution between operational fixes and utilization trends.
How to report avoidable demand without overstating causality
Credible reporting separates population risk from system reliability. A practical approach is to stratify cohorts (high acuity vs moderate), track continuity measures (72-hour contact, handoff summary receipt, first appointment attendance), and then present repeat utilization alongside these controls. If continuity improves and repeats decline without adverse safety signals, the system can reasonably infer that flow reliability is reducing avoidable demand.
When avoidable demand falls, the system gains capacity twice: fewer high-intensity episodes and less staff time consumed by repeated intake and crisis response. That is “real” capacity creation—built on reliability rather than expansion.