---
title: 06.07 The Business Continuity and Disaster Recovery Extra
description: Activate the Business Continuity and Disaster Recovery Extra, assign its seven permissions, tune the RTO thresholds, review cadence, reminder interval…
---

[Skip to content](https://support.simplerisk.com/kb/06-07-the-bcp-dr-extra#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. [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en)
3. [06 Configuring Risk and Compliance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#06-configuring-risk-and-compliance)

# 06.07 The Business Continuity and Disaster Recovery Extra

## Activate the Business Continuity and Disaster Recovery Extra, assign its seven permissions, tune the RTO thresholds, review cadence, reminder interval and exercise cadence, make sure reminders and activation notices can actually be delivered, switch on the optional AI capabilities, and understand what the Extra encrypts and what deactivating it destroys.

> **Requires:** *Business Continuity and Disaster Recovery Extra*
> 
> Business impact analysis, continuity and recovery plans, exercises and plan activation are provided by this Extra. Core SimpleRisk has none of them. The **Allow Access to Business Continuity and Disaster Recovery** permission is part of Core, though, and administrators hold it by default: without the Extra, a user who holds it sees a locked **BCP / DR** page that shows what the Extra adds. The other seven permissions described here appear only once the Extra is activated.

## Why this matters

This Extra holds the documents an organization reaches for on its worst day: who to call, what to restore first, and which version of the plan is the approved one. That changes what a configuration mistake costs. A missing mail relay means a plan activation that tells nobody. Once Core encryption is in your release, a lost encryption key means a call tree nobody can read. A tidy-minded admin who deactivates the Extra "to see what happens" deletes the lot.

Most of the Extra is configured by the people who use it. You, as the administrator, own five decisions: who holds which of the seven permissions, where the RTO thresholds sit, whether mail and the queue worker are healthy enough to carry notices and reminders, whether any of the AI capabilities are switched on, and how the encryption key is protected. This article covers each one, in that order after activation.

## Before you start

- **Admin access.** Only an administrator can activate or deactivate the Extra. Settings, once it is active, are open to an administrator or to anyone holding **Able to Manage Business Impact Analysis**.
- **A database backup, and (once Core encryption is in your release) a copy of the encryption key directory.** Take the backup before you activate on a populated install, and keep taking it afterward. The reasons are in "Deactivating the Extra" and "Protect the encryption key" below.
- **Working outbound mail.** E-mail is the only channel the Extra uses for activation notices and reminders. Configure and test mail first.
- **The queue worker running.** Reminders, retried notices and AI drafts all run through the background queue. See [Troubleshooting Common Issues](https://support.simplerisk.com/kb/12-04-troubleshooting-common-issues?hsLang=en) if you are unsure the worker is alive.
- **Optional companions.** The Secure Controls Framework (SCF) Extra is needed to link plans, processes and exercises to Secure Controls Framework controls. The Incident Management Extra is needed to link an activation to an incident. The Artificial Intelligence Extra is needed for the AI capabilities. None of them is required for the core workflow.

## Step-by-step

### 1. Activate the Extra

Open the **Settings cog**, choose **Settings Hub**, click the **Extras** chip, and open the **Business Continuity and Disaster Recovery** tile. The page shows one of three things:

- A message that the Extra is not installed. Install it first; see [Installing Extras](https://support.simplerisk.com/kb/01-06-installing-extras?hsLang=en).
- A message that it is not activated, with an **Activate** button if you are an administrator and your subscription includes the Extra.
- A green **Activated** marker with the Extra's version stamp and a **Deactivate** button.

Click **Activate**. The Extra creates its tables and registers its seven permissions. The **BCP / DR** menu entry, which until now held a single locked **Overview** item describing the Extra, becomes the full menu for users who hold the view permission.

### 2. Assign the permissions

The permission group **Business Continuity and Disaster Recovery** holds eight permissions. The view permission belongs to Core and is already there, granted to every administrator; activation adds the other seven to the same group. Assign them to roles under **Role Management**, or to individual users, the same way you assign any other permission. The names below are exactly what the permission screens display.

- **Allow Access to Business Continuity and Disaster Recovery:** Open the menu. Without the Extra, this shows the locked overview. With the Extra, it also lets a person read the business impact analysis, plans, exercises, activations, contacts and reports. Everything else builds on this one.
- **Able to Manage Business Impact Analysis:** Create, edit and delete business processes, recovery objectives, dependencies and mapped resources. Also covers requesting and accepting AI suggestions for a process.
- **Able to Manage Continuity and Recovery Plans:** Create and edit plans and submit them for approval. Also covers requesting and accepting AI suggestions for a plan draft, and exporting a draft.
- **Able to Approve Continuity and Recovery Plans:** Approve or reject a plan that is waiting for approval.
- **Able to Run Plan Exercises:** Schedule exercises, record their results and capture findings.
- **Able to Activate Plans:** Declare a plan active during a real event, notify its call tree, and deactivate it again.
- **Able to Manage Plan Contacts:** Create, edit and delete directory contacts. Without it, a user can read the directory but not the details a contact takes from a linked SimpleRisk user's profile, such as that user's e-mail address.
- **Able to Manage BCP / DR Settings:** Open the BCP/DR settings in the Settings Hub and change them. Administrators can always do this. The permission also gives its holder the Settings Hub itself, where they see only this Extra's tile.

Two design points affect how you grant these.

First, **approval is separated from authoring on purpose**. Holding the approve permission is not enough. Anyone who created, edited or submitted a particular version of a plan cannot approve that version, whatever permissions they hold. A plan therefore needs at least two people in the organization with the right permissions before its first version can go into force. On a small install, that is the thing that surprises people: the only person with both permissions can write a plan but never approve it.

Second, **keep the activate permission narrow**. Declaring an activation e-mails everyone in the plan's call tree immediately. Give it to the incident commander and one deputy, not to the whole continuity team.

### 3. Set the thresholds and cadence

Administrators, and anyone holding **Able to Manage BCP / DR Settings**, can open the settings. Click the settings cog, then the Business Continuity and Disaster Recovery Extra's tile in the Settings Hub. People who manage the BIA but don't hold that permission still see the thresholds the settings produce, in the process form's RTO hints, but can't change them. The page has four cards.

**RTO thresholds.** Two ceilings that turn a recovery time into High, Moderate or Low:

- **High: RTO up to:** 4 hours (240 minutes)
- **Moderate: RTO up to:** 24 hours (1,440 minutes)

Each field is a whole number plus a unit of minutes, hours or days. Anything longer than the Moderate ceiling counts as Low. The High ceiling must be shorter than the Moderate one, and the form refuses a pair that isn't.

These two numbers do two jobs. They set the suggested RTO range shown beside each outage-impact rating when someone fills in a business process. And they drive the Availability check on the Recovery Priority report, where an asset's Availability rating is compared with the recovery time of the processes that depend on it. Move the ceilings and that comparison moves with them. Set them to match how your organization actually talks about "critical" systems, not to the defaults for their own sake.

**BIA review cadence.** The default number of days between reviews of a process's business impact analysis, from 1 to 3650. The default is 365. It sets the next review date of any new process that has none. It does not rewrite dates on existing processes.

**Reminders and exercises.** Two numbers of days:

#### **Days between repeat reminders**

- **Range:** 1 to 365
- **Default:** 7

#### **Days between plan exercises**

- **Range:** 1 to 3650
- **Default:** 365

The first is how long someone reminded about an item waits before being reminded about the same item again (see Reminders in the next step). The second decides when a plan counts as overdue for an exercise: once that many days have passed since the plan's last exercise, or since its approval if it has never been exercised. A plan that is overdue shows up in the exercise attention list and triggers an overdue reminder. Changing the second value moves the overdue date of every existing plan the next time the page or the daily reminder job looks at it.

**Plan Types.** Which plan types people can choose when they create a plan. Two are on by default: **IT Contingency and Disaster Recovery Plan** and **Business Continuity Plan**. These two have their own section templates. The others share a general contingency template and are off until you switch them on: **Continuity of Operations Plan**, **Crisis Communications Plan**, **Cyber Incident Response Plan** and **Occupant Emergency Plan**. At least one type must stay on. Switching a type off hides it from the New Plan form but doesn't touch plans already created with it.

Click **Save**. Both new fields refuse a value outside their range and name the field in the message. **Restore defaults** puts every value on the page back to the figures above. Settings changes are written to the audit trail.

The same settings are available to scripts. `GET /api/v2/bcpdr/settings` reads them and `PATCH /api/v2/bcpdr/settings` changes `high_max_rto_minutes`, `moderate_max_rto_minutes`, `bia_review_cadence_days`, `reminder_interval_days`, `exercise_cadence_days` and `enabled_plan_types`. The patch needs the settings permission, or an administrator.

### 4. Check mail and the queue worker

The Extra sends two kinds of e-mail, and both depend on infrastructure outside the Extra.

**Activation and deactivation notices.** When someone declares or deactivates an activation, the Extra tries to e-mail each distinct contact in the call tree immediately, spending at most about 30 seconds on the attempt so a dead relay can't hang the person who clicked. Anything not sent in that window, or that fails, goes to the queue and is retried on a stretched schedule: 10 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 8 hours, 12 hours, then daily: nine queued attempts on top of the immediate one. That covers roughly 75 hours, so a mail outage has to outlast three days before a notice is given up. After that the notice shows as failed on the activation page, and a person with the activate permission can queue it again with **Retry Failed Notices** for as long as the activation is still open.

Some recipients are skipped rather than failed: a contact linked to a disabled SimpleRisk user, a contact with no usable e-mail address, and a contact deleted after the activation began. The activation log records which, without recording the address.

**Reminders.** A daily job sends reminders for:

- an exercise scheduled within the next 7 days, and one whose date has passed with no result recorded;
- a plan overdue for an exercise (see **Days between plan exercises** above);
- a plan whose review date is within 7 days or already past;
- a process whose BIA review is due on the same terms;
- a process whose RTO is not shorter than its MTD, which only happens with data that bypassed the form.

Plan reminders go to the plan's creator and the person who approved the version in force. Exercise reminders go to whoever scheduled it and to participants who are directory contacts. Process reminders go to the process owner. Retired plans remind nobody. No one is reminded about the same thing more than once per **Days between repeat reminders** (7 days unless you change it), and a changed due date starts the count again. The record of who was reminded is kept for at least 400 days after the last reminder and then cleared automatically; that never causes a repeat reminder, because it only removes entries older than any interval you can set.

Two operational consequences follow. If the queue worker is stopped, reminders stop silently, and queued notice retries wait. And because the worker has no logged-in user, retried notices and reminders go out in the instance's default language, not in the language of the person who declared the activation. The first immediate attempt does use the declaring user's language.

### 5. Decide on the AI capabilities

The Extra adds two cards to the Capabilities tab of the Artificial Intelligence page, under the **BCP/DR Extra** tier and the **Business Continuity** domain: **BCP/DR BIA Drafting** and **BCP/DR Plan Drafting**. Both are off by default. They show as locked until this Extra is active, and they need a configured AI provider. They do not need the AI Extra. See [Configuring AI Providers](https://support.simplerisk.com/kb/10-05-configuring-ai-providers?hsLang=en) for how to switch them on.

- **BIA Drafting** suggests MTD, RTO and RPO values, an impact rating and impact narratives for a business process.
- **Plan Drafting** suggests section text and recovery steps for an open plan draft.

What leaves your environment matters, because the drafting capabilities send a prompt to whichever provider you configured. The prompt carries process, asset, asset group, resource and plan names, ratings, durations, a process's description, and the plan type with its section skeleton. It never carries contact names, titles, phone numbers or e-mail addresses, process owners or teams, call trees, exercise findings, activation reasons, or the decrypted text of impact narratives and plan sections. Names and descriptions are still plain text in the prompt, so if a process name itself is sensitive, that is a reason to leave the capability off, or to point it at a local Ollama model.

Nothing an AI drafts is applied on its own. The output is stored as a pending suggestion, checked against a strict format (whole-minute durations, every RTO shorter than its MTD, no markup), and stays pending until someone holding the matching edit permission accepts or rejects it. There is at most one open suggestion per process or plan draft. Requests, acceptances and rejections are written to the audit trail.

### 6. Protect the encryption key

> **Availability of encryption.** The Extra is built to encrypt its sensitive text with Core encryption, whether or not the Encrypted Database Extra is active. Until Core encryption is part of your SimpleRisk release, the Extra stores that text as entered and the key-related behavior below does not apply. Check the release notes for the release that introduces Core encryption, and take the key backup described here from then on.

With Core encryption available, the following is encrypted:

- every contact detail: name, title, organization, e-mail address and phone numbers;
- the five impact narratives and the manual workaround of a process, and the description and contact notes of its other resources;
- plan section titles and bodies, recovery step titles and details, and the contact snapshot saved in the call tree;
- exercise summaries, finding titles and descriptions, and participant names;
- activation reasons and log notes, and the recipient labels on notices.

Not encrypted: process, plan and asset names, process descriptions, process owners and teams, ratings, dates, and the numeric BIA values, so they can be sorted and filtered.

If the encryption key is unavailable, three things happen. Saves that include encrypted text are refused with a message pointing at the Health Check page, rather than storing something blank. Values already stored show as **Unreadable** in the interface, and an edit that leaves the field alone keeps the stored value, so a missing key doesn't wipe data. And plan and BIA exports are refused outright, because a document with holes in it is worse than none.

Keep the encryption key directory in the same backup as the database. A database restore without the matching key leaves every encrypted value unreadable.

## Deactivating the Extra

> **Warning: deactivation deletes the data.** Clicking **Deactivate** drops every table the Extra owns and removes its seven permissions. All contacts, business processes and BIA values, plans and every version, exercises and findings, activations and their logs, control and risk links, and AI suggestions are gone, and they are not recovered by activating the Extra again. Risks that were opened from an exercise finding or a process stay, as ordinary risks, but lose the link back.
> 
> The seven permissions go with their assignments: every role and user that held one loses it, and after you activate the Extra again you grant them again. **Allow Access to Business Continuity and Disaster Recovery** is a Core permission, so it and its assignments stay; people who hold it see the locked overview until the Extra is active again. The Extra's settings are removed too (the RTO thresholds, the review cadence, the exercise cadence, the enabled plan types and the reminder schedule), along with notices and reminders still waiting in the queue, so a reactivated Extra starts from the defaults.

Take a database backup first. If you only want people to stop using it for a while, remove the **Allow Access to Business Continuity and Disaster Recovery** permission from their roles instead; they then see no **BCP / DR** entry at all. Export the business impact analysis and the approved plans before you deactivate for any reason; see [Continuity Plans, Versions and Approval](https://support.simplerisk.com/kb/11-03-continuity-plans?hsLang=en).

## Common pitfalls

- **Nobody can approve the first plan.** The approval rule excludes everyone who touched the version. Grant the approve permission to someone who won't be authoring plans.
- **Reminders arrive in the wrong language, or not at all.** Both trace back to the queue worker: it runs with the instance default language, and if it isn't running, nothing is sent.
- **Notices "failed" after a long mail outage.** The retry window is about three days. After that, use **Retry Failed Notices** on the activation page once mail is fixed, provided the activation hasn't been deactivated.
- **Thresholds changed, Availability report changed.** The Recovery Priority comparison uses the current thresholds each time it loads. It isn't a stored result.
- **Restoring a database onto a new server.** If the key directory didn't move with it, plan text and contact details show as Unreadable until it does.

## Related

- [Installing Extras](https://support.simplerisk.com/kb/01-06-installing-extras?hsLang=en)
- [Configuring AI Providers](https://support.simplerisk.com/kb/10-05-configuring-ai-providers?hsLang=en)
- [Troubleshooting Common Issues](https://support.simplerisk.com/kb/12-04-troubleshooting-common-issues?hsLang=en)
- [The Secure Controls Framework (SCF) Extra](https://support.simplerisk.com/kb/06-06-configuring-the-complianceforgescf-extra?hsLang=en)
- [Business continuity and disaster recovery, from policy to plan](https://support.simplerisk.com/kb/11-01-contingency-planning-in-simplerisk?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.