This original SOP on SOP template follows a fictional revision from proposal through review and activation. It preserves the version used by earlier work and tracks copies that should no longer guide new runs.
Start with the version register
The fictional procedure is P07, Book Packet Packing. Revision 1 is active in the supplied illustrative register under reference A01. These are teaching records, not actual organizational authorization.
EPA's April 2007 SOP guidance discusses reviewing and reapproving revisions, identifying versions, maintaining a master list and retaining outdated copies for historical review while controlling current use. We use those document-control concepts rather than copying an EPA procedure or treating its review examples as universal deadlines. Guidance for Preparing Standard Operating Procedures
The native master register should include:
Procedure ID / title / revision: ______
Status: ______
Approval record: ______
Effective condition and confirmation: ______
Current-copy locations: ______
Superseded-copy locations: ______
Review event and evidence: ______
In-flight work decision: ______
Responsible owner / next review basis: ______
Actual names, dates, authority and copy locations remain blank or TO CONFIRM. Define the organization's review cadence through its actual process; this template imposes no one-to-two-year rule.
Check the impact of the H03-to-H04 proposal
Revision 2 proposes replacing handout H03 with H04. Review three connected references before declaring the draft ready:
| Component | Proposed revision-2 requirement | If still H03 |
|---|---|---|
| Step text | Calls for H04 at the relevant step | Reference mismatch remains open |
| Materials list | Lists H04 | Supply description does not match the step |
| Checklist reference | Checks H04 | Execution check still targets the old handout |
All three must agree on the reviewed change. Updating only the step text is insufficient. A missing H04 checklist reference blocks readiness for activation even if a proposed effective date is present.
Keep the change request, impacted references and review evidence together. The packet supplies no completed document edits or actual review; these are requirements for the proposed revision.
Do not turn approval into automatic activation
In a separate fictional stage, A02 records approval of revision 2, but the authorized effective condition is still pending confirmation. The revision remains approved, pending activation; it is not automatically the active version or permission for a user to start work under it.
The responsible organization must verify the effective condition and activation authority. Actual date and approval evidence remain blank here. A future date typed in a draft cannot supply that verification.
Only in a separate illustrative scenario where the authorized condition is confirmed should the register mark revision 2 active for new runs and revision 1 superseded. Record the basis, date and confirmed current-copy locations at that point. The example does not perform activation, distribution or notification.
Preserve the earlier run's actual version
The historical fictional run X01 references P07 revision 1. It remains a revision-1 run after revision 2 becomes active in the illustrative scenario. Do not rewrite X01 as revision 2 or delete the earlier procedure copy.
Retain revision 1 as a read-only historical copy through the organization's authorized process, and track its superseded locations so it is not mistaken for the current instruction for new runs. “Superseded” and “removed from current use” do not mean that historical evidence has vanished.
Any in-flight work needs a separately confirmed decision about the applicable version. The template does not silently switch it to revision 2. Keep that decision open until the actual authority provides it.
Record the lifecycle without claiming automation
Use separate statuses for draft, review issues open, approved pending activation, active and superseded. Tie each transition to its evidence rather than a decorative check mark.
The maintained native SOP, master register, change-impact checklist and copy ledger remain authoritative. Actual copy handling and reapproval belong to the organization. This packet includes no automatic PDF edits, distribution, saved public-link updates or messages sent.
Copy this prompt for the revision packet
Prepare an original US-English SOP-on-SOP and native master register/change-impact checklist/superseded-copy ledger. No actual approval, activation, edits, distribution or notification.
Fictional P07 Book Packet Packing revision 1 active under illustrative register reference A01, not real authorization. Proposed revision 2 H03->H04 remains draft. Check step text, materials list and checklist reference all name H04; missing checklist change blocks readiness. Proposed future date not authority. Actual owners/approval records/dates/effective condition blank.
Separate illustrative A02 approval: revision 2 approved pending effective gate, not active or automatic user permission. Only when actual authorized effective condition is confirmed in a later illustrative scenario mark revision 2 active for new runs/revision 1 superseded, with basis and copy locations. No tool activation or sending.
Retain historical X01 referencing revision 1, never rewrite it as revision 2 or delete old copy. Organization-controlled read-only historical copy and superseded-location tracking distinct from current-copy locations. In-flight work version decision TO CONFIRM. Register ID/title/revision/status/approval/effectivebasis/currentlocations/supersededlocations/reviewevent/inflightdecision/owner/reviewbasis. Distinct draft/openreview/approvedpending/active/superseded states tied to evidence. No universal 1–2-year review deadline or regulatory certification.
Native records authoritative. Later sanitized HTML inspection controls/keyboard/360px/width tests pending. No automatic PDF updates, public-link updates, persistence, approval service, export or notifications. Do not copy EPA SOPs/diagrams.
Review the gate beside the revision
The local HTML example places the revision's linked references, approval state and effective gate together. NOS supports saving and rendering prepared HTML. Retain the native procedure and actual version/copy records.
Explore NOS to present the prepared revision review. A reader should know which version is authorized for new work and which version explains the work already recorded.