What Is an RFI (Request for Information) in Construction?
An RFI — Request for Information — is the formal question a contractor sends to the design team when the construction documents are unclear, contradictory, or missing information needed to proceed. It's the paper trail that captures the question, the answer, and the date of the exchange. On a project with hundreds of decisions happening every week, the RFI log is the permanent record of how specific questions got resolved.
RFIs aren't casual. A verbal question to the architect on site is not an RFI. An email thread buried in someone's inbox isn't an RFI. The formal RFI process logs the question with a unique number, routes it to the responsible designer, captures the response in writing, and updates the master log. Anything short of that doesn't provide the contemporaneous documentation that disputes later rely on.
The trigger for an RFI is usually one of a few situations:
Situations that typically call for an RFI
- Conflicts between drawings — structural drawings show one thing, mechanical drawings show something incompatible, and the contractor needs a reconciliation
- Missing information — the drawings show a connection detail but not for the specific condition on the project, or a note refers to a detail that isn't in the drawing set
- Ambiguous specifications — the specification allows "or equal," but the contractor wants confirmation that a specific product qualifies
- Code or inspection issues — an inspector has required something that isn't clearly shown in the drawings, and the contractor needs direction
- Field conditions — what was shown as a wall turns out to be a structural column; the contractor needs guidance on how to adjust
- Scope ambiguity — a detail is shown on one page but seems to conflict with a note or spec on another, and the contractor needs to know which governs
A good RFI asks a specific, answerable question. "How do we handle the waterproofing detail at the parapet wall?" is a poor RFI because the answer could be many things. "At detail A5/A4.2, the drainage mat extends to within 3\" of the parapet cap, but the cap flashing shown in A6/A4.2 stops 12\" short of the mat. How should the termination be detailed to maintain weatherproofing?" is a good RFI — it's specific, references the drawings, and frames an actual question.
Most contracts specify an RFI response window — typically 5 to 10 business days. Critical-path RFIs (those affecting work about to be installed) should be flagged as such, and some contracts commit to shorter turnaround on CP items.
When responses lag, the contractor tracks the delay. An RFI about foundation reinforcement that takes 3 weeks to answer while the foundation crew is idle is ground for a schedule impact claim. The RFI log, with submission and response dates, is the evidence. Sharp contractors keep the log meticulous precisely because this documentation is what makes future claims credible.
RFI turnaround metrics matter. A project with a 12-day average RFI response time will feel very different from one with a 3-day average — and the evidence is in the log.
The standard RFI flow:
Standard RFI workflow steps
- Field recognizes a question and drafts the RFI with drawing references, photos if relevant, and the specific question
- GC project management reviews the RFI for completeness and appropriate framing before transmitting
- GC submits to the architect, logging the submission in the master RFI log
- Architect assigns to the responsible consultant (structural, mechanical, electrical) if outside architect's direct scope
- Consultant responds to architect; architect compiles and returns response to GC
- GC routes response to the field and to the affected sub(s)
- RFI log updated with response date and disposition
For complex RFIs, the response may include supplemental sketches (SK drawings) — small detail drawings the architect produces specifically to answer the RFI. These become supplementary contract documents and should be incorporated into the drawing set for future reference.
Not every RFI creates a cost or schedule impact, but some do. When the answer to an RFI requires additional work beyond what was originally shown or specified — a thicker slab, an additional framing member, revised mechanical routing — the impact becomes a change order.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
The RFI response should be reviewed by the contractor for scope impact before proceeding. If the response directs work that wasn't in the bid, the contractor should notify the owner that a change order is needed before starting the work. Proceeding without that notice can forfeit the claim.
The RFI log is the master tracker. Every RFI gets a unique number (typically sequential: RFI-001, RFI-002...), a submission date, a topic, the responsible party, a response-due date, the actual response date, the response summary, and a disposition (pending, responded, closed, awaiting revisions).
On a project with 200-400 RFIs, the log is a substantial document. Modern construction management software automates most of it — submissions, timestamps, routing, and closeout all flow through the platform. The log populates automatically from workflow activity.
These three document types sometimes overlap but have distinct purposes:
RFIs, submittals, and change orders — who does what
- RFI — asks a question about the design intent; the answer clarifies but doesn't by itself modify the contract
- Submittal — proposes specific materials or shop drawings for design team approval; verifies compliance with specifications
- Change order — amends the contract; adjusts price, time, or scope based on a formal modification
An RFI that leads to a change in scope becomes a change order when the parties agree on the cost and schedule impact. An RFI that just clarifies existing documents without changing scope doesn't become a change order — the clarification is part of interpreting the contract as already signed.
Patterns that make RFIs less effective than they should be
- Poorly written RFIs — vague questions get vague answers; specific questions get specific answers
- Missing backup — RFIs without drawing references or photos force the architect to hunt for context, slowing response
- Design team delay — responses that take weeks instead of days
- Responses that don't fully answer — architect responds but the answer creates new questions, requiring follow-up RFIs
- RFIs treated as change order proposals — contractor uses RFI to propose a change rather than to ask a clarifying question
- RFI bloat — too many trivial RFIs that should have been resolved at the field level, creating noise in the log
An RFI is the paper trail for resolving questions during construction. Well-written RFIs get specific answers quickly; poorly-written ones waste time. The log is the evidence base for both project coordination and any future claims. Keeping RFIs specific, documented, and tracked is one of the highest-leverage project management disciplines — every hour spent on disciplined RFI handling saves days of downstream confusion.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts