Most people in construction use “scope gap” to mean one thing: work that got left out. That definition is comfortable, and it is wrong, and being wrong about it is expensive.<\/p>\n\n\n\n
Work almost never gets left out. Design teams are good at their jobs, and a coordinated commercial set describes the building. What goes wrong is assignment. The obligation exists in the documents, sometimes in three places, and no trade package clearly carries it. Or two packages carry it. Or one package furnishes it, and nobody installs it. According to the specs, the drawings don’t show it, and the estimator, who quantifies from drawings, never see it. <\/p>\n\n\n\n
For four different reasons, four different things fail to happen, and four different options exist for how each thing is detected. Four different things depend on each other to some degree, but because most teams view each document in a set as a standalone instance, the reviewers expect to find certain things and are shocked to discover the other things in month five.<\/p>\n\n\n\n
This article breaks scope gaps into ten distinct types. For each: what it actually is, why it occurs, where it conceals itself, what it expenses, how to entrap it. When you incorporate this taxonomy on how your team reviews documents, you will cease searching for the ambiguous term called \u201cgaps\u201d and will commence performing ten specific checks.<\/p>\n\n\n\n
Consider two findings on the same project. On sheet A-101, a general note reads “provide access as required for concealed equipment.” On sheet M-201, a note reads “duct insulation per specification,” and the mechanical package includes insulation while the insulation package also includes it.<\/p>\n\n\n\n
Both are scope gaps in casual usage. They have nothing in common operationally. The first is an ambiguous attribution problem, found by screening language, fixed by an RFI or a documented convention. The second is an overlap, found by querying for multi-assigned obligations, fixed by a scope narrative exclusion. Different search, different owner, different remedy.<\/p>\n\n\n\n
A reviewer looking for “gaps” finds whichever type she is mentally primed for. A reviewer running ten typed checks finds all ten, because each check has a defined target.<\/p>\n\n\n\n
Table 1. The Ten Gap Types at a Glance<\/strong><\/p>\n\n\n\n Two of these deserve a note up front. Type 5 is the highest-frequency gap on commercial building work and the one manual review handles worst. Type 9 is the highest-severity, because contractual boundaries involve parties outside your subcontract structure and therefore outside your control.<\/p>\n\n\n\n What it is.<\/strong> An obligation stated in the contract documents that no bid package carries. The genuine orphan.<\/p>\n\n\n\n Why it happens.<\/strong> Almost always because the obligation’s content spreads across many packages, so no single subcontractor recognizes it as theirs. Divisions 07, 09, 10, 12, and 31 generate these at a much higher rate than any others, and the reason is structural rather than technical. Firestopping appears in six divisions. Blocking appears wherever anything gets mounted. Nobody’s core trade identity includes them.<\/p>\n\n\n\n The second cause is package boundary drift. Your office has always put access panels in drywall. This project’s estimator, newer, assumed mechanical. Neither wrote it down. The panels end up in neither.<\/p>\n\n\n\n Where it hides.<\/strong> General notes on architectural sheets. Division 01. Division 10 specialties. Substrate preparation obligations. Anything described as “provide” without a system context.<\/p>\n\n\n\n What it costs.<\/strong> Variable, but the distribution is bad. Small items get absorbed. Large ones surface after installation of adjacent work, which means the fix carries removal, replacement, and delay on top of the original scope.<\/p>\n\n\n\n How to catch it.<\/strong> A division-to-package crosswalk. Every division present in the project manual is a row, every bid package is a column, and each cell is marked full, partial, or none. Any division with no full or partial mark anywhere is unexamined. Any division marked partial in every column has an unassigned remainder that somebody needs to name.<\/p>\n\n\n\n What it is.<\/strong> Two or more packages both carry the same obligation.<\/p>\n\n\n\n Why it happens.<\/strong> Broad spec section language, defensive subcontractor scoping, and the natural tendency of a GC to make sure something is covered by putting it in two places. That last one feels prudent and is not.<\/p>\n\n\n\n What it costs.<\/strong> Two ways, and the second is worse than the first. You paid twice, which is a straightforward margin loss. And when both subs believe the other one has it, neither does it, which is the same outcome as Type 1 with the added irritation of having paid for it. Overlaps look like the safe failure mode. They are not.<\/p>\n\n\n\n Where it hides.<\/strong> Insulation between mechanical and the insulation trade. Firestopping between the penetrating trade and the firestop specialist. Painting of exposed conduit and ductwork. Ceiling access provisions. Excavation and backfill between earthwork and the utility trades. Cleaning between each trade’s final clean and the GC’s general cleaning obligation.<\/p>\n\n\n\n How to catch it.<\/strong> Query the obligation register for items assigned to more than one trade where no interface was defined. Then, separately, compare the inclusion lists across adjacent packages during buyout. The second check catches overlaps that entered through subcontractor proposals rather than through your assignment.<\/p>\n\n\n\n Table 2. Recurring Overlap Pairs on Commercial Work<\/strong><\/p>\n\n\n\n What it is.<\/strong> The obligation names a responsibility but not a party. “By others.” “Coordinate with adjacent trades.” “As required.” “By installing contractor.”<\/p>\n\n\n\n Why it happens.<\/strong> Design documents are written to describe a completed building, not to divide a subcontract structure the designer has never seen. “By others” is a perfectly reasonable thing for an architect to write. It becomes a gap only when a GC’s buyout treats it as an assignment.<\/p>\n\n\n\n What it costs.<\/strong> This is the type that most reliably produces change orders, because ambiguity does not stay neutral in a competitive market. Subcontractors who read documents carefully price the narrow interpretation, win the package, and recover the difference later. Vague scope systematically selects for the bidders most willing to argue with you in month seven.<\/p>\n\n\n\n Where it hides.<\/strong> In language, not in subject matter, which is why it needs its own screening pass independent of what the obligation is about.<\/p>\n\n\n\n Table 3. Ambiguous Attribution Patterns and What They Actually Mean<\/strong><\/p>\n\n\n\n How to catch it.<\/strong> Screen the full text of every note and specification paragraph for the patterns above, before assignment. It is the cheapest check available and the one that best predicts change orders. Log every hit even when it looks harmless.<\/p>\n\n\n\n What it is.<\/strong> An obligation involving two or more trades where the responsibilities have been named at the trade level but not decomposed. Both subs know they are involved. Neither has a complete understanding of the endeavor.<\/p>\n\n\n\n Each multi-trade obligation has four separate responsibilities designed to answer the following questions: who supplies the materials, who does the installation, who arranges the location and order, and who checks the correctness. Naming two trades answers none of those four questions.<\/p>\n\n\n\n Why it happens.<\/strong> Because “mechanical and drywall” feels like a resolution. It is recorded in the log, the log shows no open item, and the analysis appears complete. This is probably the most common false resolution in preconstruction.<\/p>\n\n\n\n What it costs.<\/strong> Field disputes, almost always at the worst possible moment. Interface obligations are usually sequence-critical, so the argument happens when one trade is ready to proceed and the other is not.<\/p>\n\n\n\n Where it hides.<\/strong> Everywhere two systems meet. Equipment connections. Penetrations. Supports and attachments. Substrate handoffs. Anything owner-furnished.<\/p>\n\n\n\n Table 4. Interface Decomposition Examples<\/strong><\/p>\n\n\n\n How to catch it.<\/strong> Build the grid. Any multi-trade obligation with a blank cell is an open finding, regardless of how many trades are named. Fill it in with a superintendent in the room, because the answers depend on how work actually gets sequenced.<\/p>\n\n\n\n What it is.<\/strong> An obligation appears on one discipline’s drawings but belongs to a different discipline’s trade. Electrical work described on mechanical sheets. Concrete work described on plumbing sheets. Carpentry work described on architectural sheets.<\/p>\n\n\n\n Why it happens.<\/strong> Designers annotate where the reader needs the information, which is correct practice. A mechanical engineer noting “provide power for VAV boxes” on M-301 is being helpful to the mechanical contractor. The problem is entirely on the buyout side: estimators read by discipline. The electrical estimator reads E sheets. Nobody reads M sheets looking for electrical obligations.<\/p>\n\n\n\n What it costs.<\/strong> This is the highest-frequency gap type on commercial building work by a wide margin. A mid-size commercial mechanical set will routinely carry twenty to forty obligations belonging in the electrical package.<\/p>\n\n\n\n Where it hides.<\/strong> Predictably. The pairs repeat on every project.<\/p>\n\n\n\n Table 5. Cross-Discipline Displacement, Recurring Pairs<\/strong><\/p>\n\n\n\n#<\/strong><\/th> Gap Type<\/strong><\/th> Core Failure<\/strong><\/th> Primary Detection Method<\/strong><\/th><\/tr><\/thead> 1<\/strong><\/td> Unassigned obligation<\/td> No package carries the work<\/td> Division coverage crosswalk<\/td><\/tr> 2<\/strong><\/td> Overlap and double assignment<\/td> Two packages both carry it<\/td> Multi-assignment query<\/td><\/tr> 3<\/strong><\/td> Ambiguous attribution<\/td> Responsible party described, not named<\/td> Language pattern screen<\/td><\/tr> 4<\/strong><\/td> Interface split<\/td> Furnish, install, coordinate, or verify unassigned<\/td> Interface decomposition grid<\/td><\/tr> 5<\/strong><\/td> Cross-discipline displacement<\/td> Obligation on one discipline’s sheets, another’s trade<\/td> Trace by assigned trade across sources<\/td><\/tr> 6<\/strong><\/td> Specification-only obligation<\/td> Required in specs, absent from drawings<\/td> Bidirectional spec reconciliation<\/td><\/tr> 7<\/strong><\/td> Drawing-only obligation<\/td> Shown on drawings, no governing specification<\/td> Bidirectional spec reconciliation<\/td><\/tr> 8<\/strong><\/td> Delegated design fragmentation<\/td> Engineering, submittal, or inspection unassigned<\/td> Delegated design trigger screen<\/td><\/tr> 9<\/strong><\/td> Boundary gap<\/td> Obligation falls across a contractual boundary<\/td> Boundary matrix per boundary type<\/td><\/tr> 10<\/strong><\/td> Exclusion cascade<\/td> Every bidder excluded the same item<\/td> Exclusion reconciliation per package<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n KEY TAKEAWAY<\/strong>
Ten types, ten checks, ten different remedies. Most preconstruction teams would be best served by no longer viewing scope gap review as a single activity. These teams should assign a type and target to each inspection of the scope gap review.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nGap Type 1: The Unassigned Obligation<\/strong><\/h2>\n\n\n\n
FIELD REALITY<\/strong>
The unassigned rate on an exhaustively extracted commercial set typically runs one to three percent of obligations. If your log shows zero unassigned items, the analysis is not clean, it is incomplete. A healthy review finds problems.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nGap Type 2: Overlap and Double Assignment<\/strong><\/h2>\n\n\n\n
Obligation<\/strong><\/th> Packages That Both Claim It<\/strong><\/th> Resolution Convention<\/strong><\/th><\/tr><\/thead> Duct and pipe insulation<\/strong><\/td> Mechanical, plumbing, insulation specialist<\/td> Assign by system, state the split explicitly in both narratives<\/td><\/tr> Penetration firestopping<\/strong><\/td> Each penetrating trade, firestop specialist<\/td> Assign by penetration type, not by trade<\/td><\/tr> Painting of exposed conduit, duct, hangers<\/strong><\/td> Painting, each MEP trade<\/td> Assign to painting; exclude explicitly in MEP narratives<\/td><\/tr> Trench excavation and backfill<\/strong><\/td> Earthwork, each utility trade<\/td> Earthwork performs, utility trades supply and lay, joint hold point<\/td><\/tr> Equipment pads<\/strong><\/td> Concrete, mechanical, electrical<\/td> Concrete performs, equipment trade provides layout and templates<\/td><\/tr> Access panels<\/strong><\/td> Drywall, ceilings, mechanical, plumbing<\/td> Assign by assembly type, furnish and install stated separately<\/td><\/tr> Final cleaning<\/strong><\/td> Each trade, GC general conditions<\/td> Each trade cleans its own work; GC performs final clean; define the handoff<\/td><\/tr> Fire alarm devices and interfaces<\/strong><\/td> Electrical, fire alarm, mechanical<\/td> Assign by device and by interface point<\/td><\/tr> Sleeves and penetration formwork<\/strong><\/td> Concrete, each penetrating trade<\/td> Penetrating trade furnishes, concrete places, GC verifies before pour<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Gap Type 3: Ambiguous Attribution<\/strong><\/h2>\n\n\n\n
Phrase as Written<\/strong><\/th> What the Bidder Reads<\/strong><\/th> What You Need It to Say<\/strong><\/th><\/tr><\/thead> “By others”<\/strong><\/td> Not me<\/td> Named trade or GC-held line<\/td><\/tr> “As required”<\/strong><\/td> Whatever is drawn, and nothing more<\/td> Quantity, location, and standard<\/td><\/tr> “Coordinate with adjacent trades”<\/strong><\/td> Attend the meeting; install nothing<\/td> Who coordinates, who installs, who verifies<\/td><\/tr> “Field verify”<\/strong><\/td> Risk transferred; scope unchanged<\/td> Verification obligation with a named party and a deadline<\/td><\/tr> “By installing contractor”<\/strong><\/td> Whoever that turns out to be<\/td> The installer, named<\/td><\/tr> “Provide for” \/ “allow for”<\/strong><\/td> Leave room; supply nothing<\/td> Defined capacity, count, or dimension<\/td><\/tr> “Rough-in only”<\/strong><\/td> Stop at the wall<\/td> The precise stopping point and who continues<\/td><\/tr> “Furnish only”<\/strong><\/td> Deliver to the site<\/td> Who receives, stores, protects, and installs<\/td><\/tr> “Match existing”<\/strong><\/td> The cheapest thing that resembles it<\/td> Standard, extent, and acceptance criteria<\/td><\/tr> “Typical”<\/strong><\/td> This detail everywhere<\/td> Where it applies and where it does not<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n COMMON MISTAKE<\/strong>
When teams face uncertain attribution, the clarification is requested from the design team. Often, the design team provides restated responses. Teams then accept the item as closed. Write RFIs that force a decision. “Confirm which trade furnishes and installs access panels at fire dampers in rated assemblies, and confirm panel type per 08 31 13” gets an answer. “Please clarify access panel requirements” gets you the note you already read.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nGap Type 4: The Interface Split<\/strong><\/h2>\n\n\n\n
Obligation<\/strong><\/th> Furnish<\/strong><\/th> Install<\/strong><\/th> Coordinate<\/strong><\/th> Verify<\/strong><\/th><\/tr><\/thead> Access panel at fire damper<\/strong><\/td> Drywall or mechanical, by assembly<\/td> Drywall typically<\/td> Mechanical provides locations<\/td> Superintendent, then AHJ<\/td><\/tr> Housekeeping pad at pump<\/strong><\/td> Concrete<\/td> Concrete<\/td> Plumbing provides layout and anchor template<\/td> GC before pour<\/td><\/tr> Sleeve through rated wall<\/strong><\/td> Penetrating trade<\/td> Penetrating trade<\/td> GC<\/td> Firestop specialist and AHJ<\/td><\/tr> Final connection to owner-furnished equipment<\/strong><\/td> Owner<\/td> Named trade per system<\/td> GC<\/td> Commissioning agent<\/td><\/tr> Ceiling grid at sprinkler head<\/strong><\/td> Ceilings and fire protection<\/td> Each own component<\/td> VDC or ceilings<\/td> Superintendent<\/td><\/tr> Roof curb for RTU<\/strong><\/td> Mechanical or steel, by type<\/td> Roofing installs flashing<\/td> GC<\/td> Roofing warranty inspector<\/td><\/tr> Low-voltage backbox and pathway<\/strong><\/td> Electrical<\/td> Electrical<\/td> Low-voltage trade provides locations<\/td> Commissioning<\/td><\/tr> Seismic restraint at duct<\/strong><\/td> Delegated engineer and fabricator<\/td> Mechanical<\/td> Structural review<\/td> Special inspector<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Gap Type 5: Cross-Discipline Displacement<\/strong><\/h2>\n\n\n\n