An RFI tracking example is only useful if it reflects what actually happens on a jobsite: a foreman finds a conflict, work slows or stops, someone needs an answer, and the clock keeps moving. A spreadsheet full of RFI numbers does not protect the project if it cannot show what was asked, when it was asked, who owned the answer, and what the delay cost.
For superintendents and project managers, the goal is not paperwork for its own sake. The goal is a clean record that keeps crews moving, supports change order notices, and gives the office something defensible if the job turns into a schedule or payment dispute.
What a Good RFI Tracking Example Must Show
An RFI log should tell the full story without forcing someone to search through emails, marked-up plans, and text messages. At minimum, each entry needs an RFI number, clear subject, date submitted, responsible party, required response date, current status, and the date the answer was received.
That is the basic administrative record. The field record needs more. Add the drawing or specification reference, the party that identified the issue, a description of the work affected, and whether the RFI has a schedule, cost, safety, procurement, or rework impact. A short note identifying the crew waiting on direction can matter later. It connects an unanswered design question to real lost production.
The level of detail depends on the project. A small tenant improvement may use a simple shared log. A hospital, school, or major commercial build may require formal routing through the general contractor, architect, owner, and multiple consultants. In either case, the record should be consistent. If every superintendent writes RFIs differently, the log becomes difficult to manage and even harder to defend.
RFI Tracking Example: Structural Conflict at a Door Opening
Consider a commercial renovation where the framing subcontractor is preparing a rated corridor wall. The framing crew finds that the structural detail calls for a beam stiffener at the same elevation as the required door frame header. The architectural section does not show how the rated assembly should be modified.
The superintendent should not rely on a verbal answer from a walkthrough. The conflict needs an RFI, photos, plan references, and a record of the affected work. Here is what the tracking entry could look like.
| Field | Example Entry | | — | — | | RFI No. | RFI-047 | | Project | Northside Medical Office Renovation | | Subject | Conflict between structural beam stiffener and rated door header at Grid C-12 | | Submitted By | Framing Superintendent | | Date Submitted | May 6 | | Drawing References | S4.2 Detail 7; A6.1 Door Type D12; Wall Type 3A | | Question | Confirm required framing and fire-rated assembly detail where the structural stiffener conflicts with the door header elevation. | | Work Affected | Corridor wall framing, Door D12 installation, drywall close-in | | Responsible Party | Architect, structural engineer | | Required Response Date | May 9 | | Status | Open – work constrained | | Schedule Impact | Two-person framing crew reassigned; corridor close-in may slip if no direction is received by May 9. | | Response Received | May 10 – revised detail SK-14 issued | | Final Status | Closed May 11 | | Record Notes | Field photos taken May 6. Daily reports document crew reassignment May 7-10. |
The wording is direct because it needs to be. The question identifies the conflict, the location, and the decision required. It does not guess at a solution or bury the issue in a long narrative.
Notice the schedule language as well. It does not claim four days of compensable delay just because the response took four days. That conclusion requires contract review, schedule analysis, notice compliance, and an assessment of available work. But it does document the fact that a crew was affected and work was constrained. Those facts are the foundation for any later discussion.
How the RFI Record Connects to Daily Reports
An RFI log alone is not a complete project record. It shows the question and response cycle, but daily reports show the field consequences. The two records must agree.
On May 6, the daily report should note the discovered conflict, the location, the photos taken, and that RFI-047 was submitted. On May 7 through May 9, reports should identify the number of workers unable to complete the corridor framing scope, any reassignment made, and whether other work was available. If materials, equipment, or an inspection were also affected, document that too.
Avoid vague notes such as “waiting on RFI.” That phrase does not establish what work was stopped, whether the issue affected the critical path, or whether the contractor took reasonable steps to reduce the impact. A better note reads: “Two carpenters reassigned from Grid C-12 corridor framing due to unresolved header/stiffener conflict under RFI-047. Door D12 opening and adjacent rated wall close-in remain incomplete pending design direction.”
That level of detail helps the project team act sooner. It also prevents a common problem: the office finds an overdue RFI weeks later but cannot tell whether it was a minor clarification or a live field constraint.
Assign Ownership Before the RFI Gets Lost
Every open RFI needs one person responsible for follow-up. On many projects, the project manager owns formal communication while the superintendent owns field updates. That division works well if both sides use the same status definitions and review the open-item list regularly.
Use simple statuses that mean something in the field: draft, submitted, under review, answer received, field verification required, closed, and overdue. “Closed” should not mean an email arrived. It should mean the team has reviewed the answer, the direction is usable, affected crews have been notified, and the work can proceed.
For high-risk items, record a required response date based on the actual work sequence, not an arbitrary seven-day turnaround. If concrete is scheduled in 48 hours, an RFI affecting embeds needs immediate escalation. A response that arrives after the pour is not a timely response, even if it meets a standard administrative deadline.
Common RFI Tracking Failures
Most RFI problems are not caused by a lack of software. They come from weak habits and incomplete field information. The following failures create avoidable exposure:
- Using a subject line like “Question” or “Need clarification,” which makes sorting and searching nearly useless.
- Failing to attach photos, plan excerpts, dimensions, or exact locations when the issue is field-specific.
- Leaving RFIs marked open after an answer is issued, even when the answer creates a new cost, procurement, or constructability problem.
- Treating verbal direction as final without confirming it in writing through the proper project channel.
- Recording delay impacts only after the schedule claim is already being assembled.
There is a trade-off here. A superintendent cannot spend an hour writing every RFI while managing deliveries, manpower, inspections, and safety. But saving five minutes by submitting a thin RFI can cost days later when the architect asks for more information or the record cannot show why work changed.
The practical answer is a repeatable mobile process. Capture the photo, location, drawing reference, question, and affected activity while standing at the issue. Then let the office handle routing and formal follow-up. Construction Reporting Apps is built around that field-first principle: records are stronger when the details are captured before the crew moves on.
Build a Weekly Open-RFI Review
A weekly review should focus on active risk, not simply the total number of open RFIs. Look at every item that is overdue, affects near-term work, changes a released scope, holds up procurement, or has a possible cost impact. The superintendent should be able to answer three questions for each one: What is waiting? Who needs to respond? What happens if no answer arrives by the next workday?
This is also the right time to compare the RFI log against daily reports, look-ahead schedules, submittal logs, and change order notices. If an unresolved RFI is holding steel, finishes, inspections, or owner-furnished equipment, the project record should show that connection before the impact becomes larger.
A good RFI tracker does not create conflict. It makes the existing conflict visible while there is still time to solve it. Keep the questions clear, connect each answer to the work in the field, and document the consequence while the facts are still fresh.
Related Articles
Start writing better daily reports today
Download the Superintendent's Daily Report app or grab the free checklist.
Leave a Reply