The wrong drawing revision cost a six-figure rework bill. Here's how to set up construction document management — from naming conventions to digital control.
Somewhere on a site in the UK right now, someone is building from the wrong drawing. They don't know it yet. They'll find out in two weeks when the architect visits and notices that the partition layout doesn't match Revision D — because the operative was working from Revision B, which was still pinned to the wall in the site office.
I wish this was hypothetical. It isn't. I've seen it happen on three separate projects I was directly involved with, and I've heard similar stories from dozens of others. The cost of building from the wrong drawing — rip out, rework, material waste, programme delay — typically runs into tens of thousands of pounds. On one project, it was over £120,000 because the error wasn't caught until the M&E first fix was complete and the ceilings were going in.
All of that was avoidable with proper document control. Not complicated document control. Not a dedicated document controller on a six-figure salary. Just a basic system that ensures the right people have the right documents at the right time.
Document control is the process of managing the creation, distribution, revision, and storage of project documents so that everyone is working from the correct, current version.
For a typical small contractor project, the documents that need controlling include:
Drawings. Architectural, structural, M&E, specialist — every drawing issued for construction, tracked by number, revision, and date of issue. This is the most critical element of document control, because errors here result in physical rework. Getting drawing revision management right is fundamental to everything else in the system.
Specifications. The specification documents that define the quality, standards, and performance requirements for the works.
Contract documents. The contract itself, all schedules, the employer's requirements, and any amendments or supplementary agreements.
Correspondence. Letters, emails, meeting minutes, instructions, notices — the paper trail that records decisions, agreements, and disputes.
Submittals and approvals. Product data sheets, samples, test certificates — everything submitted for approval and the responses received. The submittals process generates a significant volume of documents that all need tracking and version control.
RFIs. Questions asked, answers received, linked to the relevant drawings and specifications.
Programmes. Baseline, updates, revised programmes — with clear records of which is the current contractual programme.
Commercial documents. Payment applications, valuations, certificates, variation instructions, quotations, daywork sheets.
You don't need Aconex. You don't need a Common Data Environment with BIM Level 2 compliance. For a small contractor running two or three projects, you need four things:
A drawing register. Every drawing received, with the drawing number, title, revision, date received, date superseded, and current status. When a new revision arrives, the previous revision is marked as superseded and physically removed from the site office (or marked clearly as superseded if you can't remove it). The register is the single source of truth for which drawings are current.
A document filing structure. A logical folder structure — whether physical or digital — that mirrors the project structure. Drawings in one place, correspondence in another, commercial documents in another. Consistent naming conventions so anyone can find anything without asking someone else.
A distribution process. When new documents arrive, who receives them? The site manager needs the drawings. The QS needs the financial documents. The subcontractors need the drawings and specifications relevant to their package. A simple distribution matrix — document type mapped to recipient — ensures nothing falls through the gaps.
Version control. The ability to tell, at any moment, which version of any document is the current one. This is the core of document control. Get this right and most of the other problems go away.
Of all the documents on a project, drawings are the ones where version control failures cause the most expensive problems. Every project must have a drawing register, maintained by one person, updated every time a drawing is issued or revised.
The register should capture: drawing number, title, revision letter or number, date of issue, date received, status (for construction, for information, preliminary, as-built), originator, discipline, and supersession history (which revision it replaced, which revision replaced it).
When a new revision arrives, the process should be: update the register, distribute the new revision to everyone who needs it, and remove or clearly mark the superseded revision. If you're working with paper drawings on site, physically replace them. If you're working digitally, ensure the system shows the current revision prominently and makes it difficult to accidentally open a superseded one.
This sounds basic. It is basic. But I guarantee that right now, on at least half the small contractor projects in the UK, the drawing register is out of date, the site office has superseded drawings on the wall, and someone is about to build something wrong.
The move from paper to digital document management is happening, slowly. Most design teams now issue drawings digitally (PDF, sometimes DWG). Most construction projects still print at least some of those drawings for use on site.
The challenge for small contractors is managing the gap between digital and paper. The architect issues Revision D digitally by email. Someone prints it. Does everyone who needs the new revision know it's been issued? Has the old print on the site wall been replaced? Is the digital copy filed in the right folder with the right naming convention?
A common failure mode: the architect emails a revised drawing to the project manager. The PM forwards it to the site manager. The site manager downloads it to their phone, glances at it, and forgets to print it and replace the version in the site office. The trades continue working from the old version.
Digital document control systems solve this by making the current revision the default — you have to actively look for old versions. But even without a dedicated system, the principle applies: when a new revision arrives, it must physically replace the old one everywhere it's being used.
This needs saying explicitly because I still encounter projects where the entire document record consists of emails. "It was in the email I sent on 14 March" is not a document control system.
Emails get lost. Emails get deleted. Emails sit in one person's inbox and nobody else can find them. Searching for a specific drawing revision in three years of email correspondence is an exercise in frustration. And when the person who received the email leaves the company, the institutional knowledge goes with them.
Every significant document should be filed — in a folder, in a system, somewhere retrievable — not just emailed. The email is the distribution mechanism. The file is the record.
Consistent file naming is a small investment that pays enormous dividends. A file named Architectural-GA-Level2-RevC-2025-10-01.pdf can be identified without opening it. A file named scan_20251001_143722.pdf cannot.
Agree a naming convention at the start of the project and enforce it. For drawings, the convention should include: discipline, drawing number, revision, and date as a minimum. For other documents: document type, reference number, date.
Document control isn't a separate activity — it's a habit built into the way you run the project. Every drawing received gets registered. Every document gets filed. Every new revision gets distributed and the old one gets retired. Ten minutes a day, every day.
At Construction AI, the project management module works as construction document management software with drawing registers, document filing, and revision tracking built into the core workflow. Drawings are registered on upload with automatic OCR extraction of drawing numbers, titles, and revisions. Superseded versions are archived but accessible. And the current revision is always the default view for everyone on the project.
But the tool is secondary to the discipline. If one person on your team is responsible for document control, and they do it consistently, the tool almost doesn't matter. If nobody's responsible, no tool in the world will save you from the wrong-revision problem.
Assign someone. Give them 15 minutes a day. Save yourself six figures in rework.
Stephen Mckenna MCIOB
30+ years in UK commercial construction, from site management to director level. Now building the project management tools he wished he'd had.
Tier-one contractor processes shouldn't only be available to tier-one contractors. Drawing registers, document control, RFIs, programmes, financial tracking — built for how you actually run projects, priced so any construction business can access them. Get started today.
By subscribing, you agree to our Privacy Policy.
A submittal stuck in an architect's inbox for three weeks is a programme delay. Here's how to manage submittals so approvals don't hold up your project.
A programme that sits in a drawer is worthless. Here's how to build a realistic construction programme and use it as a management tool, not a tender box-tick.
A bad RFI sits unanswered for a fortnight. A good one gets answered in days. Here's how to write RFIs that get responses and manage the ones that don't.
Tier-one processes, priced for any size business. Get started today.