> For the complete documentation index, see [llms.txt](https://docs.primeur.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primeur.com/panorama-2.0.1/operational-resilience/business-continuity-playbook/overview/using-the-business-continuity-playbook.md).

# Using the Business Continuity Playbook

This page describes the main steps required to configure flows, define business and technical information, and set up contingency procedures, up to the final export of a complete playbook.

{% hint style="success" %}
**Important:** Flow completeness depends on the configuration defined in the **Playbook settings** window.\
Depending on this configuration, some sections (for example Business information or Contingency procedures) may be mandatory or optional.
{% endhint %}

#### Step 1 – Import and identify critical flows

* Click the **Add** button to import modeled flows from **Data Watcher**
* Each imported flow is assigned a **FLOW\_ID** and an initial technical configuration

See [Add critical flows](/panorama-2.0.1/operational-resilience/business-continuity-playbook/add-critical-flows.md). 

#### Step 2 – Configure completeness rules (Playbook settings)

Before completing the flows, you can define which sections are required:

* Click the **Manage** button on the page toolbar
* In the **Playbook settings** window, select which tabs or fields are **mandatory for flow completion** (Business information and/or Contingency procedures)

These settings determine how completeness is evaluated in the following steps.

See [Playbook settings](/panorama-2.0.1/operational-resilience/business-continuity-playbook/playbook-settings.md). 

#### Step 3 – Complete information

Depending on the configuration defined in the **Playbook settings** window, complete the relevant fields.

In the available tabs, you can define:

* Description and purpose
* Criticality level
* Business and technical owners
* Operational notes and attributes

Only the fields marked as mandatory in the **Playbook settings** window are required for completion.

See [Configure business information](/panorama-2.0.1/operational-resilience/business-continuity-playbook/open-a-critical-flow/configure-business-information.md).

#### Step 4 – Define contingency procedures

In the **Contingency procedures tab**:

* Create one or more **contingency scenarios**
* Define:
  * Objective
  * Required inputs
  * Step-by-step actions
  * Expected outcomes

This step is required if the **Contingency procedures** section has been set as mandatory in the **Playbook settings** window.

See [Define contingency procedures](/panorama-2.0.1/operational-resilience/business-continuity-playbook/open-a-critical-flow/define-contingency-procedures.md).

#### Step 5 – Ensure completeness

A flow is considered complete when all the fields and sections marked as **mandatory** in the **Playbook settings** window are filled.

#### Step 6 – (Optional) Synchronize technical data

* Use **Data Watcher sync** to align fields
* Updates are applied **in the background** and reflected in exports

See [Data Watcher synchronization](/panorama-2.0.1/operational-resilience/business-continuity-playbook/data-watcher-synchronization.md). 

#### Step 7 – Export the Business Continuity Playbook

You can:

* Export a **single flow** (from contextual menu)
* Export **all flows** (toolbar Export button)
* Schedule **automatic daily exports**

The exported file provides a **complete and structured dataset**: it contains multiple tabs (Overview, Critical\_Flows, Technical\_Configuration, etc.) where data are linked by their **FLOW\_ID**. 

See [Export a Playbook](/panorama-2.0.1/operational-resilience/business-continuity-playbook/export-a-playbook.md).