What does RFI stand for in construction?

RFI stands for Request for Information. It is a formal written question from the contractor to the design team asking for clarification, resolution of a conflict, or a decision on something the contract documents do not answer clearly. The question and its answer become part of the contract record, which is why RFIs are handled formally rather than by phone call.

When should you submit an RFI?

Submit an RFI when the drawings and specifications conflict with each other, when a detail is missing or does not work in the field conditions actually encountered, when a specified product is unavailable or discontinued, when a dimension does not close, or when existing conditions differ from what the documents showed. Do not submit one for something the documents already answer clearly — that is the fastest way to have your real RFIs deprioritized.

How long does an RFI take to answer?

Most contracts specify a response period, commonly 7 to 14 calendar days. Industry benchmarking has consistently found average actual response times of roughly 8 to 10 days, with a meaningful share taking far longer. Because a typical commercial project generates hundreds of RFIs, response time compounds: RFIs sitting open on the critical path are one of the most common documented causes of delay claims.

What should an RFI include?

A sequential number, the project and date, the specific drawing sheet, detail, or spec section at issue, a clear statement of the conflict or question, the field condition driving it, your proposed solution, the schedule and cost impact if the answer is delayed, and the date you need the response by. Attach a marked-up sketch or photo. An RFI that makes the reviewer hunt for the problem gets answered slowly or incompletely.

Who is responsible for answering RFIs?

The general contractor reviews and transmits RFIs from its subcontractors, filtering out questions the documents already answer. The architect responds, coordinating with the relevant consulting engineer — structural, mechanical, electrical, or civil — for questions in their scope. The owner is involved when the answer changes scope, cost, or schedule.

Does an RFI response constitute a change order?

No. An RFI answer is a clarification of the existing contract documents, not an authorization to perform additional work. If the response directs work beyond the original scope, that requires a separate change order or construction change directive. Proceeding on an RFI answer alone and billing for it later is one of the most common ways contractors end up unpaid for real work.

RFI in construction: what it is and how to write one

What an RFI is

A Request for Information is a formal written question from the contractor to the design team about something the contract documents do not answer. Sheet A-501 shows a detail that conflicts with the structural drawings. The specified valve was discontinued two years ago. The dimension string does not add up to the overall. The wall the demo drawings show as non-structural has a beam sitting on it.

Every one of those is an RFI. The reason it is written and numbered rather than resolved over the phone is that the answer changes what you build, and the record of who said what — and when — is what governs if there is a dispute later.

When to send one, and when not to

Send one when:

The drawings and the specifications say different things.
Two drawing disciplines conflict with each other.
A detail does not exist for a condition that exists in the field.
Actual conditions differ from what the documents showed.
A specified product is discontinued, unavailable, or has a lead time that will not make the schedule.
A dimension does not close or a detail is not physically buildable.

Do not send one when: the documents answer it, and you have not read them. Every design team triages its RFI log. A contractor with a reputation for sending questions already answered in Division 01 gets slower responses on the questions that matter. The filter is the GC's job, and it is worth doing.

Writing one that gets answered the first time

The single biggest lever on RFI turnaround is whether the reviewer can understand the problem in thirty seconds without opening anything else.

Include:

A number and date. Sequential, never reused.
The exact reference. Drawing sheet and detail number, or spec section and paragraph. "Per the plans" is not a reference.
The question, stated once, plainly. One issue per RFI. Bundling four unrelated questions guarantees that three get answered and one does not.
The field condition. What is actually there, with a photo.
A marked-up sketch. Cloud the conflict on the drawing itself.
Your proposed solution. This is the difference between a two-week RFI and a two-day one. A reviewer who only has to say "yes, do that" answers faster than one who has to design something. It also puts your preferred outcome on the table first.
Impact and required-by date. State the schedule and cost consequence honestly, and give a real date driven by procurement or sequencing.

Why response time is a schedule issue

A commercial project of any size generates hundreds of RFIs. Contracts typically allow 7 to 14 days for a response; actual averages land around 8 to 10 days, with a long tail of stragglers. A meaningful percentage of those sit on the critical path.

The compounding is the problem. An RFI on a long-lead equipment selection does not cost you ten days — it costs ten days, plus the submittal cycle that could not start until it was answered, plus the fabrication lead time behind that. RFI logs are among the first documents produced in delay claims for exactly this reason.

Two things actually help: writing RFIs that can be answered immediately, and tracking the open log by age and ball-in-court so a stalled one gets escalated at day eight rather than discovered at day thirty.

The record

Keep the RFI log as a contemporaneous record, not a reconstruction. Number, date submitted, date responded, ball-in-court, drawings affected, whether the answer changed scope, and whether a resulting change order was written. When an answer directs work outside the original scope, say so in writing at the time and get the change order — an RFI response is a clarification, never an authorization.

Where the automation helps

Drafting an RFI is judgment work. Everything around it is not: tracking the open log, flagging RFIs past their required-by date, identifying which drawings and submittals are blocked by an unanswered one, and — before construction even starts — reading the bid set to find the conflicts that are going to become RFIs anyway.

That last one is worth more than the rest combined. Finding a spec conflict during the bid means an RFI at bid time, when the answer is free. Finding it in month four means a change order argument. That is what BidVerify does with a bid package, and what JobHost does with the RFI log once the job is running.