Skip to main content

Executing a Change Request

Every record in scope (templates, quality documents, actions, attachments, and relations) is processed correctly during the Change Request (CR) execution phase so nothing is missed and the release is compliant.

Updated over a week ago

Who Is This For?

  • Users / Authors updating templates or documents

  • Assignees completing CR Actions

  • QA / Approvers verifying completeness and final approval

  • Admins overseeing execution status and system configuration

How to Do It?

Step 1: Open the CR and review the scope

Confirm all Templates, Quality Documents, Actions, Attachments, and Relations included in scope.

Compliance reminder: Everything in the CR scope must be processed before closing the CR.

📎 References:


Step 2: Execute Template Changes (if applicable)

Process all templates included in the CR scope using the standard template workflow. Templates remain in Awaiting Release until the CR is closed.

📎 References:


Step 3: Execute Quality Document Changes (if applicable)

Author, review, and approve each quality document per the usual document flow. Documents remain in Awaiting Release until the CR is fully closed.

Compliance reminder: Effective dates for CR-controlled records are transferred from the CR upon closure — do not try to set them directly on the document.

📎 References:


Step 4: Complete CR Actions (Assignees)

Finish all CR Actions that were planned under the CR; final CR approval is blocked until every action is completed.

💡 Tip: Use My Work Dashboard to filter by Action and quickly find what’s assigned to you.

(Insert screenshot)

📎 References:


Step 5: Update Attachments and Relations

Manually review and update Attachments and Related Items linked to the CR; they do not update automatically.

💡 Tip: Remove or replace outdated supporting files so reviewers only see the current evidence.

📎 Reference: Managing Attachments


Step 6: Track CR Completion (choose one method)

Pick the tracking method that fits your control needs.

Option A: Track inside the CR document

Record progress directly in the CR file. The system won’t block approval even if something is missed—use with caution for items outside SimplerQMS.

Option B: Track via CR Attachment

Maintain a progress log as an attachment that must be approved before moving forward—adds a formal record and reduces oversights.


📎 Reference: Managing Attachments

Option C (Recommended): Track via Actions

Create a dedicated Action for each planned update; the CR cannot be finally approved until all are completed.


📎 Reference: Managing CR Actions

Compliance reminder: If you mix methods (e.g., document notes + actions), make sure scope and status match across all places to avoid audit gaps.


Tips

  • 💡 Use consistent naming (e.g., “CR-1234 – Template X – Update header”) for Actions so approvers can match Actions to scope quickly.

  • 💡 Filter Items to Change by State = Awaiting Release to confirm everything controlled by the CR is processed before closure.

  • 💡 Keep one source of truth for tracking (prefer Actions) to avoid conflicting status in notes or attachments.

What’s Next?

Did this answer your question?