What One Missed Coordination Issue Costs: RFI and Rework Data by Trade

Where Coordination Failures Enter the Document Set

Most field RFIs do not originate from ambiguous design intent. They originate from specific, traceable document failures that survived the design phase without detection. GCs and project managers who have lived through high-RFI projects often describe the experience as "fighting fires we should have caught in the drawings." Three origin types account for the majority of preventable RFIs on commercial and multifamily projects.

Spec vs. Drawing Conflicts

When a specification section calls for a product or performance standard that the drawing detail does not reflect, the field team must stop work and seek a design clarification, which becomes an RFI. A common example: Division 23 specifies a variable refrigerant flow system, but the mechanical plans show a conventional ducted layout with no equipment schedules updated to match. The subcontractor cannot proceed without written resolution.

This is one of the most common RFI triggers on commercial and multifamily projects. For a deeper look at how these conflicts arise, spec vs drawing conflicts covers the pattern in detail.

Cross-Discipline Dimensional Conflicts

Structural beams, columns, and bearing walls placed at coordinates that conflict with ductwork routing, piping runs, or electrical tray paths are a primary source of MEP RFIs. This type of conflict is rarely visible within a single discipline's drawing set. It surfaces only when sheets are compared across disciplines simultaneously. A structural engineer reviewing the structural set sees no problem.

A mechanical engineer reviewing mechanical sheets sees no problem. The conflict exists only in the gap between them. MEP coordination conflicts explains how these cross-discipline gaps form and what resolving them requires.

Missing or Deferred Information

Drawings that note "verify in field" or "coordinate with owner" without a resolution path generate RFIs at exactly the point when the trade contractor needs to act. Deferred information is not a neutral placeholder. It shifts the cost of resolution to the construction phase, where labor is mobilized, sequencing commitments are in place, and overhead is running daily. The RFI that results from a deferred condition carries a fully loaded field cost that a pre-construction document resolution would not.

RFI Volume as a Project Health Indicator

RFI volume is not just a project management metric. It is a diagnostic signal about drawing set quality. Projects with high RFI volume relative to square footage or contract value typically indicate document coordination failures that were not caught before construction began. Owners and construction managers who track RFI volume by phase are increasingly using that data to evaluate design team performance, not just contractor workflow efficiency.

Construction Industry Institute data on field rework as a percentage of project cost consistently identifies field rework originating from document errors as a measurable percentage of total project cost. That figure varies by project type but reliably exceeds the cost of pre-construction document review by a meaningful margin.

The practical implication for a general contractor (GC) or project manager:

• If RFI volume is running above your project's historical baseline by the time structural rough framing is complete, the drawing set likely contained coordination failures your pre-construction process did not catch. That is not a contractor problem. It is a document problem.
• RFI benchmarking by trade and phase is an emerging practice for owners and construction managers evaluating whether design fees reflect actual coordination effort.
• A high RFI log count tells you the document set sent to the field contained unresolved conflicts. What it doesn't tell you, until you trace each RFI back to its origin, is how many of those conflicts were preventable at the document review stage.

The true cost of construction rework covers the downstream financial consequences in full.

What Coordination Failures Cost by Trade

FMI and PlanGrid's research on RFI and rework costs across the construction industry identifies RFIs and related rework as a significant driver of unplanned cost across project types. What that research does not break down is which trades carry the highest cost per unresolved conflict. That breakdown is where the practical risk management decisions get made.

MEP: The Highest RFI Volume, the Longest Resolution Chains

Mechanical, electrical, and plumbing (MEP) coordination failures account for the majority of field RFIs on commercial construction projects. The reason is physical: these systems share ceiling plenum space, wall cavities, and shaft pathways, so a conflict between any two of them requires multi-discipline resolution.

• When a conflict surfaces after rough-in has begun, the cost is not just a design clarification. It is a sequencing correction: the MEP trade that has already installed must stop, sometimes demo, and wait for a revised routing coordination drawing before proceeding.
• MEP RFIs also tend to take longer to resolve than structural RFIs, because the response must come from multiple design disciplines simultaneously, including the mechanical engineer, electrical engineer, and architect, coordinating a single answer.

For the coordination process that prevents these conflicts, see what MEP coordination conflicts involves.

Structural: Low Volume, High Consequence

Structural RFIs are less frequent than MEP RFIs on most projects, but individual cost consequences are higher. Structural work occurs early in the construction sequence, which means a held structural pour, a revised footing layout, or a relocated beam affects every subsequent trade that ties to that structural element.

