> 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/end-users/change-request-application/navigating-the-change-request-management-workflow/implement-the-plan.md).

# Implement the Plan

Carry out assigned actions or tasks to implement the change request.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i>  **Current Task:** Implement the Plan

<i class="fa-user">:user:</i>  **Performed By:** Assigned Action/Task Owners

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FUWWO22GGLSBABuiY4tZ8%2FCR-V16-Workflow-Guide-4.png?alt=media&amp;token=e25d6714-d181-4d86-acf5-8ccf1d76c1eb" alt=""><figcaption></figcaption></figure>

***

## Accessing the Tasks

Both the **Execute the Action** and **Execute the Task** forms can be accessed via:

* The **To Do** module.
* The **Notification Panel** (via the **Notification Bell**).
* The **direct link** provided in the email notification.

***

## Completing the Tasks

After the change request is submitted for implementation, execute the assigned actions or tasks.

{% hint style="warning" %}
If an action item involves a **Supplier Corrective Action Request** (**SCAR**), the standard execution will be bypassed. Instead, the supplier representative will be notified to investigate and address the SCAR.
{% endhint %}

{% hint style="danger" %}
If no actions or tasks are defined in the implementation plan, this step is automatically skipped.
{% endhint %}

{% hint style="info" %}

#### Task Notifications

For the **Execute the Action** task, notification behavior depends on the owner's classification.

* **Internal Owners** receive both system and email notifications.
* **External or Supplier Owners** receive email notifications only.
  {% endhint %}

***

Below is a high-level overview of steps required to complete the **Execute the Action** and **Execute the Task** forms.

{% hint style="success" %}
For a detailed guide on executing an action or task, refer to the topics in the [**See Also**](#see-also) section.
{% endhint %}

{% stepper %}
{% step %}

### Accept or Reject Assignment

Review the details of the assigned action or task.&#x20;

* **Accept the assignment** if the scope and requirements are understood.
  * To accept, simply proceed with execution.
* **Reject the assignment** if further clarification or reassignment is needed.
  * To reject, select **Refuse Action** or **Refuse Task** in the **Task Resolution** dropdown, then click **Submit**.

***

{% endstep %}

{% step %}

### Document Observations & Outcomes

Document key observations, challenges encountered, and outcomes achieved during execution. Upload any relevant supporting files or documentation.

***

{% endstep %}

{% step %}

### Submit the Action or Task

After completing execution and providing feedback, select **Action Complete** or **Task Complete** in the **Task Resolution** dropdown, then click **Submit**.

* The item will be routed to the designated reviewer:
  * If **approved**, the subprocess concludes.
  * If **rejected**, the item is returned to the owner for re-execution.
    * This cycle continues until the item is approved.

{% hint style="danger" %}
In the **Change Request Management** workflow, **Action Item Management**, **Task Management**, and **SCAR Management** (where applicable) serve as integrated subprocesses.&#x20;

* For the change request to proceed, all related subprocesses—action items, tasks, and SCARs—must be completed, reviewed, and approved.
  {% 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>How to Execute an Action</strong></td><td>Follow instructions to execute the assigned action effectively.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNEKOaMQapgwlVPppSzip%2FIMS-V16-Apps-Overview-1.png?alt=media&amp;token=0cc2aab3-7135-4e81-86fd-af7eff29f414">IMS-V16-Apps-Overview-1.png</a></td><td><a href="/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-action-items/execute-action.md">Execute Action</a></td></tr><tr><td><strong>How to Execute a Task</strong></td><td>Follow instructions to execute the assigned task effectively.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F1e7q5l4hSQv1iK0NTuK5%2FIMS-V16-NAV-Library-Icons-76.png?alt=media&amp;token=00d79dcd-a572-48f6-a6cb-ebc91a64a748">IMS-V16-NAV-Library-Icons-76.png</a></td><td><a href="/interfacing-help-files/quality-managers/task-management-application/creating-and-managing-tasks/execute-task.md">Execute Task</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/end-users/change-request-application/navigating-the-change-request-management-workflow/implement-the-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.