On a lump sum bid, scope gaps are your liability. The owner's price is fixed. The sub's contract is your problem. Every item you failed to assign to someone becomes a change order, an RFI, or a dispute you absorb.
A 2024 Arcadis Global Construction Disputes Report put the average North America construction dispute value at $60.1 million. Errors and omissions in contract documents have repeatedly ranked as the top dispute cause in North America. That is not a design team problem. It starts in preconstruction, in the scope packages your team sends at bid.
This article walks through how to build a GC scope package from scratch on a lump sum project. It covers structure, trade-by-trade pitfalls, and the review habits that separate tight bids from expensive ones.
A GC scope package is the set of documents you send to each subcontractor when you invite them to bid. It defines what they are pricing, what they are not pricing, what documents govern their work, and what conditions apply on this specific project.
On a lump sum bid, the scope package does three jobs at once. It controls what the sub includes. It records what you assigned and to whom. And it forms the foundation of the subcontract if you win.
A weak scope package does the opposite. It lets subs exclude items silently, creates overlaps and gaps between trades, and gives your buyout team nothing solid to build on after award.
Most scope gaps start before anyone types anything. They start when an estimator opens a template and begins filling it in before reading the project documents.
Templates are a floor, not a ceiling. That is one of the core habits separating high-margin GCs from average ones, documented across more than 200 GC interviews in the Scope Gap Playbook. A boilerplate scope for drywall that worked on a mid-rise office will miss the gypcrete specification in a multifamily project, or the wall blocking requirement on a medical fitout.
Before writing, you need three things open:
Read those first. Then open the template.
Interface zones are where the most expensive gaps hide. These are the areas where two trades hand off to each other: drywall to framing, structural steel to MEP supports, envelope to interior finishes.
A $45,000 gap on a single slab came from a stone-depth mismatch between civil, structural, and architectural drawings. No one reconciled the three sets before writing the concrete and finishes scopes. Each trade priced what their drawing showed. The conflict surfaced in the field.
Mark those zones on your drawings before you write. Assign every item explicitly. Do not leave anything to "as per plans and specs."
Every trade scope in your package should follow the same four-part structure. Reviewers know what to look for. Subs know where to find exclusions. Your buyout team can do a line-by-line comparison after award.
List what the sub is pricing. Be specific. Not "all drywall work" but "supply and install of all interior metal stud framing, gypsum board, and taping per Spec Division 09 21 16 and Architectural Drawings A301 through A312."
A Pre-Construction Lead at a Top-ENR Canadian GC described it this way: "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 say you didn't tell them that."
If an item is on the drawing and you expect the sub to price it, it goes in inclusions. If you are not sure which trade owns it, write it in and resolve it during scope review. Do not leave it out and hope.
List what the sub is NOT pricing. This is equally important. Exclusions confirm that another trade is picking up the item. They also prevent a sub from later claiming they thought it was included.
Common items to exclude explicitly: concrete pumping (assign it to concrete or call it out separately), fire-stopping (often missed between drywall and MEP), and motor starters (frequently assumed to be in electrical but excluded by both MEP trades).
Clarifications are not exclusions. They are conditions, assumptions, and interpretations that affect price. For example: "Price assumes open web steel joist installation sequence per structural drawings. Any resequencing required by site conditions is a change." Or: "Material lead times assumed at 12 weeks. Any owner-driven acceleration requires written direction."
This section protects you. It also signals to subs that you have read the documents, which improves quote quality.
Reference specific documents. Not "as per contract documents." Name the drawing set revision, the specification divisions, and any relevant addenda by number.
Specific document references are one of the eight habits identified in the Scope Gap Playbook as consistent across the GCs with the tightest margins. Generic incorporation language like "as per plans and specs" is the most-cited anti-pattern. It is cited in disputes. It costs money.
Some trades produce more scope gaps than others. These are the ones that show up repeatedly in disputes and change orders.
The five-foot transition is a recurring gap: who handles the zone from building footprint to five feet beyond the foundation wall? Assign it explicitly. Geotech compaction requirements are another common miss. If the spec calls for engineered fill to a specific compaction percentage, that needs to be in the scope, not assumed.
Excavator unit-rate exploitation is a real risk on lump sum. Write your earthwork scope to reflect actual bid quantities, not open-ended unit rates that expand once a shovel is in the ground.
Base plate grouting is frequently excluded by both the steel and concrete trades. Write it explicitly into one of them. Concrete pumping is similar. The concrete sub often assumes the GC supplies the pump. Assign it, or it floats.
Slab assembly conflicts between structural and architectural drawings generate RFIs and field delays. Reconcile the drawings before you write the scope. If there is a conflict, note it in the clarifications section and flag it for RFI prior to bid.
Embeds and anchor bolts are the most common structural steel gap. They appear on structural drawings but are often assumed to be in concrete. Assign them explicitly. Hoisting and rigging are similar. The steel fabricator scopes fabrication and delivery, but on-site rigging may fall between trades if you do not assign it.
Miscellaneous metals are often scattered across divisions in the spec. Pull them together. Assign each item. Do not let "misc metals" become a catch-all that nobody owns at buyout.
MEP scopes generate more change orders than any other trade category on commercial ICI work. The gaps are predictable:
For a deeper look at MEP-specific scope gaps by system, the trade-specific scope gaps chapter of the Scope Gap Playbook covers each one with operator examples.
A $400,000 roof cover board was missed on a $50-million project. It was on the drawing. It was in the spec. It fell between roofing and insulation because neither sub saw it as theirs. The GC absorbed it through a relational concession from the roofing sub. That is a best-case outcome. Write the cover board into roofing explicitly.
Masonry-to-storefront flashings are another recurring gap. Both trades assume the other is providing continuity at the intersection. Neither includes it unless you write it in. Same for caulking: specify whether interior or exterior caulking is in the envelope scope or the drywall scope. Do not leave it open.
Wall blocking for millwork, accessories, and equipment is missed more often than it should be. If there is millwork, there is blocking. Write it into drywall. Hollow metal door frames are another item. They appear in the door hardware spec and the drywall spec, and both trades exclude them if you do not assign them explicitly.
Gypcrete naming collisions happen on multifamily projects. "Gypcrete," "gypsum concrete," and "floor underlayment" can refer to the same product or three different ones depending on the spec writer. Resolve it before you write the scope.
A $300,000 lead-lined glass omission on a hospital imaging suite was absorbed by the GC under "readily inferable" contract language. The sub excluded it. The GC's scope letter said "all glazing per architectural drawings." The drawings showed the lead lining in a detail. No one caught it in scope review.
Specialty items need specific treatment. List them by name. Reference the spec section. Assign them to a trade. If the item is unusual, note it in the clarifications section so subs know you expect it in their price.
One of the eight habits from the Scope Gap Playbook is the pre-issue scope review checkpoint. It is exactly what it sounds like: a structured review of the scope package before it goes out, not five minutes before bid-day close.
A five-minute bid-day scan is one of the most-cited anti-patterns across the 200+ GC interviews that informed the playbook. It finds nothing. By the time you are on bid day, the scope is what it is.
The checkpoint should happen 48–72 hours before you issue. It should check:
The goal is not perfection. The goal is that when the sub says "we didn't include that," you have a written record that says they should have.
An Estimating Manager at a Canadian ICI GC put it plainly: "We have less subs who just operate on a gentleman's agreement. They've become more quick to clarify that they're not including that one piece of scope."
That is the market in 2026. Subs are more sophisticated. They read scope letters carefully. They exclude anything you did not explicitly assign. That means your scope package needs to be explicit, not assumed.
Tailor your scope to sub sophistication. A specialty sub for a curtainwall mock-up needs different language than a concrete sub you have worked with for ten years. Know your audience and write accordingly.
Templates save time. They also create false confidence. The right way to use a scope of work template is as a starting structure, not a finished product.
Start with the template. Then compare every line to the actual project drawings. Add items the template does not cover. Remove items that do not apply. Reference the actual drawing sheets and spec divisions, not generic placeholders.
Junior estimators stuffing previous scopes verbatim into new bids is one of the most-cited anti-patterns in the playbook. The project is different. The sub is different. The spec is different. The scope needs to reflect that.
A complete lump sum scope package requires reading every relevant drawing sheet, every specification division, and every addenda for every trade. On a mid-size commercial project, that is 30–40 hours of work per bid. On a fast-track pursuit, you may not have 30 hours.
Provision's Scope Agent reads the full project set, including drawings, specs, and addenda, and generates trade-by-trade scope packages in under 60 minutes. It has reviewed over $100 billion in project value and processed more than 100,000 documents. Internal validation shows 97% match accuracy on scope item extraction. The human estimator baseline on the same exercise was 91.3%.
Scope Agent does not replace your estimators' judgment. It replaces the 30-hour document read so your team can focus on the items that need human review: the interfaces, the conflicts, and the specialty items that require a decision.
You can see how EllisDon used Scope Agent and saved $1.8 million. Or book a demo to see it work on your documents.
A tight scope package does not just protect you from change orders. It improves quote quality. Subs price what you define. If you define it well, you get apples-to-apples quotes. If you define it loosely, every sub prices differently and your leveling takes twice as long.
On a lump sum bid, the scope package is where margin is made or lost. Not in the field. Not at final account. In the document you send before the subs submit their numbers.
Write it like it will end up in front of a mediator. Because sometimes it does.
For a complete framework on scope gap causes and prevention habits, the Scope Gap Playbook covers all eight habits with operator examples from GCs across North America.
Each trade scope should include four sections: inclusions (what the sub is pricing), exclusions (what they are not), clarifications (assumptions and conditions), and document references (specific drawing revisions and specification divisions). Generic language like "as per plans and specs" creates gaps and disputes.
A complete lump sum scope package for a mid-size commercial project takes 30–40 hours of manual work. That includes reading drawings, reviewing specs, reconciling addenda, and drafting trade-by-trade scopes. Fast-track projects often do not have that time. Tools like Scope Agent reduce the window to under 60 minutes.
Interface zones produce the most gaps: MEP-to-structure, envelope-to-interior, and specialty items with no clear trade owner. Specific recurring examples include base plate grouting, roof cover boards, fire-rated louvres, motor starters, and lead-lined glass. Each needs explicit assignment in the scope letter.
Use a template as your starting structure, then customize it to the actual project documents. Compare every template line to the project drawings and spec. Remove items that do not apply. Add project-specific items the template does not cover. A template used as a finished product misses project-specific conditions every time.
Readily inferable contract language requires subs and sometimes GCs to include items that a competent contractor should have known were part of the work, even if not explicitly shown. A $300,000 lead-lined glass omission was absorbed under this language on a hospital imaging suite. Your scope needs to cover what is shown, not just what is listed.
Note the conflict in the clarifications section of the relevant trade scope. Flag it for RFI before bid. Do not leave conflicting information unaddressed and assume subs will price the higher of the two. They will price the lower one, and the delta becomes a change order.
A structured review of the complete scope package 48–72 hours before it goes out to subs. It checks that every interface zone is assigned, no items are duplicated across trades without clear ownership, specialty items are named and referenced, and document references match current addenda. It is one of the eight habits that separates tight-margin GCs from the rest.
Scope Agent reads your full project set and generates trade-by-trade scope packages so your team focuses on the gaps that need judgment.
See Scope AgentMore Articles
