STEP 01 · RAISE THE CHANGE
Capture why the document needs to change
The change request links the affected document, reason, impact and reviewers from the start.
Automates repetitive stepsSaves admin timeKeeps people in control
DocumentSOP-QA-014
Current versionv4.2
Change typeProcess improvement
OwnerQA Systems
ReviewersOperations + QA
Target effective date01 Sep 2026
Impact assessment
Training required for receiving team.
Linked records
CAPA-102 and audit observation 24-07.
STEP 02 · ROUTE APPROVALS
Every reviewer sees the same current draft
Approvals move through a clear route with comments, decision history and overdue reminders.
Automates repetitive stepsSaves admin timeKeeps people in control
AuthorDraft complete
→OperationsApproved
→QAReviewing
→Site leadPending
Operations
Approved · 18 Aug · Process accurate
QA
Reviewing · Check training impact
Site lead
Pending
STEP 03 · PUBLISH THE CURRENT VERSION
Make the latest document obvious
Once approved, the new version becomes current and old copies stay archived but traceable.
Automates repetitive stepsSaves admin timeKeeps people in control
Version
Status
Effective
Owner
v4.3
Current
01 Sep
QA Systems
v4.2
Superseded
12 Feb
QA Systems
v4.1
Archived
05 Oct
QA Systems
Current docs418
Superseded93
Wrong-version risk↓
STEP 04 · TRIGGER TRAINING
Document change connects to competence
Required readers receive acknowledgement or training tasks automatically with completion visible to QA.
Automates repetitive stepsSaves admin timeKeeps people in control
Assigned154
Completed132
Overdue22
Team
Assigned
Complete
Status
Receiving
38
36
2 overdue
QA
24
24
Complete
Warehouse
42
35
7 overdue