One Current Version: Document Control for Construction Drawings, Explained

Who This Is For

Anyone who has ever asked “wait, which set are you looking at?” on a call — project managers, site superintendents, and the office staff who keep reissuing the same drawing.

The Problem in One Sentence

A drawing gets revised, but the old copy is still sitting on someone’s desk, tablet, or truck dash — and nothing tells them it’s out of date.

Why This Keeps Happening

Email as a distribution system. Every revision goes out as an attachment, to whoever happened to be on the distribution list that week. There’s no single place that’s authoritative — there’s just the most recent email someone remembers to check.

Printed sets that outlive their revision. A set printed for a site walk two weeks ago doesn’t know it’s obsolete. It looks exactly as authoritative as the current one, because paper doesn’t carry a status.

No clear signal for “this one is now out of date.” Even digital distribution usually fails here — a PDF named Drawing-A101_v3_FINAL_reallyfinal.pdf gives no indication, at the moment someone opens it, whether a v4 exists somewhere else.

The pattern underneath all three: revision control is being handled by human memory and filenames, not by the system.

What “One Current Version” Actually Requires

A single hosted source of truth. Not a shared folder full of FINAL_v3 files with a fourth person’s edits layered on top — one location that is unambiguously the current set, for everyone who touches the project.

Permissions that let the field view and mark up, not silently fork. Field staff need to annotate, measure, and comment on drawings without that turning into an untracked personal copy that diverges from the source. The distinction matters: markup should attach to the current drawing, not replace it with a private variant.

A visible revision indicator on every drawing, every time it’s opened. Not buried in a properties panel — visible at the point someone is about to act on the drawing, so “is this current” is never a question that requires opening a second file to answer.

What Changes Once It’s Live

• Markups and measurements sync back to the office in real time, instead of arriving as a photo of a printed sheet with handwriting on it.
• RFIs and change orders reference the actual current drawing, not a PDF that was current when the RFI was written and isn’t anymore by the time it’s answered.
• “Who has the current set?” stops being a daily phone call. The answer is: everyone, because there’s only one set to have.

Getting There Without a Rip-and-Replace

Most construction companies don’t need a new platform bought from scratch — they need the platform they already have (or a reasonably priced one) configured so that revision control is structural, not optional. That means:

• Defining who can publish a new revision, and making sure it’s a small, accountable list.
• Migrating the live project set first, not the full historical archive — closeout retention is a separate problem from active revision control.
• Setting the permission model before training anyone, so the first thing users experience is the correct workflow, not a workaround they later have to unlearn.

The Bottom Line

“One current version” isn’t a feature you buy — it’s a property of the workflow. A platform that supports revision control still produces “which set are you looking at?” moments if publishing isn’t locked down, permissions allow silent forking, or the revision status isn’t visible at the point of use. Fix the workflow, and the tooling underneath it becomes a much smaller decision.

This is a service we deliver. If this article describes your operation, skip the DIY weekend — see how we build it → or send the brief →.