The RFI: How to Ask a Question That Actually Protects You

Most contractors think of the Request for Information as an interruption — a form you fill out when the drawings don't make sense, sent off with a shrug while the crew waits. That framing costs money.

An RFI is a contract document. It creates a dated, written record that a specific question was asked, when it was asked, and what answer came back. Months later, when a schedule is under scrutiny or a change order is in dispute, the RFI log is often the cleanest evidence anyone has of what was known and when. Contractors who write RFIs carelessly lose those arguments. Contractors who write them well don't have to have them.

What an RFI is actually for

An RFI exists to resolve something the contract documents do not resolve. That is a narrower purpose than most logs suggest.

Legitimate RFIs generally fall into a few categories: a genuine conflict between drawings, between disciplines, or between drawings and specifications; an omission where a condition is shown but not detailed; an ambiguity where a requirement can be read more than one way; a field condition that differs from what the documents depict, which is especially common in renovation and alteration work; or a request for clarification of intent where the requirement is legible but the design objective isn't.

What an RFI is not: a substitute for reading the specifications. Reviewers notice when a log fills up with questions already answered in Division 1 or in a general note. That pattern costs a contractor the benefit of the doubt on the questions that actually matter — which is a bad trade, because the questions that actually matter are the ones with money and time attached.

The anatomy of an RFI that gets answered

The difference between a two-day turnaround and a three-week one usually has nothing to do with the design team's workload. It has to do with how much work the RFI leaves for the person answering it.

A well-built RFI does the following:

States the question precisely, and only one question. Bundling five unrelated issues into one RFI guarantees it moves at the speed of whichever item is hardest. It also makes the response ambiguous later, because a single answer now has to be mapped back to five questions. One issue, one number.

Cites the exact documents. Drawing number, detail number, revision, specification section and paragraph. If a reviewer has to go find what you're talking about, the RFI sits in a pile.

Describes the condition factually. What is shown, what was found, what conflicts with what. No characterization of fault, no argument, no adjectives.

Proposes a resolution. This is the single biggest accelerator, and the one most often skipped. An RFI that says "please advise" asks the design team to do design work. An RFI that says "we propose to route as shown on the attached sketch, subject to your review" gives them something to approve. Proposing a solution also puts your preferred outcome — usually the one that is most buildable and least disruptive to your sequence — on the table first.

Attaches the evidence. A marked-up drawing excerpt, a dated photograph of the field condition, a sketch. Words describing a clash take a paragraph and are still arguable. A marked-up plan takes one glance.

States the impact plainly, when there is one. If the answer affects cost, schedule, procurement, or a related trade's sequence, say so, and say what work is affected. This is not a claim and should not read like one. It is notice — and notice is what preserves your position later.

The log is the deliverable

Any single RFI matters less than the log that holds all of them. On a well-run project the RFI log is a live document that shows, for every question: the number, the date submitted, who submitted it, the subject, the drawings and specifications referenced, the response required-by date, the date answered, the substance of the answer, whether it resulted in a change, and whether it is open or closed.

That log does three jobs at once. Day to day, it tells the project team what is blocking work. Weekly, it is the most honest agenda a coordination meeting can have — open items, aging, and who owes what. And at the end of the job, it is the record. Every schedule analysis, every entitlement argument, and every closeout dispute eventually goes back to the RFI and submittal logs, because those are the documents that establish the timeline.

Two disciplines make the difference between a log and a list. Number sequentially and never reuse a number, even for a voided RFI — a gap in the sequence invites questions about what was removed. And track aging actively. An RFI sitting unanswered past the response period in the contract is a schedule risk that gets worse quietly. It should be visible in the log, raised in the weekly meeting, and followed up in writing.

Timing is the part contractors get wrong

The most expensive RFI is the one submitted correctly and too late.

RFIs need lead time — the design team needs time to review, sometimes to coordinate with consultants, and sometimes to issue a revised detail. The response period is set by the contract documents, and the practical turnaround on a given project depends on the design team, the number of consultants involved, and how well the question was written. What that means operationally is that RFIs have to be generated off the look-ahead schedule, not off today's problem.

That is why disciplined contractors run a scope-gap review of the drawings and specifications early — before mobilization where possible — and generate the predictable RFIs then, when there is float to absorb the answers. It is also why RFIs should be written against procurement lead times, not just field dates. A question about a detail that drives a long-lead fabrication has to be asked and answered before the shop drawing is prepared, not when the crew arrives to install.

Answers are not automatically changes

A returned RFI response is a clarification of the contract documents. It is not, by itself, a change order. This distinction is where a great deal of money is lost.

If a response directs work that the contractor reads as beyond the original scope, the correct move is to say so promptly and in writing, through whatever change or notice mechanism the contract requires — not to build it and raise it at the end of the job. Proceeding on a response and invoicing for it later, without following the contract's notice process, is one of the most common ways a legitimate entitlement gets waived. The specific notice requirements and timeframes are set by your contract documents, and they vary; read them at the start of the job, not when the dispute arrives.

The corollary matters too: if a response resolves a question without changing the scope, close the RFI cleanly and move on. A log full of items left open for leverage is a log nobody trusts.

The bottom line

An RFI is the cheapest tool on a construction project and one of the most consistently mishandled. Written well — one question, precisely cited, factually described, with a proposed resolution and attached evidence — it removes an obstacle in days and leaves a record that protects everyone. Written poorly, it burns a week, irritates the people you need, and proves nothing later.

Ask early, ask narrowly, propose an answer, attach the proof, log everything, and follow the contract when a response changes your scope. On public work especially, the contractor with the cleanest RFI log is usually the one with the strongest position — and the fewest arguments to have in the first place.

MODRN Inc. is a New York construction management, contract administration, and estimating firm. This article is general guidance on construction RFI practice and is not legal or contractual advice; RFI response periods, notice requirements, and change-order procedures are set by your contract documents and applicable law, which you should always confirm for your specific project.