# Continuity plan

ISO 22301 | Worked example with fictional data

Step: Choose strategies and write usable plans
Owner: Business owners + continuity lead
When: Before relying on arrangements

## Gather first
- Approved business impact analysis
- Staff and supplier contact lists
- Recovery procedures and technology dependencies

## How to prepare it
1. Write when the plan is triggered, who declares it and how staff learn which version is active. Put first-hour actions near the top.
2. Describe the workarounds and recovery steps by service. Specify dependencies, checks before restoration, fallback if a supplier is unavailable and criteria for returning to normal.
3. Run a timed exercise without relying on the usual owner. Record achieved service and data recovery against targets and assign any fixes.

## Example

### Trigger
Order system down for 30 minutes with no confirmed recovery time

### First actions
Incident lead opens a log. Dispatch lead starts the emergency order queue.

### Recovery sequence
Recover database, reconcile recent orders, verify labels, resume priority dispatch.

### Fallback
Use backup printer and call the alternate courier contact.

### Return to normal
Service owner signs off after reconciliation and successful shipment test.

## Review
Someone covering the primary owner can activate the plan and verify recovery with the written instructions.

## Handoff
Give controlled copies to responders and suppliers and update the record after each exercise.

Use the current rules and any prescribed forms for your engagement.
