The formal mechanism for resolving gaps and conflicts in the contract documents — and the log that decides delay claims.
Last updated
Zepth Core module
9.9
RFIs raised per $1 million of construction cost — roughly 800 on an average project
Navigant Construction Forum · 1,362 projects, 1M+ RFIs
8–10 days
average turnaround from RFI raised to answer returned
Navigant Construction Forum
22%
of RFIs never received an official answer at all
Navigant Construction Forum
$1,080
and about 8 hours of review time — the cost of answering a single RFI
Navigant Construction Forum
2013 dollars, reviewer-side only. The all-in cost of raising, routing, chasing and implementing is higher.
15 days
before delay is recognised under AIA A201 if no response period is agreed — it requires only “reasonable promptness”
AIA A201 General Conditions
An RFI is the formal mechanism for resolving gaps, conflicts, or ambiguities in the contract documents. A contractor raises a question — about a drawing conflict, a missing detail, an ambiguous specification — and the designer or consultant answers it on the record. The RFI log becomes one of the most consequential documents on the project.
Zepth treats the RFI as a workflow with a clock, not an email thread. Every RFI carries references, impact flags, a needed-by date and ball-in-court status; routing follows your project’s actual approval chain; overdue RFIs escalate automatically.
The scale surprises people outside the industry. The Navigant Construction Forum studied 1,362 projects containing over a million RFIs and found an average of 9.9 RFIs for every $1 million of construction — nearly 800 per average project — with each one consuming about 8 hours and roughly $1,080 in review and response cost. Turnaround averaged 8–10 days, and more than a fifth of RFIs never received an official answer at all.
Every one of those numbers is margin and schedule. An unanswered RFI on the critical path means a crew standing down or working at risk. A slow answer means resequencing. And an RFI answered with new scope that proceeds without a change order means someone — usually the contractor — absorbs the cost.
The RFI log is delay-claim evidence. Date raised, needed-by date, date answered, ball-in-court history — in an extension-of-time claim, this log is primary evidence, corroborated against daily reports, photos and schedule updates. Late responses to critical-path RFIs are among the most common bases for compensable delay.
RFI volume is a design-quality signal. A project trending far above the ~10-per-$1M benchmark is telling you something: incomplete design, poor coordination, or ambiguous specifications. Owners increasingly use RFI rates as a designer-performance KPI; contractors use abnormal volumes as evidence in defective-design narratives.
RFIs are a known abuse vector. Experienced teams watch for RFI flooding — contractors papering the record to manufacture delay entitlement or fish for scope gaps convertible to change orders. Designers counter by answering “refer to drawing X” and logging it. A disciplined, transparent RFI process protects both sides.
An RFI is not a notice, and an answer is not a change order. Two traps that generate disputes: contractors who assume an RFI satisfies contractual claim-notice requirements (it generally doesn’t), and teams that proceed on an RFI answer containing changed scope without converting it to a change event.
Email-based RFIs with no log, no needed-by dates and no ball-in-court tracking produce predictable failures: questions that vanish into inboxes, duplicate RFIs from different subcontractors, answers that never reach the crew that asked, and a delay claim two years later that can’t be substantiated because nobody can prove when the question was asked or how long the answer took.
Under most contracts the fallback is weak. AIA A201 requires only “reasonable promptness”, recognising delay just 15 days after a written request for interpretation if no time is agreed. If your contract specifies 7–14 days — the common convention — the log is the only instrument that enforces it.
Faster turnaround — routing, needed-by dates and AI-drafted responses cut the cycle time that stops the work, against an industry average of 8–10 days.
A defensible delay-claim record — date raised, needed-by, date answered and ball-in-court history, exportable when the claim arrives.
Nothing unanswered — overdue RFIs escalate automatically, against an industry baseline where 22% never get a formal answer.
Scope creep caught — answers that introduce changed scope are flagged for conversion to a change event before the work proceeds.
Raise, route to the responsible discipline, answer, and close — with a needed-by date and automatic escalation, not an email thread.
Cite the exact drawing, revision and spec section each RFI concerns, so the answer is unambiguous and the record is defensible.
Track whose action every RFI awaits, and surface the overdue list — the leading indicator of delay.
Flag cost and time impact at origination, and flag answers that introduce changed scope for conversion to a change event.
Turnaround statistics, overdue items and volume by discipline — exportable for a delay claim or a designer-performance review.
A subcontractor or site engineer spots the conflict. The GC’s project engineer vets it — is this answerable from the contract documents? — before formalising. Subcontractors don’t send RFIs directly to the architect; contractual privity routes everything through the GC.
One question, referenced drawings and specs, a proposed solution, a needed-by date, and cost/time impact flags. “See attached, please advise” is how RFIs die.
To the architect or engineer, often sub-routed to specialist consultants — the double hop where most time is lost.
Answer returned, distributed to the field, log updated. If the answer changes scope, a change event is raised immediately.
Volume by discipline, average turnaround against the contract period, and the overdue list reviewed weekly.
The AI reads the question against the project’s drawings, specifications and contract, and drafts a response with cited references and a confidence score. The engineer reviews, edits and sends. Turnaround measured in hours, not the industry’s 8–10 days.
Flags RFIs already answerable from the documents — with the reference — and near-duplicates of earlier questions, before they consume a review cycle.
Answers that appear to introduce changed scope get flagged for conversion to a change event, closing the most expensive gap in the RFI process.
“Which open RFIs threaten the critical path?” — answered from live data, with charts.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
A live RFI log with turnaround statistics, the overdue list, ball-in-court status and volume by discipline — always current and always exportable, which is exactly what a delay claim or a designer-performance review needs.
Whatever the contract says — 7 to 14 days is the common convention. The AIA A201 base document requires only “reasonable promptness”, with delay recognised 15 days after a written request if no period is agreed. If your contract sets no fixed period, negotiate one.
Navigant’s benchmark across 1,362 projects: about 9.9 RFIs per $1 million of construction cost, or roughly 800 on an average project. Sustained rates far above that usually indicate design coordination problems.
No. An RFI answer clarifies; it doesn’t authorise. If the answer introduces changed scope, it must be converted to a change order or variation before the work proceeds — proceeding on the answer alone is a classic dispute trigger.
Generally not. Contractual notice requirements are separate and usually stricter. Raising an RFI about a problem does not preserve your entitlement — serve the notice the contract requires.
Read the full answerNo — contractual privity means RFIs route through the general contractor, who vets and formalises them. Direct sub-to-architect questions create uncontrolled, unlogged commitments.
One specific question, referenced documents, a proposed solution, a needed-by date, and honest cost/schedule impact flags. RFIs written this way get answered faster and stand up better as records.
Read the full answerRelated answers
Terms defined here
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
A short, tailored walkthrough on your real workflow — no generic demo.