RFIs in Construction: Writing Them, Tracking Them, Getting Paid

Every set of drawings has gaps: dimensions that do not add up, a detail contradicting the plan view, a finish schedule naming a product the specification does not, a field condition nobody drew. That is normal on any project. What separates builders who absorb the cost of those gaps from builders who get compensated for them is not skill in the field — it is whether the question was asked in writing, at the time, with the schedule impact stated. This is how to write RFIs that get answered fast, how to manage volume without damaging the relationship, and how the log becomes the document that decides who pays.

The question you ask in writing is the one you get paid for

Every set of drawings has gaps. Dimensions that do not add up, a detail that contradicts the plan view, a finish schedule that names a product the specification does not, a condition in the field that nobody drew. This is normal and expected on any project.

What separates builders who absorb the cost of those gaps from builders who get compensated for them is not skill in the field. It is whether the question was asked in writing, at the time, with the schedule impact stated.

The phone call to the architect solves the problem and creates no record. Two months later, when the schedule is three weeks long and the owner wants to know why, the conversation about who caused the delay has no evidence in it — and the party without documentation loses that conversation almost every time.

The rule that costs nothing to adopt. Call the architect whenever you want, and then send an email confirming what was decided, in one paragraph, ending with a request to confirm. It preserves the relationship and the speed of a phone call while creating the record. Builders who adopt only this one habit change their position in every future dispute.

What an RFI actually costs

Two costs run in parallel, and builders usually see only the smaller one.

The administrative cost is the time to write it, the design team's time to review and respond, and the coordination on both ends. Across the industry this is commonly estimated in the several hundreds of dollars per RFI, which is why owners and architects react badly to volume.

The schedule cost is much larger and is what actually damages projects. An RFI answered in eleven days on an item that gates the next trade is eleven days of float consumed, or eleven days of delay, depending on where it sits. Multiply by a project's typical volume and the aggregate is frequently the single largest schedule risk a builder carries and does not measure.

The practical implication is that RFI management is a scheduling discipline, not a paperwork discipline. The question is never only whether to ask — it is how early, and how to make the answer easy to give.

Keep reading — free

The rest of this article is worth the 20 seconds

Tell us where to send it and the full piece unlocks right here, along with everything else on this blog.

Rather just talk? Message us on WhatsApp.

The answerable RFI

An RFI that gets answered in two days and one that sits for two weeks usually differ in construction, not in content. Five elements make the difference.

One question. An RFI containing four questions gets answered when the slowest of the four is resolved, and frequently gets answered on three. Separate them.

The exact reference. Sheet, detail number, specification section, grid location. The reviewer should not have to search for what you are describing.

A photograph of the actual condition, when the issue is in the field. It removes an entire round of clarification.

A proposed solution. This is the technique that changes response times more than any other. Instead of asking what to do, state the conflict and propose the resolution: "the detail shows a 6-inch reveal and the elevation shows 4-inch; we propose 4-inch to match the adjacent bay — please confirm." You have converted an open design question into a yes, which is far faster to give and far easier to defend.

The impact and the date needed. State what is waiting and when the answer must arrive to avoid delay. Not as a threat — as information the reviewer needs in order to prioritize among the twelve RFIs on their desk.

Too many and too few both signal a problem

RFI volume is read by owners and architects as a measure of the builder, and it is read in both directions.

A high count suggests a contractor who did not study the documents before starting, or who is building a claim. It damages the relationship and slows responses, because a reviewer who believes the volume is strategic stops treating each item as urgent.

A very low count is worse for the builder, though it looks better. It means field decisions are being made without authority, gaps are being absorbed silently, and there will be no documentation when the owner disputes what was built or when a schedule claim needs support.

The healthy pattern is a concentration of RFIs early — generated by a thorough document review before the work starts — and a low, steady rate afterward. That distribution tells everyone the builder read the drawings, and it produces answers when they are still cheap to implement.

The document review that prevents most of them

The highest-return hour in preconstruction is a systematic review of the documents specifically hunting for conflicts, before mobilization.

