RFI Best Practices in Construction: Types, Process, and How to Write One That Gets Answered
You're three weeks into a $12M office renovation. The MEP contractor sends an RFI: "Clarify duct routing at grid line C between floors 2 and 3." No drawing reference. No photo. No indication of what the actual problem is.
You forward it to the MEP engineer. Two days later: "Need more information. What's the conflict?" Back to the contractor. Another day. They send a blurry photo with no context. Back to the design team. Two more days.
By the time an answer arrives you've burned a week and a half, the duct installers have moved to another job, and nobody has started solving the actual problem.
RFIs exist to keep construction projects moving. Written poorly, they become one of the largest sources of delay on a job. This guide covers what RFIs are, the types you'll encounter, the process they follow, and the practices that get them answered on the first pass.
What Is an RFI in Construction?
A Request for Information is a formal document used to resolve ambiguity, conflict, or missing information in the contract documents. When a drawing contradicts a spec, when a detail is absent, or when a field condition differs from the design, the RFI creates a written record of the question and the answer.
Two things distinguish an RFI from other project paperwork. It asks a question rather than confirming compliance, which is what separates it from a submittal. And it carries no authority to change scope or price, which is what separates it from a change order. An RFI response may trigger a change order, though the RFI itself is a clarification.
Types of RFIs
Categorizing RFIs helps you route them to the right reviewer and spot patterns across projects. The common types:
Design clarification
Triggered by: Ambiguous or incomplete detail
Typical reviewer: Architect
Document conflict
Triggered by: Drawing contradicts spec, or two drawings disagree
Typical reviewer: Architect or relevant engineer
Field condition
Triggered by: Existing conditions differ from the drawings
Typical reviewer: Architect plus structural
Substitution inquiry
Triggered by: Specified product unavailable or impractical
Typical reviewer: Engineer of record
Coordination
Triggered by: Two trades competing for the same space
Typical reviewer: Multiple disciplines, sequentially
Constructability
Triggered by: Design is buildable only with impractical means
Typical reviewer: Architect plus engineer
Scope clarification
Triggered by: Unclear which contractor owns a piece of work
Typical reviewer: GC and owner's rep
Tracking RFIs by type pays off over time. When half your RFIs on a project are document conflicts in one discipline, you've learned something useful about that design set, and about what to check earlier on the next job.
The RFI Process, Step by Step
- Identify the issue. A field crew, project engineer, or subcontractor spots a conflict or gap.
- Check whether it's already answered. Current drawing revision, approved submittals, prior RFI responses, meeting minutes.
- Draft the RFI with references, supporting documents, and a proposed solution.
- The GC reviews and routes it to the appropriate reviewer.
- The design team responds within the contractual window, commonly 7 to 14 days.
- The GC distributes the answer to everyone affected, including subs and suppliers.
- The response gets logged and linked to the drawings or specs it modifies.
Timing matters more than most teams realize. One analysis of 22 construction projects found that teams submitting RFIs earlier in the process reached a median closure rate of 8 days, compared with 16 days for the control group. Submitting early cuts response time roughly in half.
How to Write an RFI That Gets Answered
The number one problem with most RFIs is that they give the reviewer too little to work with.
Include specific drawing and spec references
Weak: "Clarify insulation requirements for exterior walls."
Strong: "Detail 5/A-301 shows R-19 batt insulation in 2x6 stud wall. Spec Section 07 21 00 paragraph 2.3 requires continuous R-13 exterior rigid insulation. Both requirements together exceed available wall depth. Confirm insulation assembly."
The second version tells the architect exactly where to look and what the conflict is, so they answer immediately rather than asking a follow-up question. Every RFI should cite sheet numbers, detail references, and spec section numbers.
Ask one clear, answerable question
Weak: "There are issues with the door schedule and hardware. Please advise."
Strong: "Door D-301 schedule calls for 3070 hollow metal door with Grade 1 lockset. Spec 08 71 00 requires Grade 2 locksets for all interior doors. Should D-301 receive Grade 1 per schedule or Grade 2 per spec?"
The second version can be answered in one sentence. When you have several unrelated questions, write several RFIs, because one question per RFI makes tracking and answering far faster.
Attach relevant documentation
Photos, marked-up drawings, product data, anything that spares the reviewer a hunt through their own files. For field conditions, attach photos of what you're looking at. For document conflicts, attach both conflicting pages with the difference circled and an arrow pointing at the problem.
Propose a solution
Weak: "Clarify structural support for roof-mounted HVAC unit."
Strong: "Structural drawings do not show curb support for HVAC unit per M-401. Propose installing (4) W8x15 beams spanning between existing joists at grid lines B-C. Confirm this approach or provide alternate solution."
Reviewers appreciate a contractor who has thought the problem through, and they frequently approve the proposed solution outright, which puts you back to work immediately.
Copy-Paste RFI Template
RFI #: [Number] Project: [Name]
Date submitted: [Date] Response required by: [Date]
Spec section: [Number] Drawing reference: [Sheet/Detail]
Discipline: [Arch/Struct/MEP]
BACKGROUND
[One or two sentences of context]
ISSUE
[The specific conflict or gap, with both sources cited]
QUESTION
[The single decision needed]
PROPOSED SOLUTION
[Your recommendation]
SCHEDULE IMPACT
[What work is waiting, and the date it's scheduled]
ATTACHMENTS
[Marked-up drawings, photos, product data]
Keep the whole thing under 200 words unless genuine complexity demands more.
Timing and Workflow Practices
Submit the same day the issue appears
Waiting for the weekly coordination meeting adds days to a cycle that was already long. Set a same-day or next-day standard and train project engineers and superintendents to document and submit immediately.
Tie deadlines to field activities
"Need response by March 15, rough-in inspection scheduled March 18" outperforms "please respond ASAP" every time, because the reviewer can see what breaks if they wait. Calculate the real deadline backward from the work, accounting for lead times and fabrication.
Match the review workflow to the question
Coordination questions crossing disciplines belong in sequential review, where the engineer answers before the architect. Straightforward clarifications move faster in parallel review, where everyone sees the item at once. Platforms like SubmittalLink let you set this at the project level so routing happens automatically.
Follow up before the deadline
At roughly 75% of the expected response time, send a reminder. On a 7-day turnaround, that means checking in on day 5, while there's still room to recover.
Escalate on a defined schedule
When an RFI sits for twice the expected response time, escalate rather than resending the same ignored email. A workable protocol: PM calls the reviewer at day X, owner's rep gets notified at X+3, and potential delay gets documented formally at X+5.
Common RFI Mistakes
Asking about something already answered
Before writing, check the current drawing revision, the approved submittals, previous RFI responses, and meeting minutes. RFI spam trains reviewers to deprioritize your questions, and once half your RFIs cover settled ground, they assume the rest are equally careless.
Using RFIs instead of reading the specs
"How should we install this?" for standard trade practice is not a clarification request. RFIs address genuine ambiguity in the contract documents. The test: is this a real document conflict, or does someone need to read the specification more carefully?
Burying the question in narrative
Nobody reads three paragraphs to find the ask. Use the template structure above so the question sits where the reviewer expects it.
Leaving verbal answers undocumented
The architect tells you something during a site walk. Write it up anyway: "Per our conversation on 3/12, confirm that [decision]. If this understanding is incorrect, please clarify." Verbal agreements turn into "I never said that" months later.
Letting RFIs go stale
An unanswered RFI that nobody is chasing will stay unanswered. Someone owns follow-up on every open item, every week.
Tools That Improve RFI Management
Email and spreadsheets hold up until roughly 50 open RFIs across a couple of projects. Past that, three capabilities start paying for themselves.
A centralized RFI log showing number, title, submission date, reviewer, status, due date, response date, and a summary, accessible to the whole project team so nobody asks what happened to the roof drain RFI.
Automated notifications and reminders that fire on submission, on response, and again as deadlines approach, which removes the manual chasing that consumes hours weekly. Set reminders at three days out and again on the due date.
Ball-in-court tracking that names who owes action right now. "Pending, Architect Review" beats "Pending" because it assigns responsibility rather than describing progress.
SubmittalLink handles all three. RFIs route automatically to the right reviewers in parallel or sequential order, reminders go out without anyone drafting them, RFIs link directly to the drawings they reference, and every action lands in a complete audit trail.
Reviewers can respond straight from an email notification without creating an account, which is usually what determines whether external reviewers participate at all.
Pricing is flat by construction volume, $150/month under $5M and $250/month from $5M to $25M, with unlimited users and unlimited projects so every consultant and sub joins at no extra cost.
Building RFI Discipline Into the Project
- Set standards at kickoff. Use the preconstruction meeting to establish response timeframes, documentation requirements, review workflows, and escalation procedures. Expectations set upfront get followed.
- Audit RFI quality monthly. Review turnaround times, how many of your RFIs came back asking for clarification, and how many sit past due. Show your team examples of strong and weak RFIs from their own project.
- Track the metrics that reveal bottlenecks: average response time by reviewer, percentage of RFIs requiring clarification, open RFIs past due date, and delay days attributable to slow responses.
Frequently Asked Questions
What makes a good RFI in construction?
A good RFI cites specific drawing and spec references, asks one clear answerable question, attaches supporting documentation like marked-up drawings or photos, and proposes a solution. It gives the reviewer everything needed to respond without a follow-up request.
How quickly should RFIs be submitted?
The same day or next day after the issue is identified. Research on 22 projects found early submitters closed RFIs in a median of 8 days versus 16 days for teams that waited.
How long should a response take?
Most contracts specify 7 to 14 days. Include a required-by date tied to field activities so reviewers can prioritize against your actual schedule.
What's the difference between an RFI and a submittal?
An RFI asks a question about the contract documents. A submittal proves that a proposed product or method complies with them.
Can an RFI change the scope of work?
No. An RFI clarifies existing documents. When the answer adds cost or time, it gets handled through a change order.
Who reviews RFIs?
Usually the design discipline that owns the question, with the general contractor routing and tracking. Coordination questions across trades often need several reviewers in sequence.
How do you track RFI responsibility?
Ball-in-court tracking, where the status names the responsible party rather than describing progress.
The Bottom Line
RFIs done well prevent problems. RFIs done poorly become the problem. Write them with specific references and a single clear question, propose an answer, submit the day the issue appears, tie the deadline to real field work, and follow up before it's late.
Tired of chasing RFI responses through email chains? See how SubmittalLink automates RFI workflows with ball-in-court tracking, RFIs linked to drawings, automated reminders, and review routing that matches how your team works. Book a 15-minute demo.