Consider a number nobody tracks: the total cost of working off the wrong drawing version.
Not the cost of the rework itself, though that number is significant. The full cost: the field superintendent's time spent figuring out the discrepancy, the architect's time responding to the RFI, the schedule delay while the issue is resolved, the potential change order if the fix isn't covered under the existing contract, and the relationship cost if there's a dispute about who bears it.
Multiply that by the number of version-related issues on a typical project. Then multiply it across all the active projects at your firm.
The number is larger than most principals want to think about. The Construction Industry Institute puts rework at roughly 5% of total construction cost on a typical project, with some reaching 12-15%. A 2018 Autodesk/FMI study found that 52% of that rework traces back to poor project data and miscommunication. Almost all of it is preventable.
Where the Losses Actually Show Up
Poor document control doesn't usually create one catastrophic failure. It creates a hundred small ones that compound over the life of a project.
Rework from outdated drawings. A contractor builds something from a drawing that was superseded two weeks ago. The framing is in the wrong location, or the opening is the wrong size. Now someone has to demo it and redo it. The direct cost is the rework. The indirect cost is everything else that gets pushed: the schedule, the follow-on trades, the inspections.
Coordination conflicts from mismatched sets. The architect has Rev D. The structural engineer has Rev C. Nobody knows there's a discrepancy until the two sets are overlaid during a coordination review and the wall that the arch moved isn't where the structural connection expects it to be. Catching it in coordination review is recoverable. Catching it in the field is expensive.
Wasted time searching for current files. This one is quieter but relentless. Team members open the project folder, see multiple versions of a file, and spend five minutes figuring out which is current. Or they email the PM to ask. Or they just make a judgment call and hope for the best. This happens dozens of times a week on an active project, across multiple team members.
Disputes about what was issued and when. When a contractor claims they never received the revised drawings, and the architect insists they were sent, the project grinds to a halt while both sides dig through email archives trying to reconstruct what happened. A transmittal log and a proper distribution system makes this a five-minute conversation. Without it, it's a legal question.
Late consultant feedback due to version confusion. A structural engineer reviews the wrong version of the architectural drawings and provides coordination comments that don't reflect the current design. Now the architect has to reconcile comments against a drawing that no longer exists. Or worse, the structural drawings get updated to match the wrong architectural basis, and the conflict isn't caught until both sets are finalized.
The Hidden Multiplier: Staff Time
Direct rework costs are visible. The staff time costs are invisible and often larger.
A project architect spending twenty minutes a day searching for current files is losing over an hour and a half a week to document chaos. On a twelve-month project, that's roughly a full work-week. For a project with three team members doing the same thing, it's three work-weeks.
A PM spending time each week manually distributing drawings, tracking who has what version, and fielding questions about which file is current is doing work that should be handled by a system, not a person.
These are not dramatic failures. They're friction, the kind of low-grade inefficiency that doesn't show up in a project debrief but accumulates steadily across every project, every year.
The Dispute Risk
Document control failures don't always stay internal. Sometimes they become claims.
A contractor who builds something wrong based on a drawing you can't prove was superseded before they started work has a credible argument that the error wasn't theirs. A client who received conflicting information across multiple email threads has a legitimate complaint about unclear communication. A consultant who wasn't notified of a scope change that affected their work has grounds to contest a coordination responsibility.
None of these are inevitable. But they become likely when there's no clear record of what was issued, to whom, and when. Document control is your paper trail. Without it, disputes that should be settled in an hour become disputes that involve attorneys.
What the Fix Actually Costs
The irony of document control investment is that the cost of doing it right is genuinely low compared to the cost of doing it wrong.
A naming convention costs nothing. Writing it down and enforcing it costs an hour of a PM's time.
A transmittal system — even a simple one, costs a few hours to set up and a few minutes per issuance to maintain.
A version tracking system that keeps current files separate from archived files, accessible to the whole team, and updated in real time is achievable with purpose-built software at a fraction of the cost of a single rework event.
The firms that resist investing in document control usually do so because the cost of the failures is diffuse — spread across dozens of small events, absorbed into project budgets, and rarely attributed to their root cause. If you could see the total document control failure cost on your last three projects as a single number, the investment decision would be easy.
A Starting Point
You don't have to overhaul everything at once.
Pick the single highest-impact change on your current projects: probably the current/archive folder rule, or a consistent naming convention, or a formal transmittal log. Implement it on the next project that starts. Build the habit there. Expand from there.
Olumba handles document versioning and access control out of the box: every document is tracked, every version is linked to the project, and the team always knows what's current. If version chaos is a recurring pattern at your firm, it's worth trying.
Research published in the Journal of Construction Engineering and Management (Hwang et al., 2014) found that every dollar invested in documentation quality management returned an average of $7.40 in prevented rework and delay costs. The cost of the problem is real and ongoing. The cost of solving it is much lower than most firms assume.
