Templates

RFI Management

RFI Log Template

Free to download and use, with guidance on how to fill it in.

Download this template

Free to use. No email required.

Download Free Template

What it is

An RFI log is the master tracking document for all Requests for Information on a construction project. Where an individual RFI template captures the content of a single question and response, the RFI log gives the entire project team visibility into every RFI at once — which are open, which are overdue, which have been answered, and which are approaching their required response date. A well-maintained RFI log is an essential project management tool and a critical piece of closeout documentation.

When to use it

Start your RFI log at project kick-off and maintain it continuously throughout construction. The log should be reviewed at every project meeting to identify items requiring follow-up. It is the primary tool for monitoring RFI response times, identifying overdue items, and ensuring that approved responses are distributed to the field team. At project closeout, the complete RFI log — with every question and response — forms part of the project record and may be needed for any future claims or warranty work.

How to complete it

  1. 1

    Set up the column headers

    At minimum, your RFI log should track: RFI Number, Title or Subject, Spec Section, Drawing Reference, Submitted By, Directed To, Date Submitted, Required Response Date, Date Returned, Review Action (Open/Answered/Closed), and Notes or Summary of Response.

  2. 2

    Assign a number to every RFI immediately

    Log each RFI the moment it is submitted — not after a response is received. The log is a tracking tool, not a record of resolved items only. Open RFIs need to be visible so they can be followed up.

  3. 3

    Set required response dates based on your schedule

    For each RFI, determine the date by which a response is needed to avoid a field hold. This is not the same as the contractual review period — it is the date driven by your construction sequence. Enter this date in the log so overdue items are immediately visible.

  4. 4

    Update status promptly when responses arrive

    When a response is received, update the Date Returned, Review Action, and Notes columns the same day. Stale status in your log leads to missed follow-ups and duplicate submissions.

  5. 5

    Flag overdue items at every meeting

    Filter or highlight any RFI whose Required Response Date has passed and whose status is still Open. These items require active follow-up — a polite but firm written request for expedited response, referencing the date the item was submitted and the field impact of the delay.

  6. 6

    Retain the log through closeout

    At project closeout, the RFI log and the complete response history for each item should be filed with the project record. If a future warranty claim or dispute arises, the RFI log is often the first document examined.

Common mistakes to avoid

Starting the log late

Some teams do not set up the RFI log until several RFIs have already been submitted informally. This results in unnumbered RFIs, missing response records, and a log that never catches up with reality. Set up the log before the first RFI is submitted.

Not tracking required response dates

Logging submission dates without logging required response dates means you cannot identify overdue items without reading through every entry. The required response date column is what makes the log a monitoring tool rather than just a filing system.

Allowing the log to fall behind

An RFI log updated monthly rather than daily is useless as a management tool. Status changes need to be logged within 24 hours of a submission or response to keep the log reliable.

No distribution column

Approved RFI responses need to reach the field team before the affected work begins. Adding a Distribution column — and recording when the response was sent to the superintendent and relevant subcontractors — closes the loop and prevents a situation where a good response never reaches the person who needed it.

How PlanSpan automates this workflow

PlanSpan maintains a live RFI log for every project automatically. Every RFI is auto-numbered, status-tracked, and visible to the whole project team in real time — no spreadsheet to update, no log to fall behind. Required response dates are tracked against the live log, and overdue items are surfaced immediately. The full RFI history, including every response, is retained in the project record and exportable to PDF for owner reporting or closeout documentation.

See how PlanSpan tracks RFIs →

Download this template

Free to use. No email required.

Download Free Template
Back to all templates

Skip the Spreadsheet — Use PlanSpan Instead

Every workflow this template covers is built into PlanSpan — tracked, connected, and ready to use from day one.

Start free — no credit card required