Document Change Requests

Document Change Requests (DCRs) provide a formal, traceable process for requesting modifications to released documents. Instead of directly editing a released document, submit a change request that describes the proposed change, its rationale, and expected impact.

When to use a change request

Use the Document Change Request process when:

• A released document needs content updates or corrections.
• A regulatory or process change requires document modifications.
• An error or inaccuracy is discovered in a released document.
• A user identifies an improvement to an existing document.

Note

Change requests create a formal record of the requested modification. This is distinct from creating a new version — a DCR initiates a review and approval process for the proposed change before any modifications are made.

Submit a change request

1. On the left sidebar, select Documents.
2. Select the document you want to request changes for.
3. On the document detail page, select Request Change to open the Request Document Change modal.
4. In the Request Title field, enter a brief summary of the requested change.
5. In the Description field, enter a detailed explanation, including the rationale and expected impact.
6. Select Submit Request.
7. The modal closes and the page refreshes to reflect the new request.

Form fields reference

Field	Required	Description
Request Title	Yes	A brief summary of the requested change.
Description	Yes	A detailed explanation including rationale and expected impact.

Validation rules

• The Submit Request button remains disabled until both the title and description fields contain text.
• If the API returns an error, an error alert appears within the modal with the specific message.

Handle a failed submission

If the change request submission fails:

1. Review the error message at the top of the modal form.
2. Correct the issue and select Submit Request again. Your entered data is preserved.
3. To discard the request, select Cancel or the close button.

Tip

When writing a change request description, include the following for a thorough review:

• What needs to change (specific sections, paragraphs, or content)
• Why the change is needed (regulatory update, process improvement, error correction)
• Impact on related processes, training, or other documents
• Urgency if the change is time-sensitive

Permissions

Action	Requirement
Submit a change request	Authenticated user with access to the document
View change requests	Authenticated user with access to the document