Every RFI that sits unanswered for a week can cost your project money, schedule credibility, and claims position. I've watched PEs maintain immaculate logs nobody reviews and PMs inherit logs so bloated that blocking issues disappear.
One report by Navigant Construction Forum analyzed 1.1 million RFIs across 1,362 projects. It found that the average project generates 796 RFIs at a total estimated cost of $859,680.
The management discipline around those RFIs can keep that cost contained or contribute to rework and delay risk. Functioning RFI workflows depend on daily cadence, clear role ownership, defined escalation triggers, and disciplined log hygiene.
Basics of RFI Logs: Fields, Status, and Governance
Your RFI log is simultaneously a daily management tool and a legal record. In my experience, designing it to serve both functions from day one is the discipline most teams skip.
Fields That Carry Contractual Weight
Per AIA G716-2004 and AGC/USACE guidance, a production-grade log carries four field categories beyond basic identification:
Origination and routing fields (Submitted By, Submitted To, Date Received, Assigned Reviewer) create the accountability chain.
Scheduling fields (Response Required By, Priority Category) establish the contractual clock.
Impact assessment fields (Cost Impact Y/N, Schedule Impact Y/N, Estimated Delay Days) flag potential change orders at submission.
Downstream linkage fields (Change Order Reference, ASI/PR Reference) maintain the audit trail from RFI to ASI/PR to COR to CO.
Include a contractor-side proposed solution. It often shortens response cycles and documents the GC's interpretation of design intent.
Status Definitions That Hold Up
Six statuses cover most projects:
Open — submitted and awaiting response.
Pending/In Review — acknowledged and in progress.
Answered — a response was received but not confirmed actionable.
Closed — the GC confirms the response is complete and actionable.
Void/Cancelled — withdrawn or duplicate, with the number retained.
Overdue — treat as a derived condition rather than a terminal status; reserve terminal status for Closed or Void/Cancelled.
The distinction between "Answered" and "Closed" is where most teams fail. I would keep closure authority on the GC side, because closure means the response is sufficient to proceed with work.
RFI Management Cadence
A working RFI process runs on two rhythms: a daily discipline that keeps submissions ahead of the field schedule, and a weekly review that surfaces aging items before they turn into delay claims. Each cadence has its own owners, deliverables, and escalation triggers.
Daily Discipline
RFI management works best when teams submit RFIs at least ten days before they need a response. The previously mentioned Navigant report identifies this as a lead time intended to reduce project disruption. The PE works against the field schedule, identifying information gaps far enough ahead that even a full contractual response window does not create a delay.
At submission, each RFI must include a single subject of inquiry, specific drawing or specification references organized by CSI division, assigned priority, and schedule impact language if applicable. That last item is operationally significant. Including schedule impact language at submission creates a real-time record. Adding it after the response is late weakens the claims position.
Weekly Review and Escalation
Make Outstanding RFIs a standing agenda item at project progress meetings. A construction project with the University of Tennessee explicitly requires the contractor to develop an RFI aging report and submit it at each progress meeting. That requirement turns the RFI aging report into a contract deliverable.
Define the escalation ladder at project kickoff. At five business days without a response, escalate to the PM, document the status in meeting minutes, and begin cost documentation. At the contractual deadline, send formal written follow-up and document it. That written notice creates the paper trail required to support schedule impact claims.
Who Owns the Log on a GC Team
The project engineer maintains the log daily (e.g., numbering, status updates, deadline tracking, and response distribution).
The PM reviews RFIs before upstream submission for clarity and contract alignment. They also monitor aging items for schedule risk and escalate disputes immediately.
The superintendent originates RFIs from field conditions, reviews responses for field applicability, and implements clarified instructions.
On larger projects, a contracts administrator handles log infrastructure, including numbering, filing, version control, and archival.
Give each log one clearly accountable owner. On smaller projects, the same role often holds both the tracking and infrastructure responsibilities. A common breakdown point is GC-side follow-up after the design team responds.
When the RFI Log Becomes a Graveyard
I've seen logs accumulate open items with no easy way to tell which ones are actually holding up work. The breakdowns that produce this waste follow a predictable pattern.
Log Bloat and Duplicate Submissions
A bloated log hides the RFIs that actually block work. When the register is full of transmittals and fishing expeditions, the PM cannot identify which items require action. The Navigant report documented a project where a contractor submitted 4,000 alleged RFIs. Forensic analysis revealed roughly 1,700 were routine correspondence, 500 were submittals, and 800 were duplicates of previously answered questions.
Mandatory log search by keyword, drawing reference, and specification section before drafting prevents duplicates. When an existing response is genuinely inadequate, request clarification on the existing RFI number.
Missing Owners, Missing Cadence, Missing Escalation, Inconsistent Status
When a team submits an RFI without a named GC-side responsible party, the item sits in limbo. When teams update a log but never review it weekly, open items accumulate with no indication of which ones block work. Overdue RFIs with no defined escalation path erode the GC's ability to support schedule claims. And when "Answered" and "Closed" are used interchangeably, unresolved items hide behind a label that implies completion.
Assign a named GC-side owner to every RFI at submission. Review the full open log weekly as a standing OAC agenda item. Define the escalation ladder at kickoff. Restrict closure authority to the GC side.
Where Manual RFI Management Breaks at Portfolio Scale
Across a large portfolio, RFI volume can run into the thousands. Manual logs, whether spreadsheets, email threads, or project-specific software instances, work at the project level. They do a poor job of surfacing aging patterns or respondent bottlenecks across the portfolio.
Cross-Project Blind Spots
When a single design firm is the assigned responder on RFIs across five concurrent portfolio projects, no individual PM sees the portfolio-wide bottleneck from their own log. ENR described one integrated cross-project metrics implementation on a complex project. The implementation reduced average RFI aging by 40%. When a PE rotates off a project, email-based RFI workflows mean the incoming PE often restarts from zero.
How AI Agents Strengthen the RFI Workflow
Datagrid's RFI Validator Agent validates submissions at the point of RFI creation, before they enter the log. The agent cross-references the full project files for existing answers, compares the new submission against every RFI already logged, evaluates completeness against a documented standard, and flags potential cost, schedule, or quality implications.
Traditional workflows log, route, and track RFIs after submission, so the log grows with every entry regardless of quality. Preventing unnecessary RFIs upstream changes the economics of the workflow, particularly for GC teams losing six figures per project to unjustifiable submissions.
Coverage Across the RFI Lifecycle
Beyond upstream validation, Datagrid's agents support the RFI process from submission through closeout:
Routing and coordination — direct RFIs to the right reviewers and surface conflicts between drawings, specifications, and submittals before they generate rework.
Closeout verification — confirm that final as-built drawings reflect the responses captured in the RFI record.
Reduce Contract Administration Overhead
"Buro is deploying Datagrid to help our designers and engineers resolve RFIs. We are on our way to reduce CA work by 50%."
Alain Waha, CTO, Buro Happold
Datagrid's RFI Validator Agent cross-checks submissions against your full project files before they enter the log. Fewer duplicates, fewer unjustifiable entries, and a log that actually tells you what's blocking work.
