What Is an RFI?
When the Drawings Don't Answer
Every set of contract documents has gaps, and the RFI is how the field gets them resolved in writing. Here is when to issue one, how it moves, why the response clock matters, and what an open question quietly does to the schedule.
An RFI, or request for information, is the standard construction process for resolving gaps, conflicts, or ambiguities in the contract documents. The contractor asks a specific written question; the architect or engineer answers it; the answer becomes part of the project record and can change scope.
When to Issue an RFI
The trigger is always the same underlying condition: the documents do not give the field enough to build from with confidence. These are the six situations that should produce an RFI, not a guess.
The drawings conflict with each other
The architectural plan shows one dimension, the structural plan shows another. The field cannot build both. An RFI puts the conflict in front of the designer and gets a single answer on record.
A detail is referenced but missing
The plan calls out a detail on a sheet that does not exist, or a section cut that was never drawn. The information the crew needs simply is not in the set.
The specification reads two ways
The spec language supports more than one interpretation, and the two readings carry different cost or effort. Guessing wrong means rework; an RFI makes the designer choose.
Field conditions do not match the documents
The existing utility is not where the survey shows it. The slab is thicker than the as-builts claim. The documents assumed a condition the site does not have.
A substitution or alternate needs design sign-off
The specified product is unavailable or has a long lead time, and the contractor needs written confirmation that a proposed equivalent is acceptable before ordering.
Trades clash where the documents are silent
Ductwork and structural steel want the same space, and no coordination drawing resolves it. The RFI asks the design team which element moves.
What an RFI is not: a way to request a change you simply want, a substitute for reading the documents, or a tool for shifting design responsibility onto the architect. An RFI that asks a question the documents already answer costs credibility on every RFI that follows it.
RFI vs Submittal vs Change Order vs NCR
Four documents, four different jobs. The RFI is the only one of the four that exists purely to get a question answered, and the only one that can quietly turn into one of the other three.
| RFI | Submittal | Change Order | NCR | |
|---|---|---|---|---|
| What it is | A written question asking the design team to clarify or interpret the contract documents | The contractor showing what it intends to furnish: shop drawings, product data, samples | A formal modification to the contract scope, price, or time | A formal record that completed work or material fails the specification |
| Direction | Contractor asks; architect or engineer answers | Contractor proposes; designer reviews and stamps | Negotiated and executed between owner and contractor | Raised by QC or the owner’s side; dispositioned by engineering |
| When it appears | When the documents are unclear, before or during the affected work | Before the work, on the submittal schedule | Whenever scope, price, or time actually changes | When an inspection, test, or observation finds a deviation |
| What closes it | A written answer from the design team | An approval or approved-as-noted stamp | Signatures from both parties | An approved disposition plus verified corrective action |
| Changes the contract? | Not by itself, but the answer can trigger a change order | No. It implements the contract as written | Yes. It is the mechanism that does | No, though it can lead to backcharges or claims |
Typical RFI Timelines
Most contracts state a response window, commonly in the range of one to two weeks from receipt. But the contract clock starts when the RFI lands on the architect's desk. The schedule clock started days earlier, when the field first hit the question. Five stages, and each has its own way of losing time.
| Stage | Who Owns It | Where the Time Goes |
|---|---|---|
| 1.Question identified in the field | Superintendent or foreman | The question lives on a whiteboard or in a text thread for days before anyone writes it down. This gap never appears in the RFI log, but the schedule absorbs it. |
| 2.Drafted and submitted | Project engineer or PM | Vague questions bounce back. A good RFI asks one specific question, references the exact sheet and detail, and proposes an answer the designer can simply confirm. |
| 3.Design team review | Architect of record | Routing. If the question belongs to a consulting engineer, it travels architect to consultant and back, and every handoff adds days the contract clock does not show. |
| 4.Answer returned | Architect or engineer | Answers that answer a different question, or raise a new one, restart the loop. So do answers that quietly direct extra work without acknowledging the cost. |
| 5.Distributed and closed | PM, to affected subs | An answer that never reaches the crew that asked is the same as no answer. Closure means the answer is logged, distributed, and the work released. |
Why Open RFIs Cost Money
An RFI is free to write. What it costs is everything that happens while it stays open. The cost is rarely the answer itself; it is the work standing behind the question.
Crews Wait or Work at Risk
While the question sits unanswered, the affected work either stops, and the crew is resequenced or idle, or it proceeds on an assumption. If the assumption is wrong, the answer arrives as demolition instructions.
Float Erodes Silently
An open RFI on a critical-path activity is a schedule delay that no one has called a delay yet. The float it consumes is invisible until the activity it blocks was supposed to start.
Late Answers Arrive as Changes
The longer an answer takes, the more work gets built around the open question, and the more expensive the answer becomes to implement. An answer that would have been a pen stroke in week one is a change order in week six.
The Log Becomes Claims Evidence
In a delay or change claim, the RFI log is a core exhibit: what was asked, when, and how long the answer took. A well-kept log with dates defends you. A gappy one defends the other side.
RFI Impact in POD
When the field mentions a blocked crew or an unanswered question in a daily report, POD connects the open RFI to the work it is holding, so the cost of waiting is visible today, not at the next owner meeting.
RFI Impact Today
PODDaily RFI cost
Unanswered
Open pipeline
Frequently Asked Questions
Know Which Questions Are Holding Work
Your superintendent already says it every day: "still waiting on the answer for the footing detail." POD turns those mentions into a living RFI picture, aged, connected to the crews it blocks, and impossible to lose in an inbox.