Why power-outage readiness is a public sector “must-have” (not a nice-to-have)
Hospitals and community health services don’t get to “pause” when the lights flicker. From vaccine fridges to oxygen concentrators, from electronic medication charts to call bells—electricity sits behind almost every patient experience. Yet power disruptions can come from more than storms: network faults, vehicle strikes on poles, construction incidents, cyber events, or upstream generation issues.
Across government and public sector organisations, the most effective way to strengthen resilience is to practise. A well-designed “power outage drill” is a practical, low-cost exercise that reveals hidden dependencies, improves coordination, and helps teams respond calmly when real interruptions happen.
This guide is written for operational leaders, facilities teams, clinical managers, emergency planners, and communications staff who want a repeatable approach. You’ll find step-by-step instructions, realistic examples, and actionable tips that can be adapted for a DHB newsroom audience—particularly when communicating preparedness and lessons learned.
What this guide covers (and what it doesn’t)
This is a tabletop + targeted walk-through drill approach designed for public sector health settings. It is not a substitute for engineering advice or regulatory requirements, and it won’t replace formal emergency management planning. What it will do is help you run a structured exercise that tests decision-making, communication, and continuity under realistic constraints.
Step-by-step: How to run a power outage drill for health services
1) Choose a drill scope that’s specific enough to be useful
The biggest mistake is a drill that’s too broad (“What if the hospital lost power?”) and ends up vague. Define a scenario that forces real decisions. Pick one site, one time window, and one set of services.
- Good scope example: “A partial outage affects one ward and the adjacent imaging corridor for 90 minutes at 2:00pm on a weekday.”
- Even better: “Main supply drops; generator starts but one distribution board fails, leaving Ward X without normal power. Emergency lighting works. Wi‑Fi is intermittent.”
- Too broad: “All power is out everywhere indefinitely.” (This can be a later, advanced drill.)
Tip: If you want a creative, high-value drill, model a “near-miss” you’ve experienced—like a planned shutdown that overran, or a flicker that knocked out one system. Those scenarios reveal the most practical improvements.
2) Set clear exercise objectives (3–5 only)
Write objectives that you can verify at the end. Keep them measurable.
- Confirm which critical clinical equipment is on emergency power and which isn’t.
- Test the process for prioritising load (what gets powered first and why).
- Validate internal communications when email/Wi‑Fi is degraded (radios, phone trees, runners).
- Check cold-chain protection actions for temperature-sensitive medicines and vaccines.
- Assess how quickly leadership can stand up an incident coordination structure and assign roles.
Data point to include in your planning notes: Many modern facilities rely on complex power distribution and building management systems; a generator starting successfully doesn’t guarantee every clinical area receives the right power feed. Drills frequently uncover “it’s on the generator, but not on this circuit” issues.
3) Build a cross-functional drill team (not just Facilities)
A meaningful outage response is a whole-of-system effort. Invite representatives who will actually make decisions during a real incident.
- Facilities/Estates (electrical, maintenance)
- Clinical lead from the affected area (charge nurse manager, duty manager)
- Digital/IT (EHR access, Wi‑Fi, device charging, downtime procedures)
- Pharmacy / Medicines management (fridges, dispensing, controlled drugs access)
- Security (access control, lifts, crowd management)
- Communications (internal comms, public messages, media queries)
- Emergency management / incident controller
Real-world lesson: If you exclude IT, you may miss that phones run over IP, nurse call consoles are network-dependent, or that downtime printing requires a server and a specific printer that isn’t on emergency power.
4) Map “critical dependencies” before the drill (30–60 minutes)
Run a quick dependency mapping session to identify what truly matters in the scoped area. This helps you design realistic injects (events) and prevents the drill from becoming theoretical.
- People: Who must be on site? Who can be called in? Who can authorise service reduction?
- Places: Which rooms must remain functional (resus bays, medication rooms, isolation rooms)?
- Power: Which outlets are red/emergency vs standard? Which circuits feed key equipment?
- Tech: Wi‑Fi, phones, EHR, lab systems, imaging, automated dispensing cabinets.
- Supplies: Torches, headlamps, batteries, extension leads, manual BP cuffs, paper forms.
Actionable tip: Physically walk the area and label a small set of “must-know” points: emergency power outlets, manual door overrides, stairwell lighting, and where printed downtime packs are stored.
5) Decide the drill type: tabletop, walk-through, or hybrid
For most services, a hybrid drill gives the best value without disrupting care.
- Tabletop: Talk through decisions around a table. Best for leadership and comms.
- Walk-through: Physically move through key steps without switching off power. Best for identifying “where is it?” and “who has the key?” problems.
- Hybrid: Start tabletop, then walk critical actions (e.g., checking which sockets are on emergency power).
Safety note: Do not simulate power loss by interfering with live electrical infrastructure unless you have formal approval and qualified personnel. Most of the learning happens without touching a switch.
6) Write a simple scenario script with timed “injects”
Injects are prompts that force teams to make decisions. Keep your script short: a one-page timeline is enough.
- T+0: Lights flicker; some outlets dead; emergency lighting active.
- T+10: Generator is running, but staff report the medication fridge display is off.
- T+20: Wi‑Fi unstable; VoIP phones drop in one corridor.
- T+35: A patient needs transfer; lifts are restricted to emergency operations only.
- T+50: Media enquiry arrives asking if services are safe and whether appointments are cancelled.
- T+70: Partial restoration; IT warns systems may reboot unpredictably.
Make it local: Add an inject related to your site’s known pressure points (e.g., “the only printer for downtime forms is on a standard circuit”).
7) Define roles and a communication ladder (before you start)
During outages, uncertainty spreads quickly. Agree on who is “in charge” for the drill, who logs decisions, and how information flows.
- Incident Controller: overall coordination and priorities
- Operations lead: clinical impacts and staffing
- Logistics/Facilities lead: electrical status, workarounds, generator fuel checks
- Planning/log keeper: timeline, decisions, actions
- Communications lead: internal updates and external messaging
Practical tip: Test at least one non-email channel during the drill—phone tree, radios, or a designated “runner” to deliver updates to wards.
8) Run the drill (60–90 minutes) and log decisions, not opinions
Start with ground rules: this is a learning exercise, not an assessment of individuals. Then run the timeline. Your log keeper should capture:
- What decision was made (and by whom)
- What information was used to make it
- What was unclear or missing
- What workarounds were used
Example: “At T+20, Wi‑Fi unstable. Decision: switch to paper medication administration record for new admissions. Trigger: EHR access intermittent. Owner: duty manager. Gap: paper forms not stocked in Ward X.”
9) Validate three critical “micro-processes” that outages often break
These are small steps that can cause big disruption if forgotten. Build them into your discussion and walk-through.
- Cold chain protection: Who checks fridge temps? What’s the threshold to relocate stock? Where is the validated backup fridge?
- Access and security: What doors fail-safe vs fail-secure? How do staff access medication rooms if badge readers drop?
- Patient movement: If lifts are limited, how are transfers prioritised? Who escorts? What equipment must accompany the patient?
Actionable tip: Create a “grab list” for ward leaders: torches, spare batteries, paper forms, contact numbers, and location of emergency outlets. Keep it laminated in a known drawer.
10) Pressure-test your public messaging: what will you say, when, and to whom?
For public sector health services, communications during disruption must be clear, calm, and accurate. In your drill, practise drafting two messages:
- Internal update (staff): what’s affected, what’s not, what to do next, and when the next update is due.
- External holding statement (public/media): acknowledgement, safety assurance if appropriate, what patients should do, and how updates will be shared.
Real-world example wording (external holding statement): “We’re managing a power issue affecting part of the facility. Essential services remain available. Some appointments may be delayed; patients should wait for confirmation before travelling where possible. We’ll provide an update at [time].”
As a general reference point for how widespread and disruptive outages can be—and why clear public updates matter—major incidents covered by reputable outlets can help teams understand public expectations during disruption. For broader context on outage events and public response, see reporting via BBC News coverage of power disruptions.
11) Convert findings into a 30-day improvement plan (not a long wish list)
The drill is only valuable if it results in changes. Immediately after the exercise, identify:
- Top 3 fixes that can be completed within 30 days
- Top 3 risks that need budgeting or engineering review
- Top 3 training updates (e.g., where downtime packs are kept, how to switch to paper workflows)
Practical examples of “30-day fixes”:
- Label emergency power outlets more clearly in the scoped area and brief staff on what the labels mean.
- Restock and standardise downtime packs (paper forms, clipboards, pens) and add a monthly check.
- Update the ward contact list and create a non-email escalation pathway.
Examples of “budget/engineering items”:
- Move specific critical devices to emergency circuits or add additional emergency outlets.
- Review generator load testing schedules and fuel monitoring processes.
- Assess single points of failure in network closets that impact phones and EHR access.
12) Share the learning (carefully) to build a culture of readiness
For a DHB newsroom context, a short internal write-up—or a public-facing piece if appropriate—can improve trust and demonstrate preparedness without revealing sensitive infrastructure details.
- Summarise what the drill tested and why it matters for patient safety.
- Highlight improvements made (e.g., clearer labelling, better downtime processes).
- Reinforce what patients should do during disruptions (e.g., wait for updates, keep contact details current).
Tip: Focus your story on people, process, and safety—avoid technical specifics that could create security risk.
Conclusion: Make outages boring by making practice routine
Power outages feel dramatic when they’re rare and unpractised. A well-scoped drill turns uncertainty into a checklist: who calls whom, what actions happen first, what workarounds are safe, and how to keep patients informed. If you run one hybrid tabletop/walk-through each quarter—rotating across different departments—you’ll steadily shrink the gaps that cause disruption.
The goal isn’t perfection. It’s confident, coordinated care when conditions aren’t perfect. Start small, log what you learn, fix what you can in 30 days, and repeat.
