Writing a COOP plan is the easy part. The hard part is proving it works when phones are down, staff cannot travel, the scheduling system is unavailable, and families are calling for reassurance. COOP must be activated and run like an incident response process with clear triggers, rehearsed roles, and rapid operational decisions that protect safety and rights. This guide sits within Continuity of Operations Planning (COOP) for HCBS & LTSS and uses the same control logic found in Risk Management & Controls.
Why COOP testing matters more than COOP writing
In HCBS and LTSS, “activation failure” is common: leaders hesitate, supervisors improvise, and staff do not know which instructions to follow. Testing prevents that by exposing weak points before they become harm: stale contact lists, unclear escalation thresholds, unrealistic staffing assumptions, vendor dependencies no one mapped, and gaps between clinical oversight and operations.
The goal is not a perfect drill. The goal is fast, controlled decision-making, with documented learning and repeatable improvements.
Two explicit expectations your testing program should satisfy
1) Documented training and testing with corrective actions
Oversight bodies typically expect evidence that emergency/continuity plans are trained and tested, not just written. For many provider types, training and testing requirements appear in participation rules, state licensure, or contractual obligations. The practical implication is consistent: you should be able to show training completion, exercise schedules, exercise outputs, and corrective action tracking to closure.
2) Demonstrable continuity of access and safe service delivery during disruption
Funders and regulators care less about your scenario narrative and more about your outcomes: Did you maintain essential supports? Did you escalate risks appropriately? Did you protect people’s rights and minimize restrictive or unsafe practices? Testing should generate evidence that your continuity model preserves access, timeliness, and safeguarding under stress.
Activation design: make the “go/no-go” decision unambiguous
Define triggers that match real events
Triggers should be operational, not dramatic. Examples: staffing availability drops below a set threshold for Tier 1 coverage; the scheduling system is down for more than X hours; a regional travel ban is issued; a key vendor cannot deliver medications or DME within a defined window; or a facility closure requires rapid redistribution of services.
Use a two-stage activation model
A practical approach is “COOP Standby” and “COOP Active.” Standby is when you lock leadership roles, verify rosters, and pre-position contingency resources. Active is when you formally shift to minimum service levels, redeploy staff, and start continuity reporting. This prevents overreacting while still moving quickly when indicators worsen.
Operational Example 1: 60-minute activation drill for staffing shock
What happens in day-to-day delivery. Once per quarter, the provider runs a timed activation drill based on realistic staffing loss (e.g., 25–35% call-outs due to extreme weather). The continuity lead initiates a “COOP Standby” message, supervisors verify Tier 1 cases, and the clinical lead reviews any individuals with time-critical meds or known deterioration risk. Within 60 minutes, the team produces a live coverage plan: who covers Tier 1, which Tier 2 visits are bundled or shifted, who performs welfare calls, and which families receive proactive notification. A scribe logs decisions and approvals in a simple timeline.
Why the practice exists (failure mode it addresses). Staffing shock is the most frequent continuity threat. The typical failure mode is slow, fragmented response: supervisors scramble independently while leadership debates whether this “counts” as an emergency. A timed drill forces a decision rhythm and exposes bottlenecks in real time.
What goes wrong if it is absent. Without rehearsed activation, response time stretches into hours. Tier 1 coverage gaps appear first—missed med passes, missed personal care where there is high falls risk, or unsupervised periods for individuals needing 24/7 presence. Families call repeatedly, staff morale drops, and escalation becomes reactive rather than controlled.
What observable outcome it produces. You can measure and improve activation performance: time-to-lock Tier 1 coverage, percentage of Tier 1 cases contacted within the first activation window, number of unresolved coverage gaps at 2 hours, and number of unplanned escalations. Over time, the drill reduces “first hour chaos” and produces consistent, auditable decisions.
Operational Example 2: Vendor failure exercise for meds, oxygen, and critical supplies
What happens in day-to-day delivery. The provider runs a scenario where the primary pharmacy delivery route fails or a DME supplier is unavailable. The continuity cell triggers the vendor contingency map: secondary suppliers, mutual aid partners, and internal stock controls. The clinical lead identifies which individuals have no tolerance for delay (e.g., seizure meds, insulin, oxygen, feeding supplies). Operations staff contact vendors using pre-scripted escalation language, while care coordinators notify MCO/state contacts if authorizations or emergency overrides are required. The exercise includes documentation: what was ordered, what was delivered, and who confirmed receipt.
Why the practice exists (failure mode it addresses). Supply chain problems create clinical harm quickly, but the operational failure mode is often administrative: nobody knows who has authority to switch vendors, what documentation is required, or how to handle payer authorization barriers under time pressure.
What goes wrong if it is absent. The organization discovers too late that secondary vendors cannot deliver, or staff do not know how to process emergency substitutions. People miss doses, ration supplies, or use unsafe workarounds. Documentation becomes inconsistent, which then creates audit and billing risk alongside the immediate safety issue.
What observable outcome it produces. Measurable outcomes include: time-to-escalate to secondary supply routes, percentage of high-risk individuals with confirmed supply continuity within defined windows, and post-event reconciliation accuracy. These are defensible indicators that the system can maintain essential clinical supports during disruption.
Operational Example 3: Communications and information continuity when systems are down
What happens in day-to-day delivery. The provider conducts a “no systems” exercise: scheduling platform unavailable, staff cannot access the EHR, and the main phone line is down. Teams switch to defined backups: alternate phone trees, a designated SMS broadcast tool (or other approved method), printed contact lists stored securely, and paper-based visit note templates. Supervisors perform call-backs to confirm message receipt, while the communications lead issues a single status update for staff and a parallel update for families. A log captures each outbound and inbound communication, including escalations and resolutions.
Why the practice exists (failure mode it addresses). In continuity events, misinformation spreads fast. The primary failure mode is fragmented channels: staff receive mixed instructions and families receive no reliable updates, which drives complaints, missed visits, and unsafe independent decision-making by frontline staff.
What goes wrong if it is absent. Staff may not show for shifts because they do not know expectations or fear they will not be paid. Families escalate to emergency services for reassurance, increasing avoidable ED use. The provider later cannot demonstrate what it communicated, when, and to whom—creating governance and reputational risk.
What observable outcome it produces. You can evidence communications continuity through: message receipt confirmation rates, time-to-first family update, number of unresolved inbound calls past a threshold, and the completeness of the communications log. Over time, these metrics translate into fewer complaints and fewer unplanned escalations driven by uncertainty.
After-action reviews that actually change operations
After-action reviews (AARs) fail when they become narrative write-ups with no ownership. A functional AAR is a governance workflow: define findings, assign owners, set deadlines, and require retesting of corrected elements. Keep the output short and operational: what broke, why it broke, what control fixes it, and how you will verify the fix works.
Maintenance: keeping COOP current as services evolve
COOP should update whenever the service model changes: new geographies, new high-acuity cohorts, new technology platforms, new vendors, or shifts in staffing composition. A simple discipline helps: quarterly roster and contact validation, semiannual vendor contingency review, and at least one annual full-scale exercise that includes external stakeholders (as feasible).
When COOP activation is rehearsed, evidence-based, and continuously improved, it becomes a stability asset for commissioners and a safety asset for the people you support—especially when disruption is not a one-off event but a recurring operating condition.