When I review an RFI before it goes to the design team, grammar is not my priority. I start by asking whether the reviewer can answer it without reconstructing the job from scratch.
In many cases, an RFI moves quickly or drags based heavily on how it was written as well as how complex the question is. The same problems recur across many projects (e.g., a duct hits a beam nobody coordinated, two spec sections call out different products for the same wall).
On many jobs, project engineers get little formal guidance on what a good RFI looks like versus a bad one, so the same vague questions go out, bounce back for clarification, and burn schedule float nobody had to spare. Across trades, strong RFIs identify the conflict, request a decision, and show the reviewer the affected work.
This guide will go over representative examples by trade, with the question, the resolution, and what separates the two.
What Bad RFI Writing Costs
Poorly written RFIs cost real money and real schedule, and the cost is documented in the foundational Navigant Construction Forum study, which analyzed 1,362 projects worldwide. The study found an average cost of $1,080 to review and respond to a single RFI. It also found that 21.9% of RFIs received no response at all, describing the no-response rate “one of the major indicators that a dispute will arise.”
The waste compounds when the question itself is the problem. When an RFI lacks context or tries to cover too many issues at once, the back-and-forth wastes the days you were trying to save.
Navigant classified 13.2% of RFIs as “not justifiable.” In those cases, the answer already existed in the contract documents. In one analyzed dispute involving 4,000 alleged RFIs, roughly 800 were the same question resubmitted with different wording, and roughly 300 were answered the day they arrived with a one-line spec reference.
That is float erosion you create yourself.
Representative RFI in Construction Examples by Trade
The same RFI patterns surface across every trade: a conflict between two sheets, a spec section that contradicts another, or a field condition that does not match the drawings.
The examples below walk through six of the most common scenarios I see, paired with the strong version of the question and the resolution that follows. Read them as a reference for what reviewers actually need to answer fast.
Structural: dimension conflict between architectural and structural drawings
A structural conflict RFI should identify the exact sheets, state the clash, propose a buildable decision, and tie the response date to the affected work. In this example, a beam shown on the structural sheet conflicts with an open ceiling on the architectural sheet at the same location.
A strong question reads:
"Drawing S-2.1 shows a W12×26 beam at grid B-4, while Drawing A-3.2 shows open ceiling at the same location. HVAC duct on M-2.1 routes through this area. Clarify: (1) Is beam required? (2) If yes, confirm revised HVAC routing. Contractor proposes installing beam per structural and rerouting duct 6″ north, confirm acceptable. Response required May 20 to avoid impacting framing crew scheduled May 23."
That RFI gets answered fast because it gives the reviewer exact sheets and the conflict, then adds a proposed solution and a crew-tied deadline.
The bad version reads: "Please clarify the structural drawings at the second floor. There seems to be a conflict." The reviewer has to ask where and what you want before answering.
MEP: mechanical duct routing conflict with structural framing
An MEP clash RFI needs to prove the conflict is physically impossible to build and give the engineer a practical path to choose from. Here, a duct occupies the same space as a structural beam. An academic BIM coordination paper documents coordination issues including a structural floor opening that was not big enough for a mechanical duct, HVAC conflicts with other systems, and a mechanical duct conflict with a structural concrete beam due to lack of coordination between trades. A public UConn addendum similarly required the HVAC subcontractor to generate a list of required duct penetrations in existing structural steel and coordinate beam penetrations in the correct location.
A strong RFI states the two documents directly:
"The current mechanical drawing (Sheet M202) shows a 36″ × 18″ HVAC duct running along the east corridor on Level 2. The structural drawing (Sheet S103) places a W18×40 steel beam in the same space. The two documents conflict."
The resolution should give the reviewer a buildable path: for example, modify the duct dimensions if airflow can be maintained, reroute the duct, or revise opening details, and state cost and schedule impacts where known. Giving clear options can help the engineer select a path instead of starting from a blank page.
Compare the weak version: "Please clarify the routing of the duct as it conflicts with beam B3." It gets a slower answer because the reviewer has to reconstruct the problem.
Finishes: spec section calls two products for the same substrate
A finish-spec RFI should ask which product governs and keep broad product-preference discussion out of the question. In an illustrative composite medical office renovation scenario, Section 09 91 23 specified one manufacturer's eggshell latex for gypsum board in healthcare occupancies, while Section 09 96 00 specified a different manufacturer's semi-gloss for corridor walls. Both cover corridor gypsum board. The question:
"Which specification section and product governs for gypsum board wall surfaces in interior corridors (specifically Corridor 2B, Sheet A-601)? Please confirm the governing product, manufacturer, sheen level, and applicable specification section."
A clean architect's response designates one section as controlling for corridors and confirms no change in contract sum or time. The design team's RFI response records the project team's interpretation of the contract documents. A true spec conflict is the correct use of an RFI. Swapping a specified product for a preferred alternative belongs in a substitution request, a separate process entirely.
Civil/site: grade elevation conflict between civil and architectural site plan
A civil/site RFI should identify the controlling finished floor elevation before grading or foundation work proceeds from conflicting sheets. Here, the civil grading plan establishes a finished floor elevation that differs from the architectural floor plan, a recurring coordination error. A SPU manual warns that conflicts between civil grading and utility drawings can be difficult to cross-check and may not be encountered until construction. A clear RFI names both elevations before asking which governs.
"The civil grading plan shows the building pad/FFE at [civil elevation]. The architectural floor plan shows FFE at [architectural elevation]. These elevations conflict. Which elevation governs for grading and foundation work? Please confirm the controlling FFE and advise whether the civil grading plan or the architectural documents require revision."
Resolution should follow the contract's governing-document hierarchy or order-of-precedence language. A Kentucky drawing set establishes civil drawings as the controlling source for final grade and spot elevations. The resolution also has to confirm which documents require revision so grading and foundation work are built from one controlling elevation.
Electrical: panel schedule conflicts with single-line diagram
An electrical RFI should isolate the exact mismatch between the panel schedule and single-line diagram because companion electrical documents must agree. The conflict may involve panel designation, main breaker rating, bus ampacity, voltage, AIC rating, or location. A concise field-style question addresses a location discrepancy:
"Which panel location is correct, Sheet E2.1 or Sheet E4.2?"
An AIC rating mismatch carries real consequences for how the gear gets installed and inspected. Washington State L&I's electrical submittal guide requires available interrupting current information to be coordinated with the one-line diagram, and the City of Tacoma's Tacoma Public Utilities instructions require panel schedules to match the panels called out in the one-line diagram.
Catching the conflict in an RFI is faster than catching it during inspection.
Field condition: as-built elevation discrepancy
A field-condition RFI should separate what the drawings show from what the field condition proves, then propose a path forward before work proceeds. In a representative drop-ceiling conflict, architectural ceiling plans show 9′-6″ while the mechanical sheets show 8′-6″ for equipment clearance. The RFI asks which ceiling height governs before ceiling work proceeds.
A clean response confirms the minimum ceiling height, identifies the equipment-clearance constraint, and records the agreed compromise. For field-condition RFIs, state what the plans show, identify the contradicting condition, reference the room or gridline, and propose a solution with cost and time impact.
Under AIA A201-2017 Section 3.2.3, the contractor must promptly report a discovered nonconformity to the Architect as a request for information in the required form.
Build Pre-Submission Validation Into the RFI Workflow with AI Agents
Pre-submission validation catches avoidable RFIs before they reach the design team. That is the workflow discipline behind every example above. The trivial RFIs, the already-answered RFIs, and the incorrectly submitted RFIs get resolved internally instead of consuming reviewer time.
AI agents apply the same checks a senior project engineer would run, on every RFI, without slowing the queue. Datagrid's RFI Validator Agent and RFI Checker Agent connect directly to the systems where RFIs and project files already live (Procore, Autodesk Construction Cloud, SharePoint) so the validation happens inside the existing workflow rather than as a separate review step.
The agents:
Cross-check the question against the contract drawings and specifications already in the project record
Confirm exact sheet and spec references, and flag any cost, schedule, or quality implications before routing
Resolve trivial or already-answered questions internally so only RFIs that need real design judgment reach the design team
The result is fewer avoidable questions in the reviewer queue, and project engineers spending their time on the RFIs that actually require a design decision.
Validate RFIs Before They Reach the Design Team
A clean RFI asks one question, cites the exact sheets and specifications, proposes a solution, and ties the response date to a crew. The harder work is applying that standard across project engineers and jobs.
Datagrid is the implementation path for that workflow. Its AI agents enforce consistent RFI validation before submission, so the design team receives fewer avoidable questions and project engineers stay focused on the RFIs that require real design judgment.
