What is the typical lifecycle of a standard operating procedure?
The typical SOP lifecycle has five stages: creation, review and approval, distribution, active use with periodic review, and retirement. Most companies focus only on creation and skip the rest, which is why SOPs become outdated. A healthy SOP lifecycle includes quarterly reviews, version tracking, and a clear process for retiring obsolete documents.
What are the five stages of the SOP lifecycle?
| Stage | Activities | Common Failure |
|---|---|---|
| 1. Creation | Draft the SOP, capture the workflow, add screenshots | Taking too long — perfectionism delays publishing |
| 2. Review & approval | SME reviews accuracy, manager approves | No review process — SOP goes live unchecked |
| 3. Distribution | Share with the team, add to knowledge base, announce | Buried in a folder nobody checks |
| 4. Active use & review | Team follows the SOP, quarterly accuracy checks | No review schedule — SOP drifts from reality |
| 5. Retirement | Archive or delete when process is eliminated | Outdated SOPs never removed, causing confusion |
How do you keep SOPs from dying after creation?
Three practices that keep SOPs alive through their full lifecycle:
-
Assign an owner — Every SOP has one person responsible for its accuracy. When the process changes, the owner updates the document. No owner means no accountability.
-
Set review dates — Add a "next review" date to every SOP. Quarterly reviews for frequently changing processes, biannual for stable ones. When the date arrives, the owner verifies every step.
-
Make updates easy — If updating an SOP takes 90 minutes of manual screenshotting, it will not happen. Use Glyde to re-record the process in 5 minutes — the tool regenerates annotated screenshots and contextual descriptions automatically, replacing the old version completely. The easier the update, the more likely it happens.
Retirement is the most neglected stage. When a process is eliminated or replaced, archive the SOP and mark it clearly as deprecated. An outdated SOP that looks current is more dangerous than no SOP at all.
This answer is part of our guide to process documentation.