> 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/review-and-plan-change-request.md).

# Review & Plan Change Request

Review a submitted change request, define an implementation plan, and determine the next steps.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Review & Plan Change Request

<i class="fa-user">:user:</i> **Performed By:** Assigned Reviewer (e.g., Department Manager, Quality Assurance Lead, Compliance Officer)

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FK91OmESSnUfCIfuN8CQA%2FCR-V16-Workflow-Guide-2.png?alt=media&amp;token=7ed0ff2c-8fcd-413f-b82e-4b50814e2a5b" alt=""><figcaption></figcaption></figure>

***

## Accessing the Task

The **Review & Plan Change Request** task can be accessed through any of the following:

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

***

## Completing the Task

After a change request is submitted, evaluate its content and prepare an implementation plan.

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

### Review Change Request

Review the change request to verify key information and identify any issues, considering:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>✅ <strong>Clarity</strong></td><td>Is the purpose, scope, and context of the change clearly stated?</td></tr><tr><td>✅ <strong>Justification</strong></td><td>Does the request provide a valid reason for the change?</td></tr><tr><td>✅ <strong>Impact &#x26; Risk</strong></td><td>Are potential impacts or risks identified and addressed?</td></tr><tr><td>✅ <strong>Compliance</strong></td><td>Does the request align with organizational policies, standards, or procedures?</td></tr></tbody></table>

{% hint style="info" %}
This task uses a form similar in layout and content to the **New Change Request** form.

* For instructions on how to complete each field, refer to the [corresponding form documentation](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/create-new-change-request.md).
  {% endhint %}

{% hint style="success" %}
**Tip:** Use the **Comments** field to provide feedback, ask questions, or request additional details (see [Section 3](#id-3.-provide-feedback)).
{% endhint %}

***

{% endstep %}

{% step %}

### Define Implementation Plan

After review, develop a plan for implementing the change.

#### 2.1 Key Components

* **Steps to Implement:** Outline the key activities required to carry out the change.
* **Required Resources:** Identify the personnel, tools, or materials needed to support implementation.
* **Training Requirements:** Specify any required training or onboarding for team members involved in the implementation.
* **Verification of Change:** Define how you will confirm or validate the success of the change.

#### 2.2 Action Items

Define the specific actions required for implementation.

{% hint style="info" %}
An **action item** is a significant, outcome-driven activity created to address a specific issue, risk, deviation, or improvement identified in the change request. It is corrective, preventive, or improvement-focused and is expected to have a measurable impact on quality, compliance, or risk reduction.
{% endhint %}

Click **Add** to to create a new action item.

<details>

<summary><mark style="color:blue;"><strong>Add Action Item</strong></mark></summary>

The **Add Action Item** form allows you to create actions as part of the implementation plan.

{% hint style="warning" %}
This form is a modal version of the standard **New Action** form found in the **Action Items** application. It retains nearly all the original fields and functionality, but is adapted to fit the context of the current application.
{% endhint %}

**Key Differences:**

* **Source of the Action:** This field is automatically populated based on the current application context and cannot be modified.
  * For example, in this case, the source is set to **Change Request**.
* At the bottom of the form, you can choose from the following save options:
  * **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** form](/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-action-items/create-new-action.md).
{% endhint %}

</details>

Added entries appear in the grid with the following options:

* [**Edit**](#user-content-fn-1)[^1] ( <i class="fa-pencil">:pencil:</i> ): Click to modify an action.
* **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ): Click to open an action in read-only mode.
* **Delete** ( <i class="fa-trash-can">:trash-can:</i> ): Click to remove an action.

{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undelete** ( <i class="fa-xmark">:xmark:</i> ).
{% endhint %}

#### 2.3 Task Items

Define the specific tasks required for implementation.

{% hint style="info" %}
A **task** is a smaller, routine, or administrative activity that supports the implementation of the change. It is generally operational in nature and does not represent corrective or preventive actions.
{% endhint %}

Click **Add** to create a new task item, click **Add**.

<details>

<summary><mark style="color:blue;"><strong>Add Task Item</strong></mark></summary>

The **Add Task Item** form allows you to create tasks as part of the implementation plan.

{% hint style="warning" %}
This form is a modal version of the standard **New Task** form found in the **Task Management** application. It retains nearly all the original fields and functionality, but is adapted to fit the context of the current application.
{% endhint %}

**Key Difference:**

* At the bottom of the form, you can choose from the following save options:
  * **Save and New:** Click to save the current task and open a new form to create another.
  * **Save and Close:** Click to save the task and close the form.

{% hint style="success" %}
For guidance on shared fields and functionality, refer to the [documentation for the **New Task** form](/interfacing-help-files/quality-managers/task-management-application/creating-and-managing-tasks/create-new-task.md).
{% endhint %}

</details>

Added entries appear in the grid with the following options:

* [**Edit**](#user-content-fn-1)[^1] ( <i class="fa-pencil">:pencil:</i> ): Click to modify a task.
* **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ): Click to open a task in read-only mode.
* **Delete** ( <i class="fa-trash-can">:trash-can:</i> ): Click to remove a task.

{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undelete** ( <i class="fa-xmark">:xmark:</i> ).
{% endhint %}

{% hint style="warning" %}

#### Impact of Actions & Tasks on Workflow

If defined, actions and tasks are formally tracked through the workflow, assigned to responsible owners, and require completion and approval before the change can be considered fully implemented.
{% endhint %}

***

{% endstep %}

{% step %}

### Provide Feedback

Use the **Comments** field to share feedback, ask questions, or collaborate with others. Comments remain visible throughout the workflow for transparency and communication.

{% hint style="info" %}

#### Commenting Guidelines

* You can **edit**, **delete**, or **reply** to your own comments.
* You can **reply** to others' comments but cannot edit or delete them.
  {% endhint %}

***

{% endstep %}

{% step %}

### Finalize Review

From the **Task Resolution** dropdown, select one of the following actions:

* **Needs Modification**

  Return the change request to its creator for [revisions or additional information](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/modify-change-request.md).

  → Next Step: [Modify Change Request](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/modify-change-request.md)

{% hint style="info" %}
Once changes are made, the creator can resubmit the request for further review.
{% endhint %}

* **Send for Implementation**

  Approve the request and advance it to the implementation stage.

  → Next Step: [Implement the Plan](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/implement-the-plan.md)

{% hint style="warning" %}

#### How Implementation Proceeds

Depending on the implementation plan, one of the following will occur:

* If **tasks or actions** are defined, they will be assigned to their respective owners for [execution](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/implement-the-plan.md).
  * Once all items are completed and approved, the reviewer will [verify the implementation](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/review-implementation.md).
* If **no tasks or actions** are defined, implementation is assumed to proceed without individual task tracking.
  * In this case, the reviewer will proceed directly to [validating that the implementation meets requirements](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/review-implementation.md).
    {% endhint %}

After selecting the appropriate resolution, click **Submit** to finalize your review and advance the workflow.

***

{% 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 Change Requests</strong></td><td>Monitor the status and progress of change requests using lists and dashboards.</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/end-users/change-request-application/tracking-and-monitoring-change-requests.md">Tracking &amp; Monitoring Change Requests</a></td></tr></tbody></table>

[^1]: You can also **double-click** the row to edit quickly.


---

# 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/review-and-plan-change-request.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.