Canadian institutional construction is accelerating. The Dodge Momentum Index recorded a 4.9% rise in institutional planning in August 2026. Projects like the NAIT Advanced Skills Centre signal what is coming down the pipeline: large, complex, technically demanding builds where the spec sets run to thousands of pages and the MEP scope is anything but simple.
For GCs bidding institutional work, that complexity is a risk multiplier. HVAC and electrical scope gaps that might cost $20,000 on a commercial fit-out can reach six or seven figures on a hospital or post-secondary campus build. And they are almost never random. They are caused by the same habits, in the same places, on nearly every project.
This article breaks down where those gaps hide and what a disciplined pre-construction team does to catch them before they become change orders.
Institutional projects are not just bigger versions of commercial work. They carry a different kind of specification complexity that magnifies scope risk at every stage.
On a standard commercial project, HVAC scope is mostly in Division 23. Electrical is mostly in Division 26. But on an institutional project, that scope bleeds across divisions. Fire alarm interfaces live in Division 28. Building automation and controls span 23 and 25. Lighting controls touch 26 and 25. No single trade owns the full picture.
When an estimator reviews those divisions in isolation, the gaps appear in the white space between them. The spec says the mechanical contractor provides the BAS points. It does not say who wires them. That question costs money if it is not answered before bid day.
Institutional projects routinely issue multiple addenda. Each one may modify a single clause in one spec section. If your team is managing addenda manually, the chance that a modification to Section 23 81 19 gets cross-referenced against the electrical drawings and the control sequences is low. The chance it gets missed is high.
As one Estimating Manager at a Canadian ICI GC put it: "If you miss anything, they'll bill it." On institutional work, that is not a hypothetical. It is a weekly occurrence on poorly scoped projects.
Hospitals and post-secondary institutions often specify owner-furnished, contractor-installed equipment. The spec names the equipment. It does not always name who provides the conduit, the disconnect, the final connection, or the commissioning. Each of those items is a potential gap. Each one can be claimed by the mechanical or electrical sub as excluded if it is not in the scope package.
Provision's pre-construction research and the operator interviews behind the Scope Gap Playbook's trade-specific chapter point to the same recurring gaps on institutional mechanical scope.
Emergency generators on institutional projects require field conditioning before they can be commissioned. This work includes load bank testing, temperature controls, and sometimes extended run cycles. It is frequently missing from both the mechanical and electrical scope sheets. Each sub assumes the other is carrying it. Neither is.
The Scope Gap Playbook flags generator field conditioning as one of the most recurring MEP anti-patterns in ICI construction. When it surfaces post-award, it surfaces as a change order.
The mechanical spec calls for a fan or pump with a variable frequency drive. The electrical spec covers the panel. Who supplies the VFD? Who installs it? Who provides the interconnecting wiring between the drive and the BAS? These questions seem simple. On institutional projects with dozens of VFDs, an unresolved split can represent significant cost.
Institutional buildings have strict fire separations. HVAC penetrations through rated assemblies require fire dampers, interlocks, and in some cases, rated duct wrap. The spec may call this out in Division 07 (Thermal and Moisture Protection) rather than Division 23. If the mechanical estimator is not reading Division 07, the fire damper scope lands in a gap.
Building automation scope is one of the most reliably misscoped items on institutional projects. The mechanical spec covers the control devices. The electrical spec covers power. The BAS spec (Division 25) covers the network. But the low-voltage control wiring between those three systems is often described in none of them clearly enough to avoid a dispute at buyout.
Institutional projects commonly specify daylight harvesting, occupancy-based dimming, and scheduled switching. The electrical drawings show fixtures. The spec shows controls. But the wiring between the lighting control panels, the occupancy sensors, and the dimming drivers is frequently not drawn. It is described in a spec section that the electrical estimator may not cross-reference against the fixture schedule.
Post-secondary and healthcare projects carry significant IT and AV infrastructure. The electrical sub is typically responsible for conduit, back boxes, and rough-in. The AV contractor handles the systems. When the scope sheets do not define the exact rough-in responsibility, both subs price it, or neither does. The gap becomes visible during buyout.
Institutional projects require life-safety branch, critical branch, and equipment branch circuits. The transfer switch scope, the ATS wiring, and the tie-ins to the generator are described in multiple spec sections. When the electrical scope sheet just says "emergency power system," the sub will price the minimum. The gap will be visible in the first progress claim.
Many institutional owners now require witnessed commissioning for electrical systems: switchgear testing, UPS verification, and emergency system load tests. These requirements often appear in a commissioning spec (Division 01 40 00) rather than in Division 26. If the electrical scope sheet does not explicitly include commissioning obligations, the sub will exclude them.
The gap between what the spec requires and what the scope package captures is almost never an accident. It follows from a small set of habits that experienced pre-construction teams have already identified.
The most common anti-pattern in institutional MEP review is reading each spec division in a silo. An estimator reviews Division 23 and writes the mechanical scope. A different estimator reviews Division 26 and writes the electrical scope. Nobody reads them against each other, against the drawings, or against Division 25. The white space stays white.
The Scope Gap Playbook's Eight Habits frame this clearly: Habit 1 is drawings-first, not boilerplate-first. The same principle applies to spec review. Start with what the drawings actually show. Then reconcile the spec against the drawings. Then reconcile the divisions against each other.
Boilerplate scope sheets are a floor, not a ceiling. That is Habit 4. On a standard commercial project, a boilerplate HVAC scope may cover 80% of what the spec requires. On an institutional project with a chilled water plant, a BAS integration requirement, and owner-furnished AHUs, that same boilerplate covers far less. The gaps are project-specific. The scope sheet needs to be too.
Addenda on institutional projects do not arrive as a package. They arrive one at a time, targeting specific sections. When the team is managing addenda manually, the cascade is easy to lose. A revised control sequence in Addendum 3 may change what the electrical sub is responsible for in a way that is not reflected in the scope package issued to that sub.
This is not a process failure. It is a document volume problem. Institutional projects may issue five, six, or eight addenda before close. Manual reconciliation across thousands of spec pages is where gaps get embedded.
The following steps reflect what high-performing pre-construction teams at ICI GCs do consistently. They match the Eight Habits framework from the Scope Gap Playbook.
Start with the mechanical and electrical drawings. Identify every system. Then find the spec section that governs each system. Cross-reference them explicitly. If the drawing shows a chilled water plant and the spec describes it in both Division 23 and Division 25, both sections need to be in the scope review before you write a single line of scope.
Create a simple map of which divisions govern which systems on this specific project. Mark every boundary where two divisions share responsibility. Those boundaries are where scope gaps live. They deserve a dedicated review step, not an assumption that the sub will figure it out.
When an addendum arrives, the first question is: does this change any item already in the scope package? If the answer is yes, the scope package needs to be updated before it goes to subs. This sounds obvious. It is frequently skipped under bid-day time pressure.
A scope package that says "as per plans and specs" is the most-cited anti-pattern in GC pre-construction. The Scope Gap Playbook quotes one Pre-Construction Lead at a Top-ENR Canadian GC on this directly: getting to the right level of detail means being as specific as a recipe. If the scope does not name the responsibility, the sub will not carry it.
Trade-specific scope packages for institutional HVAC and electrical work should name: the BAS scope split, the VFD responsibility, the commissioning obligation, and the fire damper scope. Every item that could reasonably be claimed as excluded needs to be explicitly included or explicitly excluded.
Habit 8 in the Scope Gap Playbook is the pre-issue scope review checkpoint. Before the scope package goes to subs, one more person reads it against the drawings and the most recent addendum. This is not a full re-review. It is a targeted check for items that changed in the last addendum cycle. On institutional projects, this step catches a material number of gaps.
The process above works. It also takes significant time on a document set that may run to 3,000 pages across a dozen addenda. That is where purpose-built tools change the math.
Provision's Scope Agent reviews the full document set together: drawings, specifications, and addenda, not one file at a time. It generates trade-specific scope packages with every item source-traced to the exact page and section. When an addendum arrives, it handles the update automatically without requiring the team to restart the review. Scope Agent achieves 97.01% match accuracy on scope item extraction on Provision's internal validation dataset, compared to a human estimator baseline of 91.3% on the same exercise.
For institutional MEP scope, the ability to read Division 23, 25, 26, and 28 against each other, and against the drawings, in a single pass is the difference between catching the BAS wiring gap before bid day and absorbing it as a change order after award.
Provision's RFI Agent addresses a related problem: it reads drawings and specifications against each other and surfaces conflicts, omissions, and unclear requirements. On a hospital project, it can identify more than 100 potential issues from the document set in an hour. Each finding is tied to the exact specification page or drawing. The pre-construction team reviews the findings and decides what becomes an RFI, a bid qualification, or a scope clarification.
EllisDon has used Provision to save over 200 hours per month on document queries across their project portfolio. See the EllisDon case study for more detail on how that workflow operates.
For teams running institutional pursuits and managing document sets at this scale, the trade-specific chapter of the Scope Gap Playbook is worth reading alongside the process above. It covers the most common gaps by trade in detail, with operator-sourced examples and dollar values that reflect what these gaps actually cost.
Scope gaps on institutional projects do not resolve cheaply. The average North American construction dispute reached $60.1 million in 2024, according to the Arcadis Global Construction Disputes Report. Errors and omissions in contract documents consistently rank as a leading dispute cause in North America.
The Scope Gap Playbook documents a $300,000 lead-lined glass gap on a hospital imaging suite that the GC absorbed under "readily inferable" contract language. It documents a $400,000 missed roof cover board on a $50 million project. These are not edge cases. They are the predictable outcome of reviewing complex spec sets with a process built for simpler projects.
Institutional construction is growing. The pipeline is real. The teams that win and deliver these projects profitably are the ones that have already solved the MEP scope review problem before they walk into the bid.
If your pre-construction team is managing institutional HVAC and electrical scope review manually, see what Scope Agent does in under 60 minutes on a real project document set. You can also explore the full Scope Gap Playbook for the research behind the patterns described in this article.
Institutional projects split MEP scope across Divisions 23, 25, 26, and 28. No single trade owns the full picture. Addenda arrive frequently and modify individual sections. When teams review divisions in isolation, the gaps form in the white space between them, and those gaps become change orders after award.
Generator field conditioning, motor starter and VFD responsibility splits, BAS control wiring, and fire damper scope in fire-rated penetrations are the most recurring gaps. They appear consistently because they sit at the boundary between two or more spec divisions and are not clearly owned by any single trade in the scope package.
Lighting control wiring, IT and AV rough-in responsibility, emergency power system scope splits, and commissioning and witness testing requirements. Commissioning obligations often appear in Division 01 rather than Division 26, so electrical estimators miss them if they are not reading the full spec set.
Institutional projects routinely issue multiple addenda, each targeting a specific spec section. When teams manage addenda manually, a modification to one section may not be reconciled against related sections or the scope package already issued to subs. The gap embeds at the addendum boundary and surfaces after award.
"As per plans and specs" is the most-cited scope writing anti-pattern among GC pre-construction teams. It transfers all interpretation risk to the sub, who will then price the minimum they can defensibly claim is included. On institutional projects, this language routinely produces disputed change orders on MEP items that were never explicitly scoped.
Provision's Scope Agent reviews the full document set together, including drawings, specifications, and addenda across all relevant divisions. It generates trade-specific scope packages with every item source-traced to the exact page and section. It handles addenda automatically without requiring the team to restart the review. Scope Agent achieves 97.01% match accuracy on scope item extraction on Provision's internal validation dataset.
Costs vary by project, but documented examples include a $300,000 lead-lined glass gap on a hospital imaging suite and recurring six-figure gaps on generator field conditioning. The 2024 Arcadis Global Construction Disputes Report puts the average North American construction dispute at $60.1 million, with errors and omissions in contract documents as a leading cause.
Scope Agent reviews your full institutional spec set and generates trade-specific packages in under 60 minutes.
See Scope AgentMore Articles
