Build the procedure around a dated question: Which revision is in effect for this document at this point of use? A larger revision number alone cannot answer it.
Two original revisions, one declared rule
Fictional document DOC01, an internal guide. The example's supplied rule is: a revision can be active only when approved and its effective date is on or before the review date. An earlier revision becomes superseded when the newer approved revision takes effect. This is an original example policy, not a rule imposed on every organization.
| Document | Revision | Approval date | Effective date | October 13, 2026 view | October 20, 2026 view |
|---|---|---|---|---|---|
| DOC01 | v1 | September 30, 2026 | October 1, 2026 | Active | Superseded; retain historical copy |
| DOC01 | v2 | October 13, 2026 | October 20, 2026 | Approved for future use | Active |
On October 13, v1 is the active revision. v2 is approved, so calling it a draft would be inaccurate, but it is not yet effective. On October 20, v2 becomes active under the declared rule; v1 remains available as a historical record rather than the current operating copy.
A draft with no approval evidence does not become active merely because somebody supplied an effective date. If approval, date or revision sequence is unclear, flag the record and obtain the responsible owner's confirmation. Do not resolve an inconsistent register by guessing which file to use.
Give the maintained register enough evidence
Record document ID, title, revision, approval evidence/date, effective date, status, responsible owner and controlled-copy locations. Preserve prior revision entries so a dated inquiry can identify the revision used at that time.
EPA's April 2007 SOP guidance discusses review and approval, revision identification, a master list and archival of outdated versions. It provides historical quality-system structure here, not a current compliance requirement. The date-gated DOC01 policy and dates are original to this exercise.
The Smartsheet document-control form asks for naming, numbering, dating and archiving conventions. Use those questions to identify missing organizational inputs; do not let a blank form supply an approver, retention period or archive location that has not been established.
Prepare the point-of-use transition
Use the organization's required Word, PDF, register or controlled workflow for the actual procedure. A useful draft sequence is:
- Identify the document and revision: Match DOC01 in the register to the copy being reviewed.
- Verify approval and effective date: Apply the supplied policy for the chosen date. On October 13, keep v1 current and label v2 approved for future use.
- Prepare the transition: List actual controlled-copy locations, the accountable owner and required distribution steps. Leave unknown locations and roles to confirm.
- Check the effective revision at each location: On October 20, the example's expected active revision is v2. Record what was actually found, by whom and when; the date rule does not prove that distribution happened.
- Handle the prior operating copies: Follow the confirmed process for preventing superseded operating use while retaining the historical revision and its context.
For each location, prepare blank fields for expected revision, observed revision, verification date, verifier, discrepancy and follow-up. A planned check is not a completed check. Do not prefill “distributed,” “acknowledged” or “all copies current.”
Preserve history without inventing retention rules
Superseded does not mean deleted. Preserve the historical copy in the confirmed archive and distinguish it clearly from the current operating revision. Retention duration, access arrangements and authorized disposal remain to confirm unless supplied by the responsible organization.
The companion compares October 13 with October 20 and reveals the corresponding DOC01 records. Changing that local date view must only change the explanation shown. It cannot approve a revision, replace a controlled document, notify recipients or complete distribution verification.
Copy a document-control procedure brief
Create one complete, self-contained US-English HTML companion for “DOC01 dated revision review”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for October 13; October 20; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Draft a document-control SOP in US English using the required native format.
Purpose, scope and covered document types: [enter]
Document IDs, revision history, approval evidence and effective dates: [paste]
Declared activation/supersession rule: [paste or TO CONFIRM]
Actual approval roles and controlled-copy locations: [paste or TO CONFIRM]
Distribution, historical archive and retention policy: [paste or TO CONFIRM]
Review dates and required register/Word/PDF/workflow: [enter]
Separate draft, approved-future, active and superseded revisions under the
supplied policy. Require approval and effective-date evidence before an active
claim. Bind every dated answer to document ID and exact revision. Do not use
revision number alone or invent authority, retention duration or locations. Retain historical records. Prepare blank actual distribution-verification and
discrepancy fields; do not imply checks, acknowledgments or notifications occurred.
Return a proposed procedure, dated register example and blank location-check
record for owner review. If requested, specify a sanitized HTML walkthrough
comparing review dates without changing actual documents. No approval controls,
file deletion, saved edits, automatic distribution or compliance guarantee.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Document Control SOP Template: Separate Approval from the Effective Date
A revised guide is approved today, but its effective date is next week. Replacing the point-of-use copy immediately would put the future revision into use too early. Keep approval, effective date and actual distribution checks as separate records.
Build the procedure around a dated question: **Which revision is in effect for this document at this point of use?** A larger revision number alone cannot answer it.
## Two original revisions, one declared rule
**Fictional document DOC01, an internal guide.** The example's supplied rule is: a revision can be active only when approved and its effective date is on or before the review date. An earlier revision becomes superseded when the newer approved revision takes effect. This is an original example policy, not a rule imposed on every organization.
| Document | Revision | Approval date | Effective date | October 13, 2026 view | October 20, 2026 view |
| --- | --- | --- | --- | --- | --- |
| DOC01 | v1 | September 30, 2026 | October 1, 2026 | Active | Superseded; retain historical copy |
| DOC01 | v2 | October 13, 2026 | October 20, 2026 | Approved for future use | Active |
On October 13, v1 is the active revision. v2 is approved, so calling it a draft would be inaccurate, but it is not yet effective. On October 20, v2 becomes active under the declared rule; v1 remains available as a historical record rather than the current operating copy.
A draft with no approval evidence does not become active merely because somebody supplied an effective date. If approval, date or revision sequence is unclear, flag the record and obtain the responsible owner's confirmation. Do not resolve an inconsistent register by guessing which file to use.
## Give the maintained register enough evidence
Record document ID, title, revision, approval evidence/date, effective date, status, responsible owner and controlled-copy locations. Preserve prior revision entries so a dated inquiry can identify the revision used at that time.
[EPA's April 2007 SOP guidance](https://www.epa.gov/sites/default/files/2015-06/documents/g6-final.pdf) discusses review and approval, revision identification, a master list and archival of outdated versions. It provides historical quality-system structure here, not a current compliance requirement. The date-gated DOC01 policy and dates are original to this exercise.
The [Smartsheet document-control form](https://www.smartsheet.com/sites/default/files/2019-07/IC-Document-Control-SOP-Standard-Operating-Procedure-Template-10622_PDF.pdf) asks for naming, numbering, dating and archiving conventions. Use those questions to identify missing organizational inputs; do not let a blank form supply an approver, retention period or archive location that has not been established.
## Prepare the point-of-use transition
Use the organization's required Word, PDF, register or controlled workflow for the actual procedure. A useful draft sequence is:
1. **Identify the document and revision:** Match DOC01 in the register to the copy being reviewed.
2. **Verify approval and effective date:** Apply the supplied policy for the chosen date. On October 13, keep v1 current and label v2 approved for future use.
3. **Prepare the transition:** List actual controlled-copy locations, the accountable owner and required distribution steps. Leave unknown locations and roles to confirm.
4. **Check the effective revision at each location:** On October 20, the example's expected active revision is v2. Record what was actually found, by whom and when; the date rule does not prove that distribution happened.
5. **Handle the prior operating copies:** Follow the confirmed process for preventing superseded operating use while retaining the historical revision and its context.
For each location, prepare blank fields for expected revision, observed revision, verification date, verifier, discrepancy and follow-up. A planned check is not a completed check. Do not prefill “distributed,” “acknowledged” or “all copies current.”
## Preserve history without inventing retention rules
Superseded does not mean deleted. Preserve the historical copy in the confirmed archive and distinguish it clearly from the current operating revision. Retention duration, access arrangements and authorized disposal remain **to confirm** unless supplied by the responsible organization.
The companion compares October 13 with October 20 and reveals the corresponding DOC01 records. Changing that local date view must only change the explanation shown. It cannot approve a revision, replace a controlled document, notify recipients or complete distribution verification.
## Copy a document-control procedure brief
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Walk through DOC01 on both review dates with the responsible owner before distributing the proposed procedure. Keep the approved register and required documents as the maintained originals, and record actual point-of-use verification separately from the expected effective revision.