← Insights

Operations

An SOP register that stays current

July 2026 · 6 min read

Most organisations manage their standard operating procedures as a folder of Word files. It feels controlled - the documents exist, they are named sensibly, they are all in one place. But a folder of Word files cannot answer the two questions that decide whether your procedures are actually under control: is this the current version? and is this SOP still in date for review? The documents sit there silently, and silence is exactly the problem. A procedure that quietly went out of review eight months ago looks identical, in a folder, to one reviewed last week.

The distinction that matters is the one between storing documents and controlling them. Storage is a folder. Control is a register - and a register is a spreadsheet's natural job.

What "controlled" actually requires

A document is controlled when you can prove three things about it at any moment. First, which version is current - so nobody is working from a superseded copy. Second, that it is still in review - so it has not drifted out of date without anyone noticing. Third, its change history - so you can show what changed, when, and who approved it. A folder of files gives you none of these on demand. You have to open each document, read its front matter, cross-check dates, and hope the filenames were kept honest. That is not control; it is an archaeology dig you perform only when an auditor forces you to.

A register turns those three questions into columns that answer themselves. List each procedure once - its ID, title, owner, department, current version and effective date - and the register can take over the arithmetic that a folder leaves to memory.

Review countdowns that compute themselves

The most valuable thing a register does is watch the calendar for you. Every SOP has a review frequency - annually, every two years, whatever your policy sets. From the effective date plus that frequency, the next review date is pure arithmetic, so the register should compute it rather than making you track it in your head.

From there, a live countdown of days remaining tells you what is coming, and the status decides itself: Current when the review is comfortably ahead, Due soon when it falls within your warning window, Overdue the day it passes - colour-coded so what needs attention stands out without anyone reading a single date. Nobody types a status, so nothing is ever stale. The register cannot lie to you the way a folder can, because it is deriving the answer live rather than trusting a field someone updated by hand months ago.

This is the difference between finding out an SOP is overdue because the register flagged it in amber three weeks before, and finding out because an auditor pulled it at random. One is control; the other is luck.

Version and revisions, linked

Version control is where folder-based SOPs quietly fall apart. A file renamed "SOP-07 v3 FINAL (2)" is not version control; it is a cry for help. Proper control needs the version story kept as data - a revision history where each re-issue is one row: the version, the date, what changed and who authored it.

The move that makes this genuinely powerful is linking the two. When the register counts each SOP's revisions back from that history automatically, the register and the change log can never disagree - update the history and the register updates with it. The version story is never lost, never contradicted, and always exactly what an auditor expects to be able to follow: this version, effective this date, changed for this reason, approved by this person. That trail is the heart of document control, and a linked register gives it to you as a by-product of just keeping the log honest.

Reading the whole system at a glance

Once the register computes its own status, a control dashboard falls out of it: how many procedures you hold, how many are current versus overdue, the percentage current, the due-soonest list to work through next, and a breakdown by department so you can see which area is letting its procedures drift. That is your entire document-control health on one page, live - the view a folder of files can never give you without a manual audit.

A folder stores your procedures. A register controls them - computing every review date, counting down the days, flagging what is overdue, and keeping the version story linked so it can never quietly go out of date.

This is exactly the control ISO 9001 clause 7.5 has in mind, but you do not need a certificate to want it. Any business with more than a handful of procedures benefits from knowing, at a glance, that every one of them is the current version and still in date. That is the difference between having SOPs and having them under control - and it is a difference a spreadsheet makes almost for free.