> 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/document-control/managing-documentation-lifecycle/managing-a-change-request-cycle.md). # Managing a Change Request Cycle Submit requests to update or correct documentation when changes are needed. The **Change Request (CR)** cycle enables users to propose updates when documentation is outdated, incorrect, or needs improvement. This cycle consists of **two key stages** to ensure CRs are properly reviewed and implemented. *** ## How the Change Request Cycle Works The process includes two clear stages: 1. **Review CR** * When an CR is submitted, the item's assigned **Accountable** user(s) review it and decide whether to approve or reject it. * This step ensures only valid changes move forward. 2. **Implement Changes** * Once approved, the item's assigned **Author(s)** updates the documentation according to the CR details. *** ## How to Assign Authors & Accountable Users for CRs In **Phase 1**, editing is not yet available in the platform. All setup and administration must be performed in EPC. For detailed instructions on managing CRs in EPC, refer to the following topic: * [Assigning Authors](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/4-12-6-2-assign-ir-implementer) * [Assigning Responsibilities (R**A**SCI-VS)](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-5-1-assign-responsibilities-rasci-vs) *** ## Working with CRs While you cannot assign authors or responsibilities in the platform, you can complete CR tasks assigned to you. See the guides below to get started:


Completing CR Tasks	Learn how to execute different CR tasks	Completing Change Request Tasks	IMS Icons (13).png
Managing Tasks in To Do	View and organize your assigned tasks.	Managing Your Tasks	to do icon.png
Raising CRs	Learn how to create CRs directly in the new platform	Raising Change Requests	IMS Icons (1).png

--- # 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/document-control/managing-documentation-lifecycle/managing-a-change-request-cycle.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.