The columns that matter
| Column | Why |
|---|---|
| RFI number | One sequence for the project |
| Subject and references | Find it fast later |
| Date sent | Starts the clock |
| Ball-in-court | Who has to act next |
| Needed-by date | Tied to the schedule, not arbitrary |
| Date answered | Measures turnaround |
| Impact | Cost or schedule impact flagged for a change order |
| Distributed | Confirms the field has the answer |
Ball-in-court, explained
"Ball-in-court" is whoever has to act next: the architect, an engineer, the owner, the GC or your own team. Updating it every time an RFI moves turns the log into a to-do list for each party.
A weekly aging report
Each week, list open RFIs by days outstanding and what each is holding up. Review it in the project meeting. Overdue RFIs with a schedule impact get escalated, in writing.
Close the loop
- Send answers to the field the same day.
- If an answer adds work, start a change order request referencing the RFI.
- File answers with the project records.
Short on time to chase RFIs? See RFI management services.
We do this all day
Stuck on this? Email us.
Send us what you have and where you're stuck. Our PMP® and LEED AP BD+C credentialed staff will reply with next steps, and if you'd rather hand it off, a project-specific proposal in 48–72 hours.
Opens your email app with a short draft. Add a line and attach PDFs.
Questions we hear
Should subcontractors keep their own RFI log?
Yes. Even if the GC runs the official log, keep your own record of questions you raised and answers you received.
What's a reasonable RFI turnaround?
Check your contract. If it's silent, agree on expectations at the start and flag urgent RFIs clearly.
Can the log be shared with the whole team?
Yes, and it should be. A shared log removes 'I never got it' from the conversation.