> 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/playbook-settings.md).

# Playbook settings

Click **Manage** on the **Business Continuity Playbook** page to open the **Playbook settings** window and configure how flow completeness is evaluated and how automatic export of playbook data is scheduled.

<figure><img src="/files/gXDSQYspWIc8ABT02jTJ" alt="" width="563"><figcaption></figcaption></figure>

#### Completeness criteria

The **completeness criteria** define the conditions under which a critical flow is considered fully complete (100%). Completion is determined by the configuration of required sections for each criticality level.

In the upper section of the window (**Completeness criteria**), a matrix is displayed with three criticality levels (**Low, Medium, and High**) and two configurable sections: **Business information** and **Contingency procedures**. Each checkbox allows you to specify whether a particular section is mandatory for flows belonging to a given criticality level.

This configuration directly impacts how completeness is computed. A flow is considered complete only if all the sections marked as required for its criticality level are properly filled in. If a required section is missing or incomplete, the overall completion percentage of the flow is reduced accordingly.

#### Schedule Playbook export

Playbook data can be **automatically exported** on a scheduled basis, ensuring that up-to-date information is available outside the platform when needed.

When automatic export is enabled, the execution time must be defined using the HH:mm format, representing the daily time at which the export process will run.

**Output and download**

Once the export is completed, the file becomes available in the **Exports panel** (top-right section) under the **Ready for download** tab.&#x20;

A list of generated files is displayed, each with:

* File name (e.g. criticalFlows\_2026-06-29\_...xlsx)
* File size
* Generation date and time

Click the **download icon** to retrieve the file locally.&#x20;

Each exported file contains multiple tabs organizing the playbook data:

* **Overview:** summary of exported data
* **Critical\_Flows**: list of all critical flows with their main attributes
* **Technical\_Configuration**: technical details related to integrations automatically sourced from **Data Watcher**
* **Scheduling**: cut-off information automatically sourced from **Data Watcher**
* **Contingency\_Scenario**: defined contingency scenarios
* **Contingency\_Steps**: detailed steps associated with each scenario

In the export file, each critical flow can be uniquely identified via **FLOW\_ID** and analyzed across all tabs, from business context to technical implementation and contingency procedures.

Files follow a standardized naming convention in the format: criticalFlows\_YYYY-MM-DD\_\<uniqueID>.xlsx.

Files are exported in the path configured in **Setup** → **System** → **Pencil icon** → **Export folder** field of the **System** window.&#x20;