How to Track RFIs in Construction
An unanswered RFI can stall work, trigger rework, and evolve into a claim. Effective tracking ensures every question gets answered on time and every response reaches the people who need it in the field.
Step 1: Establish a Numbering System
A consistent numbering system prevents duplicates, simplifies searches, and keeps the log organized as the project grows. Pick one format at the start and apply it to every RFI.
Sequential
RFI-001, RFI-002, RFI-003
The simplest approach. Each RFI gets the next available number regardless of discipline, submitter, or trade. Works well for small to mid-size projects with a single log manager.
By Discipline
RFI-MECH-001, RFI-ELEC-001
Prefixes each RFI with a discipline code. Makes it easy to filter and report by trade area, which is valuable on complex projects with hundreds of RFIs across multiple systems.
By Submitter
RFI-ABC-001, RFI-XYZ-001
Prefixes with the submitting company's abbreviation. Useful when multiple subcontractors manage their own RFI sequences and a general contractor consolidates them into a master log.
Step 2: Capture the Right Data Fields
Your RFI log is only as useful as the information it contains. Track these fields for every entry to support status reporting, aging analysis, and project closeout.
RFI Number
The unique identifier assigned at creation. This is the primary key for all tracking, correspondence, and cross-referencing.
Subject
A concise, descriptive title that identifies the element, location, and nature of the question without opening the full document.
Date Submitted
The date the RFI was formally submitted. This starts the response clock and is essential for aging calculations and contractual compliance.
Submitted By
The company and individual who originated the request. Needed for communication, accountability, and tracking submission patterns by trade.
Assigned To
The party responsible for providing the response — typically the architect, engineer of record, or owner's representative depending on the subject matter.
Priority Level
A classification that reflects the urgency: critical, urgent, standard, or low. Drives review sequencing and escalation timing.
Response Due Date
The contractual or agreed-upon deadline for receiving a response. This is the benchmark for aging reports and overdue notifications.
Date Answered
The date a formal response was received. Used to calculate actual response time and compare against the contractual window.
Status
The current lifecycle stage of the RFI (Draft, Submitted, Under Review, Answered, Closed, etc.). Enables quick filtering and dashboard reporting.
Cost Impact
Whether the response triggers a potential change order. Flag this early so the project team can track cumulative RFI-driven cost exposure.
Schedule Impact
Whether the RFI or its delayed response affects the construction schedule. Critical for time-impact analysis and delay claims.
Related Sheets
The drawing sheets, specification sections, and contract documents referenced in the RFI. Links the log entry to the source documents for easy cross-referencing.
Step 3: Define Clear Status Categories
Ambiguous status labels create confusion. Use a standardized set of categories so every team member interprets the log the same way.
Draft
The RFI is being prepared but has not been formally submitted. It may still need internal review, additional references, or management approval before going out.
Submitted
Formally sent to the responsible party. The response clock starts on this date. The RFI is now in the reviewer's queue.
Under Review
The reviewer has acknowledged receipt and is actively working on a response. This status provides visibility that the item has not been lost or overlooked.
Returned for Clarification
The reviewer needs additional information before they can provide a response. The ball is back with the submitter to revise and resubmit.
Answered
A formal response has been issued. The submitter should review the answer, confirm it is actionable, and prepare to distribute it to affected parties.
Distributed
The response has been forwarded to all affected subcontractors and team members. Field drawing sets have been updated if applicable.
Closed
The RFI is fully resolved, distributed, and incorporated into the project record. No further action is required from any party.
Disputed
The submitter disagrees with the response or believes it changes the contract scope. The item remains open and may trigger the change order or claims process.
Step 4: Set Response Time Expectations
Not every RFI carries the same urgency. Define priority tiers with specific response windows so reviewers know which items to address first and submitters set realistic expectations.
Critical
24 – 48 hours
Work is stopped or will stop imminently. Crews are standing by, and every hour of delay has a direct cost impact. Requires immediate escalation to the responsible party.
Urgent
3 – 5 days
Work will be affected within the next week. Procurement or fabrication lead times are at risk if the answer is delayed beyond five days.
Standard
7 – 10 days
The typical contractual response window. Work is not immediately affected, but the response is needed to maintain the overall project schedule.
Low Priority
14+ days
Informational or future-phase questions that do not impact current work. Still needs a response, but the timeline is flexible and does not drive near-term decisions.
Step 5: Run an Aging Report
An aging report shows how long each open RFI has been waiting for a response. Color-code the buckets so overdue items are impossible to miss during status meetings.
0 – 7 Days
Green
Within the standard response window. No action needed beyond normal tracking. The reviewer has adequate time to respond.
8 – 14 Days
Yellow
Approaching or at the contractual deadline. Send a reminder to the responsible party and flag the item in the weekly status report.
15 – 21 Days
Orange
Overdue. Escalate to the project manager or owner's representative. Document the delay and its potential impact on the construction schedule.
21+ Days
Red
Significantly overdue. Escalate to senior leadership. Issue a formal notice of delay if the unanswered RFI is affecting the critical path or causing standby costs.
Step 6: Distribute Responses Effectively
An RFI response that never reaches the field is as good as no response at all. Build a distribution workflow that ensures every answer gets to the right people and into the right documents.
Identify Affected Parties
Determine which subcontractors, vendors, and team members are directly or indirectly affected by the response. Consider both the trade that submitted the RFI and adjacent trades.
Forward to Subcontractors
Send the response directly to the relevant subs with a clear transmittal. Include the RFI number, a summary of the response, and any action items so the information is not buried in an email thread.
Update Field Drawing Sets
If the response modifies the drawings, update the field sets immediately. Mark the affected sheets and note the RFI number so crews work from the latest information.
Flag If ASI Is Needed
If the response requires a formal revision to the contract documents, request an Architect's Supplemental Instruction (ASI) to make the change part of the permanent record.
Confirm Receipt
Get written acknowledgment from each recipient that they received and understood the response. This closes the loop and provides documentation if questions arise later.
Step 7: Measure RFI Performance Metrics
Metrics transform your RFI log from a tracking tool into a diagnostic instrument. They reveal patterns in the documents, highlight slow reviewers, and quantify the true cost of design-phase gaps.
Submitted vs. Closed
Compare total RFIs submitted against total closed. A widening gap signals that the review pipeline is falling behind and open items are accumulating.
Average Response Time
Calculate the average number of days from submission to response. Track this over time to spot trends and compare against the contractual requirement.
Clarification Return Rate
The percentage of RFIs returned for additional information. A high rate indicates that submitters need better training or templates, or that questions are being sent prematurely.
Cumulative Cost Impact
Total cost exposure from RFIs that triggered change orders or potential change orders. Links document quality directly to budget performance.
Cumulative Schedule Impact
Total days of delay attributed to unanswered or late RFIs. Essential for time-impact analysis and documenting excusable delays for claims.
Most Common Categories
Group RFIs by discipline, drawing sheet, or issue type. Concentrations in one area may indicate systemic problems with a particular design discipline or document set.
Frequently Asked Questions
What is the best way to number RFIs on a construction project?
The most common approach is simple sequential numbering (RFI-001, RFI-002, etc.). For larger or multi-discipline projects, you can prefix each number with a discipline code (RFI-MECH-001) or submitter code (RFI-ABC-001) to simplify filtering and reporting. The key is choosing one system at project kickoff and applying it consistently throughout.
How often should you review the RFI log?
At minimum, review the log weekly during active construction. Many project teams review it at every OAC meeting to keep overdue items visible and ensure aging RFIs are escalated before they become critical. The goal is to catch problems early and keep responses on schedule.
What RFI metrics should a project manager track?
Focus on total submitted vs. closed, average response time, percentage returned for clarification, cumulative cost impact, cumulative schedule impact, and the most common categories. These metrics surface systemic issues in the contract documents and highlight trends that may point to design quality gaps or slow review processes.
Should RFI responses be distributed to subcontractors?
Absolutely. Every RFI response that affects field work must be distributed to the relevant subcontractors and incorporated into the project record. One of the most common causes of rework is an RFI response that was issued but never reached the crew performing the work. Build a distribution checklist into your workflow to prevent this.
Related Resources
How to Write an RFI
Step-by-step guide to writing RFIs that get answered quickly, with examples of strong subject lines, specific questions, and supporting visuals.
Change Orders Guide
Document types, pricing methods, markup structures, and processing steps for construction change orders.
Knowledge Base
Guides, references, symbols, abbreviations, and review checklists for AEC professionals.
Catch Drawing Issues Before They Become RFIs
Book a demo and see how Structured AI identifies conflicts, missing details, and coordination gaps during design review — so fewer RFIs make it to the field in the first place.
Try Automated Drawing Review