How to write a construction RFI that actually gets answered

An RFI register with sixty open items is rarely a sign that the design team is slow. More often it is a sign that the questions are hard to answer — ambiguous, missing context, or asking the recipient to do the thinking.

The fastest way to reduce RFI turnaround is not to chase harder. It is to write better ones.

What an RFI is for

A Request for Information asks a question about the design or the contract documents where the answer is not reasonably ascertainable from what has been issued. That qualification matters: an RFI raising something clearly shown on a drawing wastes a cycle and erodes credibility for the ones that count.

What a good RFI contains

• A single question. Bundling four unrelated queries guarantees the whole item waits for the slowest answer.
• The specific reference — drawing number and revision, specification section and clause. Not “the ceiling detail”.
• The location, by level, grid and room. A question about a junction is unanswerable without knowing which one.
• What you understand the position to be, and why it appears unclear or conflicting.
• A proposed solution. This is the single biggest lever on turnaround.
• The programme consequence — the activity affected and the date by which an answer is needed to avoid impact.

Why proposing a solution works

An RFI that asks “please advise” requires the recipient to design something. An RFI that says “we propose to route the containment below the beam as shown, please confirm” requires them to agree or disagree.

The second is answered in minutes and the first in weeks. It also puts you in a much stronger position if the answer is late, because the record shows a workable solution was offered.

What makes an RFI slow

• Sent to a general inbox rather than a named discipline lead
• No drawing revision quoted, so the reviewer has to establish what you were looking at
• Raised as a submittal, or a submittal raised as an RFI
• No date-needed, so it is triaged below items that have one
• Asking a commercial question in a technical channel — variations belong in the variation process, not the RFI register

Managing the register

Two habits separate registers that work from ones that become a source of dispute.

First, every RFI links to the drawing, specification and activity it concerns, so its consequence is visible rather than asserted. Second, the response clock runs against the contractual period and is visible to both parties, so a conversation about an overdue item is about sequencing rather than blame.

Where an RFI response amounts to an instruction or a change, it needs to flow into the variation and delay record immediately. RFI responses that quietly change scope, and are never picked up commercially, are one of the most reliable ways to lose margin on a project.

A note on volume

High RFI volume is often treated as a contractor problem. It is usually a design-completeness problem, and the register is the evidence. If a package generates two hundred RFIs, that is a fact worth putting in front of the client early, in the form of a trend rather than a complaint.

Our AI-enabled project management drafts responses to incoming RFIs from the specification and prior correspondence, with a confidence score and mandatory human approval — which shortens the reply cycle without moving accountability.