RFI Guide 2026

How to write a construction RFI that actually gets answered, and the mistakes that turn one RFI into three.

By Dov Cohen · Published April 27, 2026 · Updated April 27, 2026

RFIs are the most common formal communication on a construction project and the one most often written badly. A good RFI takes ten minutes to write and gets answered the same week. A bad RFI takes thirty seconds to write and triggers two weeks of phone calls, three follow-ups, and a delay claim. This guide is the one we wish we had when we were running our first commercial job.

What an RFI Is

An RFI (Request for Information) is a formal written question from a contractor or subcontractor asking the design team or owner to clarify something in the contract documents. It is a record. It travels with the project. It can be cited later in a change order, a delay claim, or a lawsuit, so the way you write it matters.

Not every question needs an RFI. A friendly call to the architect to ask which catalog item they meant by "high-quality fixture" is fine. The RFI is for moments when (a) the documents are genuinely ambiguous, (b) two documents conflict, (c) field conditions do not match the drawings, or (d) you need a written record because money or schedule may turn on the answer.

When to Send an RFI

• Drawing-spec conflict. The plans show one thing and the spec calls for another. Always RFI.
• Detail conflict between sheets. Section A4.1 and section A8.2 disagree about the same condition. RFI.
• Field condition mismatch. The existing slab elevation is not what the drawings assumed. RFI before you pour.
• Missing information. A schedule references a wall type that is not on the wall type sheet. RFI.
• Scope ambiguity that affects price. If the answer changes what you owe, RFI before you bid the change. The RFI protects you on the change order.
• Owner-driven changes mid-construction. Even if the owner verbally asks for the change, RFI it (or have them issue an ASI). Never build a verbal change.

When NOT to send an RFI: questions you can answer by reading the documents carefully, questions that are clearly your scope and your responsibility, and questions you have already asked twice. If the architect has already told you how the door is finished, do not RFI it again because you forgot.

How to Write One That Gets Answered

Step by step

1. Identify the question precisely. Pin down exactly what is unclear. Reference the drawing number, detail callout, or spec section. A vague RFI ("what color is the wall?") gets bounced. A precise RFI ("Section A8.2 callout 4 shows GWB-1 returning to grid; spec section 09 21 16 calls for GWB-2 in this area; please clarify which finish governs") gets answered.
2. Propose a solution. Always include your suggested answer. "We recommend GWB-2 to match adjacent areas." Reviewers approve recommendations five times faster than open questions because it shifts the work from authoring to checking.
3. Cite the documents. List every drawing sheet, detail, and spec section relevant to the question. Include sheet number, revision, and date. If the RFI exposes a conflict between two sources, name both.
4. Attach the evidence. Snip the drawing area, mark up the conflict, and attach as a PDF page. Most RFIs are answered faster when the reviewer can see what you see.
5. State the schedule impact. Note the date the answer is needed by to avoid delay. "Required by 2026-05-04 to maintain CMU lay-up sequence." This is what triggers the contract response time obligation.
6. Route through the right people. Most contracts route RFIs through the GC to the architect. Sometimes mechanical RFIs go directly to the MEP engineer. Use whatever the project communications protocol specifies.
7. Track the answer and distribute. When the answer comes back, log it, attach the response in your project file, and distribute to every sub affected by the change. The biggest source of jobsite mistakes is an RFI answered but never distributed.

Anatomy of a Good RFI

A good RFI has six fields and that is it.

• RFI number. Sequential per project. (RFI 047)
• Subject. One line. ("Conflict between A8.2 callout 4 and spec 09 21 16, GWB finish at corridor return")
• Question. One paragraph. State the conflict, cite the references, no opinion.
• Suggested answer. One paragraph. Your recommendation with reasoning.
• Schedule impact. Date the answer is needed by. Days of float available.
• Cost impact. "TBD pending answer" or a dollar estimate if you have one.

If your RFI is longer than one page and includes more than one question, split it. Bundling unrelated questions into one RFI is the single most common mistake we see. The reviewer answers the easy ones, gets distracted by the hard one, and the easy ones get lost.

Common RFI Mistakes

• Vague subjects. "Question about wall finish" is not a subject. "Conflict between A8.2 and 09 21 16, corridor GWB return" is a subject.
• No reference to documents. Reviewers cannot answer what they cannot find.
• No proposed solution. If you do not propose, you make the architect do all the work, and they will deprioritize you.
• Multiple unrelated questions in one RFI. Already covered. Stop doing this.
• Asking it twice. Search your RFI log first. Architects remember.
• Sending RFIs that should have been a phone call. Use RFIs for record-worthy questions. Use the phone for quick clarifications.
• Not distributing the answer. The answer matters only if every sub on the affected work sees it. This is operational discipline, not paperwork.

RFI Volume Benchmarks

For a typical mid-size commercial project (under $25M), expect 50 to 200 RFIs. For a healthcare or laboratory project of similar size, double that. For a renovation in an occupied building, double again. If your RFI count is meaningfully below benchmark, your team is probably not catching real conflicts. If it is meaningfully above, your design team is likely incomplete or your PM is RFI-spamming.

How AI Helps With RFIs in 2026

This is where the world has changed. Five years ago an RFI took 20 to 40 minutes to draft well: pull up the drawings, find the conflict, write the question, propose the solution, format the cover sheet, attach the snips, log it, and route it. In 2026, AI tools handle most of that mechanical work.

What good AI tools do well today:

• Draft the RFI text from a one-line question. "Conflict between A8.2 and spec 09 21 16 on GWB at corridor return" becomes a fully formatted RFI with the right sections, the right tone, and a proposed solution to review.
• Pull spec section references. Given a question, the AI looks up the relevant CSI MasterFormat sections and inserts the citations.
• Format the PDF. Cover sheet, RFI number, subject, question, suggested answer, schedule, signature block. All standard, all automatic.
• Track the response. Email integration so the answer comes back into the RFI log automatically.

What AI does not do well today:

• Identify the conflict in the first place. You still have to read the drawings. AI can summarize, but the field judgment of whether a real conflict exists is yours.
• Propose the right solution. AI proposes a plausible solution. You verify it makes constructibility sense.
• Replace the architect. AI is not a stamp. The architect's response is what is contractually binding, not the AI's draft answer.

If you want to see what AI-drafted RFIs look like, ConstructionBear ships them by default. You text the bear ("RFI 47, A8.2 callout 4 conflicts with spec 09 21 16 on corridor GWB return, suggest GWB-2 to match"), the bear sends a stamped PDF in 30 seconds, and you forward it. Get early access here.

Sample RFI

Internal Links

• ConstructionBear home — AI-drafted RFIs in seconds.
• Submittal templates
• Change order best practices
• ConstructionBear vs Procore — how AI-native compares to a form-driven RFI module.

External Reading

For longer-form analysis on construction document workflows, see Builders Digest.