> 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/operational-resilience/business-continuity-playbook/open-a-critical-flow/define-contingency-procedures.md).
# Define contingency procedures
The **Contingency procedures** tab allows you to define and manage the procedures required to handle operational disruptions for the selected critical flow.
This section provides a structured way to document **fallback actions** and ensure that the flow can be executed or recovered even in case of system failures.
The tab displays a list of configured contingency scenarios with the following information:
* **Contingency scenario:** Name of the scenario
* **Required inputs:** Information needed to execute the procedure
* **Number of steps:** Total steps defined for the scenario
* **Validation:** Criteria used to verify successful execution
If no procedures are defined, the table shows *No data*.
To create a new procedure, click **New**.
#### Create a Contingency scenario
Clicking **New** opens the **New Contingency scenario** window, where you can define a complete recovery procedure. Contingency procedures allow you to standardize recovery actions and provide clear operational guidance during incidents. As procedures are defined, they contribute to the **completeness status** of the critical flow.
This step is required if the **Contingency procedures** section has been set as mandatory in the **Playbook settings** window.
**General Information**
At the top of the form, you can define:
* **Contingency scenario** **(\*):** a name that identifies the specific recovery scenario.
* **Objective:** A description of the goal of the procedure (up to 2000 characters).
* **Required inputs:** Information, prerequisites, or data needed to execute the procedure (up to 2000 characters).
**Procedure steps**
Each contingency scenario is composed of one or more steps that describe the actions to perform.
For each step, you can define:
* **Title** **(\*):** A short name describing the step.
* **Description:** Detailed instructions for executing the step (up to 2000 characters).
* **Reference:** Links, documents, or identifiers related to the step.
* **Expected outcome:** The result that should be achieved after completing the step.
* **Alternative path:** Optional fallback instructions if the primary step cannot be completed.
Use the **Add Step** button to include additional steps in the procedure.
**Validation**
At the end of the scenario, you can define a **Validation** section, where you describe how to verify that the procedure has been successfully executed (up to 2000 characters).
Click **Confirm** to add the **Contingency procedure** to the table.
#### Contingency scenario Details window
From the **Contingency procedures** table, each scenario can be opened in a dedicated detail view by selecting **Details** from the contextual menu.
This action opens the **Contingency scenario – Details** window, which provides a complete, read-only overview of the selected procedure.
