Drawing version control: how the wrong revision gets built, and the discipline that stops it

Every builder has walked onto a site and found two versions of the same sheet pinned to the wall, one of them out of date. The frame is up, the setout is wrong, and the question is not who drew the wrong plan — it is who issued it, when, and to whom. Version control on a residential job is not a software problem. It is a transmittal problem, and it is solved with a register, a distribution list and the discipline to withdraw what has been superseded.

The mechanism is straightforward. A drawing is only the current revision once it has been formally issued, recorded against a transmittal, and removed from circulation in its previous form. Until that happens, it is just a file. The site will build whatever it was last handed, and if the last thing handed over was a marked-up PDF in a message thread, that is what gets built.

The mistakes that cost the most are not exotic. They are superseded sheets left in the site set, marked-up PDFs treated as instructions, revisions issued without a transmittal, and subbies working from a copy nobody in the office knows exists. None of those require a document management system to fix. They require a rule about how drawings leave the office and how superseded sheets leave the site.

Why a revision is not current until it is transmitted

Designers revise drawings for all sorts of reasons: a client change, a council condition, a structural amendment, a services clash resolved late. The revision itself is just a file sitting in someone’s system. What turns it into a build instruction is the act of transmission — a numbered record that says this sheet, at this revision, dated this day, replaces the previous one, and these are the people who have received it.

That record is what you rely on later. If a subbie builds a wall in the wrong position because they worked from an old sheet, the first question at the post-mortem is what they were issued and when. If you cannot produce a transmittal, you cannot show that the correct revision ever left your office. The conversation stops being about the drawing and starts being about your administration of the job.

The same principle applies to every downstream document that references a drawing: the scope of works, the schedule, the shop drawing register, the variation. Each of them should point at a revision, not at a drawing name. A scope that says “per architectural sheet” without a revision is a scope that will be interpreted against whatever sheet the subbie happens to be holding.

How the wrong revision actually gets onto site

In practice, wrong revisions arrive through a small number of well-worn routes. Recognising them is most of the fix, because each route has a matching control.

Superseded sheets that were never withdrawn

The most common route is the simplest. A revision is issued, a new sheet is printed, and the old one stays where it was. It might be in the site office set, in the lunch room, in a subbie’s folder or on the wall of the shed. The new sheet is technically correct and the site is still building the old one, because nobody took the old one away.

Printing a new sheet is not version control. Withdrawing the old one is. If the previous revision is still physically present on site, you have created two current revisions and no way to tell which is which without reading the title block.

Marked-up PDFs sent by message

A designer or site manager marks up a PDF with a change, photographs it, and sends it to a subbie by message. The subbie builds to the markup. Weeks later, the formal revision is issued and it differs from the markup, usually in a detail nobody flagged. The subbie has now built to an instruction that was never a drawing, was never registered, and cannot be found in the project record.

Marked-up PDFs are useful for coordination, but they are not build instructions. If a markup represents a real change, it has to become a revision and be transmitted like any other. If it does not, it has to be withdrawn in writing before anyone builds to it.

Revisions issued without a transmittal

An email with a drawing attached is not a transmittal. It does not say what the revision supersedes, it does not list the sheets, it does not record who received it, and it usually does not survive the next reply-all. When a revision is issued this way, the site often ends up with the new sheet and no idea which old sheets it replaced. The register, if there is one, falls out of step with reality within a week.

Copies that nobody in the office knows about

Subbies print their own sets, suppliers work from drawings emailed to their estimator, and consultants issue to each other directly. Each of those copies is a potential current revision that your register does not know about. The distribution list is the control: if someone is not on it, they should not be receiving drawings, and if they need drawings, they go on the list.

What a transmittal has to say to be worth anything

A transmittal does not need software. It needs to be a numbered, dated record that a person can read months later and reconstruct what happened. At a minimum it should state the project, the transmittal number, the date, who issued it and who received it. It should list every sheet being issued, each sheet’s revision and date, and the sheets or revisions it supersedes.

It should also state the purpose of the issue. A drawing issued for coordination is not the same as a drawing issued for construction, and the two should not be confused in the record. A coordination issue that gets built because it was in the same folder as a construction issue is a version error dressed up as a communication error.

Keep the transmittals in one place, in sequence, and treat them as the project record. When a dispute arises about what was issued and when, the answer is in the register, not in someone’s memory of a phone call. If you are running a small renovation and think this is overkill, consider the alternative: a variation claim built on a marked-up PDF and a verbal instruction, resolved on the basis of who has the better paperwork. The answer to that is to have the paperwork.

The site set is the only set that matters

Every project has a master set. What matters is whether the master set is on site, current, and the only one anyone builds from. The practical rule is that the site office holds one controlled set, marked with its revision status, and that set is reconciled against the transmittal register on a regular cycle.

Everything else is a copy. Copies should be traceable back to the controlled set, and any copy that cannot be traced should be treated as suspect and replaced. That includes the set in the ute, the set in the shed, the set on the wall and the set the estimator printed six weeks ago.

Superseded sheets should be stamped superseded, filed separately from the current set, or destroyed. Filing them separately matters, because you may need them later to show what was issued at a point in time. Destroying them without a record does not, because it removes the evidence you might need to defend a claim.

