> 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/to-do/completing-tasks/completing-change-request-tasks.md).

# Completing Change Request Tasks

Change Request tasks ensure that updates are properly reviewed and, when approved, implemented in the system.

Depending on the workflow stage, you may be assigned to either **review a change request** or **implement an approved change**. While both tasks follow a similar structure, the actions you take differ based on your role in the lifecycle.

By completing these tasks, you help ensure that changes are accurately assessed, applied, and ready for the next step.

***

## CR to Review Task

Learn how to review a Change Request and decide if it should move forward in the workflow.

{% @howdygo/embed url="<https://app.howdygo.com/share/e5785a35-12a8-4809-b6b5-9c8baddd644e>" fullWidth="true" %}

***

{% stepper %}
{% step %}

### Accessing a CR to Review Task

In **To Do**, select a **CR to Review** task in the list.&#x20;

* Review the documentation by minimizing the submission banner.

{% hint style="info" %}
For more guidance on using To Do, [see this section.](/interfacing-help-files/end-users/to-do.md)
{% endhint %}
{% endstep %}

{% step %}

### Bulk or Individual Review

CRs are grouped by object into a single task. You can process them in two ways:

#### Review a Single CR&#x20;

* Click on a CR to open it
* Review the form and update fields if needed
* Add a **Comment** explaining your decision
* (Optional) Attach a file
* Click **Approve** or **Reject**

{% hint style="info" %}
Click **Approve** to move the request to the implementation stage.

Click **Reject** if the proposed changes should not be implemented.
{% endhint %}

***

#### Review Multiple CRs

* Use the **checkboxes** to select multiple CRs
* Click **Approve** or **Reject**

{% hint style="warning" %}
**Notes:**

* No form fields can be edited in bulk
* The same decision (approved or rejected) is applied to all selected CRs
* Unselected CRs remain in To Do.
  {% endhint %}
  {% endstep %}
  {% endstepper %}

***

## CR to Implement Task

See how to confirm that approved changes have been implemented, or delegate the implementation if needed.

{% @howdygo/embed url="<https://app.howdygo.com/share/3b0930f4-fb33-4822-9e85-3ee9f80a232b>" fullWidth="true" %}

***

{% stepper %}
{% step %}

### Accessing a CR to Implement Task

In **To Do**, select a **CR to Implement** task in the list.

* Review the documentation by minimizing the submission banner.

{% hint style="info" %}
For more guidance on using To Do, [see this section.](/interfacing-help-files/end-users/to-do.md)
{% endhint %}
{% endstep %}

{% step %}

### Opening & Reading the CR

CRs are grouped by object into a single task.&#x20;

* Select the desired CR to view details.
* Read the **Description** and **Reviewer’s Note** for implementation instructions.
  {% endstep %}

{% step %}

### Delegating a CR to Implement Task <a href="#delegating-an-approval-task" id="delegating-an-approval-task"></a>

If you feel someone else is better suited to complete the task:

* Click on the **Delegate** button.
* Select a colleague from the list
  * Use the **Filter** box to search.
* Click **Delegate**

The task is transferred to the selected colleague.
{% endstep %}

{% step %}

### Implementing the Requested Changes

* [Switch to **EPC**](/interfacing-help-files/getting-started/switching-between-epc-and-the-new-experience.md) to update the item(s) as requested in the CR(s).
* Once the updates are complete, return to the task in IMS.
  {% endstep %}

{% step %}

### Marking CRs as Implemented

You can mark CRs as implemented in two ways:

#### Mark a Single CR as Implemented

* Click on a CR to open it
* Add a **Comment** confirming the implementation
* Click **Mark as implemented** or **Reject**

{% hint style="info" %}
Choose **Mark as Implemented** once the changes have been successfully applied.

Choose **Reject** if the implementation cannot be completed as requested.
{% endhint %}

***

#### Mark Multiple CRs as Implemented

* Use the **checkboxes** to select multiple CRs
* Click **Mark as implemented** or **Reject**

{% hint style="warning" %}
**Notes:**

* No individual comments can be added in bulk
* The same decision (marked as implemented or rejected) is applied to all selected CRs
* Unselected CRs remain in To Do
  {% endhint %}
  {% endstep %}
  {% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Begin a New Lifecycle</strong><br><br>After implementation, the lifecycle restarts with the Endorsement Cycle.</td><td><a href="/interfacing-help-files/end-users/to-do/completing-tasks/completing-an-endorsement-task.md">Completing an Endorsement Task</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F7xnyHkvLPtjKbZYQlycM%2FIMS-V16-NAV-Library-Icons-64.png?alt=media&amp;token=ac158510-5671-497b-888a-5715d4d84ddf">IMS-V16-NAV-Library-Icons-64.png</a></td></tr><tr><td><strong>Managing Your Tasks</strong><br><br>Learn the basics on how to manage your tasks in To Do</td><td><a href="/interfacing-help-files/end-users/to-do.md">Managing Your Tasks</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIicHnWRDxU9zPCTnLGLC%2FIMS%20Icons%20(1).png?alt=media&amp;token=f51f14ca-3e0c-466b-be24-aebe5b3d9570">IMS Icons (1).png</a></td></tr><tr><td><strong>Managing a Change Request Cycle (Modelers Only)</strong><br><br>Learn how to customize Change Request cycles</td><td><a href="/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-a-change-request-cycle.md">Managing a Change Request Cycle</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2Fk4sCOXBb1JOx4nqPtoSB%2FIMS%20Icons%20(2).png?alt=media&amp;token=0fb15536-368e-4949-9189-f9ce3223df8f">IMS Icons (2).png</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/to-do/completing-tasks/completing-change-request-tasks.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.