> 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-implementation.md).

# Review Implementation

Review completed implementation activities, confirm the change was successful, and approve or reject the outcome.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Review Implementation

<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%2FCoUr7EYJoWZExoINxRRA%2FCR-V16-Workflow-Guide-5.png?alt=media&amp;token=c5dd901b-3735-4514-9a66-80cf130d76a3" alt=""><figcaption></figcaption></figure>

***

## Accessing the Task

The **Review Implementation** 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 the change request is implemented, assess whether the implementation was successful and met the intended objectives.

{% hint style="warning" %}
If the implementation plan includes specific tasks or actions, this step will only be triggered once all items are completed, reviewed, and approved.
{% 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 %}

### Assess Implementation of Plan

Review the implementation plan for the change request and evaluate its execution against the defined components. Confirm the following, where applicable:

* All planned steps were completed as outlined.
* Resources were used appropriately.
* Required training was delivered.
* Change verification was performed as specified.

#### 1.1 Action Items

Expand the **Action Items** section to review completed actions. Assess whether each item meets the intended objectives and criteria.

* To **approve** an action, check the corresponding **Approve** box.
* To **reject**, check the corresponding **Reject** box.

{% hint style="info" %}
Click **Save Changes** to apply selections or click outside the grid to save automatically. To undo, click **Discard Changes**.
{% endhint %}

#### 1.2 Task Items

Expand the **Task Items** section to review completed tasks. Assess whether each item meets the intended objectives and criteria.

* To **approve** a task, check the corresponding **Approve** box.
* To **reject**, check the corresponding **Reject** box.

{% hint style="info" %}
Click **Save Changes** to apply selections or click outside the grid to save automatically. To undo, click **Discard Changes**.
{% endhint %}

{% hint style="warning" %}
In the grid, the **Times Rejected** figure indicates the number of times an action or task item has been rejected.

* If an item is executed only once, this field will remain blank.
* If an item is rejected at the [execution phase](/interfacing-help-files/end-users/change-request-application/navigating-the-change-request-management-workflow/implement-the-plan.md) or sent for re-execution in this form, however, the number will increase by 1.

Users can re-execute an item however many times they deem necessary.
{% endhint %}

***

{% endstep %}

{% step %}

### Document Lessons Learned

Capture key takeaways, insights, or notable outcomes from the implementation. These notes can help improve future planning and execution.

***

{% endstep %}

{% step %}

### Provide Feedback

Use the **Comments** field to share feedback, ask questions, or provide clarification. If you are rejecting an item, be specific about expectations or the changes required for re-execution.

{% hint style="info" %}

#### Commenting Guidelines

* You can **edit**, **delete**, or **reply** to your own comments.
* You may **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:

* **Reject Action(s) and Task(s)**

  Return the rejected items to their owners for re-execution.

  → 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" %}
At least one item must be marked as rejected to use this option. Providing a reason in the **Comments** field is recommended.
{% endhint %}

* **Approve Change Request**

  Approve the change request, confirming that the implementation is complete and satisfactory.

  * This action concludes the **Change Request Management** workflow.

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>


---

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