Document control system: keeping one version true

A document control system is the set of rules and tooling that guarantees the procedure someone is following is the current one. It matters wherever a stale document causes real harm: a superseded work instruction on a production line, a withdrawn safety procedure still pinned to a wall, a price list from last year quoted to a customer, a policy an auditor reads that contradicts what the team actually does.

Most small companies do not need the full apparatus. What they need is the small part of it that prevents the specific failure they keep having — usually two people working from different copies of the same file.

What document control has to guarantee

• One authoritative location per document. Not a master copy plus convenience copies — the convenience copies are the problem.
• A version identifier visible on the document itself, not only in a file name or a system.
• An owner: the role accountable for the content being correct.
• An approval record: who approved this version, when, and against what.
• An effective date, and where relevant a review date — a document with no review date has no accountability attached to its accuracy.
• A change history: what changed between versions and why, in a sentence a reader can use.
• Controlled withdrawal: superseded versions retrievable for the retention period, but never mistakable for current.
• A distribution rule: who must be told when a version changes, and how you know they were.

The single most common failure is uncontrolled copies. Someone downloads a procedure to their desktop, emails it to a supplier, prints it for a workstation — and each copy becomes a version that ages independently. Every piece of document-control practice exists to make the authoritative copy easier to reach than a private one.

Building the minimum viable version

1. Decide what is controlled. Not everything: name the categories where a stale version causes real harm — procedures, work instructions, policies, specifications, templates that leave the building.
2. Give each controlled document an identifier, an owner and a version, and put all three on the document itself.
3. Put them in one place with a predictable structure, and delete every other copy you can find.
4. Define what approval means for each category, and record it — even if approval is one named person marking a version approved.
5. Number versions simply. Minor for corrections, major when the meaning changes and people need to re-read.
6. Write a one-line change note with every version. It is the field that saves the most time later.
7. Set review dates on the documents that decay — anything tied to a tool, a supplier or a regulation — and treat a missed review as a defect.
8. Publish the link where the work happens, so nobody needs a private copy in order to be efficient.

How much control is enough

Formal standards demand a great deal: controlled distribution, acknowledgement that recipients have read the current version, periodic review cycles, audit trails that survive scrutiny. If you are certified or working towards it, buy a system built for that and follow its rules. If you are not, the cost of the full apparatus is usually higher than the risk it removes — and heavy control that people bypass leaves you worse off than light control they follow.

In Ettex, the controlled document itself lives in Ettex Docs: one shared location rather than copies, version history where you can see what changed and return to any earlier state, threaded comments with @mentions so a correction is raised against the paragraph it concerns rather than in a separate email, and share links so the current version is one click from wherever the work is. Where approval must be more than a status — a safety procedure, a customer-facing specification — Ettex Signature records a real signature with an audit trail. A register of controlled documents, with owner, version, effective date and review date as fields you can filter and sort, fits Ettex Records.

The boundary, stated plainly: Ettex is not a controlled-document system in the compliance sense. There is no enforced approval workflow between named reviewers, no automatic review reminders, no read-and-understood acknowledgement tracking, no controlled distribution or automatic withdrawal of superseded versions, and nothing here is certified against a standard. It gives you one location, real version history, comments and signatures — enough for most small companies, and not enough for a regulated one.

Where document control breaks

• Version numbers in file names — "procedure_v3_final_FINAL2.docx" is the sound of a system failing.
• A master copy nobody can find quickly, which guarantees private copies.
• No owner, so nobody notices when the document stops matching reality.
• Approval by email, where the approved attachment has since been edited twice.
• Superseded versions left in the same folder as current ones.
• Review dates set and never honoured, which is worse than not setting them because it implies a check happened.
• Everything controlled, so control becomes an obstacle and people route around it entirely.

Document control is one authoritative copy, a visible version, a named owner and a change note. Add ceremony only where a stale document would actually cost you something.