When crisis services clog, leaders often default to expanding beds. But many flow breakdowns happen even when physical capacity existsâbecause demand is not coordinated in real time. People are routed inconsistently, queues are invisible, and the ânext stepâ is negotiated case by case. This article is part of System Capacity & Flow Impact and should be read alongside Cost vs Outcomes, because poor routing and queue opacity create avoidable utilization, duplicated assessments, and safety risks.
Real-time coordination is not a tech project alone. It is an operating model: shared definitions, clear routing rules, daily cadence, and evidence that the system is making rights-based decisions consistently at speed.
Oversight expectations that shape real-time coordination
Expectation 1: No-wrong-door access must be credible in practice. Funders and regulators increasingly expect that people can access crisis help regardless of entry point (hotline, ED, mobile team, walk-in). A âno-wrong-doorâ claim is tested by whether routing is consistent, timely, and documented rather than discretionary.
Expectation 2: Systems must manage risk without discriminatory gatekeeping. Oversight bodies often scrutinize whether people are turned away because they are complex, uninsured, homeless, intoxicated, or behaviorally challenging. Real-time coordination must show defensible triage, escalation, and alternative pathwaysâwithout creating unlawful or unsafe exclusions.
Why demand coordination fails
Demand coordination collapses when each service holds its own list, thresholds differ by site, and no one owns the âsystem view.â People then bounce between entry points, repeat their story, and wait longerâraising risk while consuming staff time. Operationally, the system experiences âfalse scarcityâ: capacity exists but cannot be mobilized reliably.
Operational Example 1: Daily system bed huddle with a single agreed status picture
What happens in day-to-day delivery
Each morning (and again mid-day if demand is high), the system runs a short bed huddle covering crisis stabilization units, step-down slots, mobile team capacity, and ED behavioral health holds. A designated coordinator gathers standardized updates before the huddle: beds open, beds expected to open, holds awaiting placement, and people forecast to discharge. The huddle concludes with named actions: who will accept which referrals, which discharges will be accelerated safely, and where staffing can be flexed. Notes are recorded in a shared log visible to participating agencies.
Why the practice exists (failure mode it addresses)
This practice exists to prevent the failure mode of fragmented situational awarenessâwhere every unit believes it is full and every team escalates independently. Without a shared status picture, decisions are made on partial information and the loudest escalation wins.
What goes wrong if it is absent
EDs hold people longer because receiving facilities are âchecking availability.â Mobile teams spend hours phoning multiple sites. Crisis lines over-refer to ED âjust in case.â Staff burn time on logistics instead of care, and risk rises as waits lengthen.
What observable outcome it produces
A bed huddle improves responsiveness and reduces hidden queue time. Evidence includes shorter time-to-placement from ED or field contact, fewer âmultiple callsâ for a single referral, and clearer audit trails showing timely, coordinated allocation decisions.
Operational Example 2: Shared queue visibility tool with standardized referral states
What happens in day-to-day delivery
The system maintains a shared queue board (can be a platform or a controlled spreadsheet in early maturity) where every active referral has a status and timestamp: âreceived,â âclinically screened,â âawaiting transport,â âaccepted,â âdeclined with reason,â âredirected,â and âclosed.â Each status has definitions and required fields (risk flags, legal status, required supports, interpreter need). A coordinator updates status in real time based on calls and clinical screens. Receiving services are accountable for updating accept/decline decisions within defined time windows.
Why the practice exists (failure mode it addresses)
This practice addresses the failure mode where referrals disappear into back channels, and delays become invisible until harm occurs. Standardized states prevent âshadow queuesâ that accumulate in voicemail and email.
What goes wrong if it is absent
Leaders cannot see true demand. People wait without escalation triggers. Families and ED staff repeatedly chase updates, increasing conflict and risk. The system cannot learn because it lacks a reliable record of where time was lost.
What observable outcome it produces
Queue visibility improves timeliness and accountability. Evidence includes measurable reductions in time spent in âunownedâ referral states, fewer escalations due to lack of updates, and better performance against response-time standards.
Operational Example 3: No-wrong-door routing rules with escalation pathways
What happens in day-to-day delivery
The system agrees routing rules for common scenarios: suicidal ideation without imminent plan, acute psychosis, intoxication with behavioral escalation, youth crisis, co-occurring medical instability, and housing-related crises. Rules specify the default pathway (mobile response, walk-in, crisis stabilization, ED) and the escalation path when criteria change. Staff across entry points use a shared triage guide and document rationale when deviating. Escalations (e.g., medical clearance needed, legal hold, violence risk) trigger direct clinician-to-clinician handoff rather than passive referral.
Why the practice exists (failure mode it addresses)
This practice exists to prevent the failure mode of inconsistent routingâwhere similar presentations receive different responses depending on who answers the phone, which site is busy, or which service is most risk-averse that day.
What goes wrong if it is absent
People experience avoidable ED use, repeated assessments, and delayed stabilization. Staff become defensive and adopt informal gatekeeping. The systemâs âfront doorâ becomes confusing and inequitable.
What observable outcome it produces
Routing rules reduce variation and protect access. Evidence includes fewer inappropriate ED diversions, improved first-contact resolution, and documentation audits showing consistent application of triage criteria and escalation pathways.
Balancing measures to prove improvement is safe
Real-time coordination must be measured with balancing metrics, not only speed. Common balancing measures include 7/30-day re-presentation, incident rates during waits, use-of-restraint trends, and complaints related to denial or delay. If performance improves but harms rise, the coordination model needs redesignânot tighter thresholds.
What mature systems do differently
Mature systems treat coordination as a standing function: a role, a cadence, and an accountable governance loop. They invest in shared definitions and handoffs first, then automate. The goal is not perfectionâit is predictability: the system can see demand, route people consistently, and learn from delays before they become crises.
When bed management, queue visibility, and routing rules operate together, capacity becomes more usable, waits shorten, and the system can protect rights and safety without relying on heroic improvisation.