Multi-Document Change Control

When to use this article

One change must move multiple SOPs to Ready for Training on the same day, and/or obsolete older effective versions; or a type requires change control before a new draft.

Product/process change control lives in QMS, not this document change control object.

Roles

Create and populate lists

1. Create a Document Change Control object.
2. Set proposed implementation date and description.
3. Release list: add currently effective documents to revise; the system creates or links drafts.
4. Obsolescence list: add effective versions to withdraw on the implementation date; they stay Effective until that date.

Documents not on a list can still follow the standalone review path.

Approval and implementation date

1. Authors finish drafts → submit → reviewers pass.
2. Release-list documents enter Waiting for Change Control Approval when applicable.
3. Change manager sends for approval; approver approves or rejects on the workflow task.
4. Approval does not change document states; it locks the batch and date.
5. On proposed implementation date:
6. Release list → Ready for Training
   • Obsolescence list → Obsolete (not via Ready for Training)

Owners still make effective

After Ready for Training, each document owner runs Make Effective. Coordinate within the same window so related main SOPs and child work instructions do not drift.

Training handoff

When documents are Ready for Training or Effective, run Update Training Assignments or Issue Training so the matrix receives new material.

FAQ