Document summary
This page explains critical services, recovery objectives, alternatives, backups, exercises, outage communication, and post-incident review.
Business impact analysis
Each service owner identifies processes, dependencies, data, providers, maximum tolerable outage, and client and obligation impact. Recovery figures are not published before testing and approval.
Priorities and objectives
Services are classified by impact and assigned suitable recovery and data objectives. Safety, data protection, and critical obligations take priority over nonessential features.
Continuity strategies
Strategies cover people, location, connectivity, provider, storage, and safe manual alternatives. A critical service does not depend on one key, account, or person without a documented backup.
Technical recovery
Each service has a checklist, decision owner, run order, dependencies, integrity check, and rollback plan. Backups are tested through actual isolated restoration, not merely a success log.
Exercises
Tabletop and technical exercises follow risk and cover staff absence, provider failure, loss of access, and data corruption. Gaps, actions, owners, due dates, and retests are recorded.
Outage communication
The plan defines audience, channel, frequency, and approver. The status page shows confirmed information, service impact, workaround, and next update time and does not publish a root cause before verification.
Post-incident review
After recovery, we document timing, decisions, what worked, what failed, root cause, and prevention plan. Review focuses on correcting systems, accountability, and follow-up rather than blame.
Versions
Change log
- Version 1.0.0
Published the first operational version with clear scope, responsibilities, rights, and escalation routes.