What Is an RFI in Construction?

An RFI — Request for Information — is a formal question submitted by a contractor, subcontractor, or owner to the design team asking for clarification on the construction documents. It’s the mechanism the industry uses to resolve ambiguity: something in the drawings or specs is missing, contradictory, or unclear, and work can’t proceed until there’s an answer.

RFIs are routine on every project. They’re also expensive, cumulative, and — in many cases — preventable. Understanding what triggers them is the first step toward controlling them.

The basic mechanics

An RFI follows a defined path. The field or a sub identifies something they can’t build as drawn. They submit a written request to the general contractor, who logs it and routes it to the appropriate design consultant — architect, structural engineer, MEP engineer, civil, whoever owns the issue. The consultant reviews, responds in writing, and the response becomes part of the official project record.

A typical RFI response takes three to seven business days. A complex one involving multiple consultants can run two to three weeks.

That response time is the part that gets expensive. While the answer is pending, related work can stall, schedules compress, or trades proceed under their best interpretation — which may or may not match what the design team intended. Work built under a wrong assumption often becomes rework.

Who’s involved

• The party submitting — usually a subcontractor who has hit a field condition or document ambiguity. The GC typically manages the log and routes the RFI on their behalf.
• The design team — the architect of record and relevant consultants (MEP, structural, civil, etc.) are responsible for answering within their scope. Complex RFIs may require a design coordination meeting before a response can be issued.
• The owner — on many projects the owner or their representative must be copied on or approve responses before they’re binding. Responses that involve cost or scope changes may also require a formal amendment.

What triggers an RFI

RFIs come from gaps in the construction documents. The most common triggers fall into four categories:

Design conflicts. Two documents — or two sheets within the same set — contradict each other. The architectural plan shows a wall at one location; the structural plan shows a footing that interferes. The spec calls a fire door with one rating; the door schedule shows another. These are the conflicts that AI construction plan review is specifically designed to surface before construction starts.

Missing information. A detail is referenced but not drawn. A specification section describes a product but doesn’t provide installation guidance for this particular condition. A contractor needs a dimension that doesn’t appear on any sheet.

Changed field conditions. Existing conditions don’t match what the drawings assumed — a structural element in an unexpected location during renovation, soil conditions that differ from the geotechnical report, utilities at wrong depths. These RFIs are harder to prevent; they require field verification.

Ambiguous specifications. A spec section leaves genuine room for interpretation on substitutions, means and methods, or performance criteria. Contractors need a written ruling to protect themselves and to bid the work correctly.

The first two categories — design conflicts and missing information — are overwhelmingly the most common, and they’re the ones that a thorough preconstruction document review can eliminate before the first shovel turns.

RFI vs. change order vs. submittal

These three documents are often confused because they interact, but they serve distinct functions.

An RFI asks a question. It doesn’t authorize work, change the contract, or transfer any cost. It just gets an answer into the record.

A change order modifies the contract — scope, schedule, or price. Many RFI responses eventually lead to a change order when the clarification reveals that the work can’t be built as originally designed or priced. But an RFI itself is not a change order. On poorly coordinated projects the pipeline looks like: conflict in the drawings → RFI submitted → response requires a scope change → change order issued. That’s the sequence that makes RFI volume a leading indicator of project cost growth. On one real project, more than 40 change orders traced directly back to conflicts between 2D plan sheets.

A submittal flows the other direction — from the contractor to the design team. The contractor submits a shop drawing, product data, or sample for review and approval before fabrication or installation. Where an RFI asks a question about the documents, a submittal demonstrates that the contractor’s proposed execution complies with the documents.

What an RFI costs

The direct cost of an RFI is the time to process it — prepare, log, route, respond, and close. That overhead runs real money across a project’s full RFI log.

The indirect cost is usually larger. Every RFI that isn’t resolved before it hits the schedule creates ripple effects: related work stalls or proceeds at risk, subcontractors miss production windows, schedule float erodes. When the answer triggers a change order, that cost sits on top.

Industry experience — and Flikt’s own project data — consistently points to the same dynamic: errors discovered during construction cost roughly ten times more to fix than the same errors caught during plan review. The shear-wall-vs.-duct conflicts documented on Flikt’s evidence page carried $28,000–$45,000 in rework plus 14–21 days of schedule impact each. The corresponding RFI process — submitting the question, waiting for a structural and mechanical response, getting an amended detail — would have added days to that window even before a single worker picked up a tool.

For the full breakdown of where the money goes, see what an RFI costs in construction — that post covers direct cost, indirect cost, and how to quantify RFI exposure on a specific project.

The connection to drawing quality

Not all projects generate the same number of RFIs. Drawing quality is the strongest predictor of RFI volume, and it varies substantially across design teams, project types, and budget tiers.

Flikt uses conflicts per 100 sheets as a normalized drawing-quality benchmark — how many real, actionable conflicts a set contains, scaled to document size so it’s comparable across projects of different scope. A dense multifamily project with 300 sheets and 60 conflicts looks different from a 60-sheet tenant improvement with 12 conflicts even though the raw count is similar; the benchmark surfaces that difference. You can read more about how the metric works and what “good” looks like in conflicts per 100 sheets.

The practical implication: if you’re a general contractor who tracks RFI volume per project and sees it spike on certain design teams’ work, conflicts per 100 sheets is a way to quantify that pattern and make the case for better document quality up front — before the subcontracts are signed.

How to reduce RFIs before construction starts

RFIs that originate from design conflicts and missing information don’t have to be discovered in the field. The technology to find them in the documents before bid is now accessible without BIM, without a 3D model, and without a dedicated VDC team.

AI construction plan review reads the full 2D drawing set and flags the cross-discipline conflicts, spec mismatches, and missing-coordination gaps that generate RFIs downstream. For general contractors, catching those issues at design review rather than during construction is straightforwardly the highest-ROI move in preconstruction — and for owners, it’s one of the few quality gates that actually has teeth before the budget is committed. General contractors can start here.

The tactical how-to — how to structure a review workflow that systematically closes the gap between the plan set and what’s buildable — is in how to reduce RFIs before construction starts.

For teams that want a fuller framework, the pre-construction QA checklist covers the full scope of document review tasks, including but not limited to RFI prevention.

The upstream fix

Every RFI that gets submitted is a gap that existed in the construction documents before the project broke ground. The questions were always there — someone just discovered them at the worst possible time.

The upstream fix isn’t a better RFI management system. It’s better documents. And better documents come from reviewing the drawings before construction starts, systematically, against the full set — not discipline by discipline, and not assuming that because the architect and engineer each reviewed their own scope, the coordination between them is clean.

That’s the work preconstruction document review does. The RFI log is the measurement of how much of that work didn’t happen.

---

Flikt reviews 2D construction documents for cross-discipline conflicts before construction starts — no BIM required. See how AI plan review works, or talk to us about your next project on the contact page.