How to write a good RFI

A request for information (RFI) is how the contractor asks the design team to clarify, correct or complete the contract documents. A good RFI gets a clear answer in days. A bad one gets a question back, or an answer that creates three new questions, while the crew waits. The difference is almost entirely in how it's written.

1. Before you write it

Spend five minutes making sure the answer isn't already in the documents. Search the specs, check the addenda and any ASIs or bulletins issued since, and look at the related details on other sheets. Designers notice when a contractor asks questions the drawings already answer, and those RFIs slow down the ones that matter. If the answer really is there but contradictory, that's a legitimate RFI: say so and cite both places.

2. One question per RFI

Combining three issues into one RFI feels efficient, but the answer to all three waits for the hardest one, and the log can't show which part is still open. Split them. Numbering stays sequential per project (RFI 14, 15, 16), and each one can be closed on its own.

3. Point at the exact spot

Give the reader everything they need to find the problem without hunting:

Write the subject line the same way: location plus topic, e.g. “Footing step at grid C/4”. Six months later, someone searching the log for “C/4” will find it.

4. Suggest an answer

The single most effective habit is proposing a solution. It is much faster for an engineer to write “Agreed” or “Agreed, but use #5 bars” than to design an answer from scratch, and your suggestion is often the most buildable option because it comes from the people building it. Keep it concrete: a dimension, a product, a detail reference. If you have a cost-neutral option and a better-but-costlier one, offer both and say which costs more.

Careful

A suggested answer is not an instruction to proceed. Don't build your suggestion until the answer comes back, unless the design team tells you to in writing.

5. Attach what makes it obvious

A cropped snip of the drawing with the problem circled saves a paragraph of description. Add a site photo if the question comes from field conditions, and the relevant page of a product data sheet if it's about a product. Keep attachments focused: a 200-page drawing set attached to a one-line question means the reader has to find the page you meant.

6. Due date and ball in court

The due date is when you need the answer to avoid affecting the work, not just the contract's standard response time. If you need it sooner than the contract allows, say why in one sentence (“footing forms are scheduled for January 18”). Designers prioritise RFIs that explain their urgency.

Ball in court is whoever owes the next action right now. When you send the RFI it's the architect or the engineer it's assigned to. If they ask you a follow-up, it comes back to you. Keeping this column honest is what lets you walk into the weekly meeting and say “four RFIs are with the structural engineer, two are past due”.

7. Flag cost and schedule impact

Mark each RFI yes or no for cost impact and schedule impact when you send it, based on what you know. If the answer changes the contract sum or the schedule, that flag is your early notice. Follow your contract's change procedure for the change itself; the RFI log is the record that you raised it, and when.

8. A bad RFI, rewritten

Bad

Subject: Footings
Question: Footing detail doesn't work with the geotech report, please advise. Also need clarification on the rebar at the east wall and what's happening with the sump pit.

Three questions, no sheet references, no proposed answer, no due date. It will come back with “please clarify which footing”.

Better

Subject: Footing step at grid C/4

Question: S-201 detail 3 shows a 2'-0" footing step at grid C/4, but geotechnical report section 6.2 recommends one bearing elevation along the whole east wall. Is the step still required? If yes, please confirm its location and the bottom-of-footing elevation on each side.

Suggested answer: Delete the step and carry the footing at the geotech bearing elevation along grid C from 3 to 5.

Attachments: snip of S-201 detail 3 with the step circled; page 14 of the geotechnical report.

Due: January 15 (footing forms booked for January 18) · Ball in court: structural engineer · Cost impact: no · Schedule impact: yes

The rebar and sump pit questions become RFIs of their own, each with its own references.

Checklist before you send

Running the RFI log in SubmittalKit

SubmittalKit numbers RFIs per project automatically and keeps the question, suggested answer, attachments, due date, ball in court and impact flags together. The architect or engineer answers through a private review link (no account needed), RFIs past due show up on the dashboard with a ready-to-paste reminder, and every RFI prints as a one-page PDF for your records. If you prefer a spreadsheet, start with our free RFI log template.

Log your next RFI free

No seats and no email: send the reviewer a link and get the answer in the same place as the question.