A weekly discipline that costs nothing

Version control fails quietly. Nobody notices the superseded sheet until something is built to it. The fix is a short, regular check that catches drift before it becomes a defect, and it does not need a licence or a subscription.

Walk the site set against the transmittal register. Confirm every sheet in the set has a matching register entry. Confirm no superseded sheets are still pinned up or in circulation. Confirm every markup issued by message has either become a revision or been withdrawn. Confirm every subbie on site this week is on the distribution list and can name the revision they are building to.

That last question is the useful one. If a subbie cannot tell you which revision they are working from, they are working from whatever they were last handed, and you have found a version error before it was built. The same instinct applies to the other technology decisions on a residential job: the point is to make the correct thing the easy thing, whether that is drawing control or the software your team actually uses, which is covered in our article on getting your team to use the software.

Worked example: a first-floor setout in western Sydney

A builder in western Sydney is doing a two-storey addition. The structural drawings are revised late in the piece to move a beam, and the revision is sent by email to the site supervisor with the note “see attached”. The supervisor prints the new sheet and pins it in the site office. The old sheet stays where it was, on the wall of the shed, because nobody thinks to take it down.

The carpenter is working from the shed copy. The setout for the first floor follows the superseded beam position. The frame goes up, the floor is laid, and the error is not picked up until the services rough-in, when the plumber finds the beam where the new drawing says it should not be. By then the floor is on, the ceiling framing is ordered, and the fix involves propping, cutting and re-framing.

The cost is not just the carpentry. It is the engineer’s inspection, the delay to the trades behind the carpenter, the variation to the client and the argument about who pays. The builder’s position depends entirely on whether they can show that the revised sheet was transmitted, registered and that the superseded sheet was withdrawn. An email with the note “see attached” does not do that. A transmittal would have, and a returned-and-destroyed rule for the old sheet would have stopped the carpenter from ever seeing it.

The lesson is not that the builder needed software. It is that the revision was issued without a record, the superseded sheet was never withdrawn, and the site was left with two current revisions. Any one of those three would have been survivable. Together they produced a defect that surfaced at the worst possible time.

Choosing controls that suit a residential job

Not every job needs the same level of control. A single-dwelling renovation with one designer and three trades can run on a transmittal register in a spreadsheet, a controlled site set and a weekly check. A project with multiple consultants, a certifier, a principal contractor and a dozen subbies needs the same things, applied more strictly.

The variable is not the size of the project. It is the number of people who can issue a drawing and the number of people who can build from one. Every additional issuer is a new opportunity for a revision to enter circulation without a record. Every additional builder is a new opportunity for a superseded sheet to survive on site.

Where a job does justify more tooling, the tool should follow the discipline rather than replace it. A document management system that nobody uses is worse than a spreadsheet that everybody does, because it creates the appearance of control without the practice. If you are weighing up whether to change systems, the same logic that applies to estimating applies here, and our article on estimating software switching costs sets out how to think about the real cost of a changeover.

Where version control sits in your obligations

Version control is not a standalone legal duty. It sits underneath several duties that are. Building work has to comply with the approved plans and the relevant standards, and the principal contractor has to manage the site and the people on it. If the site is building from a superseded drawing, both of those are at risk, and the record you keep is the evidence that you managed the risk.

The same principle runs through other regulated areas of residential work. Flood risk management, for example, depends on the site being built to the approved levels and the current flood planning requirements, and the NSW Government’s flood risk management manual sets out how those requirements are framed. If a revision changes a floor level, the version control failure is also a compliance failure.

Small-scale technology certificates under the renewable energy target work the same way: the certificate depends on the system that was actually installed matching what was designed and claimed. A drawing revision that changes the array layout, the inverter position or the cable route has to flow through to the paperwork that supports the claim. The Clean Energy Regulator’s guidance on small-scale technology certificates is the reference point for what has to match.

None of that is a reason to buy software. It is a reason to treat the transmittal register as part of the project record, alongside the approvals, the inspection records and the certificates. If it is part of the record, it gets maintained, and if it gets maintained, the site builds the current revision.

What to do on Monday

Start with the site set. Take it down, sheet by sheet, and check every revision against the register. Anything without a register entry is suspect. Anything superseded comes out of circulation and is stamped or filed separately. Anything that was issued by message and never formalised is either turned into a revision or withdrawn in writing.

Then fix the front end. Every drawing that leaves the office goes with a numbered transmittal, and every transmittal goes in one place. The distribution list gets updated to match who is actually on site. The weekly check goes into the site routine. If you want the background on how this fits with your continuing professional development as a NSW builder, the PointCPD guide to how NSW builder CPD works explains the framework, and the course catalogue covers the practical side of site management and technology.

Version control is unglamorous and it is the cheapest insurance on the job. The alternative is a defect that surfaces at fit-out, a variation argument you cannot win, and a subbie who genuinely believed they were building the current drawing. The discipline that prevents it is small, repetitive and entirely within your control.

Questions builders ask

• Laser Scanning
• Renovations
• Technology

Published 6 July 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.