Document Control in Construction: The Cost of Working From the Wrong Drawing

It’s 7:15am on a multi-level residential job in Parramatta. The formwork crew has been setting out a core wall since 6am, working off a printed A1 sheet pulled from the site office two weeks earlier. At 7:15 the structural engineer walks the pour and stops walking. The grid line is 400mm out.

A revision superseding that sheet went out eleven days ago, and it never made it past someone’s inbox. This is the plain, unglamorous cost of document control breaking down on a construction site: a full day of formwork undone before the concrete truck even arrives.

The problem with construction document management on a live site

This is not one crew’s bad luck. It plays out on Australian sites every week, because most construction document management still runs on a mix of printed sets, email PDFs, personal cloud folders and whatever happens to be saved on a supervisor’s tablet. A drawing gets revised in the office. The revision gets emailed to twelve people. Ten open it. Two don’t.

Nobody confirms who is holding which version, and nobody strips the superseded sheet off the site shed wall. The register might say Revision C is current. The wall says Revision A. Both are technically true, and only one of them is safe to build from.

The villain here is never the crew on the tools. It’s a system where the same drawing can exist in six places at once, each copy looking identical, only one of them correct. Nobody signed off on that arrangement. It’s just what happens when construction document management is left to grow organically across email, print and personal cloud storage instead of being designed on purpose.

Poor project data and miscommunication together drive close to half of all rework on construction projects, according to research from FMI and Autodesk covering nearly 600 construction professionals.[1]

48%

of all rework on construction projects is caused by poor project data and miscommunication.

FMI and Autodesk, Construction Disconnected, 2018[1]

Why drawing version control breaks down on real projects

None of this happens because site teams are careless. A commercial build can carry anywhere from 200 to 2,000 live drawings across architectural, structural, hydraulic, electrical and fire disciplines, each one capable of being revised independently by a different consultant on a different day. Drawing version control across that volume is genuinely hard to hold together by hand.

The trade contractor working from a printed set has no way of knowing, mid-pour, that a revision landed in someone’s inbox that morning. The site engineer juggling five active packages cannot manually check every superseded sheet off every wall before every trade starts. And the document controller, if the project even has one, is usually managing the register in a spreadsheet alongside two or three other systems that don’t talk to each other.

The result isn’t one failure. It’s a structural gap between where the current drawing lives and where the work is actually happening.

That gap tends to widen right when it can least afford to. Design keeps evolving deep into construction on most Australian projects, driven by client changes, authority conditions and buildability fixes discovered on site. Every one of those changes produces a new revision, and every new revision is another chance for the printed set on a bench somewhere to fall a step behind.

“It is the absence of information at an early stage that often causes large changes during project delivery, which drive variations and contract changes.”

Australia and New Zealand Guide to ISO 19650, 2019[2]

The cost of inaction

Run the numbers on a mid-size commercial job and the wrong drawing stops being an abstract risk. A national survey of Australian construction professionals by Love and Edwards found the average project loses 6.4% of contract value to direct rework costs alone, before the indirect costs of delay, remobilisation and disputes are even counted.[3] On a $20M build, that’s $1.28M gone before anyone has argued about who caused it.

6.4%

Average direct cost of rework as a share of contract value on Australian construction projects, before indirect costs are added.

Love and Edwards, 2005[3]

The professional indemnity side is just as real. Berkley Insurance Australia’s published claims examples include an architect whose plans put a lift and stairwell in the wrong position, an error carried through an uncorrected drawing set, settled for around $100,000 including expenses.[4] That’s one drawing, one project, one error. Multiply it across every set of unmanaged revisions moving through a live program, and the exposure compounds fast.

None of this stays contained to the trade that made the mistake. A wall built off a superseded drawing becomes a variation claim, a delay to the following trades, and often the opening line of an extension of time notice once the programme slips. The wrong drawing rarely costs one number. It costs the rework, the schedule impact, and whatever it takes to resolve the argument about whose drawing was current on the day the work happened.

Australian research tracking 168 projects managed on the Aconex platform found the average project spends close to AUD$910,000 processing RFIs, a large share of them raised because a drawing on site didn’t match the design office record.[5] On a $20M build, that alone is close to a full point of margin.

