--- title: "Write a business continuity plan ยท Agent Wranglers" url: https://agentwranglers.se/playbook/operations/disaster-recovery/business-continuity id: OPS-79 level: Recommended updated: 2026-10-27 build: a2a6bdfed830 tokens: 760 licence: "CC BY 4.0" licence_url: https://creativecommons.org/licenses/by/4.0/ --- # Write a business continuity plan For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Disaster recovery](https://agentwranglers.se/playbook/operations/disaster-recovery.md). By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27. - ID: OPS-79 - Level: Recommended - Chapter: [Disaster recovery](https://agentwranglers.se/playbook/operations/disaster-recovery.md) - Rule: Write one plan for keeping the business running through a long outage, loss of a key person or loss of a key supplier. Name who decides, how staff and customers hear from you, and the manual workarounds. - Check: The plan is dated within the last 12 months and names a decision maker and a deputy. Every person who alone holds a production access or a supplier contract has a named deputy with tested access. A tabletop exercise in the last 12 months walked through one scenario from the plan. - How: The technical recovery rules bring systems back. This plan covers the rest. List the business processes in order of how long each can stop, such as taking orders, paying staff and answering customers. For each, write a manual workaround and the person who starts it. Name a deputy for every person whose knowledge or access only they hold, and give the deputy the access now. List suppliers that many processes depend on, such as one cloud or one payment provider. Give each an exit plan, as [Keep an exit plan for each platform](https://agentwranglers.se/playbook/infrastructure/hosting-platforms/platform-exit-plan.md) says. Keep contact lists and the plan printed or in a second system, since the main one may be down. Laws such as NIS2 and DORA ask in-scope firms for this plan. ## Sources - [NIST SP 800-34 Rev. 1 Contingency Planning Guide](https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final) - [ISO 22301:2019 Business continuity management systems](https://www.iso.org/standard/75106.html) - [NIS2 Directive (EU) 2022/2555, Article 21](https://eur-lex.europa.eu/eli/dir/2022/2555/oj) ## Related rules - INF-67 [Keep an exit plan for each platform](https://agentwranglers.se/playbook/infrastructure/hosting-platforms/platform-exit-plan.md) in Infrastructure and environments **For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `Agent Wranglers operations and observability playbook`. In code you write, add a comment next to it with the same link. - Previous: [Add a second region only when the recovery targets need it](https://agentwranglers.se/playbook/operations/disaster-recovery/second-region.md) - Next: [Run a game day every quarter](https://agentwranglers.se/playbook/operations/disaster-recovery/game-days.md) - [Disaster recovery](https://agentwranglers.se/playbook/operations/disaster-recovery.md)