---
title: 11.03 Continuity plans
description: Create a continuity or recovery plan from a typed template, fill in its scope, recovery steps and call tree, take it through review and approval by…
---

[Skip to content](https://support.simplerisk.com/kb/11-03-continuity-plans#main-content)

English

Show submenu for translations

[Customer portal](https://support.simplerisk.com/tickets?hsLang=en)

[![SimpleRisk logo of a man walking a tight rope](https://support.simplerisk.com/hs-fs/hubfs/simplerisk_logo_long_small-4.png?width=377&height=72&name=simplerisk_logo_long_small-4.png)](https://www.simplerisk.com/)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://support.simplerisk.com/tickets)
- [Contact us](https://www.simplerisk.com/about-us/contact-us)

[Contact us](https://www.simplerisk.com/about-us/contact-us)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [SimpleRisk Knowledge Base](https://support.simplerisk.com/kb?hsLang=en)
2. [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en)
3. [11 Business Continuity and Disaster Recovery](https://support.simplerisk.com/kb/user-guide?hsLang=en#11-business-continuity-and-disaster-recovery)

# 11.03 Continuity plans

## Create a continuity or recovery plan from a typed template, fill in its scope, recovery steps and call tree, take it through review and approval by someone other than its author, change it through new versions, and export it as a PDF or Word document.

> **Requires:** *Business Continuity and Disaster Recovery Extra*
> 
> Plans, versions, the call tree and plan export are part of this Extra.

## Why this matters

A plan is only worth following if you can tell which copy is the real one. People have written a plan, edited it in place after an incident, and then been unable to say what it said on the day. SimpleRisk avoids that by making the approved version a snapshot. Once a version is approved, nobody can change it. Changes happen in a new version, which has to be approved in turn, and the old one stays in force until then.

## Before you start

- Authors need **Able to Manage Continuity and Recovery Plans**. Approvers need **Able to Approve Continuity and Recovery Plans**. They must be different people for any given version.
- Have your processes, and for recovery plans your assets, in place. See [Contacts and the business impact analysis](https://support.simplerisk.com/kb/11-02-contacts-and-business-impact-analysis?hsLang=en). The call tree can only use people who are already in the directory.

## Step-by-step

### 1. Create the plan

Open **Continuity Plans** and click **New Plan**. Give it a name and choose a **Plan Type**. Your administrator controls which types are offered. By default you'll see **IT Contingency and Disaster Recovery Plan** and **Business Continuity Plan**; the others are **Continuity of Operations Plan**, **Crisis Communications Plan**, **Cyber Incident Response Plan** and **Occupant Emergency Plan**. The type can't be changed afterward.

Click a plan in the list to read it without opening the plan page. The summary shows the plan's type, status, the version in force and any version in progress, then the version's scope, each section of text, the recovery steps, the call tree with each contact's details, any compliance controls and linked risks, and the version history. Pick an earlier version from the **Version** list to read it instead. **Export PDF** and **Export Word** in the header download the version on screen. People who can edit plans get an **Edit** button there, and the pencil in the row, which open the plan page. Approvers who can't edit plans get an **Open plan** button for the same page, where **Approve** and **Reject** live. The address of a summary is the list address with `?plan=` and the plan's number, so you can send a colleague a link straight to it. The status filter above the list narrows it to drafts, plans in review, approved plans or retired ones.

![The read-only summary of an approved disaster recovery plan, with its details, version and scope, and the Export PDF, Export Word and Edit buttons in the header](https://support.simplerisk.com/hubfs/docs-sync/plan-summary-modal.png)

The new plan starts from the template for its type, following the SP 800-34 shape: **Introduction**, **Concept of Operations**, **Activation and Notification**, recovery, **Reconstitution** and **Appendices**. The first two types ship with tailored guidance text in each section. Treat it as a prompt, not as content: replace it.

### 2. Fill in the draft

A new plan has one version, version 1, in draft. On the plan page:

- **Plan Details**: the name, **Next Review Date** and, once an exercise has been recorded, **Last Tested**.
- **Scope**: what the plan covers. Each type is meant for one kind of scope. A **Business Continuity Plan**, **Continuity of Operations Plan**, **Crisis Communications Plan** or **Occupant Emergency Plan** covers business processes; an **IT Contingency and Disaster Recovery Plan** or **Cyber Incident Response Plan** covers assets and asset groups. The card accepts either, so keep to the one that fits the type. A plan that names nothing covers nothing in the coverage report.
- **Recovery Tier**: optional, a whole number from 0 to 7. Tier 0 has no off-site recovery capability; tier 7 recovers automatically with no data loss.
- **Sections**: edit the text of each section, rename sections, and use **Add Section**, **Move up** and **Move down** to shape the document.
- **Recovery Steps**: click **Add Step**. Each step has a **Phase** (recovery or reconstitution), a description, optional details, an **Assigned Contact** from the directory, and a **Checklist item** option. Checklist items become the live checklist during an activation. Steps not marked as checklist items stay in the plan as reference.
- **Call Tree**: click **Add to Call Tree**, **Choose a contact**, and give each entry a role, whether it is **Primary** or **Backup**, and an **Escalation Order**. Put a backup behind every key role. A call tree with no backup contact is one of the gaps the gap report looks for.

Click **Save Draft** as you go. The plan page also shows the **Compliance Controls** and linked risks cards, covered in [Reports, controls and AI suggestions](https://support.simplerisk.com/kb/11-06-reports-controls-and-ai-suggestions?hsLang=en).

![A draft Business Continuity Plan page showing the plan details, a scope with two business processes ticked, the section list, two recovery steps, a call tree with primary and backup entries and the recovery tier](https://support.simplerisk.com/hubfs/docs-sync/plan-draft-page.png)

### 3. Submit it for approval

Click **Submit for Approval**. The version moves to in review and locks: nobody can edit it until it is approved, rejected or withdrawn. If you spot a mistake after submitting, click **Withdraw** and it returns to draft, editable again.

### 4. Approve or reject

An approver opens the plan, reads it, and clicks **Approve** or **Reject**.

- **Approve** puts the version in force. A previous version, if any, is retired as superseded.
- **Reject** returns it to its authors as a draft.

The approver can't be anyone who created, edited or submitted that version, whatever permissions they hold. If the version changed after the approver opened it, or another version of the plan is now waiting for approval, SimpleRisk refuses and asks them to reload and review again. That is what you want: the approval applies to the text the approver actually read. Approval is also refused if a contact in the call tree or a process in the scope has been deleted since, until you fix the plan.

### 5. Change an approved plan

An approved version can't be edited. Click **Start New Version** to copy it into a new draft. The approved version stays **In Force** while the new one is drafted, reviewed and approved. A plan can have only one new version in progress at a time. Earlier versions stay viewable, marked as earlier versions that can't be changed.

### 6. Retire a plan

**Retire Plan** retires every version and can't be undone. A retired plan can no longer be changed, covers nothing in the reports, and can't be activated. Its history, exercises and links remain. The same action is the archive button in the plan's row on the list, and it only appears for plans with an approved version in force.

A plan that was never put in force is different. If you started a draft and don't need it, the trash button in its row deletes it, along with its draft versions and links. That button disappears as soon as the plan has been submitted for approval, and a plan that an exercise or an activation uses can't be deleted. Anything that has been submitted or approved is history, so you retire it instead.

### 7. Export a copy

On the plan page, **Export PDF** and **Export Word** produce a whole document: header, every section, the recovery steps, the scope, the recovery tier, and the call tree with names, roles, phone numbers and e-mail addresses. Export a copy of every approved plan and store it somewhere that doesn't depend on SimpleRisk, since the point of an export is that it works when the platform doesn't.

Anyone with view access can export an approved, superseded or retired version. A draft or in-review version can be exported only by people who can edit plans, and carries a banner reading "DRAFT - NOT APPROVED - DO NOT RELY ON THIS COPY" (or the in-review equivalent). The e-mail address of a contact taken from a linked user's profile is left out for people without **Able to Manage Plan Contacts**. If any text in the plan can't be decrypted, the export is refused entirely.

## Common pitfalls

- **Approving your own work.** It isn't possible, so plan the approval step before you need it.
- **Leaving template guidance in place.** An approved plan that still says "State why this plan exists" is worse than a draft.
- **A call tree of primaries only.** The person you need is on holiday.
- **Forgetting that new versions don't take effect until approved.** During an incident, the plan in force is the last approved one, not your better draft.

## Related

- [Contacts and the business impact analysis](https://support.simplerisk.com/kb/11-02-contacts-and-business-impact-analysis?hsLang=en)
- [Exercises and findings](https://support.simplerisk.com/kb/11-04-exercises-and-findings?hsLang=en)
- [Activating a plan](https://support.simplerisk.com/kb/11-05-activating-a-plan?hsLang=en)

- [FAQs](https://support.simplerisk.com/kb/faqs?hsLang=en)
- [SimpleRisk Extras](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#main-content)

    - [Vulnerability Management Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#vulnerability-management-extra)
    - [Team Separation Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#team-separation-extra)
    - [Import-Export Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#import-export-extra)
- [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#main-content)

    - [00 About This Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#00-about-this-guide)
    - [01 Installation and Deployment](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#01-installation-and-deployment)
    - [02 Upgrades and Maintenance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#02-upgrades-and-maintenance)
    - [03 Users and Permissions](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#03-users-and-permissions)
    - [04 Authentication](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#04-authentication)
    - [05 Customization](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#05-customization)
    - [06 Configuring Risk and Compliance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#06-configuring-risk-and-compliance)
    - [07 Integrations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#07-integrations)
    - [08 The API](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#08-the-api)
    - [09 Encryption and Data Security](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#09-encryption-and-data-security)
    - [10 Workflows and Automation](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#10-workflows-and-automation)
    - [11 Reporting and Auditing](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#11-reporting-and-auditing)
    - [12 Operations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#12-operations)
    - [13 Reference](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#13-reference)
- [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en#main-content)

    - [00 Foundations of GRC](https://support.simplerisk.com/kb/user-guide?hsLang=en#00-foundations-of-grc)
    - [01 Risk Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#01-risk-management)
    - [02 Compliance Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#02-compliance-management)
    - [03 Governance](https://support.simplerisk.com/kb/user-guide?hsLang=en#03-governance)
    - [04 Asset and Data Inventory](https://support.simplerisk.com/kb/user-guide?hsLang=en#04-asset-and-data-inventory)
    - [05 Threat and Vulnerability Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#05-threat-and-vulnerability-management)
    - [06 Assessments](https://support.simplerisk.com/kb/user-guide?hsLang=en#06-assessments)
    - [07 Incident Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#07-incident-management)
    - [08 Audit and Reporting](https://support.simplerisk.com/kb/user-guide?hsLang=en#08-audit-and-reporting)
    - [09 Day-to-Day SimpleRisk](https://support.simplerisk.com/kb/user-guide?hsLang=en#09-day-to-day-simplerisk)
    - [10 Continuous Improvement](https://support.simplerisk.com/kb/user-guide?hsLang=en#10-continuous-improvement)
    - [11 Business Continuity and Disaster Recovery](https://support.simplerisk.com/kb/user-guide?hsLang=en#11-business-continuity-and-disaster-recovery)
- [SimpleRisk User Guides](https://support.simplerisk.com/kb/simplerisk-user-guides?hsLang=en)
- [Troubleshooting](https://support.simplerisk.com/kb/troubleshooting?hsLang=en)
- [SimpleRisk Hosted](https://support.simplerisk.com/kb/simplerisk-hosted?hsLang=en)
- [How To videos](https://support.simplerisk.com/kb/how-to-videos?hsLang=en)

[![favicon-1](https://support.simplerisk.com/hs-fs/hubfs/favicon-1.png?width=35&height=35&name=favicon-1.png "favicon-1")](https://www.simplerisk.com)

<https://www.facebook.com/simplerisk/> <https://www.twitter.com/simpleriskfree/> <https://www.linkedin.com/company/simplerisk/>

Copyright © 2026, SimpleRisk, Inc.