Guide · Drawing revision control
The drawing changed.
The site never found out.
On most jobs the drawings will be revised more than once. The danger is rarely the revision itself. It’s the gap between a new revision arriving and everyone on the job actually working from it. A revision that sits in one person’s inbox is, on site, a superseded set being built to as if it were current.
Written by Brad Caldon, Founder, VIABUILD. Licensed builder (NSW) · Registered Building Practitioner (Class 1 to 9) · B.Construction Management (Hons)
01 / The basics
In plain English
Drawing revision control is the discipline of making sure there is one current set of plans for a job, that everyone who needs it is working from that set, and that the old set is clearly retired the moment it’s replaced. It sounds obvious. It is also one of the quietest ways a job goes wrong.
The reason it goes wrong is that a revision has to travel. An engineer or designer issues an updated drawing, and from there it has to reach the estimator, the supervisor, the relevant trades and, where steel or joinery is being made off site, the fabricator. Each handover is a place the revision can stall. The most common failure isn’t a bad drawing. It’s a good drawing that never finished the journey.
A revision has to clear three steps before it’s safe to build to:
- Logged: someone records that a new revision exists and which set it replaces.
- Published: the new set is put where everyone reads from, not emailed to one person.
- Notified and retired: the field is actively told it has changed, and the old set is marked superseded so it can’t be picked up by mistake.
Miss any one of those and you can have the latest drawing in the business and the wrong drawing on the saw bench at the same time. The set is only as current as the last person to receive it.
02 / The reality
Where builders get stuck
The revision that stays in an inbox
An updated drawing lands with one person and goes no further. There’s no step that takes it from “received” to “live for everyone”, so it quietly sits while the job keeps moving on the old set.
Two sets in circulation
Once a revision reaches some people and not others, two versions are live at once. Nobody decides to build off the wrong one. They just never learn there’s a right one.
No single owner of “current”
When everyone assumes someone else rolled the revision out, no one does. Without a named owner of the current set, propagation depends on goodwill and memory.
The field is never told
Filing a new revision is not the same as telling the people building to it. If the supervisor and trades aren’t actively notified, a new set in the system still changes nothing on the ground.
Email as a filing system
Drawings sent as attachments scatter across inboxes with no record of who has the current one. The newest version is whatever happens to be open on someone’s screen.
Caught by chance, not control
The mismatch surfaces because someone happens to ask the right question, not because the system flagged it. A near-miss that depended on a sharp supervisor was never actually under control.
03 / The fix
A workflow that holds up
- 01
Give the current set one owner
Name the person responsible for logging every revision and rolling it out. One owner removes the “I assumed someone else had it” gap that lets revisions stall.
- 02
Publish to one place everyone reads
Put the current set where the office, supervisor, trades and fabricators all go to look. If the latest drawing only lives in an inbox, it isn’t published.
- 03
Stamp and supersede the old set
The moment a new revision goes live, mark the previous one superseded. A retired set that still looks usable is the one that ends up on the bench.
- 04
Notify the field, don’t just file it
Actively tell the people building that the set has changed and what changed. Filing the revision is record-keeping; notifying the field is what actually moves the job onto it.
- 05
Confirm it landed
For changes that affect work already being set out or fabricated, get acknowledgement that the right people have the current set. Especially for off-site work like steel and joinery, where a wrong detail is cut before anyone sees it.
- 06
Make the wrong set hard to use
The strongest control isn’t a reminder, it’s a system where the superseded set is obviously retired and the current one is obvious. Build it so working off the old drawing takes effort, not so avoiding it does.
04 / The tooling
How software helps
Revision control is a visibility and control problem, not a drawing problem. The drawing is fine. What fails is the path from “revision received” to “revision live for everyone”, and that path is usually a chain of manual handovers held together by individual diligence. The first time someone is busy, on leave or simply forgets, the chain breaks and nobody can see that it has.
Software helps by removing the manual relay. One current set, held in one place, that every role works from. When a revision is loaded, the previous version is flagged superseded automatically rather than left looking valid, the people on the job are notified that it changed, and there’s a record of which revision was current when, so a question can be answered by checking rather than by memory. That turns “did the latest set reach site?” from a hopeful assumption into something you can actually see.
05 / In practice
Where VIABUILD fits
VIABUILD is built around one current set, visible to the whole job.
The principle VIABUILD works to is single source of truth: the office, the supervisor and the trades read from the same current plans rather than from whatever happens to be in an inbox. When the field works from the platform instead of a stack of emailed attachments, the gap where a revision goes missing has nowhere to hide.
ViaSite puts the current set in the supervisor’s hand on site, alongside the daily diary, photo logs and defects, so the people building are reading from the same place the office publishes to. Tie that to a real schedule and the work that depends on a drawing is connected to the drawing itself, not tracked separately and hoped to stay in step.
- One current set, read by every role
- Superseded sets clearly retired
- Current plans in the field via ViaSite
- The field notified, not just the file updated
- A record of which revision was current when
- Plans connected to the work that depends on them
06 / FAQ
Common questions.
It’s the practice of keeping one current, authoritative set of plans for a job, making sure everyone who needs it works from that set, and clearly retiring the old set when it’s replaced. The hard part is rarely producing the revision. It’s getting the new revision to reach every person building to it, and making sure the superseded set is taken out of play.
It should be one named person’s job. The most common failure is a revision that reaches one inbox and stops, because everyone assumed someone else would publish it and notify the field. Giving the current set a single owner, with a defined path from “received” to “live for everyone”, removes that gap.
Usually because the new revision was filed but the field was never actively told, or because it reached some people and not others, so two sets were live at once. If the old set still looks usable and nobody is notified of the change, the people on site keep building to what they have, with no signal that it’s no longer current.
More often it’s a process gap than a tool fault. A revision can sit unsent in any system if there’s no defined step that takes it from received to published to acknowledged. Software helps most when it closes that gap by design, holding one current set, flagging superseded versions and notifying the field, so propagation doesn’t depend on someone remembering to do it.
About the author
Brad Caldon
Founder, VIABUILD
Brad Caldon is the founder of VIABUILD and a builder and property developer with nearly two decades across residential construction and development. He holds a NSW Home Builder Licence, is a Registered Building Practitioner across Class 1 to Class 9 buildings, and holds a Bachelor of Construction Management (Building) (Honours) from the University of Newcastle.
More about VIABUILD →07 / Keep reading
Related guides & features
See it on your own jobs.
Start with 7 days free: the full platform, your real data. $199 for your first month, then $435/mo. Month-to-month, no lock-in.