In construction project management, few administrative processes carry as much hidden cost as the Request for Information (RFI) workflow. An RFI is a formal written request from a contractor or subcontractor seeking clarification on construction documents, specifications, or drawings. While the process seems straightforward on paper, the data tells a different story. Research from the Navigant Construction Forum, which analyzed over 1,300 construction projects and more than 1 million individual RFIs, found that roughly 22 percent of all RFIs are never answered. That statistic alone should concern every project manager, owner, and contractor in the industry. When an RFI goes unanswered, the project does not stop. Work continues under ambiguous conditions, risk increases, and disputes become far more likely. This article explores the real cost of unanswered RFIs, the root causes behind poor response rates, and the practical steps your team can take to improve the process. For a broader look at how construction project management strategies from top building teams can streamline operations, that resource pairs well with the RFI-specific guidance below.
Understanding RFI Response Rates: What the Numbers Reveal
The Navigant study, published in the research paper “Impact and Control of RFIs on Construction Projects,” provides the most comprehensive data set available on RFI performance. The projects analyzed ranged from $5 million to $5 billion in value, spanning multiple sectors and geographies. The findings paint a clear picture of an industry-wide problem.
The 22 Percent Unanswered Statistic
Nearly one in four RFIs submitted on a construction project never receives a formal response. Navigant identifies this no-response rate as one of the strongest leading indicators that a dispute will arise later in the project. When a contractor submits an RFI and receives no answer, they must make assumptions about how to proceed. Those assumptions may conflict with the owner’s or architect’s expectations, creating fertile ground for change orders, rework, and claims. Projects with high unanswered RFI rates consistently experience more friction during closeout and a higher likelihood of litigation.
Average Response Times and Cost Per RFI
Even when RFIs do receive a response, the timeline is far from ideal. The study found that the average response time per RFI hovered just below 10 days. In fast-paced construction environments where work proceeds daily, a 10-day wait can stall critical path activities, delay subcontractors, and push project completion dates to the right. The administrative and technical cost of processing each RFI averaged slightly more than $1,000. When you multiply that by the hundreds or even thousands of RFIs on a large project, the total cost burden becomes substantial.
Cost Implications of Delayed and Unanswered RFIs
The financial impact of a poor RFI process extends beyond the direct cost of review and response. Delays caused by unanswered RFIs can force crews into idle time, require resequencing of work, and lead to acceleration costs when the schedule tightens. Subcontractors may submit change orders for work performed under unclear conditions. The cumulative effect can add significant unplanned expense to a project budget. A practical guide for building professionals on construction project communication and documentation offers additional strategies for keeping these costs under control through better communication workflows.
Why RFIs Go Unanswered: Root Causes in Construction Projects
Understanding why RFIs go unanswered is the first step toward fixing the problem. The causes are rarely malicious. They stem from systemic issues in how construction projects manage information and assign responsibility.
Lack of Formalized Procedures
Navigant’s research points to a lack of formalized RFI procedure as the primary reason most RFIs go unanswered. On many projects, there is no clear escalation path for what happens when an RFI sits in someone’s inbox past the contractual response period. No automatic reminders, no secondary review assignments, and no consequence for non-response. The absence of structure means RFIs fall through the cracks, especially on busy projects where team members juggle multiple responsibilities.
Communication Breakdowns Between Stakeholders
RFIs often pass through multiple hands before reaching the person with the authority to answer. A subcontractor submits to the general contractor, who reviews and forwards to the architect, who may need to consult with the owner or a structural engineer before responding. Each handoff introduces the risk of delay or loss. When communication channels are unclear, or when stakeholders use different tools and platforms, the likelihood of an RFI being forgotten increases dramatically.
The Role of Contract Language
The contract itself plays a significant role in RFI outcomes. Navigant recommends adding specific language regarding RFI procedures directly into the contract, including required response times, escalation protocols, and consequences for missed deadlines. Projects with clearly defined RFI clauses in their contracts tend to achieve better response rates and fewer disputes than those that leave the process to informal custom and practice.
Best Practices for Improving RFI Response Rates
Both owners and contractors have a role to play in improving RFI outcomes. The best results come when all parties adopt mutually supporting practices that create accountability, speed, and clarity throughout the process.
Best Practices for Owners and Architects
- Use a consistent RFI numbering system across all projects to simplify tracking
- Indicate required response times for RFIs in the contract documents
- Respond to RFIs as quickly as possible, even if the answer is preliminary
- Use electronic RFI tracking software to monitor open items
- Require that RFIs be handled using the lowest-cost appropriate method
- Distribute RFIs to every relevant team member via email or platform notifications
- Ensure all RFI responses are written and formally documented
- Make responses as specific as possible, referencing a specific drawing or detail number
- Use hand-drawn clarifications when appropriate to save time
- Incorporate all RFI responses into revised drawings at project closeout
Best Practices for Contractors and Subcontractors
- Submit RFIs as soon as the need for clarification is identified
- Allow at least 10 days for a response in your project schedule
- Limit each RFI submittal to a single, focused subject
- Assign a priority level to each RFI so reviewers know what needs immediate attention
- Include specific references to drawings, specifications, and detail numbers
- Include a suggested resolution when possible to speed up the review
- Disclose upfront if the RFI will cause time delays or cost changes
- Indicate clearly if the RFI is time-sensitive for the construction schedule
- Assume that RFI responses constitute approval unless noted otherwise
| Practice Area | Owner/Architect Responsibility | Contractor/Sub Responsibility |
|---|---|---|
| Response Time | Respond within contractual timeframe | Allow minimum 10 days for response |
| Documentation | Write responses referencing specific drawings | Include drawing and spec references |
| Tracking | Use electronic RFI tracking software | Assign priority to each RFI |
| Scope | Answer each RFI completely | Limit submissions to single subject |
| Proactive | Distribute RFIs to all stakeholders | Submit RFI as soon as needed |
Implementing these practices consistently across your organization will reduce the percentage of unanswered RFIs and lower the overall cost impact of the RFI process on your projects.
Leveraging Technology to Track and Manage RFIs
Technology offers some of the most effective solutions for RFI management. The days of tracking RFIs through email threads and spreadsheets are giving way to purpose-built platforms that automate the workflow and provide real-time visibility.
Electronic RFI Tracking Software
Dedicated RFI tracking software, whether standalone or integrated within a construction project management platform, provides automated assignment, escalation, and deadline management. When a response deadline approaches, the system notifies the responsible party. If the deadline passes without a response, the system escalates to a supervisor. This automation alone can dramatically reduce the percentage of unanswered RFIs. Platforms like Procore, Autodesk Build, and Bluebeam Revu all offer RFI modules that integrate with drawing sets and daily logs. For projects already using a reliable submittal tracking tool, adding an RFI module extends the same accountability framework to requests for information.
Integrating RFI Management with Daily Documentation
RFIs do not exist in isolation. They connect to daily reports, submittals, meeting minutes, and change orders. When RFI data lives in a separate silo, the connections between an unanswered RFI and a delayed activity on the schedule are harder to spot. Modern construction platforms bridge these gaps by linking RFIs directly to the drawings, contracts, and daily logs they reference. This integration makes it possible to track the downstream impact of each RFI and identify patterns before they become disputes.
Mobile Forms and Real-Time Updates
Field teams often identify the need for an RFI but lack an easy way to initiate one from the jobsite. Mobile forms and apps now allow superintendents and foremen to submit RFIs directly from their phones or tablets, including photos of the condition that requires clarification. This capability reduces the lag between identifying an issue and formally documenting it. For a deeper look at how mobile forms are transforming construction documentation and field reporting, that article covers the broader ecosystem that supports RFI management in the field.
By combining clear contractual language, well-defined best practices, and modern tracking technology, construction teams can move the needle on RFI response rates, reduce project risk, and keep their projects on schedule and on budget.