The 10 Most Common Errors in Construction Documents, From 10,000+ Real RFIs

Most articles about construction document errors are written from intuition. This one is written from data. At Tuuli, we have analyzed more than 10,000 real RFIs from large institutional projects to understand what actually goes wrong in construction documents, which errors recur, and which ones carry real cost.

The context matters: industry research has long suggested that 30 to 50 percent of RFIs trace back to errors, omissions, or ambiguities in the documents themselves, and the average cost to process a single RFI runs around $1,080 with responses taking roughly ten days. Multiply that across a typical project and document errors become one of the largest controllable costs in design and construction.

Here are the ten error patterns that show up again and again, roughly in order of how often they appear and how much trouble they cause.

1. Cross-discipline coordination conflicts

The classic: structure says beam, mechanical says duct, both occupy the same space. Architectural ceiling heights that do not survive contact with the structural framing plan. Plumbing risers landing in shear walls. These conflicts dominate RFI logs because each discipline's set can be internally perfect while the combined set is unbuildable. They are also among the most expensive, since resolving them mid-construction often means redesign, resequencing, or demolition.

2. Callouts pointing nowhere

A detail callout references 7/A-501, but sheet A-501 contains only four details. A section mark points to a sheet that was renumbered two issues ago. Broken references are the most mechanical of all document errors, and the most preventable, yet they survive review constantly because checking every callout across hundreds of sheets manually is mind-numbing work that nobody has time to finish.

3. Schedule and plan disagreements

Door 104A is type B on the plan and type C in the door schedule. A finish schedule lists a room that no longer exists. Equipment tags on the mechanical plan that never made it into the equipment schedule. Schedules are edited separately from plans, often by different people at different times, and they drift apart silently.

4. Missing details and information gaps

The condition exists in the building but nobody drew it. A wall type transitions at a condition with no detail. A roof edge that the set simply does not address. Crews cannot build what is not documented, so they stop and ask, and every one of those questions is schedule risk.

5. Dimension discrepancies

The same corridor dimensioned at two different widths on two sheets. Strings of dimensions that do not add up to the overall. Grid offsets that disagree between architectural and structural. Dimensional conflicts force the field to choose which number to trust, and when they choose wrong, the result is rework.

6. Specification and drawing mismatches

The drawings show one product, the spec book requires another. A spec section is referenced in general notes but was deleted in an addendum. Performance criteria in the spec that contradict the detail as drawn. These mismatches are especially costly because they often surface during submittals or procurement, after long-lead items are already in motion.

7. Revision and addendum fallout

A change gets made in one place and not the other four places it touches. An addendum revises a wall type but the affected sections still show the old assembly. Phase-to-phase drift, where the permit set, pricing set, and construction set quietly diverge, is one of the most common sources of confusion in our data, and it compounds late in documentation when changes come fastest.

8. Code and accessibility issues

Clearances that do not meet accessibility requirements, egress paths that fail when measured precisely, fire-rating continuity broken at a junction between assemblies. These are lower in raw frequency than coordination issues, but they punch above their weight in consequence: a code issue found by the authority having jurisdiction means resubmission delays, and one found in the field can mean tearing out finished work.

9. Ambiguous notes and instructions

"Match existing." "As directed by architect." "Typical, U.N.O." applied to conditions that are anything but typical. Ambiguity transfers decisions from the design team to the field, and the field responds the only way it can: with an RFI. Two contractors reading the same ambiguous note will price and build it two different ways.

10. Inconsistent terminology and tagging

The same wall type called W1 on one sheet and WT-1 on another. Room names that differ between plan and schedule. A material referenced by three different names across the set. Individually trivial, these inconsistencies erode confidence in the documents and generate clarification requests that are pure waste.

The pattern behind the patterns

Two things stand out across thousands of RFIs.

First, the overwhelming majority of these errors are mechanical, not creative. They are not failures of design judgment. They are failures of synchronization: between sheets, between disciplines, between drawings and schedules, between revisions. That is exactly the category of error that exhaustive, systematic review catches and that tired human reviewers at the end of a deadline crunch miss.

Second, and this is the part most firms underuse: error patterns are firm-specific. Every firm has its own signature mistakes, driven by its templates, its standards, its workflow, and its people. Your RFI log is a precise map of where your documents historically fail. A review process that ignores that history rechecks for everything and specializes in nothing.

What to do with this

The practical takeaways: run a systematic cross-reference pass before every issue, not just a senior read-through. Reconcile schedules against plans as a discrete step. Treat addenda and revisions as full-set events, not local edits. And mine your own RFI history, because it is telling you exactly what to check first. For the design-phase playbook in full, see our guide on how to reduce RFIs in construction.

This is the problem Tuuli was built for. It runs systematic checks across an entire drawing set, callouts, schedules, dimensions, cross-discipline coordination, and it learns from your firm's own RFI and change order history, so the review is tuned to the errors your projects actually repeat. Every finding is cited back to the exact sheet so a human can verify it in seconds. To see how this approach compares with other tools, read our guide to the best AI construction drawing review software.

Want to see what a review trained on real RFI data finds in your set? Tuuli offers a free initial review of a real project. Get a free review.