Revision C is pinned to the wall of the site cabin. Revision E sits in a shared drive folder somebody named FINAL. The steel fabricator priced from D, which was superseded on a Friday afternoon by an email that went to five people, three of whom were on leave. Nothing is wrong with any of those documents. What is wrong is that there is no way, standing on that site, to know which one governs.
Construction document management is the discipline of controlling that: making sure every drawing, specification, method statement, certificate and record has one identifiable current version, that the right people can find it, and that the old versions are visibly marked as superseded. It sounds like filing. Almost every expensive rework story starts with somebody building to a document that had been replaced, so treat it as risk control instead.
How many versions of the same drawing are live on your job right now?
Nobody knows. That is the position on most sites, and it is not a competence problem. Documents multiply because the work demands it. A drawing gets marked up in the cabin, photographed, WhatsApped to the design team, redrawn, issued, printed, and marked up again. Each of those steps is somebody doing their job properly. The result is six artefacts that all look authoritative.
The cost surfaces late and lands somewhere that looks unrelated. A window opening built 150mm off, discovered at second fix. A duct run that clashes with a beam that moved two revisions ago. Both get written up as coordination failures. Both were version control failures with a coordination failure downstream of them.
What counts as a construction document?
More than drawings, and the extra categories are the ones that get lost.
| Category | Examples | Typical failure |
|---|---|---|
| Design | Drawings, models, specifications, schedules | Superseded revisions still circulating |
| Commercial | Contract, subcontract orders, instructions, variations | Amendments held only in email |
| Safety and compliance | RAMS, permits, competence records, statutory notifications | Approved once, never reviewed against changed sequence |
| Progress records | Site diary, photographs, delivery tickets, inspection records | Captured on personal phones, never filed |
| Handover | As-builts, O&M manuals, test certificates, warranties | Assembled retrospectively from whatever survived |
Look at the fourth row. Progress records are the ones that decide disputes, and they are the ones held most casually. A site manager photographs a void in a slab that should not be there, sends it to the project manager, and the conversation moves on. Eighteen months later that photograph is the difference between recovering the cost and absorbing it, and it is on a phone belonging to somebody who has since left. Our piece on the construction site diary covers why this record in particular is worth being strict about.
Why a common data environment is not the whole answer
Most contractors of any size already have one, or have access to the client’s. A common data environment gives you a single repository, a naming convention, a status against each file, and an audit trail. All of that is worth having.
What it does not do is govern the documents that never enter it. The amended subcontract that was agreed by email. The revised sequence that exists as a marked-up print. The certificate the specialist sent to one person. A repository controls what you put in it, and the material that causes trouble is disproportionately the material that stays outside.
So the useful question when reviewing a document management setup is which documents live outside the system, and why. The answers tend to be practical: the environment is slow on a 4G connection, the naming convention takes ninety seconds a file, the subcontractor has no licence, and the mechanical specialist works for four main contractors and will not learn four portals. Each of those has a fix. None of them is fixed by buying something bigger.
Handover is when the debt comes due
Two weeks before practical completion somebody opens the handover folder and finds 3,400 files, no consistent naming, and three folders called Archive. The client’s facilities team asks for the asbestos register and the commissioning certificates for the AHUs. Finding them takes a fortnight of somebody’s life, and the retention conversation gets tense.
The health and safety file that CDM 2015 requires is a legal deliverable, not an administrative courtesy, and it has to carry information useful to whoever alters or demolishes the building later. Assembling it from scattered sources at the end is how it ends up thin. Building it as you go is unglamorous and takes about an hour a week. Our CDM Regulations 2015 guide sets out where that duty sits.
Where does AI make a difference?
In the reading. A construction project generates more documents than any team can hold in mind, and the failures above are all failures of nobody having read two things side by side.
Extraction is the first use that stands up: pulling dates, values, obligations and references out of documents so they become searchable data rather than PDFs. Comparison is the second, reading a revised drawing or specification against the previous one and reporting what changed, including the changes that were never listed on the revision cloud. Classification is the third, filing an incoming document by type, project and package without anyone naming it by hand. That last one matters more than it looks, because it removes the ninety seconds that causes the workaround in the first place. A fourth, retrieval in plain language, is arriving but is still uneven on drawings.
None of that fixes a culture where the real decisions happen on WhatsApp. Technology cannot make a document exist. It can make the documents that do exist far cheaper to keep straight, which is enough to change the arithmetic. We have written more broadly about AI in construction and where the useful applications sit.
Common questions
Is construction document management the same as a common data environment?
No. The environment is the tool; the management is the discipline of what goes in it, who approves it and how supersession is signalled. Plenty of contractors have the first without the second, which is how a well-licensed CDE ends up holding three versions of the same drawing all marked as shared.
What naming convention should we use?
Whichever one your largest client already uses. The convention matters far less than its consistency, and adopting the client’s saves an argument at every issue. If nothing is imposed, the BS EN ISO 19650 field structure is a sensible default because it is what most consultants will already recognise.
How long do construction documents need to be kept?
It depends on the contract and the limitation period that applies to it, so treat twelve years as a working floor for anything executed as a deed and check the specific terms. Health and safety file material stays with the building rather than with you.
Does this matter as much on demolition projects?
More, in some respects. The document set changes faster because the structure changes daily, the compliance paperwork is heavier, and the pre-demolition information you were given is often incomplete. Getting a version-controlled record in place is one of the first things we look at with demolition contractors. The same logic applies to supply chain paperwork, which we covered in subcontractor management software. If you want the wider picture of what software can take off a demolition firm’s desk, our piece on AI in demolition starts with the tender and works outwards.
Can we improve this without buying anything?
Yes, and it is usually the right first move. Pick one live project. Establish which folder is authoritative, mark everything else superseded, and agree one route by which a document becomes current. Most of the benefit arrives in that first fortnight, before any procurement conversation starts.
Start with one project, not one platform
The contractors who get this right are rarely the ones with the most expensive system. They are the ones where everybody on site can answer the version question without ringing the office. That is a low bar, and remarkably few jobs clear it.
If your document set has quietly become a liability, book a discovery call and we will look at it with you.