Give every SOP a clear lifecycle
An SOP is not a document; it is a controlled process: drafted, reviewed, approved, active, eventually superseded or archived. Making the lifecycle explicit is what separates SOP management from files on a shared drive — each status change becomes a recorded decision with an actor and a date, rather than a rename. A typical set of states: draft → review → approved → active → superseded, with archived for retired procedures.
Control versions
A version number that is bumped by hand drifts from reality within months. Substantive changes — title or document body — should bump the version automatically, while superseded versions remain readable. When "v3" reliably means a specific document text, conversations like "are you on the new protocol?" end in seconds.
Record review and approval
Approval should leave a trail: who approved, when, and a note or signature. A useful safeguard is preventing authors from approving their own SOPs — review by a second person is usually required by the lab's process, and the system should make skipping it impossible rather than merely discouraged. Review due dates keep the review stage from becoming a parking lot.
Track effective dates
The effective date answers "since when is this the procedure we follow?" — it should be stamped when an approved SOP is activated, not inferred from file timestamps. A review date works the same way in reverse: it schedules the next look, and ACTIVE SOPs approaching their review date should surface where someone will see them (a dashboard queue, a digest) rather than in a folder nobody opens.
Record acknowledgements per version
For SOPs that people must read before doing the work, an acknowledgement is only meaningful against the exact version that was read. Record who acknowledged which version — and when a new version comes into effect, the requirement resets. This is what turns "everyone has been trained" into a verifiable per-person, per-version list.
Keep superseded versions readable
Superseded SOPs still have value: experiments were run under them, questions arise later about what procedure was in force on a given date. Keep old versions accessible and clearly marked superseded, rather than deleting or overwriting them.
A note on compliance
Versioning, approvals, effective dates, acknowledgements, and an audit trail are the mechanics labs use within their quality processes. Whether they satisfy a specific regulatory requirement depends on the lab's whole system and its context — no tool alone certifies anything.
Where software carries the load
The lifecycle above is exactly what laboratory SOP management software enforces: automatic version bumps, recorded approvals with self-approval blocked, effective and review dates, per-version acknowledgements, and a readable history. It pairs naturally with an inventory system in the same lab platform — and if you are evaluating bigger systems, see the LIMS alternative comparison.