A missed grid mismatch between the structural drawings of record and the architectural layout, discovered after formwork is set, can hold concrete placement for days while the engineer of record issues a revised design.

Slab edge conditions and opening sizes are two of the most common conflict points between structural and architectural documents. The cost behavior in these cases is not linear. It compounds across the full trade sequence that was downstream of the structural element.

Civil and Site: The RFIs Nobody Budgets For

Civil and site coordination failures generate RFIs before the building structure begins, which is precisely why they are underweighted in pre-construction risk assessments. A conflict between survey data and design grades, a utility crossing that conflicts with foundation work, or a stormwater routing error discovered during excavation creates an RFI that holds a fully mobilized crew with equipment on site and daily overhead running.

These RFIs are frequently categorized as site condition problems rather than document failures. That categorization is often incorrect. Survey data that was not incorporated into the civil design, or utility as-builts that were not cross-referenced against the foundation layout, are document coordination failures.

The cost of resolving them in the field is a function of crew mobilization, not design complexity.

Contractual Response Obligations and What Happens When They Are Breached

Response timeframes for RFIs and related design clarifications are not always left to professional courtesy. In many commercial contracts, they are codified in the General Conditions. The AIA A201-2017 General Conditions of the Contract for Construction is the standard reference document for architect obligations during construction, including the obligation to respond to contractor requests for information in a timely manner.

• When a design team fails to respond within the contractually required timeframe, the practical consequences extend beyond the immediate schedule hold. Depending on contract language and the jurisdiction, delayed or absent responses can support a contractor's claim for a time extension or cost recovery under the contract.
• GCs managing live projects should document RFI submission dates, response dates, and any schedule impact that resulted from delayed responses. That project documentation becomes evidence in a dispute.

This is not a prediction that every slow RFI response becomes a claim. It is a practical observation that the RFI process has contractual weight that many project teams treat as administrative. The construction workflow around RFIs is where cost and schedule risk crystallize. A constructability review conducted before construction begins is one mechanism for reducing the volume of RFIs that test those response obligations.

How Pre-Submission Document Review Reduces RFI Volume

Catching coordination conflicts in the document set before construction begins eliminates the category of RFI that originates from document errors. That category is preventable. The conflicts that generate MEP, structural, and civil RFIs described in this article are not field conditions.

They are document failures that reached the field without detection. InspectMind reviews full construction document sets across disciplines simultaneously, flagging structural-vs-architectural conflicts, MEP routing conflicts against structural elements, and spec-vs-drawing discrepancies before the drawings go to the field or to the building department.

For project teams focused on RFI prevention, the review starts at $50 per upload with a 5+ issues found guarantee or a full refund.

Frequently Asked Questions

What causes most RFIs on a construction project?

The majority of RFIs on commercial projects originate from document coordination failures, specifically spec-vs-drawing conflicts, cross-discipline dimensional conflicts, and information deferred to field conditions rather than resolved during design. These are preventable at the document review stage. RFIs that originate from genuine field conditions or unforeseen site circumstances are a smaller share of total RFI volume on most projects.

How does RFI volume relate to drawing set quality?

High RFI volume relative to project size is a reliable indicator that the construction drawings contained unresolved coordination conflicts when they went to the field. Projects with well-coordinated document sets and thorough pre-construction review consistently generate fewer RFIs than projects where document conflicts are discovered during construction. RFI volume is increasingly used by owners and construction managers as a performance signal for design team coordination quality.

Who is responsible for responding to an RFI, and how long do they have?

The architect or engineer of record responsible for the drawing or specification being questioned is the appropriate respondent for most RFIs. Response timeframes are set by the General Conditions of the contract. The AIA A201-2017 is the most common reference document for architect obligations during construction, though project-specific contract documents may modify those timeframes. Delayed responses can carry contractual consequences if the project documentation shows schedule impact.

What is the difference between an RFI and a change order?

An RFI is a formal request for design clarification. It does not modify the contract on its own. A change order is a formal contract amendment that adjusts scope, cost, or schedule. An RFI becomes the basis for a change order when the design team's response reveals that the work required differs from what the original contract documents showed, generating a cost or schedule adjustment that must be executed through the change order process.

Can pre-construction document review reduce RFI volume?

Yes, for the category of RFIs that originate from document errors. Pre-construction document review that cross-references drawings across disciplines can identify coordination conflicts before construction begins, eliminating the field RFI that would have resulted. RFIs from genuine field conditions or project owner decisions are not addressable through document review. But the document-error category, which accounts for a significant share of RFI volume on most commercial projects, is preventable with thorough pre-construction QA.