Is this the current drawing? Document control explained

Picture a site team about to pour a slab. The drawing in the site office shows one set of openings, but the designer changed them last week. Which version is right, and can anyone prove it?
Document control exists to answer that question. It is the set of rules and records that shows which version of each project document is current, what it can be used for, who approved it and who has received it.
The main point: in NURU's view, good document control depends less on software than on a few agreed rules, followed every time a document moves. Archived UK guidance from 2020 makes a similar point about information systems: develop the workflows first, then choose the technology to support them.
Why it matters
Unreliable information can be expensive. A 2021 study by Autodesk and the consultancy FMI estimated that decisions based on poor data cost the global industry $88.69 billion in rework in 2020. Its survey of over 3,900 professionals supplied one input to that model, the 33% share.
That figure is an estimate from a study released by a software company, and it covers project data broadly rather than document control alone. It is best read as a sign of scale, not a measure of what document control saves.
The five working parts
1. The document register
The register is one list of every project document, with its number, title, current revision, status and date. It is the first place to check before anyone relies on a drawing.
If the copy on your desk shows revision B and the register shows revision C, you know to stop and get the new one. The status column then tells you whether revision C can be built from or is still out for comment.

2. The naming convention
A consistent number lets people identify a document without opening it. It also helps stop the same file circulating under several names.
Many projects combine codes for the project, originator, document type and sequence. The exact structure is agreed for each project.
3. Revision control
Revision control is a clear rule for when a revision changes, with a record of what changed. It matters because teams design and build from each other's information.
Suppose an architect moves a wall in revision C of a floor plan. If the services engineer is still routing ducts from revision B, both can work carefully and their work still will not fit.
4. Status codes
A status code shows what a document is fit for, such as information, review, approval or construction. This is separate from its revision: the latest revision of a drawing may still be out for review and not yet fit to build from.
5. Transmittals
A transmittal records what was sent, to whom, when, at which revision and for what purpose. Together, transmittals form a history of what was issued and, where receipt is acknowledged, what was received.
Suppose a subcontractor says it never got a revised drawing. A transmittal log can show whether the drawing was issued and whether anyone confirmed receipt, without a search through old email threads.
How a drawing moves through review
The details vary, but review cycles tend to follow a similar route. A drawing may go round the review loop several times before it is approved.

NURU recommends changing the register when the document moves, not at the end of the week. Once a new revision is issued for use, the older one should be withdrawn or clearly marked as superseded.
What poor control can look like
These are illustrative scenarios, not accounts of real projects.
An old set stays on the wall. A crew installs work from a superseded drawing, and it has to be taken out and redone.
A revision goes out by email only. A supplier prices the earlier specification, and the difference surfaces at delivery.
An approval cannot be traced. A client queries a change months later, and nobody can show who approved it or why.
The register is updated on Fridays. For the rest of the week it cannot be trusted, so people stop checking it.
Where ISO 19650 fits
ISO 19650 is an international series of standards from the International Organization for Standardization (ISO) on managing information about built assets. ISO 19650-1 gives recommendations for a framework that includes exchanging, recording, versioning and organising information. A revised edition is in draft.
It helps to keep three things apart:
General practice. Registers, transmittals and review loops are common document control tools, whether or not a project adopts ISO 19650.
ISO 19650 principles. Guidance on the standard describes information moving through four states in a common data environment (CDE), the combination of technical solutions and workflows a project uses to manage and share information: work in progress, shared, published and archive.
Project procedures. The file names, status codes and approvers on your project are set by that project's client, contract and procedures.
Status codes show why the difference matters. Codes such as S3, for review and comment, come from the UK National Annex to BS EN ISO 19650-2, and archived UK guidance from 2020, written to the 2018 Annex, says codes can be expanded or excluded when documented and agreed. So check your project's requirements instead of assuming one set applies everywhere.
A simple test
Pick any drawing on your project and ask three questions:
What is the current revision?
Who approved it, and when?
Who has received it?
If a new team member can answer within a minute or so, the system is working. If not, start by writing down the rules and naming one person responsible for the register. In NURU's view, that will usually do more than changing the software.
This briefing is a general introduction to common practice. Requirements differ between clients, contracts and projects, and it is not project-specific, contractual or legal advice.
Sources
ISO 19650-1:2018, International Organization for Standardization
Guidance Part C, Edition 1, UK BIM Framework, September 2020, archived
Common Data Environments, Dr Stephen Hamil, NBS, 5 April 2019
Autodesk and FMI study release, Autodesk, 14 September 2021
Cover photo: Marina Zvada, Pexels



Comments