← All field guides

RFIs2 min readNov 7, 2026

RFI log template: what to track, and when a spreadsheet stops working

The columns every construction RFI log needs, five signs your Excel RFI log has outgrown itself, and what RFI software does differently.

In this post
  1. The columns every RFI log needs
  2. Five signs the spreadsheet has stopped working
  3. What RFI software does differently

Almost every contractor's first RFI log is a spreadsheet, and that's fine. A good template handles a small job well. The trouble starts when the job gets bigger, more people need to see the log, and nobody is sure which version is current. Here is what a solid RFI log should track, and the signs it's time to move on from Excel.

The short version

  • Track number, question, who owes the answer, due date and ball in court.
  • Flag cost or schedule impact on every RFI.
  • Two versions of the log, or answers stuck in email, mean it's time to move on.

The columns every RFI log needs

  • Number. Sequential, never reused (RFI-001, RFI-002). Voided RFIs keep their number.
  • Subject. Short and searchable: "Footing depth at grid C-4."
  • Question. The full question, with the drawing sheet and spec section it refers to.
  • Suggested answer. What you propose. A question with a proposed answer gets answered faster.
  • Asked by / sent to. Who raised it on your side and who owes the answer (architect, engineer, owner).
  • Date sent and date due. Use the response time in the contract (often 5 to 10 working days).
  • Ball in court. Who has to act next. This is the most useful column in the log.
  • Status. Draft, open, answered, closed.
  • Cost or schedule impact. Yes, no or unknown. An answer that adds cost should become a change order, not a footnote.
  • Answer and date answered. The official response, word for word.

Five signs the spreadsheet has stopped working

  1. There are two versions of the log. One on the PM's laptop and one emailed to the architect last Tuesday.
  2. Answers live in email. The log says "answered," but the answer is in someone's inbox with the attachment.
  3. Nobody knows what's overdue without sorting columns and comparing dates by hand.
  4. The field can't see it. The super finds out about an answer after the work is already in place.
  5. You're retyping. The same question goes into the log, then into an email, then into the meeting minutes.

What RFI software does differently

The point isn't fancier columns. It's that the RFI, the conversation, the attachments and the official answer are one record that everyone opens. Whoever owes the answer is notified, and overdue items show up on their own. When the answer comes back, the person who asked hears about it right away.

Set up your RFI log

  • Start numbering at RFI-001 and never reuse a number
  • Add due date, ball in court and status columns
  • Set each due date from the contract’s response time
  • Cite the sheet and spec section in every question
  • Propose an answer with every question you send
  • Flag cost or schedule impact on every RFI
  • Paste the official answer into the log, not just “answered”
  • Keep one live copy and share it with the field
  • Review overdue RFIs in the weekly meeting

Try it in ProjectAire

RFIs in ProjectAire keep the question, drawings, comments and official answer together. Every RFI shows where it stands in one sentence, like "Waiting on Sarah Nguyen, due Jul 24, 9 days late." Already have a spreadsheet log? Import it from CSV and keep going. If you're weighing the move, ProjectAire vs. spreadsheets walks through the trade-offs honestly.

Start free See the RFI demo

Put this to work on your next job.