> 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/contact-critical-stakeholders.md).

# Contact Critical Stakeholders

Contact stakeholders in assigned contact groups.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Contact Critical Stakeholders

<i class="fa-user">:user:</i> **Performed By:** Communications Lead (e.g., Incident Manager, Communications 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 **Contacts** task can be accessed through any of the following:

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

{% hint style="danger" %}

#### Task Assignment by Contact Group

A separate task is created and assigned to the responsible party for each of the following contact groups:

* **Emergency Contacts**
* **Key Supplier and Customer Contacts**
* **External Emergency Contacts**
* **Regulatory Contacts**

If no responsible party is assigned to a contact group, no task is created for that group.
{% endhint %}

***

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

Reach out to the stakeholders in your assigned contact group.

You can review the operational plan for context as you work. Any filters applied when the plan was initiated remain in effect, keeping your task focused on what applies to the current incident.

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

### Contact Stakeholders

Reach out to the stakeholders in your assigned group using the provided contact information. If a communication strategy has been defined, use it to guide your outreach.

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

As you make contact with each stakeholder, select the corresponding **Contacted** checkbox.

{% hint style="info" %}

#### Managing Contact Selections

After making changes in the grid, you can:

* **Save Changes:** Click **Save Changes** or click outside the grid.
* **Discard Unsaved Changes:** Click **Discard Changes**.

When available, you can also:

* **Mark All as Contacted:** Click **Select All**.
* **Clear All Selections:** Click **Deselect All**.
  {% endhint %}

***

{% endstep %}

{% step %}

### Submit Contact Record

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

* Upon submission, the checkbox for the contact group is automatically selected 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, indicating the applicable status:
  * *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.*

{% hint style="danger" %}
You cannot submit this task until the **Contacted** checkbox is selected for each stakeholder in the group.
{% 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/contact-critical-stakeholders.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.