Four passes catch most issues. Compare dimensions across drawings and confirm they close. Cross-check the architectural, structural, mechanical, electrical and plumbing drawings at the points where they must agree — ceiling heights, chase locations, structural penetrations, equipment clearances. Reconcile the finish schedule against the specifications and against the drawings, which disagree remarkably often. And check the specifications for products that are discontinued, unavailable in your region, or carry lead times the schedule does not allow.

Issues found here become RFIs answered before the schedule depends on them, which costs a fraction of the same issue discovered by a framer on a Tuesday.

The log, and the aging that matters

An RFI log with number, date sent, question, status, date answered and the trade waiting is not bureaucracy — it is the document that determines who pays for a delay.

The column that does the work is aging. An RFI open eighteen days is a fact. Sent weekly to the owner and the design team, along with the trade it is holding, it does three things: it prompts answers, it establishes contemporaneous notice, and it makes the cause of any resulting delay a matter of record rather than of argument.

This should be sent routinely and neutrally, not only when a problem develops. A log that appears for the first time during a dispute reads as a claim being assembled. A log that has been sent every Friday for four months reads as a fact.

Managing the relationship, not just the process

The paperwork above is correct and it is not sufficient, because the response time you get is substantially a function of how the design team experiences working with you.

Three practices produce faster answers. Batch non-urgent items into a weekly submission rather than sending them individually as they arise, which respects the reviewer's time and makes urgent items genuinely urgent. Distinguish clearly between what is holding work and what is not, so priority is obvious. And when you receive a fast, helpful answer, say so — architects on residential and small commercial projects are frequently under-resourced, and a builder who is easy to work with moves to the top of the pile.

The alternative posture, in which every RFI is framed as a defect in the drawings, produces slow responses and a design team looking for reasons the delay was yours.

One project, measured

A residential and light commercial builder, roughly $9 million in annual volume, on a fourteen-month mixed-use project.

Previous project, for comparison. 78 RFIs, average response time 9.4 days, 31 of them submitted after the affected trade was already on site. Delay claims disputed at closeout, with the builder absorbing 19 days of extension costs because verbal answers had no documentation.

What changed. A two-day structured document review before mobilization, conducted with the superintendent and the two largest subcontractors. Every RFI written with a proposed solution. A weekly log sent to the owner and architect regardless of status. And a standing rule that any verbal answer was confirmed by email within the same day.

Result. 64 RFIs, of which 41 were submitted during preconstruction. Average response time fell to 3.8 days, and to 2.1 days on the ones carrying a proposed solution. Only 6 were submitted after the affected trade mobilized.

At closeout, the builder submitted 11 days of compensable delay supported by the log and email confirmations, and 9 were accepted without dispute. The comparable figure on the previous project was zero accepted out of a much larger claim.

RFIs from your subcontractors

On most projects, a large share of RFIs originate with subcontractors rather than with the builder, and how that flow is managed determines whether the process helps or becomes a second full-time job.

Two failure modes are common. In the first, subcontractors contact the architect directly, which produces answers the builder never sees, decisions that conflict with other trades, and a scope change nobody priced. In the second, the builder becomes a pure relay, forwarding every subcontractor question upward without review — which inflates the count, damages the builder's standing with the design team, and passes along questions that were already answered in the documents.

The workable middle has three rules. All RFIs go through the builder, stated in the subcontract and enforced from the first week, because a single point of contact is the only way the answers stay consistent across trades. The builder screens before forwarding, and a meaningful share of subcontractor questions are resolved by pointing at the sheet where the answer already is — which takes minutes and preserves credibility with the architect. And the answer goes back to every affected trade, not only to the one who asked, since a clarification on a ceiling height concerns the mechanical, electrical and framing contractors simultaneously.

That last rule is the one most often skipped, and it is the source of a specific and expensive failure: a decision made in response to one trade's question, implemented correctly by that trade, and contradicted a week later by another trade who never received it.

Five mistakes with RFIs

Accepting verbal answers. The decision is made and the record is not, which is exactly backwards.
Asking without proposing. An open question invites deliberation; a proposal invites a yes.
Bundling multiple questions. The RFI moves at the speed of its slowest item.
Submitting after the trade is on site. The same question costs several times more once someone is standing there waiting.
Producing the log only during a dispute. Contemporaneous documentation is persuasive; reconstructed documentation is not.

