How to update an SOP
Update an SOP by documenting the trigger, assessing affected steps, reviewing a fixed draft, approving a new issue and withdrawing the old one.
To update an SOP, assess the proposed change against actual work, approve a fixed new issue, publish it and make sure affected users stop following the old one.
The short version
- Record the reason for change and the work, roles and records it affects.
- Review and approve the exact candidate revision before giving it an effective date.
- Withdraw old copies and complete required training before the new instruction takes effect.
An edit is complete when the new instruction is in use
A corrected paragraph in a draft does not change how work is done. Identify the trigger and the affected steps, records, systems and roles. Review the draft with people who perform the task, then decide whether the change affects training or an effective-date cutover.
This guide follows one operational update through release. /guides/how-to-track-changes-in-an-sop covers the entry that records what changed, while /guides/how-to-manage-sop-revisions covers numbering and the register across many changes. Use the same route whether your team calls the result an update or a revision.
Release a changed SOP
The example shows how changed procedure content reaches technical review, approval and controlled issue.
Revise the affected instruction
The SOP's owner and scope establish what the change touches; the draft updates the relevant step and deviation path.
Resolve review and authorization
A subject matter expert checks the candidate against actual work before the designated approver accepts the exact revision.
Put the new issue into use
After version checkpoint and publication, the owner checks old-copy withdrawal and the training needs of affected roles.
How it works
Describe and assess the change
Capture the trigger, current revision, proposed change and impact on controls, forms, systems, people and related SOPs.
Review a fixed candidate
Test changed steps with operators, resolve comments and obtain an approval tied to the revision that will be issued.
Release and verify
Set the effective date, publish one current issue, withdraw the former one, and record training or acknowledgement where the impact calls for it.
Mistakes to avoid
Issuing before users are ready
If a changed step requires training, coordinate the effective date with that training and verify old copies are removed.
Related QueryChart feature
Map an SOP update
Adapt the controlled SOP example and add your training and old-copy withdrawal checks.
Frequently asked questions
Is updating an SOP the same as revising it?
In everyday use, yes. Both describe changing controlled content; the issued result needs a documented revision and approval.
Does every edit need retraining?
Assess the effect on work. A material change may need training, while a harmless correction may only need a recorded update.
Can the old SOP be deleted?
Withdraw it from use but retain its historical issue according to your record rules so past work can be reconstructed.