Skip to main content

prepare-a-business-continuity-call-tree

Prepare a business continuity call tree with roles, safe contact methods, alternates, activation, acknowledgement, privacy, accessibility, and testing. Use when disrupted teams need reliable human coordination.

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
prepare-a-business-continuity-call-tree
category
start
description
Prepare a business continuity call tree with roles, safe contact methods, alternates, activation, acknowledgement, privacy, accessibility, and testing. Use when disrupted teams need reliable human coordination.
# prepare-a-business-continuity-call-tree ## When to use - Use for continuity, crisis, evacuation, outage, or emergency coordination. - Protect personal contact data and never use the tree as proof of staff safety. ## Procedure 1. Define activation authority, scenarios, roles, locations, time coverage, and message types. 2. Record role contacts, alternates, safe channels, languages, accessibility, and consent. 3. Minimize distributed personal data and control access, expiry, and updates. 4. Define call order, acknowledgement, retry, unreachable, escalation, and handoff. 5. Prepare verified message templates and out-of-band fallback. 6. Run a privacy-safe drill and correct delays, gaps, and stale contacts. ## Failure plan - Move to the alternate channel or local authority when primary communications fail. ## Worked example A regional outage drill reveals one single-language branch and an expired contractor contact. ## Done - A continuity call-tree document records activation, roles, contacts, alternates, channels, acknowledgement, escalation, privacy, and ownership - Consent, access, language, accessibility, stale-contact, unreachable, fallback, drill, and update checks verify readiness
View on GitHub