Creating a Change Request

Who Is This For?

Authors / Owners – Creating the CR and setting initial details
Reviewers – Reviewing the CR content and scope later in the process
Approvers / QA – Verifying compliance and granting approval
Admins – Managing roles, access, and configuration (Entity Types, Change Types)

Go to Change Request from the sidebar.
Click New Change Request from the topbar.
Enter a clear Title.
Select the appropriate option under ‘What kind of change are you making?’ to determine the correct Change Request workflow.
Click Create.

Go to Document from the sidebar.
Search and select the document that requires a Change Request.
Click Requires CR in the properties card.
Enter a Title.
Select the appropriate option under ‘What kind of change are you making?’ to determine the correct Change Request workflow.
Click Create.

💡Tips:

Use a short, descriptive title so it’s easy to find and report on later.
Change Types are configured by your admin and may alter the workflow (e.g., Review, Approval, Effectiveness Check).

📎 Reference:

Open the CR and click the pencil in the Details card. Update fields and click Save.

Field	Description	Note
Title*	Title of the Change Request
Effective Date*	When the CR becomes active in the QMS	Must be set before routing the CR for Approval (execution phase)
Due Date	Target date for CR release	Optional
Quality Process	The process the change follows	Not the impacted process
Tags	Keywords to categorize the CR	Optional; org-configurable
Impacted Processes	Processes impacted by the change	Creates relations only; does not change process metadata
Change Priority	Urgency/criticality	Defined by your change control procedure

❗ Compliance: The Effective Date is required before you can send the CR for Approval.

📎 Reference: Understanding the Change Request Workflow

In the properties card, click the pencil to Manage Access.
Search for users or groups and assign roles: Owner, Author, Reviewer, Approver, Viewer.
Click Save.

💡 Assign Reviewers and Approvers early to avoid delays later.

📎 References:

💡 Set the Effective Date early to avoid blockers before Approval.
💡 Use templates whenever available for consistency and completeness.
💡 Keep scope focused—only add impacted processes and tags that improve search and reporting.