An RFI \u2014 Request for Information \u2014 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.<\/p>\n
RFIs are routine on every project. They’re also expensive, cumulative, and \u2014 in many cases \u2014 preventable. Understanding what triggers them is the first step toward controlling them.<\/p>\n
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 \u2014 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.<\/p>\n
A typical RFI response takes three to seven business days. A complex one involving multiple consultants can run two to three weeks.<\/p>\n
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 \u2014 which may or may not match what the design team intended. Work built under a wrong assumption often becomes rework.<\/p>\n
RFIs come from gaps in the construction documents. The most common triggers fall into four categories:<\/p>\n
Design conflicts.<\/strong> Two documents \u2014 or two sheets within the same set \u2014 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 Plan de revisi\u00f3n de construcci\u00f3n con IA<\/a> is specifically designed to surface before construction starts.<\/p>\n Missing information.<\/strong> 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.<\/p>\n Changed field conditions.<\/strong> Existing conditions don’t match what the drawings assumed \u2014 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.<\/p>\n Ambiguous specifications.<\/strong> 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.<\/p>\n The first two categories \u2014 design conflicts and missing information \u2014 are overwhelmingly the most common, and they’re the ones that a thorough preconstruction document review can eliminate before the first shovel turns.<\/p>\n These three documents are often confused because they interact, but they serve distinct functions.<\/p>\n An RFI<\/strong> asks a question. It doesn’t authorize work, change the contract, or transfer any cost. It just gets an answer into the record.<\/p>\n A change order<\/strong> modifies the contract \u2014 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 \u2192 RFI submitted \u2192 response requires a scope change \u2192 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.<\/p>\n A submittal<\/strong> flows the other direction \u2014 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.<\/p>\n The direct cost of an RFI is the time to process it \u2014 prepare, log, route, respond, and close. That overhead runs real money across a project’s full RFI log.<\/p>\n 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.<\/p>\n Industry experience \u2014 and Flikt’s own project data \u2014 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<\/a> carried $28,000\u2013$45,000 in rework plus 14\u201321 days of schedule impact each. The corresponding RFI process \u2014 submitting the question, waiting for a structural and mechanical response, getting an amended detail \u2014 would have added days to that window even before a single worker picked up a tool.<\/p>\n For the full breakdown of where the money goes, see what an RFI costs in construction<\/a> \u2014 that post covers direct cost, indirect cost, and how to quantify RFI exposure on a specific project.<\/p>\n 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.<\/p>\n Flikt uses conflictos por cada 100 hojas<\/strong> as a normalized drawing-quality benchmark \u2014 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 conflictos por cada 100 hojas<\/a>.<\/p>\n 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 \u2014 before the subcontracts are signed.<\/p>\n 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.<\/p>\n Plan de revisi\u00f3n de construcci\u00f3n con IA<\/a> 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 \u2014 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<\/a>.<\/p>\n The tactical how-to \u2014 how to structure a review workflow that systematically closes the gap between the plan set and what’s buildable \u2014 is in c\u00f3mo reducir las Solicitudes de Informaci\u00f3n (RFIs) antes del inicio de la construcci\u00f3n<\/a>.<\/p>\n For teams that want a fuller framework, the pre-construction QA checklist<\/a> covers the full scope of document review tasks, including but not limited to RFI prevention.<\/p>\n Every RFI that gets submitted is a gap that existed in the construction documents before the project broke ground. The questions were always there \u2014 someone just discovered them at the worst possible time.<\/p>\n 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 \u2014 not discipline by discipline, and not assuming that because the architect and engineer each reviewed their own scope, the coordination between them is clean.<\/p>\n That’s the work preconstruction document review does. The RFI log is the measurement of how much of that work didn’t happen.<\/p>\n Flikt reviews 2D construction documents for cross-discipline conflicts before construction starts \u2014 no BIM required. See how AI plan review works<\/a>, or talk to us about your next project on the contact page<\/a>.<\/em><\/p>\n Sube tu conjunto de planos y obt\u00e9n detecci\u00f3n de conflictos con IA, no se requiere BIM.<\/p>\n Comenzar<\/a> An RFI \u2014 Request for Information \u2014 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 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-508","post","type-post","status-publish","format-standard","hentry","category-blogging"],"yoast_head":"\nRFI vs. change order vs. submittal<\/h2>\n
What an RFI costs<\/h2>\n
The connection to drawing quality<\/h2>\n
How to reduce RFIs before construction starts<\/h2>\n
The upstream fix<\/h2>\n
\n\u00bfListo para detectar conflictos a tiempo?<\/h3>\n
\n\ud83d\udcc5 Reservar una demostraci\u00f3n<\/a>\n<\/div>","protected":false},"excerpt":{"rendered":"