RFI log template
A clean request-for-information log with ball-in-court, due dates and cost and schedule impact columns. Free to download for Excel, Google Sheets or LibreOffice.
Download the template
What each column is for
| Column | What to enter |
|---|---|
| RFI # | Sequential per project: 1, 2, 3… Never reuse a number, even when an RFI is withdrawn. |
| Subject | A short, searchable title: location plus topic, e.g. “Footing step at grid C/4”. |
| Question | One question, with the sheet, detail, grid line and spec article it refers to. |
| Suggested answer | Your proposed solution. It is usually faster for the designer to agree than to start from nothing. |
| Date sent | When the RFI went out. |
| From | Who asked: your project engineer, the superintendent, or a sub through you. |
| Ball in court | Who owes the next action right now: the architect, an engineer, the owner, or you. |
| Due | When you need the answer to avoid a delay. If that is sooner than the contract response time, say why in the question. |
| Answer | The designer's response, word for word. |
| Date answered | When the answer came back. Days open = date answered minus date sent. |
| Cost impact (Y/N) | Will the answer change the contract sum? Flag it when you send, and update it when you get the answer. |
| Schedule impact (Y/N) | Will it change the schedule? Same rule: flag early, confirm later. |
| Status | Draft, open, answered or closed (dropdown). |
| Notes | Follow-ups, related submittals, or the ASI or change document that resolved it. |
An example row
RFI 1: Footing step at grid C/4
Question: S-201 detail 3 shows a 2'-0" footing step at grid C/4, but geotechnical report section 6.2 recommends one bearing elevation along the whole east wall. Is the step still required? If yes, confirm its location and the bottom-of-footing elevation on each side.
Suggested answer: Delete the step and carry the footing at the geotech bearing elevation along grid C from 3 to 5.
Ball in court: structural engineer · Due: 4 working days after sending · Schedule impact: yes (footing forms are booked)
Notice what makes it answerable: one question, the exact detail and report section, a proposed answer the engineer can accept with one word, and a due date tied to real work. Our guide on how to write an RFI that gets answered goes through this in more detail, with a bad example rewritten.
Keeping the log useful
- Review it in every OAC meeting. Sort by Due and read out anything open past its date, with who has the ball.
- Watch “days open”. If answers routinely take longer than the contract allows, the log is your record of it.
- Close the loop. An RFI is not closed when the answer arrives; it's closed when the answer is distributed to the field and the affected subs, and any cost or schedule impact has been raised through the contract.
- Link RFIs and submittals. If an answer changes a product or a dimension, note which submittals have to be revised.
Run it online free
SubmittalKit numbers RFIs per project, stores attachments, lets the architect answer through a private link without an account, flags RFIs past due on the dashboard and prints any RFI as a PDF.