Document control that survives an audit
Versions, approvals, distribution and retention held as a system, so the copy in use is provably the current one.
- Migration
- Your existing documents, with revision history preserved
- Typical first release
- Three to four weeks from the document register
- Point of use
- Printed copies carry a print date and a check code
- Retention
- Set by your own procedure and your certification scheme
Document control is not a folder structure. It is knowing which revision is current, who approved it, who has the old one, and being able to show all three. We build that as a working system and migrate your existing documents into it with their history intact.
- 01 Enquiry
- 02 Systems audit
- 03 Specification
- 04 Build
- 05 Pilot
- 06 Deploy
- 07 Handover
- 08 Support
Document control that survives an audit sits at step 4 of the build cycle. You receive a working increment you can use.
Version control is not a folder structure
Every organisation we have looked at believes its documents are controlled. Most of them are controlled up to the point of printing.
The master is right. The shared drive is mostly right. Then someone prints the inspection form and pins it to a wall, a supervisor keeps a copy in a binder, and an operator has a photograph of it on a phone. Two revisions later, the wall, the binder and the phone are all wrong, and none of them know it.
That is the finding an auditor writes. Not that you lack a procedure, but that the record in front of them was produced on a superseded form. The system has to reach the point of use or it has not done anything.
It also has to survive people leaving. If the person who knows which folder holds the approved version is on leave, a controlled system is one where that does not matter.
The controls a document system has to enforce
| Control | How it is enforced | Evidence it leaves |
|---|---|---|
| Unique identity | Document number, title and revision assigned by the system, not by a filename. | The document register |
| Approval before issue | A draft cannot become current until the named approver signs it in the system. | Approval record with date and person |
| Controlled distribution | Who holds a copy, in what form, and whether it is controlled or uncontrolled. Printed copies carry a print date and a check code. | The distribution list |
| Supersession | Issuing a revision withdraws the previous one everywhere it was distributed, and marks the archive copy as superseded. | Revision history per document |
| Periodic review | Every document carries a review date and raises its own review task. | Review log |
| Retention and disposal | Records held for the period your own procedure and scheme require, then disposed of on a recorded decision. | Disposal record |
What an auditor can open
The document register
Every controlled document with its number, revision, owner, approver, issue date and review date. One page, exportable.
Revision history per document
What changed, who approved it and when, with the superseded version still retrievable and clearly marked.
The distribution list
Who holds which copy in which form, so a recall is a list and not a search of the building.
The review schedule
What is due for review, what is overdue, and what was reviewed with no change, which is a valid outcome that most systems cannot record.
A migration report
What came across from your old structure, what was found in duplicate, and what had no identifiable owner. Uncomfortable reading and worth having.
The life of one document
- 01
Drafted
Created against a number reserved by the register, so a draft cannot be confused with a live document at any point.
- 02
Reviewed
Comments held against the draft rather than in an email thread that nobody keeps.
- 03
Approved
The named approver decides what becomes current and signs. The system records who, when and which revision, and that record is locked afterwards.
- 04
Issued
Distribution runs to the list. Holders of the previous revision are told, and printed copies are stamped with a print date.
- 05
In use
The point-of-use copy can be checked against the register from a code on the document itself.
- 06
Reviewed again, or superseded
The review date arrives. Either it is confirmed unchanged, which is recorded, or a new revision starts and the cycle runs again.
A Jubail contractor moving to ISO 9001:2026
A maintenance contractor serving plants in Jubail holds several hundred documents on a shared drive, and it wants its management system moved to ISO 9001:2026 before its next surveillance audit.
The first piece of work is a register of what exists. Profiling finds duplicates, forms with no owner, and procedures revised without an approval. That migration report goes to the quality manager before anything moves, because deciding what to leave behind is the contractor's call.
The system goes live with one approval route and a review date on every document. A filtered view lists every document that cites a 2015 clause, with an owner and a date against each line. Forms used on site are printed with a check code.
The contractor holds the register, the migration report, revision history per document and a distribution list that turns a recall into a list rather than a search of the building.
Two moments that test the system
A transition is a document control exercise
ISO 9001:2026 was published on 16 September 2026, with a three-year transition to September 2029. For most organisations the revision itself is modest. The work is finding every procedure, form and record template that cites a 2015 clause, a withdrawn term or an old revision of a linked document. On a shared drive that is a search. In a controlled register it is a filtered list with an owner against each line.
- Every document citing an old clause, listed with its owner
- Each re-issue approved and recorded like any other revision
- The consultancy side of the transition runs through ITF Consult
Unmarked paper is the problem, not paper
A supervisor with a binder can keep the binder. Printed controlled copies carry a print date and a short check code that anybody can look up against the register in seconds. Uncontrolled prints are stamped as uncontrolled when they come off the printer.
- A print date and check code on every controlled copy
- Uncontrolled prints marked at the printer
- Superseded copies traced through the distribution list
What buyers ask about document control
Will this satisfy the documented information clauses of our standard?
It is built to what those clauses ask for: identification, approval before issue, control of distribution, control of changes, retention, and protection of records. Whether your whole system passes depends on what your people actually do with it, which no software decides. What we can say is that the evidence will exist and be retrievable on the day.
How long do we have to keep records?
Set by your own procedure and your certification scheme, and those are the two places to look rather than a general rule. We build the retention period as a configurable value per document type, because it varies by record and because the answer changes when your scheme changes. If somebody quotes you a single national number for all records, ask them for the source.
Can we migrate what we already have?
Yes, and the migration is most of the work. We profile what exists first, which usually finds duplicates, documents with no owner and revisions that were never approved. You get that report before the migration, because deciding what not to bring across is a decision only you can make.
What drives the cost?
The size and state of your existing document set, the number of document types with genuinely different rules, whether external parties need controlled access, and whether approvals need to reach people outside the system. A clean set of two hundred documents with one approval path is straightforward. A twenty-year shared drive is a project.
Do we need this if we already use a cloud drive?
If your drive enforces approval before issue, records who holds a copy, withdraws superseded revisions and raises review dates, then no. Most do none of those four. The honest test is to pick a document and try to prove, from the drive alone, who approved the current revision and when.
Usually part of the same scope
Workflow automation
Review dates, approvals and the chasing that makes them happen on time.
Read moreDigitalAudit and inspection apps
Making sure the form being filled in on site is the current revision.
Read moreConsultDocument control, written
The master list, the procedures and the retention rules themselves, with ITF Consult.
Read moreConsultThe ISO 9001:2026 transition
What changed in the standard and how a working system moves across.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Start with the document register
Before anything is built we produce a register of what you actually hold. It is a short piece of work and it is usually the moment the scale of the problem becomes clear.