Ask ten project managers where their last job lost money and at least four of them will say "the drawings". Not the structure itself — the management of drawings. Someone built to Rev B when Rev C had been issued. A subbie priced off a superseded DA set. A certifier signed off on a revised detail that nobody had redlined into the site copy. Every one of those is a document control failure, and document control failures are expensive in ways that are hard to unpick after the fact.
Document control is the least glamorous discipline in construction management and one of the most financially significant. This article walks through what document control actually means, the five principles that matter in practice, and how to build it into a real workflow without adding so much friction that people just go around it.
What document control is (and isn't)
Document control is the set of processes that make sure the right version of the right document reaches the right person at the right time, with a clear trail of who approved it, when, and against what.
It is not filing. Filing is where documents go to die. Good document control is actively pushing current documents to the people who need them, suppressing the ones that have been superseded, and keeping a clean approval and audit trail.
It applies to:
- Design documents (drawings, specifications, schedules, BIM exports)
- Contract documents (contracts, variations, schedules of rates)
- Quality documents (ITPs, checklists, test results, sign-offs)
- Submittal documents (shop drawings, product data sheets, samples)
- Construction records (daily diaries, toolbox talks, incident reports)
The rest of this article focuses on drawings and design documents, because that's where most of the pain is. The principles generalise.
The five rules of good document control
1. There is only ever one "current" version
On any project, on any given date, there is exactly one version of each document that is the live authoritative version. Everybody — the owner, the builder, the consultants, the subcontractors, the certifier — must be able to see which version that is without asking anyone.
The two-second test: can a subcontractor on site, on a phone, identify the current revision of a given sheet without calling someone? If yes, you have document control. If no, you don't.
2. Superseded versions are marked, not deleted
You don't throw old revisions away. You keep them, but you mark them clearly as superseded, and you make the current one the default view. That way, if a dispute comes up ("we priced Rev A, not Rev B"), you can still produce Rev A — but nobody's accidentally building to it.
The common failure mode: people email PDFs around, and the "current" version exists only in the latest email. Six months later, nobody can find the definitive file.
3. Every change has a trail
Who issued it, when, what changed, who approved it. For a drawing revision, that means a revision number, a date, a description of changes, and an approver. For a contract variation, it's a variation number, a price impact, an approval, and a date.
This isn't bureaucracy — it's the difference between winning and losing a progress claim dispute, an insurance claim, or a defect liability argument. Without the trail, every change becomes a he-said-she-said.
4. Access is explicit, not assumed
Not everyone should see every document. Commercial terms between the head contractor and the client aren't the subcontractor's business. Draft designs that haven't been issued aren't the certifier's business. Access should be granted explicitly to documents or groups of documents, and it should be easy to audit who can see what.
The accidental-access failure (giving the whole project team access to a contract negotiation folder) is one of the most expensive mistakes you can make. It's also one of the easiest.
5. The current version is pushed, not pulled
If your document control process depends on everyone checking a folder regularly to see what's new, your document control process will fail. People are busy. They will miss updates. They will use yesterday's drawing because they didn't check the folder.
Good document control pushes — notifies users by email (or app notification) when a relevant document changes, and ideally with a summary of what changed, not just a "Revision C issued" link.
Where most teams break document control
Three places, consistently.
Email as the document repository. PDFs attached to threads. "Latest version" meaning "the file in the most recent email I remember". This works fine with 10 documents. It breaks catastrophically at 100.
Cloud drives with no versioning discipline. SharePoint, Google Drive, Dropbox — fine as a file store, but they don't enforce revision discipline. Anyone can upload anything. "Which of these three files is the current one?" becomes a regular question.
PM tools that treat drawings as generic files. Plenty of project management platforms let you upload PDFs, but treat them like any other document — no revision chain, no supersession, no approval trail, no discipline-level grouping. That's not document control; it's cloud storage with UI.
What good document control tooling looks like
A tool that actually helps with document control — rather than just making you feel organised — should do six things.
Revisions as first-class objects. When you upload a new version, the old one should be automatically superseded, the new one marked current, and the full history visible. You should never have to rename files to keep track.
Automatic comparison between revisions. Knowing a new revision has been issued is step one. Knowing what changed is what prevents people building to the wrong version. AI-powered comparison (vision models that diff old vs new pages) is now a viable default for this, and it's far less noisy than pixel-diff tools.
Approval workflows built in. Every document that needs to be signed off should have a visible approval chain — who approved it, when, and any comments. This should be queryable later.
Granular sharing. Share an individual drawing, a discipline (e.g. all hydraulic sheets), a project, or your whole workspace. Different stakeholders should see different slices without you having to build custom folders for each one.
Notifications that summarise, not just alert. "A revision was uploaded" is weak. "Rev C supersedes Rev B on S-100: slab thickness changed from 200 to 250 mm" is strong.
An audit trail you can actually use. Every upload, download, approval and view should be logged, and you should be able to answer "who last saw this document?" in a few clicks.
How Doclio handles document control
Document control is a significant part of what Doclio was built to do.
Revisions. Every drawing has its own revision history. Upload a new revision and the previous one is automatically superseded but retained. You can view the revision chain, see who uploaded each version, and open any historical version if needed.
AI revision comparison. When a new revision lands, Doclio runs a Claude Sonnet vision model over the old and new sheets in the background and pre-computes a categorised summary of what changed — "design changes" separated from "title block only" edits. By the time you open the drawing, a structured summary is cached and ready. No manual pixel-diff review.
Approvals. The Approval annotation type has a full workflow: add approvers, they get tokenised email links, they approve or reject on a public page without needing a Doclio account, and the approval trail is kept on the annotation itself. Reporting on outstanding approvals is built in.
Granular sharing. Share at the project level, discipline level (all architecturals, all hydraulics), individual drawing level, or via a tag. Different external users can have different access — viewers, commenters, editors.
Notifications with context. When a drawing is added, updated or deleted, notifications include the drawing number and title. Revisions trigger a summary. Digest emails batch these for users who prefer once-a-day rather than per-event alerts.
Audit trail. Every report, drawing, approval and annotation keeps a log of who did what and when. The external report viewer also logs who opened a report and when — useful for demonstrating that the client genuinely received the issued version.
Starting small
You don't have to boil the ocean to get document control right. Start with three changes:
- Move drawings off email into a tool with revision versioning. Anything is better than attachments.
- Define who approves what. Even a simple "I approve all structural revisions before they're issued" discipline is better than nothing.
- Make sure the team knows where the current version lives. One URL, one rule: "always check Doclio (or your tool of choice) before you cut anything".
Those three alone will prevent most of the expensive mistakes.
---
Run your next project in Doclio — proper revision control, approval workflows and AI-powered drawing comparison, starting from a free Starter plan.