Business Continuity Architect

Draft Continuity Brief — Online Retailer

Scenario: Regional power outage; primary warehouse unavailable for up to two days.

Status: Planning exercise only. No operational capability, backup site, inventory status, supplier agreement, legal requirement, or recovery time has been verified. Owners must validate all assumptions before operational use.

Critical outcomes to protect

1. Protect employees and visitors; follow local emergency responders and site safety procedures.
2. Preserve order, payment, customer-service, and inventory records.
3. Communicate accurate service status without promising unverified restoration times.
4. Resume the minimum feasible set of order and support activities once people, systems, and facilities are safe.

Initial impact and unknowns

No maximum tolerable downtime, recovery time objective, capacity, backlog, or service promise is assigned until owners provide evidence and approve it.

First-response roles (names to be assigned)

• Incident lead: activates the plan, confirms scope, records decisions, and sets the next briefing time.

Safety/site lead: accounts for people and determines whether the location can be entered, following qualified local direction.

Operations lead: assesses order backlog, stock visibility, alternate fulfillment options, and safe minimum service.

• Communications lead: coordinates approved employee and customer updates using verified facts.
• IT/data lead: checks system availability, data protection, and approved recovery procedures.

Keep an offline contact tree and current call order in a controlled copy of the plan. Do not store sensitive phone numbers in a public listing.

First 0–4 hours: decision checklist

1. Confirm the incident through an authoritative source and follow emergency instructions; do not send staff into an unsafe facility.
2. Account for employee safety and availability using established internal procedures.
3. Identify affected systems, warehouse functions, service channels, and time of last verified data.
4. Convene decision owners; record time, decision, evidence, owner, and review trigger.
5. Decide whether to pause, queue, or accept orders based on verified system capability and customer transparency.
6. Issue a holding update with known impact, next update time, and support route.

Minimum-operation options to validate

• Pause new orders or clearly label expected delays if fulfillment cannot be supported.
• Use an already contracted, safe alternate fulfillment provider only after confirming capacity, data handling, inventory access, and approval.
• Route urgent customer requests to staffed support channels; avoid sharing personal order details publicly.
• Maintain a controlled manual log for approved offline work, then reconcile against system records after restoration.

Communications drafts

Employee update: “Our primary warehouse is unavailable due to a regional power outage. Please do not travel to or enter the site until the designated safety lead confirms it is safe. [Approved manager/channel] will provide the next update at [time]. Contact [internal route] for support.”

Customer update: “We are experiencing a fulfillment delay affecting some orders. We are assessing the impact and will post another update by [time]. If you need help with an existing order, contact [verified support channel]. We will share an updated estimate only when confirmed.”

Recovery and validation

Restore only after safety clearance and system/data checks by accountable owners. Reconcile offline transactions and inventory changes, prioritize the oldest or most time-sensitive orders using an approved policy, document customer remedies, and capture lessons learned. Verify backup power, alternate fulfillment, staff coverage, contact tree, data backups, and supplier agreements before assigning recovery targets.

Tabletop exercise

Inject 1: warehouse power fails; confirm activation and people-safety checks.

Inject 2: ecommerce platform continues accepting orders; decide whether to pause or label delays.

Inject 3: alternate provider reports limited capacity; define priority rules and approval authority.

Inject 4: customers post order identifiers publicly; test privacy-safe support response. Record decision time, missing data, role confusion, and corrective action owner/date.

Reference: CISA Instructional Guide to the Active Assailant Emergency Action Plan Template — Business Continuity considerations. This example is not a complete plan and must be adapted and approved by qualified organizational owners.