A procedure revision can reach outlets at different times. One team may have read the new text while another still uses a printed form from the previous version. Change control makes the approved revision, effective scope and remaining transition work visible.
This guide covers controlling revisions to existing procedures: impact review, approval, a controlled pilot, distribution of current copies, evidence of use, withdrawal and archiving, and authorised exceptions. It assumes you already have a playbook. The procedure, outlets and statuses in the example are fictional.
Start with the change request
Record what is changing, why, who asked for it and which procedure and revision it affects. Then review the impact. Which outlets, roles, forms and training materials does it touch? Does it interact with other procedures? Does it affect any food control or legal requirement?
A change that touches food controls or regulatory requirements needs the review and approval those requirements demand. This guide does not replace that review, and the change process must never be used to bypass a requirement. The worked example deliberately involves a low-risk administrative change for that reason.
Review, approve and pilot
Have the draft reviewed by people who know the work, and ideally tested by someone other than the author. Approval should come from the person with authority for that procedure, recorded with their name and date.
Choose pilot scope according to the change and its risks. For the administrative change in this guide, one outlet tests the candidate revision before rollout. Record the draft identifier, what was tested, what staff found unclear and any resulting edit. Recheck any changed steps as needed, then approve the final text before issuing it. A pilot approval is not approval for every outlet to adopt an unreviewed draft.
Worked example: SOP-HO-01 revision 1.3
In this fictional chain, the shift handover procedure SOP-HO-01 is being revised from 1.2 to 1.3. The only change is a new field on the handover form naming the next owner for each open issue. It is administrative and changes no food control step.
A candidate for revision 1.3 was piloted at Outlet 1, clarified and checked again before the final 1.3 text was approved for rollout to four outlets. The table shows each outlet at the latest review. Receipt, training, replacement of old copies and observed use have separate evidence. The rollout record names the effective date and any authorised transition for each outlet; there is no readiness score.
Outlet 4 is closed for refurbishment. Its authorised deferral covers deployment while closed, not permission to operate indefinitely on revision 1.2. Adoption of the approved revision is a recorded prerequisite for reopening, with an owner and review date. Outlet 3 has a separate, time-limited authorised transition for this administrative change; its existing controls remain in force while training and copy replacement are completed.
| Outlet (fictional) | Receipt acknowledged | Training evidence | Old copies replaced | Use observed | Current status |
|---|---|---|---|---|---|
| Outlet 1 (pilot) | Yes | Yes | Yes | Yes | Using 1.3 |
| Outlet 2 | Yes | Yes | Yes | Not yet | 1.3 issued; observation due |
| Outlet 3 | Yes | Not yet | Not yet | Not yet | 1.2 under authorised, time-limited transition; training and replacement due |
| Outlet 4 (closed) | Deferred | Deferred | Deferred | Not operating | Authorised deployment deferral; adopt 1.3 before reopening |
Why the stages stay separate
Receipt acknowledgement shows that a message or copy arrived. Training evidence shows what was taught and assessed within a stated scope. Replacing old copies reduces the chance of selecting the wrong version. An observation against the approved revision provides evidence of use during that observation; it does not prove that every future shift will follow it.
Agree training, copy replacement and the effective date together. Outlet 3 can use its old administrative version only within the recorded transition authority and end condition. If a requirement must take effect immediately, the manager must resolve the operating arrangements through the responsible authority; incomplete training is not a general justification for extending a superseded procedure.
Withdraw, archive and keep the index current
Keep one current version index listing each procedure's ID, current revision, issue date, owner and status. When a revision takes effect at an outlet, withdraw the superseded copy there and archive it where it can be consulted for history but cannot be mistaken for the current version.
Record exceptions in the same place: what is excepted, at which outlet, who authorised it, why and when it ends. An exception is a recorded decision, not a quiet delay.
Keep a usable revision history
Store the change request, reviewed draft, final approval and effective scope together under the stable procedure ID. Give draft candidates distinct identifiers so a pilot copy cannot be mistaken for the final issue. Record which linked forms and quick-reference sheets change at the same time.
When a concern appears after rollout, log the actual revision in use, the observed problem and the responsible reviewer. Do not quietly restore an old file or edit the approved copy in place. A correction or rollback is another controlled decision with an authorised scope, communication and evidence; prior versions remain available for historical review without becoming current by accident.
Background on document control
Historical US environmental quality guidance on standard operating procedures, from 2007, sets out stable document-control principles. Procedures are reviewed and tested by competent people, approved, and updated and re-approved when practice changes. Each carries an ID and revision. A master list is maintained, and outdated versions are archived so they cannot be used by mistake. It is cited only for those general principles. It is not current restaurant law, a current requirement or restaurant compliance guidance.
Put it into practice
Your action checklist
Your progress saves in this browser. No sign-up needed.
0 of 8 complete
From reading to doing
SOP revision and outlet rollout register
The SOP Change Control worksheet is a set of manual records: a change and evidence register (request, impact review, reviewer, approval), a pilot log, an outlet rollout matrix recording receipt, training, copy replacement and observed use separately, a current version index, and a controlled exceptions and archive record. It does not calculate a readiness percentage or declare any outlet ready.
Open the SOP Change Control tab in the launch workbook. Keep a copy for your own business.
Download the free workbook See what’s inside the toolkit →Sources & further reading
- Guidance for Preparing Standard Operating Procedures (SOPs), EPA QA/G-6 ↗
April 2007, retrieved 7 November 2026. Historical general environmental-quality guidance, used only for document-control principles. Not current restaurant law, a current EPA requirement or compliance guidance.
Published by Keystonne Grow. Product links connect to the Keystonne ecosystem; check the linked product or service for its current scope.
