How to retire an SOP without losing operational knowledge

Retire a procedure when updating it would mislead

Not every old SOP needs another revision. Retire it when the task no longer exists, a system has been replaced, a policy prohibits the old path or another approved procedure now owns the same outcome. If only a label or screen changed, updating the current guide may still be clearer than creating a historical branch.

Confirm the decision with the process owner before changing what readers can find. A low-traffic page may still support a monthly exception, an audit trail or a recovery process that the main team rarely sees.

Capture the retirement record

Record the procedure title, owner, last verified date, retirement date and reason. Name the product or policy state that made the instructions obsolete. If a replacement exists, link to its approved location and describe whether it fully replaces the old task or only covers the common path.

Keep enough evidence to explain the decision without preserving unnecessary private information. Screenshots can contain customer names, tokens, account details or internal navigation. Review every retained image, remove irrelevant frames and apply redaction before the archive leaves its original access boundary.

Replace instructions with a useful notice

Do not leave the old steps online with a small warning at the top. Readers arriving from search, bookmarks or an old ticket may skip the warning and follow the screenshots. Replace the actionable body with a concise retirement notice, the effective date, the reason and the next approved destination.

When the publishing system supports redirects, point the old URL to the closest replacement. Keep a visible archive only when policy, audit or support work requires it, and restrict access if the historical screenshots reveal systems that current staff should not use.

Test every route readers use

Search the knowledge base for the old title and common task terms. Check navigation, onboarding lists, support macros, training decks, bookmarks and links from related SOPs. The retirement is incomplete while a normal reader can still land on an actionable stale copy.

Open the replacement as a reader with ordinary permissions. Verify that its prerequisites, screenshots and success state match the current workflow. If no replacement exists, say who now owns the task and how a reader should request help instead of inventing a temporary procedure.

Preserve the source separately from the published page

The maintained authoring source and the reader-facing page serve different purposes. Preserve the final approved source, associated images and retirement record according to the team's retention policy. Remove or redirect the published instructions so discovery leads to current work.

Use a stable file name, version note and owner. If the source is exported, keep the document and its assets together: Markdown commonly relies on a companion image folder, while PDF or self-contained HTML can preserve a portable review copy. Test the archive after moving it rather than assuming the links and images survived.

Build retirement into routine maintenance

Add a retirement outcome to the same review process used for updates. A review should be able to confirm the SOP, revise it, replace it or retire it. That prevents owners from repeatedly approving a page whose underlying task has already moved elsewhere.

Track links to the retired source, its replacement, the decision owner and the next review trigger. For a broader cadence, see how often SOP documentation should be reviewed. For final delivery checks, use the StepShot export guide.

Where StepShot fits

StepShot is a local-first SOP and step-by-step guide generator for macOS 14 and later. It can capture a current workflow in action-driven or screen-recording mode, let an author edit and reorder steps, apply locally reviewed pixel redaction, and export PDF, Markdown or self-contained HTML.

StepShot does not govern a hosted knowledge base, redirect published URLs or apply an organization's retention policy. Use it to create and review the source evidence, then make retirement and access decisions in the system that owns publication. The capture guide explains how to record the replacement workflow, and features lists the current product boundaries.