> 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-related-plans.md).

# Execute Related Plans

Execute related plans, monitor completion, and submit them for closure.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Execute Related Plans

<i class="fa-user">:user:</i> **Performed By:** Plan Executor (e.g., Department Manager, Incident Manager, Business Continuity Coordinator)

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="danger" %}

#### How Related Plan Tasks Work

The **Execute Related Plans** subprocess creates a **Check Completion of the Plan** task for each related plan that is triggered. This task combines the functionality of the **Execute Plan** and **Check Completion of the Plan** tasks used for the primary plan, allowing you to both initiate the required activities and monitor their progress through completion.
{% endhint %}

***

## Accessing the Task <a href="#accessing-the-task" id="accessing-the-task"></a>

The **Check Completion of the Plan** task can be accessed through any of the following:

* The **To Do** module.
* The **direct link** provided in the email notification.

***

## Completing the Task <a href="#completing-the-task" id="completing-the-task"></a>

Execute the related plan and monitor its progress.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% 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 %}

{% hint style="info" %}

#### Saving Your Work

To save progress without submitting, click **Save** in the top-right corner of the panel.

* The task remains in the **To Do** module for you to revisit and complete later.
  {% endhint %}

***

{% stepper %}
{% step %}

### Execute Related Plan

Review the related plan and initiate the activities required for its execution.

Use the available sections to:

* Apply filters based on the incident context.
* Trigger any plans related to the current plan.
* Review relevant BIAs and notify process owners as needed.
* Select and initiate applicable actions.
* Initiate communication activities for the appropriate contact groups.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="info" %}
These sections function the same as in the [**Execute Plan**](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-plan.md) form for the primary plan, except that the following fields are automatically populated and cannot be changed:

* **Select the Plan to Execute**
* **Responsible**, for each contact group
  {% endhint %}

***

{% endstep %}

{% step %}

### Monitor Related Plan Completion

Monitor the execution of the related plan. Review the status of initiated related plans, actions, and communication tasks to confirm that all required activities are complete.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="info" %}
Progress is tracked in the same way as for the primary plan.

* For detailed instructions, see [**Check Completion of Plan**](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/check-completion-of-plan.md).
  {% endhint %}

***

{% endstep %}

{% step %}

### Submit Related Plan for Closure

From the **Task Resolution** dropdown, select **Submit**, then click **Submit.**

→ Next Step: [Sign Off & Document Lessons Learned](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/sign-off-and-document-lessons-learned.md)

{% hint style="warning" %}
As the related plan progresses through the **Execute Related Plans** subprocess, the **Related Plan Status** section in the primary plan’s **Check Completion of the Plan** form updates automatically to reflect its current stage, providing visibility from execution through final closure.
{% endhint %}

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tracking &#x26; Monitoring Executed Plans</strong></td><td>Browse and monitor operational plans throughout execution and closure.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNZOvD3ldHJ3i1zsvDksS%2FCR-V16-Icons-1.png?alt=media&amp;token=7c420cc4-9abf-4601-8fc3-8e9769771b27">App-V16-Icons-1.png</a></td><td><a href="/interfacing-help-files/business-continuity/executing-business-management-plans-apps/tracking-and-monitoring-executed-plans.md">Tracking &amp; Monitoring Executed Plans</a></td></tr></tbody></table>


---

# 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-related-plans.md?ask=<question>&goal=<endgoal>
```

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