> 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/raising-change-requests.md).

# Raising Change Requests

Propose and submit changes to improve documentation.

**Change Requests (CRs)** allow you to contribute to better documentation. By raising a CR, you provide feedback that helps the team refine content, clarify instructions, and keep information accurate and reliable. 

Each request is carefully tracked and reviewed to ensure updates are evaluated and applied effectively.

***

## Interactive Tour

See how to raise, fill out, and submit a CR.

{% @howdygo/embed url="<https://app.howdygo.com/share/3ca9167d-6693-4ed0-8ba2-a5c30798f360>" fullWidth="true" %}

***

## Step-by-Step Guide

{% stepper %}
{% step %}

### Opening the CR Form

You can raise a CR from the **Details Panel** anywhere in the platform.

* Click the vertical ellipsis (<i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>).
* Select **Raise New Workflow** → **Change Request**

The CR form opens in a side panel, allowing you to retain visibility of your current context.

***

{% endstep %}

{% step %}

### Completing the Form

Fill in the form.

* Click **Add File** to attach supporting documents.

***

{% endstep %}

{% step %}

### Submitting the Request

When all required fields are complete, click **Submit**.&#x20;

***

{% endstep %}
{% endstepper %}

***

## What Happens Next?

After you submit a CR:

* A **review task** is created and assigned to the item's **Accountable** user (CR reviewer).
* The CR reviewer **approves or rejects** the CR and provides justification.
  * If approved, an **implementation task** is created and assigned to the **Author**.
  * If rejected, the CR is closed and the justification is recorded.

***

## 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>Completing Change Request Tasks</strong></td><td>Take action on assigned CR tasks.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F5Aeu2y0v898h8TlT2GMk%2FIMS-V16-Intro-7.png?alt=media&amp;token=4c09eacd-abdd-44d1-b318-8d6dbb4a11b1">IMS-V16-Intro-7.png</a></td><td></td></tr><tr><td><strong>Participating in Posts</strong></td><td>Learn how to access and create Posts.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FhmqdnRCr28kSQVBY3KNd%2F63.png?alt=media&amp;token=6e298b1b-213d-4b2b-b9c0-6f0c5d6549ad">icons.png</a></td><td><a href="/interfacing-help-files/end-users/participating-in-posts.md">Participating in Posts</a></td></tr><tr><td><strong>Managing a Change Request Cycle (Modelers Only)</strong></td><td>Assign users and see how each role contributes to reviewing, approving, and completing CRs.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FnlrSCUvF1qfN1L6DRhNb%2FIMS%20Icons%20(7).png?alt=media&amp;token=bf418ecc-06bf-486a-8368-a33805a5a25f">IMS Icons (7).png</a></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></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/raising-change-requests.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.