What Is an RFI in Construction?

That distinction explains almost everything about how an RFI behaves on a project. Because the response becomes part of the contract record, it has to be written, numbered, dated, and routed through a defined chain — contractor to construction manager to architect, often out to a consultant, and back again.

A question that would take thirty seconds to answer verbally takes a week to answer formally, and the week is the point: the written answer is what protects both parties if the work later turns out to be wrong. Verbal direction on a job site is not a substitute, and experienced teams treat it as a prompt to raise an RFI rather than as an answer.

The trigger is almost always a gap between what the documents say and what the field needs. Four situations account for most of them: the documents are ambiguous, two documents conflict, information the contractor needs is simply missing, or the existing conditions on site do not match what was drawn.

A fifth category shows up constantly but is not really a question at all — the substitution request dressed up as an RFI, where a specified product is unavailable or expensive and the contractor asks whether an alternative is acceptable. Sorting genuine document questions from substitution requests and from questions already answered elsewhere is most of the review work.

The contractor writes the question, gives it a number, references the specific sheet or specification section it relates to, and usually proposes an answer. It goes to the construction manager or general contractor, who screens it and forwards it to the design team.

The architect researches the question, routes it to the relevant consultant if it is structural, mechanical, electrical or civil, and issues a written response. If the answer changes scope, cost or schedule, it does not stop at the RFI — it becomes a change order, an architect supplemental instruction, or a bulletin.

Throughout, the RFI log tracks the number, the date issued, the date required, the responder, and the status. Cycle time — the days between issue and close — is one of the most watched metrics in construction administration, because an open RFI on a long-lead item is a procurement delay waiting to happen.

A large commercial project routinely generates several hundred RFIs, and volume is the usual complaint. But a substantial share of RFIs are not genuine design questions. They are requests for information that already exists somewhere in the set — a dimension on a different sheet, a requirement in a specification section nobody opened, a detail that was answered on a previous RFI months earlier.

The rest split into real coordination gaps, differing field conditions, and substitution requests. Treating the total count as the metric hides that split. A project with two hundred RFIs where most are genuine coordination gaps has a different problem than one with two hundred where most were already answered in the documents.

Answering an RFI properly means finding every place the project already speaks to the question: the plan, the section, the schedule, the specification section, the approved submittal, the previous RFI on the same assembly. On a project with a document set running to thousands of pages across multiple revisions, that search is where engineering hours disappear.

It is also where inconsistency creeps in, because the quality of an answer depends on how thoroughly the person answering happened to look. Two RFIs on the same assembly, answered by two people a month apart, can contradict each other — and that contradiction is exactly what surfaces later in a dispute.

First, close the loop. When an RFI reveals a genuine documentation gap, the same gap usually exists on the firm’s other projects. Catching it during drawing review is an order of magnitude cheaper than catching it in the field, and firms that feed RFI patterns back into their standards see the recurring questions disappear.

Second, track cycle time by responder rather than in aggregate. An average that looks acceptable often hides one consultant sitting on the critical-path questions while everything else closes quickly.