Strong diversion governance does not pretend failures wonât happenâit builds a learning system that makes failures rarer, less harmful, and less repeatable. This guide extends Crisis Diversion Governance and connects to operational design in Crisis Response Models, focusing on near-miss review, root cause analysis (RCA), and corrective action that partners can trust.
Why incident governance is different in diversion pathways
Diversion spans multiple settingsâphone triage, mobile response, crisis receiving, stabilization, respite, step-down, and follow-up. Incidents often occur in the gaps: an incomplete handoff, an unclear medication plan, a delayed transport, or a mismatch between acuity and setting. A traditional âprovider-onlyâ incident process misses these system seams, so the same failure mode repeats across agencies.
Effective incident governance is not just compliance. It is a structured method to (1) detect issues early (near-misses, not only harm), (2) reconstruct what actually happened across partners, and (3) implement corrective actions with owners, deadlines, and verification.
Oversight expectations to design around
Expectation 1: Timely reporting with documented follow-through. Funders and oversight bodies commonly expect prompt reporting of serious incidents and a documented investigation process that results in corrective action and monitoring. âWe retrained staffâ without evidence of changed practice is rarely persuasive.
Expectation 2: Partner transparency without breaching privacy. Diversion involves protected health information and often sensitive law enforcement/EMS interfaces. Governance must define what can be shared, with whom, and how, so partners can improve the system without creating new privacy or liability risk.
Operational Example 1: A near-miss trigger that catches âalmost harmâ before it becomes harm
What happens in day-to-day delivery
The system defines near-miss triggers that automatically generate a review task: for example, ED arrival within 6â12 hours of diversion; unplanned transfer from crisis receiving within 12â24 hours; refusal/denial after clinical acceptance; missing follow-up contact within the required window; or medication reconciliation not completed for high-risk meds. A quality coordinator pulls the case packet (call notes, risk screens, handoff logs, transport timestamps) and schedules a short review within 72 hours with the relevant supervisor and frontline staff.
Why the practice exists (failure mode it addresses)
This practice targets the failure mode where leadership only learns about problems after serious harm occurs. Near-misses are often the same operational pattern as harm events, just with a luckier ending. Catching them early allows corrective action when staff memory is fresh and system levers (capacity, criteria, handoff tools) can still be adjusted.
What goes wrong if it is absent
Without near-miss governance, systems normalize warning signs: frequent âdiverted then EDâ episodes, repeated failed placements, or recurring missed follow-ups. Teams become desensitized until a sentinel event occurs, at which point the response is reactive and punitive, and partners become risk-averseâreducing diversion willingness and shrinking capacity.
What observable outcome it produces
Over time, near-miss review produces fewer repeat occurrences of the same trigger, improved timeliness of follow-up, and better alignment between triage decisions and destination capability. Evidence includes declining near-miss trigger rates, documented corrective action completion, and improved audit scores for the specific workflow elements that were previously failing.
Operational Example 2: Cross-partner RCA for an adverse outcome after diversion
What happens in day-to-day delivery
When a serious incident occurs (self-harm, violence, elopement with high risk, severe medication event, or unexpected death), the system launches a cross-partner RCA. A convenor gathers a timeline across agencies: 988 triage, mobile response actions, destination acceptance, transport, handoff, stabilization plan, and follow-up. The RCA meeting uses a structured format: facts first, contributing factors (people/process/technology/environment), and âcould this happen again tomorrow?â The group assigns corrective actions that are specific (tool change, staffing change, criteria change), with named owners and due dates.
Why the practice exists (failure mode it addresses)
This prevents the failure mode where each agency investigates only its own slice and misses the seam failures that actually drove the outcome (e.g., handoff omission, unclear medical clearance, transport delay, or mismatch between acuity and setting). It also prevents âblame shiftingâ that erodes collaboration and pushes the system back toward ED default.
What goes wrong if it is absent
Without cross-partner RCA, corrective actions are often superficial and duplicative: everyone âre-trains staffâ while the underlying workflow remains unchanged. Partners become defensive, data sharing becomes restricted, and governance meetings turn into contractual disputes rather than improvement forumsâreducing diversion success and increasing system fragmentation.
What observable outcome it produces
Observable outcomes include faster implementation of workflow changes, fewer repeat incidents of similar type, and improved partner confidence in diversion pathways. Evidence includes RCA completion within defined timelines, verified completion of corrective actions, and post-change audits showing that the new controls (checklists, escalation gates, handoff tools) are consistently used.
Operational Example 3: Corrective action tracking that proves the system actually changed
What happens in day-to-day delivery
Every corrective action is logged into a shared tracker with: the failure mode, the specific change, the owner, the due date, and the verification method. Verification is not âtraining completedââit is proof of practice (chart audit pass rate, reduction in trigger events, system configuration change, updated criteria adoption). The governance group reviews the tracker weekly until actions are closed, then performs a 30â60 day âsustainment checkâ to ensure the fix persisted.
Why the practice exists (failure mode it addresses)
This addresses the failure mode where corrective actions are announced but not embedded. In crisis systems, staff turnover and workload mean that unverified changes degrade quickly. Tracking with verification ensures that improvements are real, measurable, and durable.
What goes wrong if it is absent
If corrective actions are not tracked and verified, the same incidents recur, often with small variations. Leadership loses credibility with partners and funders because âwe fixed thisâ does not match outcomes. Staff also lose trust, because they experience the same operational breakdowns repeatedly despite prior âimprovement initiatives.â
What observable outcome it produces
Evidence of success includes closure rates on corrective actions, improvement in the verification metrics tied to each fix, and declining recurrence of the original failure mode. Over time, the incident portfolio shifts from severe events to lower-severity near-missesâan indicator the system is catching problems earlier.
Making incident governance safe for partners and staff
Incident learning collapses when people fear punishment or reputational damage. Governance should separate âaccountabilityâ (clear expectations, escalation compliance, documentation standards) from âblameâ (individual fault narratives that ignore system context). Use structured templates, anonymize learning summaries where appropriate, and define what information is shared in joint forums versus retained within each agencyâs protected quality process.