> 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/check-completion-of-plan.md).

# Check Completion of Plan

Oversee plan execution by tracking the progress and completion of its initiated activities.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Check Completion of Plan

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

***

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

Monitor the execution of the plan, tracking its initiated activities through to completion.

{% hint style="warning" %}
To view the latest status of related plans, actions, and communications, exit and reopen the form.
{% endhint %}

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

### Monitor Related Plans

Under **Related Plan Status**, use the **Status** column in each grid to track the progress of the initiated plans:

* **Check Completion of the Plan:** The plan is being executed and monitored for completion.
* **Sign-Off and Lessons Learned:** The plan is undergoing final review before closure.
* **Execute Plan Closed:** The plan has been successfully executed and closed.

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

***

{% endstep %}

{% step %}

### Monitor Actions

Use the **Started** and **Completed** columns in the grid to track the status of each action:

* **Started:** The action has been initiated using the **Start Action Items** button.
* **Completed:** The action has been executed and closed.

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

{% hint style="success" %}

#### Initiating Additional Actions for Execution

You can initiate additional actions as needed to support response and recovery.

* To appear in the grid, actions must meet the filter criteria applied when the plan was initiated.

For guidance on managing actions for execution, refer to the [relevant section](/interfacing-help-files/business-continuity/executing-business-management-plans-apps/initiating-and-managing-plan-executions/execute-plan.md#select-actions-for-execution) in **Execute Plan**.
{% endhint %}

***

{% endstep %}

{% step %}

### Monitor Communications

Use the checkboxes to track whether outreach has been completed for the assigned contact groups:

* *All emergency contacts have been contacted.*
* *All key supplier and customer contacts have been contacted.*
* *All external emergency contacts have been contacted.*
* *All regulatory contacts have been contacted.*

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

{% hint style="danger" %}
Communication tasks are created only for contact groups with an assigned responsible party.
{% endhint %}

***

{% endstep %}

{% step %}

### Submit 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)

***

{% 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/check-completion-of-plan.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.