The number circulates through AEC industry discussions often enough that it starts to feel like received wisdom: the average construction RFI costs $15,000. The figure is an industry estimate — not a peer-reviewed study from a single source — and the range is wide in practice, from a $2,000 simple clarification to a $60,000+ clash-driven rework event. But the directional truth is not in dispute among anyone who has managed construction administration on a complex project: RFIs are expensive, the expense is often preventable, and clash-related RFIs are the most preventable category of all.
Understanding where that cost actually comes from changes how you think about the investment in upstream clash detection. Most discussions focus on the obvious component — rework. Tear out the duct that was installed where the beam goes. Reinstall. But rework is only one of four cost drivers, and depending on the project, it may not even be the largest.
The Four Components of RFI Cost
1. Direct Rework Cost
Rework is the labor and material cost to remove and reinstall work that was installed in conflict with another trade. For a typical MEP clash — say an HVAC duct run that conflicts with a structural beam — the direct rework cost includes: labor to demobilize the installed duct section, material cost if new fittings or duct segments are required, labor to reinstall, and any required inspections for the affected system. On a standard commercial project, this runs $3,000–$12,000 depending on duct size, accessibility, and the complexity of the surrounding work.
The rework cost is the one that shows up in contractor change order requests and is therefore the most visible. It is also, counterintuitively, the most negotiable — contractors vary widely in how they price rework, and the architecture firm's ability to challenge or negotiate the change order depends partly on whether the clash was documented as a coordination issue before construction began.
2. Schedule Impact Cost
Schedule impact is where RFI costs frequently exceed the direct rework. When a duct-beam clash is discovered in the field, work in the affected zone typically stops. The MEP contractor cannot proceed with the downstream duct work until the routing conflict is resolved. If the RFI response time runs 10–15 business days (which is not unusual on a busy project), and if the MEP work in that zone is on the critical path, the schedule delay can trigger liquidated damages or acceleration costs that dwarf the rework itself.
A conservative estimate for schedule impact on a 6-month construction delay caused by field-discovered coordination issues: on a project with $500/day liquidated damages, a 10-business-day field stop translates to $5,000–$7,500 in direct schedule cost, plus the GC's overhead for managing the RFI process and coordinating trade sequencing around the stopped zone. For a hospital or data center with hard mechanical completion dates, schedule impact costs can run an order of magnitude higher.
3. Design Professional Time
The architecture firm's internal cost of processing an RFI is routinely underestimated because it is absorbed as overhead rather than billed. A field-discovered clash RFI requires: field verification of the conflict by the project architect or engineer of record, a coordination meeting or calls with the affected consultants, revised drawing production (even if minor), review and sign-off of the response, and documentation of the resolution in the project record. The total professional time per clash RFI typically runs 8–16 hours across the team.
At $150–$200 per hour blended rate, that is $1,200–$3,200 in unbillable professional time per RFI. On a mid-size commercial project with 40–60 clash-related RFIs, the cumulative internal cost to the architecture firm is $48,000–$192,000 in absorbed overhead. This cost does not appear in any single RFI response — it accumulates invisibly across the construction administration phase.
4. Relationship and Liability Risk
The hardest to quantify is the relationship cost. When field-discovered clashes generate RFIs, the implicit question in every response is: whose coordination failure is this? The architecture firm's? The responsible consultant's? The contractor who should have noticed? That question surfaces in closeout negotiations, in retention disputes, and occasionally in claims. The architecture firm that cannot demonstrate that it ran thorough clash detection — with documented coordination rounds, clear issue assignment, and sign-off records — is in a weaker defensive position than the firm with a full coordination log.
This is not theoretical. E&O claims involving coordination failures are the most common category of claim against architecture firms in AEC professional liability. Documented, systematic clash detection is a significant factor in how those claims resolve.
Which RFIs Are Actually Preventable
Not all RFIs are clash-related, and not all clash-related RFIs are fully preventable. Industry estimates suggest that 25–35% of RFIs on commercial construction projects are attributable to coordination clashes that were present in the design model before construction began (these are industry-range estimates; the figure varies significantly by project type and team sophistication).
Within that category, clash-related RFIs break into three sub-types:
- True coordination failures: the clash existed in the federated model at LOD 300 or higher and was either not detected or detected and not resolved before construction. These are fully preventable with systematic pre-construction clash detection.
- LOD gap clashes: the clash became visible only when the model advanced to LOD 350 or when construction revealed connection details not modeled. These require LOD-aware detection (see the LOD 350 article) but are preventable if the coordination window extends to LOD 350.
- Field condition clashes: the model was accurate, but as-built conditions diverged from the construction documents due to field decisions, substitutions, or existing conditions that didn't match survey data. These are not fully preventable through model-stage detection, though some can be caught through model-to-field verification practices.
The first two categories — together representing 70–80% of clash-related RFIs by most project teams' experience — are the target for upstream clash detection. The third category is a different problem requiring different tools.
The Prevention Math
Take a mid-size commercial office building: 95,000 square feet, four-story, steel structure, standard MEP package, 18-month construction schedule. Based on industry-range experience for this project type, expect 80–120 total RFIs during construction, of which 25–35 are clash-related.
At $12,000–$18,000 average cost per clash RFI (using the industry-range estimate weighted toward the lower end for a straightforward project type), total clash-related RFI cost over construction: $300,000–$630,000 across all parties. The architecture firm's share of that — direct CA cost plus absorbed coordination overhead — is typically 15–25% of the total, or $45,000–$157,000.
Systematic clash detection upstream reduces the clash-related RFI count. A realistic target — based on what well-managed BIM coordination programs achieve — is 50–70% reduction in clash-related RFIs. That translates to $150,000–$440,000 in project-wide cost avoidance. The cost of systematic coordination tools and process represents a fraction of that.
We are not saying clash detection eliminates RFIs. Field conditions, owner changes, and substitutions will always generate RFIs. The argument is that the specific category of RFIs generated by design-stage coordination failures — clashes that were present in the model and not caught — is the most cost-effective category to prevent, because the correction cost at the model stage is a few hours of coordination time, not a week of field rework on a critical-path activity.
The Construction Administration Burden Shift
There is a secondary benefit that does not appear in the RFI cost math: when clash-related field RFIs are reduced, the project architect's construction administration engagement shifts from reactive firefighting to proactive oversight. CA phases on projects with high RFI volumes are consumed by response drafting, consultant coordination, and change order review. CA phases on projects with thorough pre-construction coordination look different — the architect is doing site observation, quality review, and owner advisory work, which is both higher-value professionally and better service to the client.
That shift also affects the risk profile of the CA phase. An architect whose time is split between 60 active RFIs has significantly less attention available for each one than an architect managing 20. Missed details in RFI responses — particularly in multi-page packages with complex routing changes — is a documented source of claim exposure. Reducing the RFI volume reduces that exposure, even before the direct cost savings are counted.