Skip to main content

design-a-disaster-communications-plan

Design resilient communications for severe operational disruption. Use when organizations need roles, channels, audiences, message controls, and rehearsals that work during facility, technology, supplier, safety, or regional failure.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
design-a-disaster-communications-plan
category
write
description
Design resilient communications for severe operational disruption. Use when organizations need roles, channels, audiences, message controls, and rehearsals that work during facility, technology, supplier, safety, or regional failure.
# design-a-disaster-communications-plan Plan for communication when normal identity, network, staff, or approval paths are degraded. ## Inputs - Continuity scenarios, critical services, affected groups, locations, and communication obligations - Contact authorities, accessibility and language needs, privacy boundaries, and stakeholder owners - Primary and alternate channels, vendors, identity dependencies, and current contact sources ## Procedure 1. Define scenarios, activation criteria, communication objectives, and accountable incident authority. 2. Segment employees, responders, customers, families, suppliers, regulators, media, and community partners by need. 3. Map for each audience who decides, drafts, verifies, approves, publishes, receives replies, and records delivery. 4. Establish primary, alternate, and last-resort channels with independent dependencies where practical. 5. Design message templates for activation, safety action, service impact, uncertainty, cadence, correction, and stand-down. 6. Define authoritative status sources and methods for verifying identity when normal systems fail. 7. Protect personal contact data, sensitive locations, security tactics, and family information. 8. Plan multilingual, accessible, low-bandwidth, offline, and no-device delivery paths. 9. Test contact freshness, alternate-channel access, approval latency, reach, replies, corrections, and handoffs. 10. Record gaps, update sources and owners, and schedule scenario-specific retests. ## Guardrails - Never use an exercise message that could be mistaken for a real emergency. - Do not promise safety, restoration, or government action without verified authority. - Avoid a single communications platform or person as the only path. - Coordinate with authorized emergency and legal owners for regulated or life-safety messages. ## Done - Activation, audiences, roles, channels, and fallback paths are explicit - Templates preserve facts, uncertainty, accessibility, and privacy - Contact and alternate-channel tests produce evidence - Failed paths and remediation receive owners and retests
View on GitHub