Most conversations about RFI prevention in the AEC industry converge on document management: better revision tracking, cleaner drawing sets, faster turnaround on consultant responses. Those practices reduce administrative RFIs — questions about spec sections, drawing reference conflicts, material substitution requests. They don't address the category that generates the most expensive RFIs: design coordination failures that were present in the construction documents before they were issued.
The upstream opportunity is larger. The design model contains the coordination conflicts that will become field RFIs. Most of them are visible, detectable, and resolvable before construction begins. The question is whether the architecture firm's coordination process catches them at the model stage, where a resolution costs a few hours of design time, or whether they surface in the field, where a resolution costs $15,000 and a two-week schedule disruption.
The Two Types of Upstream RFI Prevention
Effective RFI prevention at the model stage operates on two different levels that are often conflated. Understanding the distinction matters because each requires a different response.
Geometric clash prevention addresses physical conflicts between model elements: the duct that occupies the same space as the beam, the pipe that penetrates a shear wall at a structurally compromised location, the sprinkler branch that doesn't clear a ceiling grid. These are detectable by federated model clash analysis and are the primary target of systematic BIM coordination.
Design intent ambiguity prevention addresses conflicts between what the drawings show and what the construction team needs to know to build it. This category includes: transitions between systems that are not detailed on any drawing, coordination conditions that require field judgment when they shouldn't, and specification conditions that don't match what the model shows. These conflicts don't show up in a clash detection run because they aren't geometric. They show up as "clarification requested" RFIs during construction.
Most BIM coordination programs address geometric clashes reasonably well. Design intent ambiguity is the harder and larger opportunity, particularly because it is less systematized.
Model-Stage Geometric Prevention: What Actually Works
For geometric clash prevention, the practices that demonstrably reduce field RFI rates are well-established among firms with mature BIM programs. The gaps are in execution consistency, not in the knowledge of what to do.
The three practices that have the highest impact per coordination effort hour:
LOD 350 Coordination Before CD Issue
Most architecture firms run their final coordination round against LOD 300 models and treat it as the pre-CD coordination complete checkpoint. The problem: LOD 300 structural models typically omit connection details that, at LOD 350, create real conflicts with MEP routing. Running a confirmation coordination round — even a targeted one, focused only on high-risk zones identified in previous rounds — against LOD 350 models before CDs are issued catches a specific class of conflict that LOD 300 coordination systematically misses.
This is not a proposal for full LOD 350 coordination on every zone of every project. It is a targeted final check on the zones identified as high-risk: primary mechanical rooms, structural-intensive floor plates with complex MEP routing, and any zones where the structural engineer flagged connection geometry updates since the last LOD 300 coordination round.
Red Zone Coordination
On any complex project, certain spatial zones carry disproportionate clash risk: primary mechanical rooms, rooftop mechanical yards, congested floor plate zones near cores, and transition zones between structure types. Identifying these "red zones" early — typically by the end of schematic design, based on structural system geometry and mechanical system routing requirements — allows targeted, intensive coordination effort to be concentrated where it generates the most RFI prevention value.
Red zone coordination operates at higher frequency and higher scrutiny than standard project-wide coordination. Weekly rather than biweekly model updates from the relevant discipline leads. Immediate clash detection runs when updates arrive. Direct coordination between discipline leads (structural engineer + mechanical engineer + architect) rather than routed through the BIM Coordinator alone. This intensity is not sustainable project-wide, but for a 3–4 zone set on a typical commercial building, it is feasible and directly reduces the RFI risk in the highest-consequence locations.
Clash-to-CD Drawing Verification
The final step that many firms skip: verifying that the resolved coordination issues from the coordination register are accurately reflected in the issued construction documents. A clash that was resolved in the coordination meeting — "MEP will reroute the HVAC main trunk to avoid the moment frame" — still needs to be drawn correctly on the mechanical drawings and coordinated with the architectural reflected ceiling plan. Coordination resolution in the model is necessary but not sufficient. The construction document set must reflect the resolution.
A clash-to-CD verification pass — comparing the coordination register's resolved items against the issued drawing set — before CDs are released catches the category of RFI that is most embarrassing: the coordination issue that was identified and resolved in the model, then drawn incorrectly in the document. These RFIs are preventable with essentially zero cost if the verification step is in the production workflow. They are expensive and relationship-damaging when discovered in the field.
Design Intent Ambiguity: The Harder Problem
Preventing design intent ambiguity RFIs requires a different approach than clash detection. The relevant question is: what will a GC superintendent or subcontractor need to know in the field that isn't explicitly shown in the documents?
Experienced project architects do a version of this check intuitively — reviewing their own drawings and specifications for conditions that a builder might interpret differently than intended. The systematic approach makes this explicit: a pre-CD document review specifically targeting ambiguity, conducted by someone with construction field experience (ideally a project architect who has done CA on similar building types).
The categories that generate the most ambiguity-driven RFIs on commercial construction projects:
- System transitions and interfaces: where does the MEP contractor's scope end and the GC's scope begin for a mechanical equipment connection? What are the clearances required for access during installation that aren't shown on the drawings?
- Specification vs. drawing conflicts: the specification section calls out a product with a different dimensional footprint than what's shown in the plan. No one noticed during production because spec review and model coordination are separate workflows.
- Assumed field conditions: the drawing assumes the foundation contractor will install an anchor bolt pattern at a specific location. The detail doesn't show how that location relates to the rebar mat. The ironworker asks for clarification in the field.
- Sequence-dependent conditions: the drawing sequence requires work in a specific order that isn't obvious from the drawings. Without a sequencing note, the field crew attempts the work out of order and asks for an RFI when the result doesn't match the intent.
We are not saying every one of these conditions can be identified before construction — experienced field crews encounter genuinely ambiguous conditions that no pre-construction review would catch. The point is that the systematic, targeted pre-CD review of specific ambiguity categories catches a meaningful fraction of these before they become field questions, at a cost of 1–2 days of senior staff review time per project. The return on that investment, measured in CA hours not spent drafting RFI responses, is typically positive on any project over $5 million construction value.
Tracking What You Catch
RFI prevention is most actionable when firms track the clashes they catch at the model stage and compare them against the RFIs that surface during construction on the same project. The firms that do this consistently develop a detailed understanding of where their prevention programs are working and where they're not: which clash types they're catching reliably, which types are still leaking through to construction, and which design intent categories are generating repeated field questions across projects.
That feedback loop — model-stage clash catch rate vs. construction-stage RFI profile — is the mechanism by which coordination programs improve. Without it, coordination improvements are based on intuition rather than data. With it, the firm can make specific, evidence-based changes to its coordination process that reduce RFI rates on the next project type where the gap appears.