Field

RFI log template

An RFI log tracks every request for information on a job: what was asked, who has it, when the answer is due, and whether it changed cost or schedule. Download this template as a CSV for Excel or Google Sheets, or print it.

A superintendent holds a drawing while a foreman points to a framed opening inside a building under construction.
Connect the clarified drawing to the exact location and crew that need it. AI-generated illustration.

An RFI log template is the one-page list of every request for information on a project. Each RFI gets a row with its number, the drawing or spec it points to, who it went to, when the answer is needed, when it came back, and whether it moved cost or time. The individual RFI is the question; the RFI log is how you keep 40 open questions from turning into a schedule delay nobody can explain.

Superintendents feel this first. The duct does not fit under the beam at grid C-4, the crew is standing around, and the question has been sitting in the engineer's inbox for a week. A log with a required-by date and a days-open count makes that visible before it costs you.

What the RFI log is for

The log does three jobs. It drives follow-up, since every open RFI has an owner and a date. It builds the record for delay and change claims, since an RFI answered late or answered with new scope is the paper trail behind a delay claim or a change order. And it shows patterns: if most RFIs hit the same consultant's drawings, that is worth raising early.

Review the log in every weekly meeting. Sort open items by required-by date and read them out loud. People answer faster when their name is on a list in front of the room.

How to fill in each column

  • RFI no.: sequential, never reused. Add a revision suffix (RFI-014.1) if the same question is resubmitted.
  • Date sent: when it left your hands, not when the question came up in the field.
  • Subject: a few words someone can scan.
  • Reference: drawing sheet, detail, and spec section. Precise references get precise answers.
  • Sent to: the person responsible for answering: architect, engineer, owner's rep.
  • Required by: the date the answer is needed to avoid impact. Base it on the look-ahead, not a generic seven days.
  • Date answered: when a usable answer came back. A reply that says see drawings is not an answer.
  • Days open: date answered minus date sent, or today minus date sent while open.
  • Impact: none, cost, schedule, or both. Link the change order number when one results.
  • Status: open, answered, closed, or void.

Common mistakes

  1. Sending RFIs for things the documents already answer. It burns credibility and slows real questions.
  2. Not logging the impact, then finding out at closeout that four answered RFIs added scope nobody priced.
  3. Leaving the required-by date blank, so the design team sets its own pace.
  4. Closing an RFI when the reply arrives rather than when the answer is confirmed workable in the field.
  5. Keeping the log separate from the submittal and change order logs, so connected items never get linked.

Related forms and guides

Write each request with the RFI template, and read how to manage RFIs without slowing the job. RFIs with cost impact feed the change order log template. Product questions often belong on the submittal log template instead, and required-by dates should come from the three-week look-ahead template.

Smart Business Automator logs RFIs per project, tracks days open, and can draft the RFI text from your field notes for review. See RFI and submittal tracking automation.

RFI log

Download CSV
RFI no.Date sentSubjectReferenceSent toRequired byDate answeredDays openImpactStatus
RFI-0112026-04-20Ceiling height at corridorA-501 detail 4Architect2026-04-272026-04-244NoneClosed
RFI-0122026-04-28Outlet count in break roomE-201Architect2026-05-052026-05-013Cost, see CO-001Closed
RFI-0132026-05-02Fire rating at demising wallA-101, spec 09 21 16Architect2026-05-092026-05-1210Schedule, 1 dayClosed
RFI-0142026-05-08Duct conflict with beam at grid C-4M-301, S-201Structural engineer2026-05-1312Schedule, TBDOpen, past due
RFI-0152026-05-15Tile layout start point in lobbyA-601Interior designer2026-05-225TBDOpen
  • Sample data only. Replace the example RFIs with your own.
  • Days open = date answered minus date sent. For open RFIs it is counted to the log date; the sample log is dated 2026-05-20.
  • Mark any open RFI past its required-by date as past due and raise it at the next meeting.
  • Record the change order number in the impact column whenever an answer adds cost or time.
  • Attach the full RFI and response to each row, or note where they are filed.

Frequently asked questions

What is an RFI log in construction?

It is a list of all requests for information on a project with their number, subject, references, recipient, due date, response date, days open, impact, and status.

How long should an RFI take to answer?

Many contracts set a response time, so check yours first. If it is silent, set the required-by date from your schedule so the answer arrives before the work it affects.

Who maintains the RFI log?

Usually the general contractor's project engineer or project manager. Subs often keep their own log of the RFIs they have sent up through the GC.

Can I use this RFI log in Excel?

Yes. Download the CSV and open it in Excel or Google Sheets. Add a formula for days open and conditional formatting for past-due rows.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment