Skip to content
Buildalytic
Field notes / Closeout, documents and change orders

How to write a construction RFI: template, six examples and what gets answered fast

How to write a construction RFI that gets a fast, usable answer: the fields every RFI needs, a template, six before-and-after examples, response tracking and the cost of unnecessary RFIs.

By Buildalytic Research Desk6 min read

Editorial scene of a project engineer writing an RFI with drawings open
Illustrative editorial scene. Examples in this article are written for illustration.
The short answer

A good construction RFI asks one specific question, cites the exact drawing, detail and spec section, explains the conflict or missing information, proposes a solution, and states the date an answer is needed and what happens to cost and schedule if it's late. Check the contract documents first, because many RFIs are already answered there. Buildalytic turns field questions into focused RFIs with references and follows up until they're answered.

What to take away

  • One question per RFI, with the drawing, detail and spec references.
  • Propose an answer; reviewers respond faster to a yes or no.
  • State the date you need the answer and the cost or schedule effect if it's late.
  • Search the documents first: a 2013 industry study found more than 13 percent of RFIs were already answered in them.

Why RFI quality matters

Every RFI costs time on both sides. A widely cited 2013 Navigant Construction Forum study of more than a thousand projects estimated the average cost to review and respond to an RFI at about $1,080, found a median response time of 9.7 days, and judged that more than 13 percent of RFIs asked questions the contract documents already answered. Whatever your own numbers are, a vague RFI takes longer to answer and is more likely to come back with a question instead of a decision.

Sources: Procore: lower the cost of your RFIs (summarizing the 2013 Navigant Construction Forum study)

The fields every RFI needs

Use your project's RFI form or system; these are the fields that make it answerable.

The fields every RFI needs
FieldWhat to writeExample
Number and titleSequential number and a short, searchable titleRFI 047: Beam B-12 bottom elevation conflicts with duct
ReferencesEvery sheet, detail, grid and spec section involvedS-201 detail 4; M-301; grid C/4; spec 23 31 13
QuestionOne specific questionCan the duct be lowered 4 inches to clear beam B-12?
BackgroundWhat you found and why it conflictsBeam bottom at 11'-2" per S-201; duct top at 11'-4" per M-301
Proposed solutionYour recommended answerLower the duct to 10'-10"; ceiling at 10'-6" still clears
Needed byThe date and whyNeeded by 11/24 to release duct fabrication
ImpactCost and schedule effect, or none expectedNo cost if answered by 11/24; 5-day delay to ceiling close-in if later
AttachmentsMarked-up sheet, photo, model viewPhoto of the field condition; marked-up M-301

Seven rules for RFIs that get answered

Search first. Check the drawings, specs, addenda, approved submittals and earlier RFIs before you write. Ask one question per RFI, so the answer is a decision, not an essay. Cite exact references. Describe the conflict, not just the location. Propose a solution. Give a needed-by date tied to a real activity. Say whether you expect a cost or schedule impact, which protects your right to claim one under most contracts' notice provisions, and avoids surprises later.

Six examples, before and after

Illustrative wording.

Six examples, before and after
TopicWeak RFIBetter RFI
ConflictDuct and beam conflict on level 2. Please advise.Can the supply duct on level 2, grid C/4, be lowered 4" to 10'-10" to clear beam B-12 (S-201/4)? Ceiling at 10'-6" still clears. Needed 11/24 to release fabrication.
Missing dimensionNeed dimension for door.Door 214 rough opening width is not shown on A-401 or the door schedule. Confirm 3'-0" leaf per hardware set 7? Needed 11/20 for framing.
Spec vs drawingWhich tile is correct?Spec 09 30 00 calls porcelain PT-2; A-601 finish plan shows PT-3 in corridor 120. Which governs? We propose PT-2 per spec. Needed 12/2 for order lead time.
Field conditionExisting pipe in the way.Existing 4" cast iron drain found at grid F/2, 18" below slab, not shown on survey. Can new footing F2 shift 12" east (S-101)? Photos attached. Needed 11/19; crew on hold.
Product substitutionCan we use a different fixture?Specified fixture L-3 has a 16-week lead time. Request approval of equal fixture (cut sheet attached, same lumens, CCT and mounting). Needed 11/22 to hold the schedule.
Unclear scopeWho does the firestopping?Spec 07 84 00 assigns firestopping to Division 7; electrical sub's scope excludes it. Confirm GC self-performs penetrations at rated walls on levels 1 to 3?

A copy-ready RFI template

RFI number and title. Date sent. To (the design professional or owner's representative) and from. References: sheets, details, grids, spec sections. Question: one sentence ending in a question mark. Background: what you found and where, with measurements. Proposed solution. Needed by: date and the activity it drives. Cost and schedule impact: none expected, or the expected effect. Attachments: marked-up sheets and photos.

Keep the question and the proposed solution in the first lines. A reviewer reading on a phone should know what you need before scrolling.

Track responses, not just submissions

Log every RFI with the date sent, the contractual response time from Division 01 or the contract, the needed-by date and the ball-in-court. Review the open list weekly, call before an RFI goes late, and escalate the ones that hold work. When an answer comes back, distribute it to the field and the trades it affects, check whether it changes cost or time, and close it only when the field confirms the answer is usable.

When an RFI answer changes the work

An answer that adds or changes scope is a potential change, not just information. Note it on the RFI, give any notice the contract requires, and price it promptly. Many disputes start with an RFI answer that quietly changed the work and a change order that was never requested.

RFIs from subcontractors

Most RFIs start with a question from a trade. Ask subs to send questions with the same fields, review them before forwarding, and combine duplicates. A GC that forwards raw questions gets slower answers and loses track of which RFI belongs to which trade.

What to measure

Track RFIs per month, average days to answer against the contract time, the share answered by the needed-by date, RFIs that turned into change orders, and RFIs answered by "see documents". The last one tells you how many could have been avoided with a better search first.

How Buildalytic helps

Foremen send questions by text or call, with photos. Buildalytic checks the project documents first and answers with the source when the answer is already there. When it isn't, the question becomes a focused RFI with sheet and spec references for your project engineer to review and send, and Brody follows up with the reviewer before the needed-by date.

Common questions

What should a construction RFI include?

One specific question, the drawing, detail and spec references, background on the conflict, a proposed solution, the date an answer is needed and any expected cost or schedule impact, with marked-up attachments.

How long does an RFI response take?

The contract usually sets the response time. A 2013 Navigant Construction Forum study reported a median of 9.7 days.

Should an RFI propose a solution?

Yes. A proposed solution lets the reviewer answer yes or no, which is faster than designing an answer from scratch.

Is an RFI the same as a change order?

No. An RFI asks for information. If the answer changes scope, cost or time, give the notice the contract requires and request a change order.

Sources and editorial notes

Prepared with AI assistance. Reference date: 2026-11-16. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.

How we prepare and update field notes
See it on your workflow

Turn field questions into answerable RFIs.

Bring a week of field questions. See which ones the documents already answer, and the rest turned into focused RFIs.

Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.

See RFI follow-up Explore the relevant capability