Template preview · Public service
Public service continuity
Keep an essential public service available through disruption with clear priorities.
A continuity plan for a fictional public-facing service.
Sample purpose
Keep an essential public service available through disruption with clear priorities.
Audience: Service manager, Continuity lead- Structure
- 4 sections
- Criteria
- 12
- Sources
- 8
- Watches
- 3
- Default approach
- Review first
Set the purpose first. Then change every section, criterion, and agent setting before anything runs.
Fictional sample
Structure and criteria
Sample content shows the shape of a useful document. Copying it is optional.
01 Review firstEssential service priorities
For this public service continuity, ranks services and minimum service levels.
Criteria
- Each service has a minimum operation and recovery time.
- Each recovery time is justified by a named harm if missed, such as a statutory permit deadline or a stalled build site.
- Ranking uses current request volumes (for example 60 permit applications a week) dated within the last quarter.
Sources
- FEMA continuity ready.govEssential functions.
- Lakeborough volumes (fictional) api.lakeborough-permits.exampleFictional demand.
Sample content
Essential service Minimum operation Lead Restore by Urgent permit intake Accept phone requests and issue reference number Dana 4 hours Public outage notice Update accessible status page Comms lead 1 hour 02 Review firstAlternate service procedure
For this public service continuity, defines authorized alternate process and accountable roles.
Criteria
- Each step has an owner and trained backup.
- Names where paper intake forms are stored and the reference number format used so entries can be keyed in after recovery.
- Each alternate channel has a test date and the number of requests it handled per hour in that test.
Sources
- Lakeborough backup manual (fictional) api.lakeborough-permits.exampleFictional paper process.
- NARA records guidance archives.govHandling records.
Watches
- Follows Essential service priorities
Sample content
- ☐ Use approved paper form and secure daily transfer log
- ☐ Assign one staff member to status updates
- ☐ Escalate suspected duplicate permit before issuing
03 ManualPublic updates and access
For this public service continuity, maintains accessible status channel and update cadence.
Criteria
- States the update cadence before an outage starts, such as every 2 hours from 08:00 to 18:00, and the time of the next update.
- The status channel does not depend on the failed system, such as a static page or phone line outside the permit platform.
- Each update tells residents what they can do now, such as submit by email, and what deadlines are extended.
Sources
- USWDS designsystem.digital.govAccessible communication.
- Lakeborough channels (fictional) api.lakeborough-permits.exampleFictional channels.
Watches
- Follows Essential service priorities
Sample content
- 2026-10-02 09:00 · Outage noticeDana posts known impact and next update time.
- 2026-10-02 13:00 · Service checkPermit lead confirms received requests are logged.
- 2026-10-03 10:00 · Recovery reviewReconcile temporary register with restored system.
04 Review firstRecovery and exercise
For this public service continuity, tests restoration and captures improvement actions.
Criteria
- Each exercise records its date, the scenario, who took part and the measured recovery time against the target.
- Each gap found in an exercise becomes an action with an owner, a due date and the exercise that will retest it.
- Shows the status of actions from the previous exercise and flags any still open past their due date.
Sources
- Ready.gov exercises ready.govExercise evaluation.
- Lakeborough exercises (fictional) api.lakeborough-permits.exampleFictional records.
Watches
- Follows Alternate service procedure
Sample content
- Urgent requests assigned reference
- 100% within 30 minutes
- Status updates on schedule
- Every 4 hours
- Unreconciled paper cases
- 0 target