Document control
Numbering, revisions, owners and a review cadence — the discipline this site is built on, given away in full.
The discipline of controlled documents, stated plainly. This page carries its own control block because the site teaches the discipline by being it.
Why an uncontrolled document is worse than none
An uncontrolled document cannot be cited, because nobody knows whether the version in front of them is current. That uncertainty makes people ignore the documents and rely on memory instead. A document with a number, a revision and an owner is a fact you can point at; one without them is a suggestion.
Numbering
Every document gets a stable identifier — a prefix for the type and a sequence for the number, like SOP-001. Number documents in a way that survives growth: a prefix per type, a sequential number, and a revision that increments on change. Do not number by department or folder, because departments and folders move.
Revisions
A revision is a dated, recorded change. Bump the revision number in the control block whenever the document changes, and keep a one-line history of what changed and when. The discipline is not the number; it is that a change is visible and attributable.
Owners
One named role owns each document: the person who answers questions about it and approves changes to it. A document owned by everyone is owned by no one. The owner is stated in the control block, and the owner is the person an audit talks to first.
Review cadence
Documents are reviewed on a set date, and off-cycle when something material changes. A review is a check that the document still describes what happens, with the outcome recorded. Standards that publish certification frameworks generally require documented procedures and a review process — a management system standard like the ISO 9001 family is an example of a framework that asks for controlled documents. This site makes no claim that these templates meet any standard; it only uses the same discipline, which is why every page here carries a control block.
These documents are starting structures for you to build on, not professional or legal advice. Anything that will have legal or contractual effect, or that varies by jurisdiction, should be reviewed by someone qualified in the relevant place.
Common questions
- Why do documents need a revision history?
- Because a document without one cannot be cited — nobody can tell whether the version in front of them is current. A number, an owner and a dated revision history mean the person using a procedure knows it is the version that was approved, and the person reviewing it knows what changed since the last one.
- Who should own a controlled document?
- One named role should own each document: the person who answers questions about it and approves changes to it. A document owned by 'everyone' is owned by no one, so it drifts and nobody notices. The owner is stated in the control block at the top of the document.