
Most downtime planning focuses on activation: how quickly can departments move to backup procedures once the EHR goes offline. That matters, and we cover it in our post on the first 30 minutes of a major EHR outage. But the current threat environment, particularly ransomware, means outages can run for days. The real test is not minute 20. It is hour 9, when the shift changes, supplies run low, and the people who activated everything are tired.
A 24-hour playbook gives your organization a plan for that stretch. It does not replace your downtime policy. It is a practical, time-sequenced companion that tells each role what to do and check at each stage.
Hours 0 to 1: Activate and Confirm
This phase follows your first-response protocol. The playbook should simply confirm that these items are complete before moving on:
- Downtime formally declared and all department leads notified through a channel that does not depend on the EHR
- Priority departments active on their downtime workstations, confirmed through the Downtime Dashboard
- A downtime operations coordinator named, separate from the IT lead managing restoration
- An event log started, recording activation times and the first status update
Hours 1 to 4: Stabilize
Once departments are on backup workflows, the goal is a steady operating rhythm.
- Set the communication cadence: updates every 30 minutes at first, moving to hourly once the situation is stable
- Confirm the restoration estimate from IT and note when it was last updated
- Check that new registrations are using downtime encounter numbers and that a log of numbers issued is being kept
- Spot-check the first batch of completed eForms for completeness
- Brief leadership with a short, structured update covering cause, scope, current operations, and expected duration
- Begin scripted patient communication in registration and high-volume clinical areas
For the coordination structure behind this, see our post on building a downtime command center.
Hours 4 to 8: Sustain
This is where supply and capacity problems start to appear.
- Check wristband stock, label stock, printer supplies, and toner at every downtime workstation
- Review how much of the downtime encounter number bank has been used and project whether it will last through the next 24 hours
- Confirm that printed last-resort binders are accessible in each clinical area, with the understanding that they reflect the last update before the outage
- Arrange staff breaks and relief, especially for charge nurses and registration leads carrying extra load
- Decide whether elective procedures and scheduled outpatient visits will proceed, using the decision authority defined in advance
- If the outage extends beyond a few hours, send early notice to payers and other external parties whose deadlines may be affected
Hours 8 to 12: Manage the Handoff
Shift change is the highest-risk moment in an extended event because information has to cross a human boundary while the usual EHR support for handoffs is unavailable.
- Hold a short, scripted briefing for incoming leads covering current status, what is working, known problems, and the restoration estimate
- Use a handoff eForm so outgoing nurses leave a documented summary instead of relying on memory
- Make accountability explicit: who owns downtime activation and coordination on each unit as of the handoff
- Brief agency and travel staff who joined mid-event on workstation locations and basic workflows
- Have the outgoing coordinator hand over the event log, the encounter number tracker, and the open issues list in person or by phone
Hours 12 to 24: Plan for the Long Haul
If the event is still running past the 12-hour mark, the playbook shifts from reacting to planning.
- Watch for fatigue. Rotate people out of the most demanding downtime roles and confirm that critical documentation is still being completed accurately
- Refresh patient communication so people who have been waiting for hours hear current, honest information
- Run a documentation quality audit on a sample of eForms from each department and correct problems while staff can still be coached
- Begin reconciliation planning before the EHR returns: which records are highest priority, which billing deadlines are approaching, and who will do what. Our post on reconciling downtime data back into the EHR provides the sequence
- Review whether the board, regulators, or legal counsel need to be notified based on your pre-defined thresholds
- Reassess staffing for the next 24 hours, including whether additional coverage is needed
The Cyber Branch
If the cause is or may be a security incident, the playbook needs a parallel track. Containment decisions may change which workstations can safely stay connected, and legal and breach assessment steps may start in the first hours. This is why the downtime program and the cyber incident response plan should be aligned in advance, as covered in our post on aligning your downtime preparedness program with your cyber incident response plan. The playbook should reference the specific decisions that are pre-made rather than leaving them to be debated in real time.
Format and Testing
Keep the playbook short enough to use under pressure. A two-to-four page document organized by time window, with role-specific checklists, will be used. A forty-page document will not. Store a printed copy where it can be reached without the network.
Then test it. A tabletop exercise that walks leadership through hour 9 and hour 20 reveals gaps in staffing, supplies, and decision authority that a first-30-minutes drill will never find. To build a playbook around your specific facilities and workflows, contact our team or request a demo.