> 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/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-plan.md).
# Execute Plan
Coordinate and initiate the execution of an operational plan through the Plan Execution & Closure workflow.
## Workflow Overview
:location-dot: **Current Task:** Execute Plan
:user: **Performed By:** Plan Executor (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)
IMAGE
***
## Completing the Form
Use one of the following forms to initiate the execution of an approved and active operational plan:
* **Execute Business Continuity Plan**
* **Execute Crisis Management Plan**
* **Execute Disaster Recovery Plan**
IMAGE
{% hint style="danger" %}
#### Workflow Triggers
Throughout this form, the following buttons initiate activities within the **Plan Execution & Closure** workflow:
* **Trigger Related Plans**
Initiates the execution of plans associated with the selected plan.
→ See: [Execute Related Plans](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-related-plans.md)
* **Notify the Process Owners**
Sends email notifications to the owners of impacted business processes.
* **Start Action Items**
Initiates the execution of selected actions.
→ See: [Execute Action(s)](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-action-s.md)
* **Initiate Contact**
Initiate communication with each contact group through its designated responsible party.
→ See: [Contact Critical Stakeholders](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/contact-critical-stakeholders.md)
{% endhint %}
{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}
***
{% stepper %}
{% step %}
### Select Plan & Configure Execution
Select the operational plan to execute and apply the appropriate filters to define the incident context.
{% hint style="info" %}
These selections determine the information, actions, and contacts displayed throughout the form.
{% endhint %}
IMAGE
* **Select the Plan to Execute:** Select the BC, CM, or DR plan to execute.
* Instead of a dropdown menu, this field opens a form.
* Double-click a plan to select it. The form will close automatically, and the plan will populate the field.
Only approved and active plans are available for selection.
This selection filters the following areas:
- Asset List
- BIA List
- Action List
- Emergency Contact List
This selection filters:
- BIA List (Note: Disasters marked as No Impact in the BIA will not be included)
- Action List
- Emergency Contact List
IMAGE
* **Plan Overview:** Review the high-level summary of the selected plan.
* **Document and Plan References:** Use the available grids to review the assets, documents, and plans associated with the selected plan.
* **Assets:** All critical assets associated with the selected plan.
Assets are filtered based on sites selected in the Site dropdown.
To view the document, click its hyperlink in the Documentation URL column.
These related plans are organized into two grids based on the type of plan being executed:
For a Business Continuity Plan (BCP):
- Related Disaster Recovery Plans
- Related Crisis Management Plans
For a Disaster Recovery Plan (DRP):
- Related Business Continuity Plans
- Related Crisis Management Plans
For a Crisis Management Plan (CMP):
- Related Business Continuity Plans
- Related Disaster Recovery Plans
Plans that are directly linked to the selected plan or associated through another plan will automatically populate in the appropriate grid.
IMAGE
* **Notify the Process Owners:** Click to notify the owners of impacted business processes.
* A confirmation message will appear, displaying the total number of email notifications sent.
* Each email includes:
* The impacted business process.
* The workaround documented [in the BIA](/interfacing-help-files/business-continuity/managing-business-impact-analyses-apps/creating-and-managing-bias/complete-bia.md#assess-alternative-workarounds) to support operational continuity until recovery.
{% hint style="danger" %}
Notifications are only sent for BIAs currently visible in the grid. If a BIA is filtered out, its process owners will not be notified.
{% endhint %}
***
{% endstep %}
{% step %}
### Select Actions for Execution
Review all active and approved actions related to the selected incident context. Select the actions to initiate or add new actions based on real-time needs.
{% hint style="info" %}
After selecting a plan, this section remains empty until filters are applied based on one or more of the following:
* **Site:** As selected in the **Site** dropdown.
* **Disaster Type:** As selected in the **Disaster** dropdown.
* **Threat Vectors:** As selected in the **Disaster Threat Vectors** dropdown.
{% endhint %}
IMAGE
{% hint style="success" %}
#### Selecting Actions for Execution
* **Select Actions:** Check the **Selected** box for each action to execute.
* **Save Selections:** Click **Save Changes** or click outside the grid.
* **Clear Selections:** Click **Discard Changes**.
{% endhint %}
Click **Add** to create a new action for the plan.
Execute – New Action Item
The **Execute - New Action Item** form allows you to create new actions for execution.
{% hint style="warning" %}
This form is a customized version of the **New Action Item** form from the **Action Item Management** module. It retains nearly all the original fields and functionality, but is adapted to fit the selected plan and its execution needs.
{% endhint %}
**Key Differences:**
* **Type:** Automatically populated based on the selected plan type (non-editable).
* **BCP** – Business Continuity
* **DRP** – Disaster Recovery
* **CMP** – Crisis Management
* **Save Options:** Replace the standard submission process, allowing users to save progress.
* **Save and New**: Click to save the action and open a new form to create another.
* **Save and Close**: Click to save the action and close the form.
{% hint style="success" %}
For guidance on shared fields and functionality, refer to the [documentation for the **New Action Item** form](/interfacing-help-files/business-continuity/managing-action-items-apps/creating-and-managing-action-items/create-new-action-item.md).
{% endhint %}
**Start Action Items:** Click to initiate the execution of all selected actions.
* A confirmation message will appear, displaying the total number of actions initiated.
* Each action will be assigned to its designated owner.
{% hint style="info" %}
Once initiated, the **Is Started** checkbox will be automatically selected for each corresponding action in the [Check Completion of the Plan](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/check-completion-of-plan.md) form.
{% endhint %}
***
{% endstep %}
{% step %}
### Initiate Communication Strategy
Review the communication strategy and assign or verify the responsible parties for each activity. Initiate communications with the required contact groups.
{% hint style="info" %}
This section is initially empty but automatically populates with relevant information once a plan is selected.
{% endhint %}
IMAGE
* **Responsible:** Review or update the user or role responsible for each contact group.
{% hint style="info" %}
Responsibilities can be assigned for:
* **Emergency Contacts**
* Emergency Contacts are filtered based on:
* **Site:** As selected in the **Site** dropdown.
* **Disaster Type:** As selected in the **Disaster** dropdown.
* **Key Supplier and Customer Contacts**
* **External Emergency Contacts**
* **Regulatory Contacts**
{% endhint %}
* **Initiate Contact:** A button to initiate communication with the specified contact groups.
* A confirmation label will appear, indicating that the communication tasks have been assigned to the designated responsible parties.
{% hint style="danger" %}
If no responsible party is assigned to a contact group, no task is created for that group.
{% endhint %}
***
{% endstep %}
{% step %}
### Submit Plan for Execution
After addressing all sections and triggering the necessary tasks, click **Submit** to begin the **Plan Execution & Closure** workflow.
* The [next task](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/check-completion-of-plan.md) provides ongoing visibility into the status of actions, communications, and overall plan completion.
***
{% endstep %}
{% endstepper %}
***
## See Also
---
# 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/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-plan.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.