The numbers to watch

Five metrics show whether this process is protecting the project. Average response time, tracked by reviewer, which tells you where the bottleneck actually is. Open RFI aging, with anything past your stated turnaround flagged, since this is the number that prevents delay rather than documenting it. Percentage submitted before the affected trade mobilizes, which is the single best measure of whether your document review is working. RFIs that resulted in a change order, which quantifies what document gaps are worth on your projects and informs how much preconstruction review is justified. And the share of decisions confirmed in writing, which is the habit that determines your position in every dispute you have not had yet.

Find out what your document gaps are costing

Send us your RFI count and average response time from your last project, plus any delay days you absorbed. We will run the schedule impact math with you, and show you where preconstruction review would have paid for itself.

Talk on WhatsApp See how it works

Frequently asked questions

How do you write an RFI that gets answered quickly?

Five elements make the difference between an RFI answered in two days and one that sits for two weeks. One question per RFI, because an RFI containing four questions gets answered when the slowest of the four is resolved. The exact reference — sheet, detail number, specification section, grid location — so the reviewer does not have to search for what you are describing. A photograph of the actual condition when the issue is in the field, which removes an entire round of clarification. A proposed solution, which is the technique that changes response times more than any other: instead of asking what to do, state the conflict and propose the resolution, converting an open design question into a yes that is faster to give and easier to defend. And the impact and date needed, stated as information the reviewer needs to prioritize among everything else on their desk, not as a threat.

Why does it matter to document answers in writing on a construction project?

Because the phone call to the architect solves the problem and creates no record. Two months later, when the schedule is three weeks long and the owner asks why, the conversation about who caused the delay has no evidence in it — and the party without documentation loses that conversation almost every time. The rule that costs nothing to adopt is to call the architect whenever you want, then send an email confirming what was decided in one paragraph, ending with a request to confirm. It preserves the relationship and the speed of a phone call while creating the record. Builders who adopt only this one habit change their position in every future dispute, and the difference shows up at closeout: on one project, eleven days of compensable delay were submitted with log and email support and nine were accepted without argument.

Is a high number of RFIs a bad sign?

Volume is read by owners and architects as a measure of the builder, and it is read in both directions. A high count suggests a contractor who did not study the documents before starting, or who is building a claim, which damages the relationship and slows responses because a reviewer who believes the volume is strategic stops treating each item as urgent. A very low count looks better and is worse for the builder: it means field decisions are being made without authority, gaps are being absorbed silently, and there will be no documentation when the owner disputes what was built or when a schedule claim needs support. The healthy pattern is a concentration of RFIs early, generated by a thorough document review before work starts, and a low steady rate afterward — which tells everyone the builder read the drawings and produces answers while they are still cheap to implement.

What should a construction RFI log include?

Number, date sent, question, status, date answered and the trade waiting — but the column that does the work is aging. An RFI open eighteen days is a fact, and sent weekly to the owner and design team along with the trade it is holding, it does three things: it prompts answers, it establishes contemporaneous notice, and it makes the cause of any resulting delay a matter of record rather than of argument. The critical detail is that this should be sent routinely and neutrally, not only when a problem develops. A log that appears for the first time during a dispute reads as a claim being assembled; a log that has been sent every Friday for four months reads as a fact. That difference is worth more at closeout than any argument made after the schedule has already slipped.

How should subcontractor RFIs be handled?

Through the builder, with screening, and with answers distributed to everyone affected. Two failure modes are common: subcontractors contacting the architect directly, which produces answers the builder never sees and decisions that conflict across trades; or the builder acting as a pure relay, forwarding every question upward without review, which inflates the count and passes along questions already answered in the documents. The workable middle has three rules. All RFIs go through the builder, stated in the subcontract and enforced from the first week, because a single point of contact is the only way answers stay consistent. The builder screens before forwarding, resolving a meaningful share by pointing at the sheet where the answer already is. And the answer goes back to every affected trade, not only to the one who asked — the rule most often skipped, and the source of the most expensive contradictions.