Poor Document Control Kills More Projects Than Bad Weather

A framing crew builds a wall based on the architectural drawings in their foreman's binder. The wall is in the wrong location. Not because the foreman can't read drawings. Because the drawings in his binder are from ASI-3. The current set is ASI-7. Four revisions happened in the last eight weeks. Nobody replaced the drawings in the field binder. The wall gets built, inspected, and drywalled before anyone notices it's six inches off from the current design.

This is a document control failure. It costs $22,000 to tear out and rebuild the wall. It delays the adjacent work by a week. And it was entirely preventable.

FMI/CURT estimates that $4.2 billion in annual construction rework is caused by poor document control. That number is probably conservative. It doesn't include the schedule impacts, the dispute costs, or the relationship damage that follows every rework event.

The three document control failures

1. Version control

A mid-size commercial project generates 30-50 ASIs (Architect's Supplemental Instructions) during construction. Each one modifies drawings, specifications, or both. The current set of contract documents is not the set that was issued at contract award. It's the original set plus every ASI, bulletin, and RFI response issued since.

The question is: does the person installing the work have access to the current set? On a well-run project with digital plan rooms and tablet-based field access, probably. On a project where foremen work from printed sets, the answer is “depends on who updated the binder.”

The fix is straightforward: digital drawings in the field, with automatic updates when new revisions are issued. Procore, Bluebeam, PlanGrid, and every major platform support this. The challenge is adoption. Many field workers prefer printed drawings. They're bigger, they don't need batteries, and you can mark them up with a pencil. The transition to digital requires providing tablets, training, and making the digital workflow easier than the paper workflow.

2. RFI response distribution

An RFI is submitted asking about a ceiling height discrepancy. The architect responds: “Ceiling height at corridor shall be 9'-6”, not 9'-0” as shown on A-302.” The response goes to the PE. The PE logs it in Procore. The framing sub, who needs the information to set the top track, doesn't see the Procore notification because their foreman doesn't check Procore.

RFI responses are contract document modifications. They have the same weight as an ASI. But the distribution path is different. ASIs go to every trade. RFI responses go to the requestor and the distribution list. If the affected trade isn't on the distribution list, they don't get the information.

The fix: every RFI response that changes a dimension, material, or installation method should be communicated directly to the affected trade foreman, in the field, with a read receipt or signature. Email notification is not enough. Procore notification is not enough. Walk the response to the foreman and make sure they understand the change.

3. As-built documentation

As-built drawings are supposed to be maintained throughout construction. In practice, they're compiled at the end of the project by a PE who wasn't on site for most of the work, working from daily reports and memory. The result is as-built drawings that are 60-70% accurate.

The owner uses these drawings for 20+ years of facility maintenance. When a plumber needs to find a shutoff valve or an electrician needs to trace a circuit, the as-built drawings are the reference. If they're wrong, the maintenance work takes longer, costs more, and sometimes requires exploratory demolition to find what the drawings say should be there but isn't.

The fix is continuous as-built documentation. Each trade marks up their drawings as work is installed, not at closeout. Digital markup tools make this practical. The PE reviews the markups monthly. The final as-built set is compiled from trade markups, not from memory.

The AI opportunity

Document control is information management. AI is good at information management. Specific applications that work today:

ASI impact analysis. Upload an ASI and the current drawing set. Ask the AI to identify every area affected by the change and every trade that needs to be notified. This catches the ripple effects that a busy PE might miss.
RFI response routing.When an RFI response is logged, AI can analyze the content and identify which trades are affected beyond the original requestor. “This response changes a ceiling height. The framing sub, mechanical sub, and fire protection sub should be notified.”
Drawing revision tracking. AI can compare two versions of a drawing and highlight what changed. This is especially useful for spec-heavy drawings where a single note change buried in a detail can have significant field impact.

The $4.2 billion problem is not a technology problem. The technology exists. It's a process problem: the gap between where the information lives and where the work happens. AI can help close that gap, but only if the process puts the right information in front of the right people at the right time.