MEP scope gaps are not a mechanical problem. They are a coordination problem. The architect draws a detail. The mechanical engineer specifies a system. The electrical engineer notes a requirement. Nobody reconciles all three against the same scope baseline before bid day.
That is how a hospital imaging suite ends up with $300K in lead-lined glass missing from the GC's scope. The specification called it out. The drawings showed the room layout. No one read both documents together and wrote the requirement into the scope package before it went to subs.
This happens on almost every complex MEP project. The question is whether your team catches it before bid day or absorbs it in the field.
MEP is the trade cluster where drawing-to-spec conflicts are most common and most expensive. Here is why.
First, MEP work spans three disciplines (mechanical, electrical, plumbing) plus controls, fire protection, and sometimes a fourth in building automation. Each discipline has its own engineer, its own drawing set, and its own specification sections. Conflicts between them are almost guaranteed on anything above a simple renovation.
Second, MEP specification sections are where the "readily inferable" trap is deepest. Spec writers include system performance requirements, equipment standards, and testing protocols that do not appear anywhere on the drawings. Subs read the drawings. They often skim the specs. That gap is where six-figure change orders are born.
Third, MEP scopes are highly sensitive to addenda. A generator spec change in Addendum 3 that overrides the original equipment schedule is easy to miss when your team is cross-referencing 2,000 pages of bid documents in the final 72 hours before bid day.
These are the specific items that appear most often in the GC interviews and project reviews that form the basis of Provision's Scope Gap Playbook chapter on trade-specific gaps. Each one is recoverable if caught before the scope sheet goes out. Each one is expensive if it surfaces during buyout or in the field.
This is the most frequently cited MEP gap in operator interviews. Generator specifications often include field conditioning requirements: load bank testing, runtime hours, and startup commissioning by a factory-certified technician. These items do not appear on the electrical drawings. They are buried in Division 26 or Division 33 spec sections.
When the scope goes to the electrical sub without those requirements, the sub prices the equipment and rough-in. The field conditioning cost sits unpriced. One estimating manager at a Canadian ICI GC described recurring disputes totaling "millions" across multiple hospital and institutional projects where generator conditioning was not clearly assigned.
The mechanical drawings show equipment. The electrical drawings show power connections. Neither consistently shows who supplies and installs motor starters and VFDs. The spec sections for each discipline claim it differently, or the division of responsibility is left ambiguous.
This is a classic MEP interface gap. The mechanical sub says it is electrical scope. The electrical sub says it was not in their bid. The GC absorbs the cost or fights a change order through project delivery.
Mechanical drawings show louvre locations and sizes. The spec requires fire-rated assemblies with specific UL listings. The architectural drawings show the exterior aesthetic. None of the three consistently call out the supplier or installer.
Fire-rated louvres are specialty items with long lead times and specific structural backing requirements. Missing them at bid means a procurement crisis and a schedule impact in addition to the cost gap.
Plumbing drawings show drain locations. Civil or structural drawings show slab details. Neither reliably assigns responsibility for the trench: excavation, backfill, compaction, and concrete reinstatement. When the scope sheet for the plumbing sub does not specify trench scope, the sub excludes it. The GC finds out during buyout.
This is one of the most consistent gaps in MEP bid packages at mid-market GCs. The fix is a single line in the scope sheet. The miss can cost $40K–$80K on a mid-size commercial project.
Lighting control specifications have migrated to networked systems over the past decade. The electrical drawings show fixture locations and circuit homerun points. The spec section for lighting controls describes a BAS-integrated system with a separate controls contractor, proprietary software, and commissioning requirements.
When the electrical scope sheet goes out without calling this out explicitly, the sub prices standard switching. The controls scope is unassigned. On a large commercial project, that gap runs $150K–$300K depending on the system complexity.
This gap appears at the interface between the plumbing sub and the equipment supplier on projects with commercial kitchens, labs, or medical gas systems. The spec assigns rough-in to the plumbing sub and final connection to the equipment supplier. In practice, both parties read the spec differently and each excludes the final tie-in.
The $45K stone-depth mismatch documented in Provision's operator research is a structural parallel. Two disciplines drawing to different reference points, with no one reconciling the interface.
Most MEP gaps trace back to one of four root causes. Understanding the cause tells you where to look in the documents.
Specifications are often written from master spec templates and issued with the bid set before the design is finalized. The engineer-of-record updates the drawings through multiple design development rounds. The spec section does not always follow. The result: the spec references equipment that was substituted in the drawings two months earlier.
On design-bid-build projects, the mechanical, electrical, and plumbing engineers coordinate through the architect. That coordination is imperfect. Interface items such as condensate drain routing, electrical power to mechanical equipment, and plumbing connections for HVAC coils fall into gaps between discipline drawings.
Addenda are the single most common source of document inconsistency on a bid set. An addendum that revises an equipment schedule in the spec does not automatically update the electrical single-line. An addendum that revises a plumbing fixture type may not update the rough-in detail on the architectural drawings.
Catching addenda conflicts requires reading the original spec section, the revised addendum section, and the corresponding drawing detail together. Under time pressure, this is exactly the step that gets cut.
The single most cited scope anti-pattern in Provision's operator research is scope sheets that read "as per plans and specs" for MEP work. This language assigns responsibility without defining it. Every sub reads it differently. Every sub prices it differently. The GC holds the gap.
A pre-construction lead at a Top-ENR Canadian GC put it clearly: "It's descriptive, bread, put it on a plate, use the open jar. You have to get to that level of detail or else they'll just be like, 'you didn't tell us that.'"
That same contact added: "If you miss anything, they'll bill it."
The following process is drawn from the eight habits framework in the Scope Gap Playbook. It is designed for the 72-hour window before bid day when your team is under the most pressure and the most likely to miss something.
List every MEP system on the project. For each system, identify which discipline drawing set covers it and which specification division governs it. Note every system that appears in more than one drawing discipline. Those are your highest-risk interface points.
This step takes two hours on a mid-size commercial project. It produces a reference document that your entire pre-construction team can use when cross-checking scope assignments.
Subs read Division 21, 22, 23, 26, and 28. They skim Division 01 (general requirements) and often skip it entirely. Division 01 contains testing and commissioning requirements, temporary utilities assignments, and equipment startup protocols that carry real cost.
Your review process should include Division 01 MEP-related sections as a mandatory check. The generator field conditioning cost and BAS commissioning requirements are almost always in Division 01 or in the front-end of the relevant trade section, not in the body of the spec that subs review most carefully.
For each addendum, identify the primary document it modifies. Then ask: does this change affect any other drawing, spec section, or equipment schedule that was not revised in this addendum?
Document your cross-reference in writing. If an addendum revises the mechanical equipment schedule but the electrical power schedule has not been updated, that is a flag. Write it into your pre-bid RFI or call it out as an assumption in your scope sheet.
Before a scope sheet goes to any MEP sub, verify three things:
This is Habit 1 from the Eight Habits: drawings-first, not boilerplate-first. The scope sheet is built from what the documents actually say, not from what the last similar job included.
If your cross-document review finds a genuine conflict between a drawing and a spec (not just an omission, but an actual contradiction), issue a pre-bid RFI. Document the conflict with specific references: drawing number, sheet, detail, and spec section and paragraph.
This protects your bid. If the owner does not respond before bid day, your bid qualifications can reference the open RFI and exclude the disputed scope. That is a defensible position. "As per plans and specs" is not.
This is Habit 8 from the Eight Habits framework. Before scope sheets go to MEP subs, a senior estimator or pre-construction lead reviews each package against the interface matrix built in Step 1. The review is not a proof check. It is a coverage check: does this scope sheet address every item on the interface matrix?
On a complex MEP project, this review takes 60–90 minutes. It is the step most often cut under bid-day pressure. It is also the step that catches the $150K lighting controls gap before the sub's number is in your bid.
Manual cross-document review is limited by time and attention. On a project with 800 drawing sheets and a 2,400-page specification book, a two-person estimating team cannot read every document against every other document before bid day.
Provision's Scope Agent reads the full project set together: drawings, specifications, and contracts. It generates complete trade-by-trade scope packages with every item cited to the source document, drawing number, and specification section. It does not require an estimator to reconcile the mechanical drawing against the Division 23 spec manually. That cross-reference is built into the output.
Provision has processed more than 100,000 construction documents across $100 billion in project value. The platform has identified more than 1,000,000 risks and answered more than 50,000 estimator queries across real bid sets. The Scope Agent's scope extraction matches at 97% accuracy on validation testing, compared to a 91.3% human baseline on the same exercise at roughly four days per project.
For MEP-heavy bids where the interface matrix is complex and the document set is large, that accuracy gap and that time gap are where margin is protected or lost.
Provision's Risk Review handles the contract-side of the same problem. If a specification section includes performance requirements that shift risk to the GC under a "readily inferable" clause, Risk Review flags it with a citation to the exact section and paragraph. That is 80% less time spent on spec review with 99% accuracy on risk identification.
For teams doing deep document searches during bid prep, Chat Agent answers construction document questions in under 20 seconds with cited answers drawn from the project set. Instead of searching a 2,400-page spec book for the generator commissioning requirement, an estimator asks the question and gets the answer with a source reference.
See how the EllisDon case study demonstrates what this looks like on a complex institutional project.
You do not need new software to improve your MEP scope review this week. Start with these three changes to your current process.
MEP scope gaps are not random. They are produced by specific document coordination failures and specific review shortcuts. Fix the process, and you fix the margin.
An MEP scope gap is a requirement that appears in the mechanical, electrical, or plumbing bid documents (drawings, specs, or both) but is not assigned to any sub in the scope of work. These gaps surface during buyout or field execution as change orders. They are most common at the interface between disciplines or between drawing sets and specification sections.
Drawings and specs are authored by different engineers on different timelines. Specs are often written from master templates before design is final. Drawings evolve through multiple revisions. When addenda revise one document but not the other, conflicts result. MEP work has the highest density of cross-discipline interfaces, so conflicts are more common than in other trades.
Generator field conditioning, motor starters and VFDs, fire-rated louvres, plumbing trench scope, lighting controls and BAS integration, and final equipment connections are the most frequently missed items. Each one shares the same root cause: the requirement lives in a specification section that does not appear on any drawing.
Issue a pre-bid RFI with specific document references (drawing number, sheet, spec section, and paragraph). If the owner does not respond before bid day, include a bid qualification that references the open RFI and excludes the disputed scope. "As per plans and specs" is not a defensible position when the plans and specs say different things.
On a mid-size commercial project with 400–800 drawing sheets and a standard spec book, a structured MEP interface review takes 8–16 hours for a senior estimator. Purpose-built tools like Provision's Scope Agent compress this to under 60 minutes by reading the full document set together and generating cited, trade-by-trade scope packages.
Many contracts include language requiring the GC to provide all work "readily inferable" from the contract documents, even if not explicitly shown. On MEP work, this language can assign spec-based requirements (like generator commissioning or BAS integration) to the GC without a drawing reference. The $300K lead-lined glass gap documented in Provision's operator research was absorbed under exactly this type of clause.
Provision's Scope Agent reads drawings, specifications, and contracts together and generates trade-by-trade scope packages with every item cited to its source document. For MEP bids, this means interface items between disciplines are surfaced automatically rather than caught (or missed) in a manual review. Risk Review flags spec-based risk clauses with exact section references at 99% accuracy.
Scope Agent reads your full project set and flags every cross-document gap before scope sheets go to subs.
See Scope AgentMore Articles
