SOP maintenance · Sep 26, 2026
SOP version control for small teams
A useful version history tells readers which instructions were approved, what changed and when to check them again.
Small teams rarely need a complicated approval system to keep a procedure current. They do need one editable source, a clearly identified published copy and a record of the decisions between them. A filename such as final-v3-new cannot answer which version a colleague should follow today.
Keep one source and name the published copy
Store the editable project where its owner can find it. For each published SOP, record a short identifier, the task or application it covers, the owner, approval date and the location of the copy readers actually use. Archive superseded exports rather than silently replacing them when a fixed audit or training record matters. Make the current link unambiguous.
StepShot keeps captured steps editable so an author can reorder, annotate, crop or add explanatory text before exporting. An exported PDF, Markdown document or self-contained HTML file is a delivery artifact, not the source of truth for the next edit. PDF export requires a paid licence; the Free tier exports Markdown or HTML for the first 10 captured steps.
Log changes that alter the reader's action
A change note should identify the affected step and why it changed: a renamed control, a new permission requirement, a different expected result or a corrected screenshot. Distinguish an editorial correction from a procedure change. If an application update affects only two screens, review the surrounding transitions as well, then replace only the evidence that is stale.
Do not infer a new procedure from a release note alone. Run the real task with the relevant access level, confirm the result and capture the changed states. For an exception path you cannot reproduce, mark it for the workflow owner to verify instead of presenting a plausible guess as tested instruction.
Review the file that people will open
Before approval, compare the export with the editable source. Check step order, text, screenshots, links, privacy redaction and the beginning and end of the task. Open the output in its actual destination: page breaks in PDF, image paths in Markdown and embedded assets in self-contained HTML may behave differently from the editor preview. The SOP export review checklist covers those format-specific checks.
Set the next review trigger
Record who approved this version and what should reopen it. A changed interface, policy update, failed task or reader report is a stronger trigger than a calendar date alone; a scheduled review remains a useful backstop. When replacing an SOP, update the current link and point any old landing page to its successor so readers do not have to guess which instructions apply.
Version control is a team practice, not a claim that a capture tool automatically publishes or keeps a knowledge base in sync. StepShot helps create and revise the guide on macOS 14 or later; the team remains responsible for approval, distribution and retirement. See the editor guide and maintenance guide for the related workflows.