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

# Export a Playbook

The **Playbook export** functionality allows you to generate and retrieve playbook data either on demand or automatically on a scheduled basis, ensuring flexibility and continuous data availability.

#### Manual export

Panorama supports two types of manual export:

1. **Export a single critical flow:** 
   * Open the three-dot menu associated with the desired flow 
   * Select **Export** to generate a file containing only the selected critical flow and all its related information.
2. **Export all critical flows:** 
   * Click the **Export** button available in the **Business Continuity Playbook** page toolbar. This action generates a file containing the current state of **all critical flows**, including completeness status, criticality level, business information, contingency procedures, and technical data. 

#### Automatic export

Automatic export can be configured from the [Playbook settings](/panorama-2.0.1/operational-resilience/business-continuity-playbook/playbook-settings.md#schedule-playbook-export) window and allows playbook data to be generated and saved on a recurring basis. 

When this option is enabled, exports are produced at the configured time, ensuring that the most up-to-date information is consistently available outside the platform without requiring manual intervention.

#### 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. 

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. 

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;