How to Write an RFI That Gets Answered Fast
A well-written RFI can be resolved in days. A vague one bounces between parties for weeks. The difference comes down to clarity, precision, and providing the reviewer with everything they need to respond on the first pass.
Why RFI Quality Matters
RFIs carry real cost and schedule weight. Every poorly written request wastes time for the submitter, the reviewer, and everyone waiting on the answer. These numbers illustrate why getting it right the first time is critical.
Average Processing Cost
~$1,080 per RFI
When you factor in labor time from the contractor, architect, and owner's rep, each RFI carries a significant administrative burden.
Typical Resolution Time
10 – 15 days
The average RFI takes 10 to 15 days from submission to a usable response, assuming it does not require follow-up clarification.
Poorly Written RFIs
2 – 3x longer to close
Vague or incomplete requests take two to three times longer because they require additional rounds of back-and-forth before a resolution.
Clarification Rate
30 – 40% need follow-up
Nearly a third of all RFIs require additional clarification before they can be resolved, often because the original submission lacked key details.
Step 1: Verify You Actually Need an RFI
Before drafting anything, make sure the answer is not already available in the existing contract documents. Many unnecessary RFIs can be avoided with thorough document review.
Review Related Drawings
Cross-reference architectural, structural, and MEP sheets. The answer may appear on a different discipline's drawing or in a detail referenced elsewhere.
Check Specifications
Read the relevant specification sections in full. Many questions about materials, methods, and performance criteria are addressed in the specs rather than the drawings.
Search Previous RFIs
Check whether the same question or a closely related one has already been asked and answered on this project. Duplicate RFIs waste everyone's time.
Review Addenda & Bulletins
Addenda issued during bidding and bulletins issued during construction may have already addressed the issue. Always work from the latest document revision.
Check Meeting Minutes
OAC meeting minutes, pre-installation conferences, and coordination meeting notes may contain decisions or clarifications that resolve your question.
Step 2: Write a Descriptive Subject Line
The subject line is the first thing a reviewer sees, and it determines how quickly your RFI gets routed to the right person. A specific subject line accelerates the review; a generic one buries it.
Weak Subject Lines
"Plumbing question" — gives the reviewer no idea what the issue is, where it is, or which drawing to open.
Weak Subject Lines
"Clarification needed" — applies to virtually every RFI ever written and provides zero context for prioritization.
Weak Subject Lines
"Drawing conflict" — which drawings? Which area? What conflict? The reviewer cannot begin without more information.
Strong Subject Lines
"Roof drain size conflict — P-301 vs P-501 at Grid C-4" — tells the reviewer exactly what, where, and which sheets to pull up.
Strong Subject Lines
"Missing fire-rating for CMU wall at Stair 2, Level 3 (A-211)" — identifies the element, location, floor, and sheet in a single line.
Strong Subject Lines
"Duct routing conflict with structural beam — Level 2 Corridor B (M-201 / S-102)" — names both disciplines and both sheets so the right reviewers engage immediately.
Step 3: Describe the Issue Clearly
The body of the RFI should give the reviewer a complete picture of the problem in four parts: where it is, what element is involved, what the issue is, and why it matters.
Location
Specify the building, floor, area, grid lines, or room number. Be precise enough that someone unfamiliar with your daily work can find the spot on the drawings.
Element
Identify the specific component: duct, pipe, wall type, structural member, fixture, or finish. Use the terminology from the contract documents so there is no ambiguity.
Issue
State the problem: conflicting dimensions, missing information, contradictory notes between sheets, or a condition that does not match the specification.
Impact
Explain what happens if the issue is not resolved: work stoppage, rework, material procurement delay, or downstream coordination failure. This helps the reviewer prioritize.
Step 4: Provide Exact Document References
Never make the reviewer hunt for the relevant documents. Cite every drawing, detail, and specification section that relates to the issue so they can evaluate it immediately.
Sheet Numbers
List every drawing sheet that shows the condition in question. Include both the plan sheet and any referenced details or sections.
Detail References
Cite specific detail numbers, section cuts, and enlarged plans. Use the format shown on the drawings (e.g., Detail 3/A-501) so the reviewer can locate them instantly.
Specification Sections
Reference the spec section number, paragraph, and any specific clause that is relevant. Include the section title for clarity (e.g., "Section 07 92 00 — Joint Sealants, 3.03.B").
Revision Dates
Note the drawing revision number and date you are working from. This ensures the reviewer evaluates the same version and avoids confusion from superseded information.
Marked-Up Excerpts
Attach cropped and annotated portions of the relevant drawings. Highlight the conflict, circle the missing information, or cloud the area in question so the reviewer can see the issue at a glance.
Step 5: Ask a Specific Question
The question is the most important part of the RFI. A vague question invites a vague answer. Frame your question so the reviewer can give a direct, actionable response.
Vague Question
"What should we do about the pipe routing?" — Does not identify which pipe, where, or what the conflict is. The reviewer cannot answer without asking follow-up questions.
Specific Question
"The 6-inch chilled water supply shown on M-201 conflicts with the W12x26 beam at Grid D-3, Level 2. Should we route below the beam or offset north to clear?" — Gives the reviewer all the context to decide.
Vague Question
"Please confirm the wall type." — Which wall? Where? What about it is uncertain? This will be returned for clarification.
Specific Question
"A-201 labels the corridor wall at Grid B-2 as Type W3 (1-hr rated), but the partition schedule on A-601 lists it as Type W5 (2-hr rated). Which rating applies?" — Identifies both sources and asks for a clear resolution.
Vague Question
"Is this correct?" — The reviewer has no idea what "this" refers to without digging through attachments. State the issue explicitly.
Specific Question
"S-301 shows #5 rebar at 12 inches on center for the slab at Level 4, but the structural note on S-001 specifies #4 at 10 inches for slabs over 8 inches. Which reinforcing schedule governs?" — Precise enough for a one-line response.
Step 6: Suggest Possible Solutions
Offering options shows the reviewer you have thought through the problem and gives them a starting point. It is faster to evaluate two proposed solutions than to create one from scratch.
Option A
Describe the first potential resolution: what would be done, how it affects the design, and any cost or schedule implications. Include enough detail for the reviewer to approve or reject.
Option B
Describe the alternative approach. Note any trade-offs compared to Option A: different materials, routing, structural impact, or long-term maintenance considerations.
Contractor Recommendation
State which option you prefer and why. Your field experience adds value to the decision. If you have no preference, say so — but always provide options when possible.
Step 7: Include Supporting Visuals
A marked-up drawing or a site photo can communicate in seconds what takes a paragraph to describe. Visual evidence removes ambiguity and speeds up the review.
Marked-Up Drawings
Crop the relevant portion of the drawing, cloud or highlight the area in question, and add callouts that point to the specific conflict or missing information.
Site Photographs
Take clear, well-lit photos of the field condition. Include a reference object for scale, and annotate the photo to show exactly what the RFI is about.
Comparison Images
Place conflicting details side by side so the reviewer can see the discrepancy instantly. Label each image with the sheet number and revision date.
Solution Sketches
If you are proposing alternatives, include a quick sketch or annotated diagram showing the proposed routing, connection, or layout change. It does not need to be polished — just clear.
Step 8: Communicate the Urgency
Telling the reviewer "this is urgent" is not enough. Show them why by tying the RFI to specific schedule milestones, dependent work, and real consequences of delay.
Work Start Date
State when the affected work is scheduled to begin. A response needed three weeks from now gets different treatment than one needed in three days.
Dependent Activities
Identify which downstream trades or activities are blocked until this RFI is resolved. This helps the reviewer understand the ripple effect of a delayed response.
Delay Consequences
Quantify the impact: crew standby costs, critical path delay, or missed inspection windows. Concrete numbers get faster attention than generic urgency claims.
Response Deadline
Provide the latest date you need a response to avoid impact. Work backward from the construction schedule and include procurement lead times if materials are involved.
Frequently Asked Questions
How long should an RFI response take?
Most construction contracts establish a response window of 7 to 14 calendar days. The exact timeframe depends on contract terms and the complexity of the question. Time-sensitive or critical RFIs may justify a shorter turnaround negotiated between the parties. If no contractual timeframe is specified, industry practice defaults to 7 to 10 business days.
What is the difference between an RFI and a submittal?
An RFI asks a question to resolve ambiguity, conflict, or missing information in the contract documents. A submittal provides product data, shop drawings, or material samples for the architect to review and verify compliance with the design intent. Put simply: RFIs seek clarification, while submittals seek approval.
Can an RFI response change the contract scope?
An RFI response that clarifies existing contract documents does not change the scope of work. However, if the response directs work that goes beyond the original contract requirements, the contractor should issue a notice of potential change and follow the change order process defined in the agreement. Always review RFI responses carefully for scope implications.
Related Resources
How to Track RFIs
Set up numbering, status tracking, aging reports, and metrics to keep your RFI log under control.
Change Orders Guide
Document types, pricing methods, markup structures, and processing steps for construction change orders.
Knowledge Base
Guides, references, symbols, abbreviations, and review checklists for AEC professionals.
Reduce RFIs Before They Start
Book a demo and see how Structured AI catches drawing conflicts, missing details, and coordination issues during design review — before they become costly RFIs in the field.
Try Automated Drawing Review