Project Setup
RFI Summary
RFI / Technical Query Log
| No. | RFI Ref No. | Discipline | Subject / Query | Raised By | Assigned To | Date Raised | Priority | Response Due | Response Date | Status | Remarks / Response |
|---|
About this RFI tracker tool
This tool builds an RFI / technical query register directly in the browser, for project managers, document controllers and site engineers who need a clear log of every Request for Information raised or answered on a project.
Logging RFIs by discipline and priority
Each entry records a reference number, discipline, subject or query, who raised it, who it is assigned to, and the date it was raised. Tagging the discipline routes the query to the right reviewer, while a priority level makes it easy to see which RFIs are blocking site progress and need an urgent answer.
Tracking pending and overdue responses
Set a response due date on any RFI that requires a reply. Once a response date is recorded the RFI is marked closed; if the due date passes with no response it is automatically flagged overdue, so nothing waiting on a technical answer gets lost in a busy project inbox.
What the summary reports
- Total RFIs logged
- Pending — awaiting a response, not yet due
- Overdue — past the response due date with no reply
- Closed — response received and recorded
- Critical/high-priority RFIs still open
- Closure rate — the share of RFIs answered so far
Getting data in and out
The register saves as a project file to reopen later, exports to CSV for further analysis or a handover file, prints directly as a PDF, and can generate a full detail report with every query and response written out in full for a monthly progress report. For logging general project correspondence rather than technical queries, see the project correspondence register.
Frequently asked questions
What is an RFI (Request for Information)?
An RFI is a formal request raised when a drawing, specification or scope of work is unclear, missing or conflicting, asking the design team or client for clarification before work can proceed. A technical query register logs each of these requests along with who raised it, who must answer it and when a response is due.
Why track RFIs by discipline and priority?
Tagging each RFI with a discipline — architectural, structural, MEP, civil and so on — routes it to the right reviewer quickly, while a priority level (low, medium, high, critical) makes it obvious which queries are blocking site progress and need an urgent answer.
How is an overdue RFI identified?
Each RFI can carry a response due date. If that date has passed and no response date has been recorded, the RFI is automatically flagged as overdue, so nothing waiting on a technical answer is missed or forgotten.
Can the RFI register be exported for a project report?
Yes. The register can be exported to CSV for further analysis, saved as a project file to reopen later, printed directly to PDF, or turned into a full detail report listing every RFI with its complete query and response text for a monthly progress report or handover file.
What is the difference between an RFI and a technical query?
In practice the two terms are used interchangeably on most projects: both describe a written question raised during construction or design that needs a formal answer. Some teams reserve "RFI" for contractually significant requests and "technical query" for informal clarifications, but both belong in the same log so nothing raised falls through the gaps.
Related project management tools
Planning and reporting on the same project: