> 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.md).
# Creating & Managing Change Requests
Perform tasks assigned to your role to advance requests through the CR Management workflow.
## Workflow Overview
The **Change Request** application operates through a single, standardized workflow: the **Change Request Management** workflow. This workflow governs the full lifecycle of a change request, from creation through final evaluation.
***
## Interactive Tour
Explore the **CR Management** workflow and learn how each stage works, with key guidance and best practices along the way.
***
## Workflow Stages
The workflow is organized into **five key stages**, each with specific roles and responsibilities.
{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}
{% stepper %}
{% step %}
### Create New Change Request
> **Performed By:** Request Creator (e.g., Process Owner, Quality Specialist, Project Manager)
**Responsibilities**:
* Identify the need for a change related to a process, product, document, or service.
* Provide the necessary details (e.g., subject, priority, due date, description, justification).
* Submit the request to initiate the workflow.
***
{% endstep %}
{% step %}
### Review & Plan Change Request
> **Performed By:** Assigned Reviewer (e.g., Department Manager, Quality Assurance Lead, Compliance Officer)
**Responsibilities:**
* Evaluate the clarity, rationale, and potential impact of the request.
* Develop an implementation plan, including required tasks and actions.
* Provide feedback to the requester if revisions are needed.
* Approve the request for implementation or return it for modification.
{% hint style="warning" %}
This stage is triggered only if the request is returned for modification after the initial review.
{% endhint %}
***
{% endstep %}
{% step %}
### Implement the Plan
> **Performed By:** Assigned Action/Task Owners
This stage includes the **Implement the Plan** subprocess, which manages all actions or tasks required to execute approved changes. It integrates both the [Action Item Management](/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-action-items.md) and [Task Management](/interfacing-help-files/quality-managers/task-management-application/creating-and-managing-tasks.md) workflows.
**Responsibilities:**
* Accept or decline assigned action(s) or task(s).
* Execute assigned items according to instructions.
* Document progress and provide evidence of completion.
* Report any issues or deviations from the plan.
* Submit completed work for approval.
{% hint style="warning" %}
This stage is triggered only if specific actions or tasks were defined during review and planning.
{% endhint %}
***
{% endstep %}
{% step %}
### Review Implementation
> **Performed By:** Assigned Reviewer (e.g., Department Manager, Quality Assurance Lead, Compliance Officer)
**Responsibilities**:
* Verify that the change has been implemented as planned.
* Ensure all tasks and actions are complete.
* Confirm that documentation is accurate and compliant.
* Approve the final implementation or return items for rework if incomplete or incorrect.
***
{% endstep %}
{% endstepper %}
***
---
# 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.md?ask=&goal=
```
`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.
