Fire protection isn't a single trade. It's a coordination problem. The sprinkler contractor touches MEP rough-in, the envelope subcontractor owns louvre penetrations, the mechanical sub handles unit connections — and the GC holds all the risk in between.
When specs are vague or drawings conflict, the GC absorbs the cost. A 2018 PlanGrid and FMI study found that miscommunication and bad project data drove $31.3 billion in U.S. rework. Fire protection coordination failures contribute directly to that number. And according to Arcadis's 2024 Global Construction Disputes Report, the average North American construction dispute reached $60.1 million — with errors and omissions in contract documents ranking among the top causes.
In 2026, healthcare and institutional work is making this worse. Sprinkler design requirements, fire-rated penetration details, and drain testing protocols are growing more complex with each code cycle. If your scope sheets haven't kept up, your subs' exclusions already have.
As one Pre-Construction Lead at a Top-ENR Canadian GC put it: "If you miss anything, they'll bill it."
This post walks through the three fire protection scope gaps that show up most consistently in GC bids — and what to put in your scope sheet to stop absorbing them.
Sprinkler rough-in sits at the intersection of three trades: mechanical, electrical, and fire protection. The fire protection sub scopes the heads and mains. The mechanical sub scopes the equipment connections. The electrical sub scopes the control wiring. Nobody scopes the interface.
The most common omissions in sprinkler rough-in scope packages include:
The most-cited anti-pattern in the Scope Gap Playbook's trade-specific chapter is writing "as per plans and specs" and calling it a scope. For sprinkler work on an institutional project, that phrase is a liability.
Fire protection drawings are often issued by the sprinkler contractor as a deferred submittal — after bid. The sub who priced the job based on architectural and mechanical plans may not have seen the actual sprinkler design. When those drawings arrive, the gaps become change orders.
Write the scope to define what's included at bid, not what might be on future drawings.
A complete sprinkler rough-in scope sheet should answer these questions explicitly:
Each of those six items has been a change order on a real project. None of them is ambiguous on a well-written scope sheet.
Fire-rated louvres sit at the boundary between two scopes: the envelope (or framing) sub and the mechanical sub. Neither wants to own the fire-rated version. The standard louvre is in the mechanical scope. The fire-rated louvre is in the spec. Which sub read the spec?
This gap appears repeatedly on healthcare projects, data centers, and institutional buildings — anywhere that HVAC penetrations pass through fire-rated walls or floors. It also appears in stairwells, equipment rooms, and any smoke-compartment boundary.
The $300K lead-lined glass gap documented in the Scope Gap Playbook follows the same pattern: a specialty material required by the spec, buried in a single callout, missed by every sub who bid the enclosing trade. Fire-rated louvres work the same way. The spec says it. Nobody included it.
Three things typically go wrong simultaneously:
One Estimating Manager at a Canadian ICI GC described the shift happening across the industry: "We have fewer subs who just kind of operate on a gentleman's agreement… they've become more quick to clarify that they're not including that one piece of scope."
Fire-rated louvres are exactly the kind of item subs now exclude by default. If your scope sheet doesn't address it explicitly, assume it's out.
For every project with mechanical penetrations through fire-rated assemblies, your fire protection scope package needs to answer:
On healthcare and institutional projects in 2026, add this to your scope review checklist before you release bid packages. The specs are getting more specific. Your scope sheets need to match them.
Tools like Risk Review can flag spec cross-references across divisions — the kind that link a Division 23 mechanical scope to a Division 08 louvre requirement — before you hand the bid package to subs. With an 80% reduction in spec review time, you can catch these cross-division callouts on every pursuit, not just the ones where you have a week to spare.
Drain testing on fire protection systems is required by NFPA 13, and it generates real cost: system shutdown time, water management, coordination with the authority having jurisdiction (AHJ), and documentation. Most sprinkler subs include the test itself. Fewer include everything around it.
The items that regularly fall out of scope:
Healthcare and institutional projects increasingly involve phased occupancy. A hospital wing opens while the rest of the building is still under construction. That means the fire protection system needs to be tested, signed off, and operational — floor by floor, zone by zone — months before substantial completion.
Every additional drain test is a mobilization cost. If the scope sheet doesn't specify that re-tests and phased-occupancy testing are included, the sub will price that as an extra. And they'll be right to.
This is the same dynamic that drives generator field-conditioning disputes — a recurring cost that appears "in the field" precisely because the scope sheet never addressed it. The Scope Gap Playbook's trade-specific chapter documents this pattern across MEP scopes: the cost isn't random, it's predictable. And it's preventable if your scope sheet addresses it before bid.
Add these items to every fire protection scope sheet on healthcare, institutional, or phased-occupancy projects:
Fire protection requirements don't live in one place. NFPA 13 drives the sprinkler design. Division 07 governs fire-stopping. Division 08 covers rated assemblies and louvres. Division 13 or 21 holds the suppression system spec. Division 28 handles fire alarm and detection. And the supplementary conditions of the contract may add requirements on top of all of them.
A sub bidding Division 21 reads Division 21. They don't cross-check Division 08 for louvre requirements or Division 07 for fire-stopping at penetrations. That's the GC's job at scope review — and it only happens if the GC's scope sheet forces the coordination.
A Director of Pre-Construction at a Mid-Market Southeast GC described a version of this problem that exists in almost every firm: "Pre-con is working in the scope sheet world and project management is working in the scopes of work." The gap between those two is where fire protection scope gaps live.
The fix isn't a longer exclusion list. It's a scope sheet that explicitly assigns responsibility for every cross-division item. For fire protection, that means:
That's Habit 2 from the Scope Gap Playbook: specific document references, not generic incorporation. "Per plans and specs" doesn't assign responsibility. A section number does.
Reading across Division 07, 08, 13, 21, and 28 — plus the structural and architectural drawings — is exactly the kind of multi-document coordination task that takes hours manually and still produces misses.
Scope Agent generates complete scope-of-work packages from the full project set — drawings, specs, contracts, and addenda — in under 60 minutes. It replaces 30 to 40 hours of manual work per bid, with 97% accuracy on scope item extraction. On a fire protection scope package, that means catching the cross-division louvre callout, flagging the deferred sprinkler submittal, and surfacing the drain testing requirements from the NFPA 13 spec — before the bid package goes out.
Provision has processed over 100,000 construction documents and reviewed more than $100 billion in project value. The patterns that produce fire protection scope gaps show up consistently across project types. EllisDon used Provision to catch scope gaps that saved $1.8M — the same category of gap that healthcare and institutional GCs are absorbing in 2026.
For specific spec cross-references during bid review, Chat Agent answers questions about your project documents in under 20 seconds — cited to the exact section, drawing, or page. Ask it which spec section governs fire-rated louvres. Ask it what NFPA 13 testing is required before phased occupancy. You get an answer tied to your actual project documents, not a generic code summary.
Use this before releasing bid packages on any healthcare, institutional, or complex commercial project.
The $300K lead-lined glass gap documented in the Scope Gap Playbook was absorbed by the GC under "readily inferable" language. The same dynamic applies to fire-rated louvres on a hospital project. The spec requires it. The sub didn't include it. The GC held the contract risk.
That's not a one-off. It's a pattern. And according to Arcadis, North American construction disputes now average $60.1 million. Fire protection scope gaps don't start at that number — but they compound. A $40K louvre gap, a $25K drain testing dispute, and a $60K sprinkler rough-in change order on a single project adds up to a real margin hit before the project is half done.
The firms with the best margins do the same things consistently. They write scope sheets that assign responsibility at the trade-division level. They read specs across divisions before bid day. They call out the fire-rating requirement on every louvre and the testing protocol on every riser. That's not extra work. That's what the scope sheet is for.
For a full breakdown of trade-specific scope gaps — including MEP, envelope, and specialty trades — see the trade-specific chapter of the Scope Gap Playbook. It's built from 200+ interviews with GC pre-construction professionals and documents the exact patterns that produce change orders on real projects.
The three that appear most consistently are: sprinkler rough-in interfaces (sleeves, core drilling, escutcheons), fire-rated louvres omitted from both mechanical and envelope bids, and drain testing inclusions that stop at the test itself and exclude water management, re-testing, and AHJ coordination. Each one is preventable with a well-written scope sheet.
It depends on the project and how the spec is written. Fire-rated louvres often appear in Division 08 but are assumed by mechanical subs to be in Division 23 — or vice versa. The GC must assign responsibility explicitly in the scope sheet before bid. Neither sub will assume it voluntarily.
Forward flow testing, water disposal during testing, re-testing after failed inspections, phased-occupancy testing mobilizations, and AHJ witnessing coordination are all regularly excluded. The test itself is usually included. Everything around it often isn't. Specify each item individually in the scope sheet.
Healthcare projects have stricter fire protection requirements — rated assemblies at more boundaries, smoke compartmentalization, NFPA 13 compliance with AHJ oversight, and phased occupancy that requires zone-by-zone testing. Each layer adds spec complexity. In 2026, those specs are more detailed than they were five years ago, and standard scope sheets haven't kept up.
"As per plans and specs" doesn't assign responsibility for interface items — it defers it. On fire protection bids, that means nobody explicitly owns sleeves through rated assemblies, fire-stopping at penetrations, or fire-rated louvres that span two trade divisions. Those gaps become change orders at buyout or in the field.
Yes, when the tool reads the full project set. Provision's Scope Agent ingests drawings, specs, and contracts together — so it can flag a Division 08 louvre requirement that a Division 21 scope sheet missed. Risk Review surfaces cross-division spec references and citations with 99% accuracy on pre-built checklists. Generic AI tools without construction-specific training won't catch these cross-division gaps consistently.
Reference the governing spec section for each scope item. Assign furnish versus install for every cross-trade item. Call out testing inclusions by type — main drain, forward flow, phased-occupancy — and specify water management responsibility. Don't use "as per drawings" for any item that spans two trade divisions. A scope sheet that assigns responsibility is a scope sheet that prevents disputes.
Scope Agent reads your full project set and builds trade-level scope packages in under 60 minutes.
See Scope Agent workMore Articles