> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/business-continuity/simulating-business-management-plans-apps/running-and-managing-plan-simulations.md).
# Running & Managing Plan Simulations
Perform tasks assigned to your role to advance plans through the Plan Simulation & Validation workflow.
## Workflow Overview
The **Plan Simulation & Validation** workflow governs the planning, execution, review, and validation of Business Continuity Plans (BCPs), Disaster Recovery Plans (DRPs), and Crisis Management Plans (CMPs).
***
## Interactive Tour
Explore the **Plan Simulation & Validation** workflow and learn how each stage works, with key guidance and best practices along the way.
***
## Workflow Stages
The workflow is organized into **six key stages**, each with specific roles and responsibilities.
{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}
{% stepper %}
{% step %}
### Simulate Plan
> **Performed By:** Plan Simulator (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)
**Responsibilities**:
* Select an approved and active operational plan to simulate.
* Apply filters to tailor the plan to the simulation scenario.
* Initiate required activities, as applicable:
* Initiate related operational plans for simulation.
* Notify owners of business processes included in the simulation.
* Initiate actions required to be performed as part of the simulation.
* Initiate communication with required contact groups through the designated responsible parties.
* Submit the plan to initiate the workflow.
***
{% endstep %}
{% step %}
### Execute Related Plans
> **Performed By:** Plan Simulator (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)
This stage includes the **Related Plan Execution & Closure** subprocess, which manages the execution, monitoring, and closure of operational plans associated with the primary plan.
**Responsibilities**:
* Review the related plan and apply filters based on the simulation scenario.
* Initiate required activities, as applicable:
* Initiate additional related plans for simulation.
* Notify owners of business processes included in the simulation.
* Initiate actions to be performed as part of the simulation.
* Initiate communication with required contact groups.
* Monitor initiated activities through to completion.
* Once all required activities are complete, submit the related plan for [final sign-off and closure](#sign-off-and-document-lessons-learned).
{% hint style="warning" %}
This stage is triggered only if related plans are initiated during simulation of the primary plan.
{% endhint %}
***
{% endstep %}
{% step %}
### Execute Action(s)
> **Performed By:** Assigned Action Owners
This stage includes the **Action Execution & Closure** subprocess, which manages the execution and closure of actions initiated as part of the simulation.
**Responsibilities**:
* Carry out the assigned action according to instructions.
* If applicable, complete the assigned checklist, ensuring that all items satisfy any required status constraints.
* Document the action outcome, including simulation performance, key findings, and lessons learned.
* Submit the completed action.
{% hint style="warning" %}
This stage is triggered only if selected actions are initiated during plan simulation.
{% endhint %}
***
{% endstep %}
{% step %}
### Contact Critical Stakeholders
> **Performed By:** Communications Lead (e.g., Incident Manager, Communications Manager, Business Continuity Coordinator)
This stage includes the **Stakeholder Communication** subprocess, which coordinates outreach to the required contact groups as part of the simulation.
**Responsibilities**:
* Review the assigned contact group and applicable communication strategy.
* Contact each stakeholder in the group and confirm completion of the outreach.
* Submit the contact record.
{% hint style="danger" %}
If no responsible party is assigned to a contact group, no task is created for that group.
{% endhint %}
***
{% endstep %}
{% step %}
### Check Completion of Plan
> **Performed By:** Plan Simulator (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)
**Responsibilities**:
* Monitor initiated activities (related plans, actions, communications) through to completion.
* Initiate additional actions as needed.
* Once all required simulation activities are complete, submit the plan for final sign-off and closure.
***
{% endstep %}
{% step %}
### Sign Off & Document Lessons Learned
> **Performed By:** Plan Simulator (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)
**Responsibilities**:
* Review the completed plan simulation and assess overall performance.
* Document the total time required to recover from the disruption.
* Document key insights and improvement opportunities to strengthen the plan and future simulations.
* Sign off and close the simulated plan to conclude the workflow.
***
{% endstep %}
{% endstepper %}
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://interfacing.gitbook.io/interfacing-help-files/business-continuity/simulating-business-management-plans-apps/running-and-managing-plan-simulations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