AUD$910,000

Average cost of processing RFIs on an Australian construction project, across 168 projects studied, many raised because a drawing on site didn’t match the design record.

Aibinu, cited in Global Construction Review[5]

What good document control looks like

What changes isn’t more paperwork. It’s fewer places for the truth to hide. When drawing version control lives in one connected register instead of a shared drive and a stack of printed sets, every person on site opens the same file, and it’s always the latest drawing revision the construction team has issued, not whichever one happened to be printed last.

A revision goes out, superseded sheets are stamped and archived, and the people who need to know get a transmittal the same day, not whenever someone remembers to forward an email. When an RFI is raised because a drawing conflicts with a specification, the RFI drawing revision it references is logged precisely, so the response updates that exact sheet and nothing else drifts out of sync.

This is achievable now, with disciplines Australian projects already understand. TasNetworks’ own drawing management standard uses exactly this approach: every drawing carries a defined status such as concept, design, construction or as-installed, and once a sheet is superseded it is stamped and archived rather than deleted outright.[6] The principle isn’t new. What’s new is doing it automatically, at the pace a live site actually moves.

It also changes what a dispute looks like. When every revision, transmittal and markup carries a timestamp, reconstructing who knew what, and when, stops being a forensic exercise months after the fact. The record already exists. Nobody has to rebuild it from inboxes and memory once a variation or an EOT claim is on the table.

• Every trade opens the same current drawing, from the same source, the same morning.

• Superseded sheets are stamped and archived the moment a revision is issued, not weeks later during a defect walk.

• Transmittals record exactly who received which revision, and when, with a timestamp that holds up in a dispute.

• RFIs are logged against the precise drawing and revision that triggered them, not “the plan we had on Tuesday.”

• A clash between disciplines surfaces before the pour, not during handover.

• Markups and redlines are captured against the live drawing, not lost on a paper set left in a ute.

The Australian context

Document control is one of the few parts of construction where Australia is actively catching up to a global standard. Standards Australia’s BD-104 committee has been working through the national adoption of AS ISO 19650, the international framework for managing information across a building’s life, since it was first published in 2018.[2]

The industry-authored Australia and New Zealand Guide to ISO 19650 exists precisely because so many projects were still running document control on ad hoc, project-by-project conventions with no shared language for a drawing’s status.

That gap matters more as margins tighten and schedules compress. A sector already absorbing rising material costs and tighter finance cannot keep funding rework that a working drawing register would have caught for free. Getting the register right is one of the few controls on a project that pays for itself the first time it stops a clash before the pour.

Where Plexa fits

Plexa’s Document Control module closes exactly this gap. Every drawing lives in one indexed register with version control and revision tracking, so the platform always knows which sheet is current and which has been superseded. Transmittals go out automatically the moment a revision is issued, with a matrix tracking exactly who received what and when.

Side-by-side and overlay comparison shows precisely what changed between revisions, and markups carry timestamps so nothing gets lost between the office and the site.

Custom folder structures and naming conventions keep the register organised the way a project actually works, not the way a generic template assumes it should. The Drawings Tool gives every trade single-click access to the latest version of any sheet, with full version history behind it, so nobody is choosing between “the drawing I have” and “the drawing that’s correct.”

Go back to that core wall in Parramatta. With a connected register, the revision to that grid line reaches every device on site the moment it’s issued, the superseded sheet is pulled from circulation automatically, and the formwork crew never sets out from a drawing that stopped being current eleven days earlier. That’s the difference between a pour that proceeds and a pour that gets torn out.

Related reading

Wrong drawings and unanswered questions are two sides of the same coin. We cover how that plays out in what a good RFI process actually looks like in construction. The person usually accountable for the model and the drawing register in the first place is covered in what a BIM manager actually does on an Australian project.

And when the wrong drawing does make it into the ground, the defect management process is usually where the cost resurfaces.

The redline markups that record what actually got built against what was drawn belong in the same connected file as the daily record of when it happened, and we cover that pairing in our post on construction’s most underused legal document.

If you want to see how Plexa keeps every drawing, transmittal and revision in one connected register, book a 30-minute demo with the Plexa team.