Skip to main content

Change Requests for Updates

Run updates (or retirements) of existing records under a change control.

Updated over 3 weeks ago

Who Is This For?

  • Authors / Owners โ€“ Creating the CR for updates/retirements and defining scope

  • Reviewers โ€“ Validating the update/retirement plan and rationale

  • Approvers / QA โ€“ Authorizing the plan and ensuring compliance

  • Assignees โ€“ Completing actions tied to the updates

How to Do It?

Step 1: Choose the correct Change Type

Select the Change Type that allows updating or retiring existing records (includes controlled items).

๐Ÿ’ก Tip: Change Types are configured by your admin and may alter the workflow (e.g., Review, Approval, Effectiveness Check).

๐Ÿ“Ž References:

๐Ÿ“Ž Reference: Creating a Change Request


Step 2: Add records to update or retire

Scope the records that will be changed under this CR.

  1. Open the CR and go to Items to Change.

  2. Add existing records (documents, templates, products) that you intend to update or retire.

  3. Click Save.

๐Ÿ’กTip: Keep the list focusedโ€”only include records that are truly impacted.

๐Ÿ“Ž Reference: Planning a Change Request


Step 3: Execute updates or retirements

After plan approval, process each scoped record according to its standard workflow.

  • Documents โ†’ follow the document authoring, review, and approval flow
    โ€‹๐Ÿ“Ž Reference: Managing Quality Documents

  • Templates โ†’ follow the template authoring, review, and approval flow
    โ€‹๐Ÿ“Ž Reference: Managing Templates

๐Ÿ’กTip: Use CR Actions to assign and track each update/retirement task.


Tips

๐Ÿ’ก Select the Change Type that matches your SOP before scoping itemsโ€”workflow and permissions depend on it.

๐Ÿ’ก Use CR Actions to block final approval until every update/retirement task is completed.

๐Ÿ’ก Group related updates in one CR to keep traceability clean and reviews efficient.

Whatโ€™s Next?

Did this answer your question?