Works out what happens over time if each activity stops, following ISO 22301 clause 8.2.2 and NIST SP 800-34. You receive the impact of each activity over time, its priority, its recovery objectives checked against the longest stop it can tolerate, the financial exposure, the recovery target each system must meet compared with what its last test achieved, and the dependencies several activities share. It rests on the estimates you give: it tests nothing itself.
Contents
1. Document Information
2. Executive Summary
3. Scope and Method
4. Impact Criteria
5. Impact Over Time
6. Activity Priorities
7. Recovery Objectives
8. Financial Exposure
9. Resources and Dependencies
10. System Recovery Targets
11. Shared Dependencies
12. Gaps to Decide
13. Workaround Review
14. Findings and Recommendations
15. Approval and Review
16. Document Version History
What you provide
Deliverable — Its title, its author and its structure are yours: they steer what is written.
Scope of the analysis — What is analysed, and who answers for it.
Impact criteria — What each level of impact means here, so that departments score alike.
Activities and their impact — One line per activity, with the person who runs it. Rate the impact if it stopped for that long.
What each activity needs — Separate several entries in a cell with a comma: shared dependencies are found from them.
