The RFI process.From open question to answered.
A 2026 reference for the construction RFI process: when to issue one, how to write RFIs that get answered fast, ball-in-court tracking, response-time benchmarks, and what an unanswered RFI costs the project every day it sits.
An RFI (request for information) is a formal written question from the contractor to the designer or owner when the contract documents are unclear, incomplete, or conflicting. Every day an RFI sits unanswered, the affected work either proceeds at risk or stops. Both outcomes cost money.
RFI vs submittal vs change order
Three documents, three different jobs. An RFI asks a question, a submittal demonstrates conformance, and a change order amends the contract. The most expensive confusion on a project is treating an RFI answer that changed the work as if it were a free clarification.
| Attribute | RFI | Submittal | Change Order |
|---|---|---|---|
| Purpose | Resolve ambiguity, gaps, or conflicts in the contract documents | Demonstrate that intended materials and methods conform to the specification | Formally modify the contract scope, sum, or time |
| Initiated by | Contractor (usually raised in the field, drafted by the PM or engineer) | Contractor, per the submittal register the specification requires | Either party; frequently born from an RFI answer that changed the work |
| Responded to by | Architect or engineer of record, routed to consultants; owner when a decision is required | Architect or engineer of record | Owner executes; designer reviews pricing and scope |
| Typical trigger | Two documents conflict, a detail is missing, or a field condition the documents never anticipated | The specification requires review before installation | Scope, cost, or schedule is changing and the contract must follow |
| Outcome | A written clarification that becomes part of the project record | Approved, approved-as-noted, or revise-and-resubmit | An amended contract sum or contract time |
| Changes the contract? | No, unless the answer changes the work; then it is a constructive change | No | Yes, by definition |
The submittal register runs on the same clock as the RFI log, and stalls the same way: items pile up in one review stage while the schedule waits. This is what the sibling pipeline looks like when its stages are tracked:
Submittal Velocity
PODSubmittal pipeline
Pipeline health
Anatomy of an RFI that gets answered
Response time is not something that happens to an RFI. It is largely determined the moment the RFI is written. Five moves separate a question that comes back in one pass from one that bounces for weeks.
- 1
Confirm the documents don't already answer it
Search drawings, specifications, addenda, and prior RFI answers before drafting.
An RFI whose answer is already sitting in the documents costs the one currency that determines how fast your future RFIs get answered: credibility. Reviewers triage. The contractor whose last five RFIs were all genuine gaps gets read first. If the answer exists but conflicts with another document, cite both sheet references in the question. The conflict is the real RFI, and naming both sides of it is what separates a one-pass answer from a round of "please clarify your question."
- 2
Ask one question per RFI
A compound RFI moves at the speed of its slowest answer.
Five questions inside one RFI number means the four easy answers wait for the one hard answer, and the whole item ages as a single unit. Split them. Each RFI gets its own number, its own reviewer routing, its own closure. This also keeps the log honest: an aging report that shows one 40-day monster hiding four resolved questions misstates where the project actually stands. One question, one answer, one closure date.
- 3
Propose a solution
Convert an open-ended design exercise into a yes-or-no review.
"How should we resolve this?" hands the designer a blank page. "We propose to resolve this per the attached sketch; please confirm" hands them a decision. Decisions come back faster than designs, and the difference is measured in days, not hours. A proposed answer also puts the contractor's preferred means and methods on the table first, which matters when more than one resolution is technically acceptable but only one of them is cheap to build.
- 4
Attach markups and photos
The reviewer should never have to reconstruct the question from a sheet number.
Clip the drawing region in question, cloud the exact location, and attach it. If the condition exists in the field, attach a photo with enough context to orient someone who has not walked the site. Every minute a reviewer spends hunting through sheets to find your question is a minute added to every RFI behind yours in their queue. What a reviewer can see in ten seconds, they can often answer the same day.
- 5
State the cost-and-schedule impact date
Name the date an answer is needed and the consequence after it.
An RFI without a needed-by date is a question without a priority. State the date the answer must arrive, and what happens the day after it does not: which activity stops, which crew goes idle, or what the field will build at risk. This does two jobs at once. It gives the reviewer a real triage signal today, and it starts the contemporaneous written record that a delay claim will stand on later. If the impact date passes unanswered, the daily report should say so, every day, in writing.
The RFI lifecycle and ball-in-court
An RFI is a relay race between three parties, and ball-in-court is the answer to the only question that makes aging actionable: whose move is it right now? Aging that is not attributed to a holder is a number nobody owns. Aging that is attributed is a to-do list with names on it.
- 01
Drafted
Ball in court: ContractorThe field flags the question, the PM or project engineer verifies the documents don't already answer it, assigns the next RFI number, and packages the question with markups and an impact date. Time spent here is invisible on most logs, but a question that sits in a superintendent's notebook for three days before it becomes an RFI has already aged three days.
- 02
Submitted
Ball in court: Transfers to designerThe RFI enters the designer's queue and the contractual response clock starts. The submission timestamp is the anchor for every aging calculation that follows, which is why it belongs in a log the moment it happens, not at the end of the week.
- 03
In review
Ball in court: Designer / OwnerThe architect routes structural questions to the structural engineer, mechanical questions to the mechanical engineer, and cost-bearing decisions to the owner. Each handoff in that chain is a place where an RFI can silently stall, and none of those handoffs are visible to the contractor unless ball-in-court is tracked at the sub-step level. This is where most aging accumulates.
- 04
Answered
Ball in court: Back to contractorThe answer arrives and the contractor makes the single most consequential judgment in the RFI process: is this a clarification of what the documents already required, or does it change the work? A clarification gets incorporated. A change triggers notice and a potential change order. Absorbing a change silently is how contractors donate scope.
- 05
Incorporated & closed
Ball in court: ContractorThe answer is distributed to the affected crews, the record drawings are marked, blocked work is released, and the RFI is closed with a date. An answer that reaches the PM's inbox but never reaches the crew that asked the question has not actually closed anything; the field builds from what it knows.
Response-time benchmarks
The benchmark that governs is the one in your contract: the response window written into the general conditions or Division 01, commonly on the order of one to two weeks. What the contract cannot tell you is where an RFI is aging or why. That takes buckets. The four below are a management convention, not a statistic, and they exist to trigger a named action at a named age instead of a monthly shrug at the log.
Inside almost any contractual response window. Monitor; no action beyond routine log review.
Approaching or past a typical contract window. Confirm whose court it sits in and send a written status request.
Raise at the OAC meeting by number, with the blocked activity and impact date on the record. Follow up in the daily report.
Formal written notice of delay impact. If work is proceeding at risk, document exactly what is being built on which assumption.
Plotted as a cascade, the aging picture answers the question a flat log cannot: not how many RFIs are open, but how much exposure is concentrated in the oldest ones.
RFI Aging Cascade
PODAging cost waterfall
Impact
What an unanswered RFI costs per day
An open RFI that blocks work forces a daily choice between two costs: stop and pay for idle time, or proceed and carry rework exposure. Neither is free, and the per-day figure is not a mystery. It is the labor and equipment committed to the blocked activity, readable straight off the daily report, multiplied by every day the ball sits in someone’s court.
Idle labor and standby equipment
If the crew stops, the meter runs anyway: the labor committed to the blocked activity, the equipment on rent whether it turns or not, and the remobilization cost when the answer finally lands and the crew comes back. This number is knowable to the dollar from the daily report, which is exactly why the daily report should name the RFI blocking the work.
Proceed-at-risk rework exposure
If the crew keeps going, the project trades a visible daily cost for an invisible contingent one: everything built on the assumed answer is exposed until the real answer arrives. When the assumption holds, the gamble was free. When it does not, the cost is demolition plus rebuild plus the schedule to do both, and the record must show the owner knew the field was proceeding at risk.
Critical-path multiplication
An open RFI on a non-critical activity consumes float. The same RFI on the critical path consumes the project: every successor slips day-for-day, general conditions burn on the whole job, and the completion date moves. The cost per day of an RFI is not a property of the RFI; it is a property of where the blocked activity sits in the schedule.
Compression at the far end
Days lost waiting for answers are usually paid back later at premium rates: overtime, added crews, resequenced trades stacking in the same area. The project pays twice, once when the work stops and again when it accelerates. Delay claims exist because that second payment is real and provable, but only if the first was documented on the day it happened.
This is what the daily picture looks like when each blocking RFI carries its cost-per-day and the activity it holds hostage:
RFI Impact Today
PODDaily RFI cost
Unanswered
Open pipeline
When RFIs become change orders
Some RFI answers clarify what the documents already required. Others quietly change the work: a heavier member, an added layer, a more expensive method. The second kind is a constructive change, and it is compensable, but only for contractors who catch it, give notice inside the contractual window, and keep the paper chain intact. Four failures give that entitlement away.
- 01
Absorbing scope silently
The designer answers an RFI with a detail that upgrades a material or adds work the documents never required, and the contractor just builds it. That answer was a constructive change. Every RFI answer should pass through one explicit gate before incorporation: does this change the cost or time of the work? If yes, it gets a potential change order number before a crew touches it.
- 02
Missing the notice window
Most contracts require written notice of cost or schedule impact within a defined number of days of the direction that caused it. A contractor who receives a scope-changing RFI answer and waits three weeks to price it may have already waived the claim. The notice does not need final pricing; it needs to be written, dated, and to reference the RFI number.
- 03
Pricing after the work is done
Work performed before it is priced is work negotiated from weakness. Once the material is installed, the only leverage left is the paper trail. Where the schedule truly cannot wait, proceed under a documented time-and-materials directive or a signed work-change directive so the entitlement question is settled even while the price is not.
- 04
Losing the RFI-to-change-order thread
A change order that cannot be traced back to the RFI answer that caused it, and from the RFI to the daily reports that show the impact, is a claim standing on memory. The chain that wins reviews is boring and complete: RFI number, answer date, notice date, PCO number, and the daily reports in between, all telling the same story.
The RFI log and the daily report usually live in different files, which is why nobody can answer the only question that matters at the morning meeting: which open RFI is costing us money today? Plan of Day connects the two. When a superintendent speaks the daily report and says a crew is waiting on an answer, POD ties that open RFI to the activity it blocks, the crew and equipment committed to it, and the days it has been sitting in whose court. POD Intelligence surfaces the aging picture and the blocking items in the morning brief, so escalation happens at day eight in writing instead of day thirty in a claim. The paper chain that a constructive change depends on, from RFI number to answer date to notice to the daily reports in between, builds itself as a byproduct of reporting the day.
Frequently asked questions
Further reading
Free Construction RFI Log Template
A ready-to-use RFI log with ball-in-court, aging, impact date, and status fields already structured.
Free Construction Submittal Log Template
The sibling log: track submittal stages, review cycles, and the approvals your schedule is waiting on.
What Is an RFI? (Request for Information)
The short glossary answer, for anyone who needs the definition without the full process guide.
Sources
- AIA G716 Request for Information (RFI) — the standard RFI form: question, proposed solution, response, and attachments.
- AIA A201 General Conditions of the Contract for Construction — governs document interpretation, claims, and the notice provisions constructive-change entitlement depends on.
- ConsensusDocs 200 Standard Agreement and General Conditions — alternative contract framework with comparable information-request, direction, and notice provisions.
- Associated General Contractors of America (AGC) — project delivery and documentation guidance, including RFI and change-management practice.
- Navigant Construction Forum, “Impact & Control of RFIs on Construction Projects” (2013) — widely cited industry research on RFI volumes, review effort, and response times.