{"id":494,"date":"2026-06-05T13:47:19","date_gmt":"2026-06-05T18:47:19","guid":{"rendered":"https:\/\/flikt.ai\/?p=494"},"modified":"2026-09-13T13:38:33","modified_gmt":"2026-09-13T18:38:33","slug":"cuanto-cuesta-una-rfi","status":"publish","type":"post","link":"https:\/\/flikt.ai\/es\/what-does-an-rfi-cost\/","title":{"rendered":"\u00bfCu\u00e1nto cuesta realmente una RFI? Un punto de referencia para 2026"},"content":{"rendered":"

The short answer<\/h2>\n

A single request for information (RFI) is widely costed at roughly $1,080 to review and respond to<\/strong> \u2014 counting only the labor to process the question and route the answer.\u00b9 That figure is an estimate the study’s authors built from interviews with three firms, not a measurement; they noted it may vary widely (full trace<\/a>).<\/p>\n

That number is almost beside the point. The processing cost is the tip of the iceberg. The RFI itself is usually a symptom of a documentation gap<\/em> \u2014 a conflict, omission, or ambiguity in the drawings or specs \u2014 and the gap is what generates the expensive consequences downstream: rework, change orders, and schedule delay.<\/p>\n

On a typical commercial project, the documentation-error bill runs into the low single-digit millions of dollars, and the majority of it is preventable<\/a> before construction starts.<\/strong><\/p>\n

Here’s how that math works, with every number sourced.<\/p>\n

How many RFIs is “normal”?<\/h2>\n

The most-cited industry benchmark comes from the Navigant Construction Forum’s 2013 study of more than 1,300 projects: about 9.9 RFIs per $1 million of construction value<\/strong> on a typical project.\u00b9<\/p>\n

That scales fast:<\/p>\n

\n\n\n\n\n\n\n\n\n
Project value<\/th>\nExpected RFIs (\u22489.9 \/ $M)<\/th>\nProcessing cost (\u2248$1,080 \/ RFI)<\/th>\n<\/tr>\n<\/thead>\n
$5M<\/td>\n~50<\/td>\n~$54,000<\/td>\n<\/tr>\n
$25M<\/td>\n~250<\/td>\n~$270,000<\/td>\n<\/tr>\n
$50M<\/td>\n~500<\/td>\n~$535,000<\/td>\n<\/tr>\n
$100M<\/td>\n~1,000<\/td>\n~$1,070,000<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

So before a single change order is written, a $50M commercial project can expect to spend roughly half a million dollars just processing<\/em> RFIs<\/strong> \u2014 the back-and-forth of writing the question, researching the answer, and documenting the response.\u00b9<\/p>\n

Two things move that number:<\/p>\n

    \n
  • Documentation quality.<\/strong> The single biggest lever. A clean, well-coordinated drawing set generates far fewer RFIs than one full of conflicts and gaps.<\/li>\n
  • Project complexity.<\/strong> Healthcare, labs, and heavily-serviced buildings run hotter because they pack more disciplines into the same space.<\/li>\n<\/ul>\n

    The cost most people miss: open RFIs eat your schedule<\/h2>\n

    The average RFI stays open for about 9.7 days<\/strong> waiting on a response.\u00b9 Most of those don’t matter \u2014 but the ones sitting on the critical path<\/strong> stall the trades behind them. A handful of critical RFIs can quietly add weeks<\/strong> of cumulative slip to a job, and schedule delay is its own line-item cost (extended general conditions, escalation, liquidated damages).<\/p>\n

    This is the cost that never shows up cleanly on an invoice, which is exactly why it’s underestimated.<\/p>\n

    Change orders: the 5\u201310% you budgeted (and shouldn’t have to)<\/h2>\n

    Most owners carry a contingency for change orders because they expect them. Industry baselines put change orders at roughly 5\u201310% of contract value<\/strong> on commercial work.\u00b2<\/p>\n

    On a $50M project, that’s $2.5M\u2013$5M<\/strong> \u2014 money the owner has effectively pre-committed to fixing problems found during construction<\/em>. A meaningful share of those changes trace back to the same root cause as the RFIs: information that conflicted, was missing, or was wrong in the documents.<\/p>\n

    Rework: where bad data becomes a hard cost<\/h2>\n

    Rework \u2014 tearing out and redoing work that was already built \u2014 runs about 4\u20136% of total project value<\/strong> on average.\u00b3 And in a landmark FMI \/ Autodesk study, roughly 14% of all rework was attributed directly to bad data<\/strong> \u2014 wrong, missing, or conflicting information.\u2074<\/p>\n

    For scale, a 2004 U.S. government study (NIST\/NIBS) estimated that inadequate interoperability \u2014 the cost of information not lining up across the parties and systems building a facility \u2014 costs the U.S. capital-facilities industry about $15.8 billion a year.<\/strong>\u2075<\/p>\n

    Putting it together: the documentation-error bill<\/h2>\n

    Stack the layers for a representative $50M commercial new-build:<\/p>\n

    \n\n\n\n\n\n\n\n\n
    Cost layer<\/th>\nEstimate<\/th>\nSource basis<\/th>\n<\/tr>\n<\/thead>\n
    RFI processing labor<\/td>\n~$535K<\/td>\n9.9 RFIs\/$M \u00d7 $1,080\/RFI \u00b9<\/td>\n<\/tr>\n
    Schedule slip (critical-path RFIs)<\/td>\nweeks of delay<\/td>\n9.7-day avg open duration \u00b9<\/td>\n<\/tr>\n
    Change orders<\/td>\n$2.5M\u2013$5M<\/td>\n5\u201310% of contract \u00b2<\/td>\n<\/tr>\n
    Rework<\/td>\n$2M\u2013$3M<\/td>\n4\u20136% of project value \u00b3<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

    Not all of these are independent (a change order often pays for<\/em> the rework), so you don’t simply add every row. But the order of magnitude is unambiguous: the documentation-error cost of a mid-size commercial project is measured in millions, not thousands<\/strong> \u2014 and a large portion of it traces back to a single, addressable cause.<\/p>\n

    The root cause: drawing and spec conflicts<\/h2>\n

    When you sort RFIs and change orders by what triggered them, the largest single category is the same one every time: coordination conflicts and gaps across the drawing set<\/strong> \u2014 a duct routed through a beam, a fixture with no power shown, a dimension that disagrees between two sheets, a detail referenced but never drawn.<\/p>\n

    The reason these slip through is structural, not careless: every individual sheet can be correct while the set<\/em> is wrong.<\/strong> The architect’s plan is right. The structural plan is right. The mechanical plan is right. The conflict only exists between<\/em> them \u2014 and no single discipline owns the space where two trades overlap. Traditional plan review is done discipline-by-discipline, so the cross-discipline conflicts are exactly the ones that survive to the field.<\/p>\n

    That’s the gap that turns into an RFI, then a change order, then rework.<\/p>\n

    What you can actually do about it<\/h2>\n

    The cheapest RFI is the one you never have to write, because the conflict was caught and resolved on paper. Three moves that move the needle:<\/p>\n

      \n
    1. Treat preconstruction QA as a cross-discipline activity, not a per-discipline one.<\/strong> The conflicts live between<\/em> the drawings, so the review has to look between them.<\/li>\n
    2. Benchmark your RFI burn-rate.<\/strong> If you’re running well above ~10 RFIs per $1M, the documents \u2014 not the field \u2014 are usually the problem.<\/li>\n
    3. Catch conflicts before the set is issued.<\/strong> Every conflict resolved in design is an RFI, a change order, and a rework cycle that never happens.<\/li>\n<\/ol>\n

      Where Flikt.AI fits<\/h2>\n

      This is the problem Flikt.AI<\/a> was built to solve. Flikt.AI is AI-powered plan review<\/a> that cross-references complete 2D PDF plan sets across 16 disciplines \u2014 architectural, structural, mechanical, electrical, plumbing, fire protection, fire alarm, low-voltage, telecom, civil, landscape, interior design, food service, signage, zoning, and specifications \u2014 to flag the coordination conflicts that become RFIs and change orders, before construction begins.<\/strong> No BIM model required.<\/p>\n

      On a South Florida commercial retail project, every conflict Flikt.AI flagged was confirmed real by the general contractor \u2014 zero false positives \u2014 representing six figures of avoided exposure. On a residential project, it caught an HVAC-vs-structure clash that the field team missed; resolving it after the fact cost $10,000+ and two weeks of schedule<\/a>.<\/p>\n

      If the math above looks like your projects, that’s the cost Flikt.AI is designed to take off the table.<\/p>\n

      FAQ<\/h2>\n

      How much does one RFI cost?<\/h3>\n

      About $1,080<\/strong> to review and respond to, counting processing labor (Navigant Construction Forum, 2013).\u00b9 That figure is an estimate the authors built from interviews with three firms, not a measurement, and they noted it may vary widely. The larger cost is usually the rework, change order, or schedule delay the RFI signals.<\/p>\n

      How many RFIs should a project expect?<\/h3>\n

      Roughly 9.9 RFIs per $1 million<\/strong> of construction value on a typical project \u2014 so ~500 on a $50M job (Navigant, 2013).\u00b9 Cleaner documentation lowers it; complex, heavily-serviced buildings raise it.<\/p>\n

      What percentage of a contract goes to change orders?<\/h3>\n

      Industry baselines put change orders at about 5\u201310% of contract value<\/strong> on commercial work (CII \/ Dodge SmartMarket).\u00b2<\/p>\n

      How much does rework cost on a construction project?<\/h3>\n

      About 4\u20136% of total project value<\/strong> on average, with roughly 14% of that rework caused by bad data<\/strong> \u2014 wrong, missing, or conflicting information (Dodge, 2018; FMI\/Autodesk, 2020).\u00b3,\u2074<\/p>\n

      What causes the most RFIs?<\/h3>\n

      Coordination conflicts and gaps across the drawing set \u2014 information that disagrees or is missing between disciplines. Every sheet can be individually correct while the combined set still conflicts.<\/p>\n

      Can you prevent RFIs?<\/h3>\n

      Not all of them, but a large share are preventable by catching drawing\/spec conflicts before the set is issued \u2014 which is the purpose of cross-discipline preconstruction plan review.<\/p>\n

      Sources<\/h2>\n
        \n
      1. Navigant Construction Forum, Impact and Control of RFIs on Construction Projects<\/em><\/a>, 2013 \u2014 RFI rate (9.9\/$M), average cost per RFI ($1,080), average open duration (9.7 days).<\/li>\n
      2. Construction Industry Institute, RT-265, Change Management<\/em>, 2011; Dodge Data & Analytics, SmartMarket Report \u2014 change-order rate baseline (5\u201310% of contract).<\/li>\n
      3. Dodge Data & Analytics, SmartMarket Report on Project Rework<\/em>, 2018 \u2014 rework cost as % of project value (4\u20136%).<\/li>\n
      4. FMI & Autodesk, Harnessing the Data Advantage in Construction<\/em><\/a>, 2020 \u2014 share of rework attributable to bad data (~14%).<\/li>\n
      5. NIST GCR 04-867 (NIBS), Cost Analysis of Inadequate Interoperability in the U.S. Capital Facilities Industry<\/em><\/a>, 2004 \u2014 macro interoperability loss ($15.8B\/yr).<\/li>\n<\/ol>\n

        Figures are drawn from publicly summarized study findings and are presented as benchmarks and order-of-magnitude ranges, not project-specific estimates. They are not suitable for litigation, damages, or contract negotiation.<\/em><\/p>\n

        Those are averages from other people’s projects. The number that matters is your own — and if you have a finished job with its RFI log, you can run the review against the set your team bid<\/a> and see how much of that log was answerable from the drawings.<\/p>\n