NewRFI Agent is now available: drawing and spec conflicts, found before tenderRead the announcement →

Pre-Buyout Scope Package Review Template: What to Check Before Every Subcontract Goes Out

By Provision·December 17, 2026

TL;DR

  • Most scope gaps are locked in at buyout, not discovered in the field.
  • A pre-buyout review checks six areas: scope completeness, coordination items, Division 1 requirements, addenda coverage, inferred work, and commercial terms.
  • Coordination flags (work between two trades) appear in 74% of scope packages, according to Provision's Q3 2026 Scope Gap Index across 1,290 packages from 24 projects.
  • Use the template below before every subcontract goes out. It takes 20–30 minutes per trade. It is worth every minute.

Buyout moves fast. Award pressure from the owner, subs pushing for a quick scope sign-off, and an estimating team already chasing the next bid. In that environment, scope packages go out with gaps. Those gaps become change orders. By then, you are the one absorbing them.

A 2018 PlanGrid and FMI study put the annual cost of U.S. rework from miscommunication and bad project data at $31.3 billion. Arcadis pegged the average North American construction dispute at $60.1 million in its 2024 Global Construction Disputes Report. The root cause, in both reports, is the same: incomplete or ambiguous scope at the time of commitment.

This template gives you a structured check for every scope package before the subcontract goes out. Use it as a checklist, a team handoff tool, or a training baseline for junior estimators running their first buyout.

For a deeper look at how scope gaps form, and what the highest-margin GCs do differently, the Scope Gap Playbook is built from 200+ GC interviews and walks through the habits and anti-patterns that separate clean buyouts from expensive ones.

Why Scope Gaps Survive to Buyout

Scope packages get written under time pressure. Addenda arrive late. Drawings get revised. The estimator who built the original scope package may not be the one issuing the subcontract. Each handoff is a chance for something to fall through.

The most common anti-patterns, documented in the Scope Gap Playbook's chapter on subcontract language, include:

An Estimating Manager at a Canadian ICI GC put it plainly: "If you miss anything, they'll bill it." That is the operating environment. The template below is designed for it.

The Pre-Buyout Scope Package Review Template

Work through each section before the subcontract goes out. Flag any item that needs resolution. Do not issue the contract until flagged items are either resolved or formally accepted as risk.

Section 1: Scope Completeness

Start with the basics. Does the scope package describe the work clearly enough that a sub could price it accurately without assumptions?

Check Item Pass / Flag / N/A Notes
Every major work item is named explicitly, not by reference to "plans and specs."
Drawing and specification references are specific (sheet number, section number).
Scope matches the current drawing revision. Not the issue-for-tender set.
All addenda have been reviewed and reflected in the scope.
Finish standards, material standards, and performance requirements are stated.
Scope was not copied from a previous job without review against current documents.

Section 2: Coordination Items (Trade Interfaces)

Coordination flags are the most common type of scope gap. Provision's Scope Gap Index, covering 1,290 packages from 24 projects in Q3 2026, found that 74% of packages had at least one coordination flag. These are items that sit between two trades, with neither scope naming them.

Common coordination gaps by category:

Interface Typical Gap Assigned To / Flagged
Concrete / Steel Embeds and anchor bolts: who supplies, who sets.
Roofing / Envelope Sealants and flashings at the roof-to-wall joint.
Drywall / Millwork Blocking and backing for cabinetry, grab bars, and wall-mounted equipment.
Mechanical / Structural Penetrations through rated walls: who sleeves, who seals, who certifies.
Electrical / General Motor starters, lighting controls, and field-conditioning of generators.
Finishes / Structure Tolerances at trade interfaces: gypcrete naming, slab flatness handoffs.

For trade-specific gap patterns across MEP, envelope, and specialty trades, the Scope Gap Playbook's chapter on trade-specific scope gaps is the most detailed reference available.

Section 3: Inferred Work

Inferred work is the category that generates the most expensive surprises. These are items the drawings or specs require without naming a responsible party. Under "readily inferable" contract language, the GC often absorbs them.

Three documented examples from the Scope Gap Playbook:

Use this checklist for inferred work:

Check Item Pass / Flag / N/A Notes
Temporary protection of finished work is assigned to a specific trade.
Testing, inspection, and certification requirements are named with a responsible party.
Material protection on site (storage, lay-down, coverings) is specified in at least one scope.
Work described in specifications but not on drawings is explicitly included or excluded.
Specialty items (lead-lined assemblies, acoustic treatments, mass timber) are traced to a specific scope package.

Section 4: Division 1 Requirements

Division 1 (General Requirements) is where the most broadly applicable obligations live. It is also where subcontractors most often assume the GC is covering everything.

Check Item Pass / Flag / N/A Notes
Submittals, shop drawings, and O&M manual requirements are assigned.
Commissioning obligations for mechanical, electrical, and specialty trades are reflected.
Coordination drawing requirements (BIM, clash detection) are named.
Mock-up requirements are assigned (curtainwall, tile, finishes).
Project-specific site constraints (access hours, noise bylaws, phasing) are reflected where relevant.

Section 5: Addenda and Revision Coverage

Addenda are the most common source of post-award disputes. A scope package written at tender and not updated at award is an open invitation to a sub saying "that wasn't in my number."

Check Item Pass / Flag / N/A Notes
All addenda issued through tender close have been reviewed against this scope package.
Addenda-driven drawing revisions are reflected in the scope (new details, revised plans).
Addenda-driven specification changes are reflected (substitutions, clarifications).
The sub's bid was confirmed as including all addenda (confirmed in writing or recorded in bid tabulation).

Section 6: Commercial Terms and Scope Boundaries

Scope packages are not just technical documents. The commercial language determines who carries risk when something is ambiguous.

Check Item Pass / Flag / N/A Notes
Inclusions are listed explicitly. Not just exclusions.
Exclusions are specific, not generic ("all work not shown on drawings" is not an exclusion).
Allowances and unit rates are confirmed and documented.
Scope aligns with what the sub priced. Any deviations from their bid are noted and reconciled.
Readily inferable work that creates GC exposure is identified and risk-accepted or mitigated.

How to Run the Review Without Adding Days to Buyout

The objection to any pre-buyout checklist is time. Here is how to make it fit into a real workflow.

Assign the review before award, not after

The best time to start the review is during bid levelling. If your team is already comparing scope packages from multiple subs, they are already doing a version of this check. Build the template into the levelling process rather than treating it as a separate step.

Use it as a team handoff document

If the estimator who built the scope is not the one writing the subcontract, the template bridges the gap. A completed review gives the contracts team the context they need without a 45-minute debrief call.

Set a threshold, not a perfect score

Not every flag requires resolution before the contract goes out. The goal is to make sure every flag is a conscious decision. "We know this is a risk and we accept it" is a defensible position. "We didn't notice" is not.

Automate the first pass where you can

Provision's Scope Agent generates trade-specific scope packages directly from digital drawings, specifications, and project documents. It flags inferred items and coordination gaps before you reach buyout, and it traces every scope item to the exact drawing or spec page. That means the pre-buyout review starts from a more complete baseline, and your estimators spend their time on judgment calls rather than gap hunting.

ProWest Constructors cut estimating time by 50% on the first project they scoped with Provision, saving three to four days. See the ProWest case study for the full picture.

The Eight Habits That Prevent Scope Gaps at Source

A pre-buyout review catches what has already slipped through. The Scope Gap Playbook's eight habits prevent the slippage in the first place. The two work together.

The habits most directly relevant to buyout readiness are:

Read all eight habits in the Scope Gap Playbook.

Frequently Asked Questions

What is a pre-buyout scope package review?

A pre-buyout scope package review is a structured check of a subcontract scope package before the contract is issued. It confirms that scope is complete, coordination items are assigned, addenda are reflected, and commercial terms are clear. The goal is to catch gaps before they become change orders, not after the sub is on site.

How long does a pre-buyout scope review take?

A thorough review using a structured checklist takes 20–30 minutes per trade package. That time is typically recovered on the first clarification call or change order it prevents. For complex MEP or envelope packages, budget 45 minutes.

What are coordination flags in a scope package?

Coordination flags mark work that sits between two trades, where neither scope explicitly names who is responsible. Examples include embed supply and setting between concrete and steel, penetration sealing between mechanical and drywall, and blocking between drywall and millwork. Provision's Q3 2026 Scope Gap Index found coordination flags in 74% of 1,290 scope packages reviewed.

What is inferred work, and why does it matter at buyout?

Inferred work is work the drawings or specifications require without naming a responsible trade. Under readily inferable contract language, the GC often absorbs these items if no sub has included them. A $300K lead-lined glass omission and a $400K missed roof cover board are documented examples from GC interviews in the Scope Gap Playbook.

Should Division 1 requirements be in every scope package?

Division 1 obligations that apply to a specific trade should be reflected in that trade's scope package. Submittals, commissioning, BIM coordination, and mock-up requirements are the most commonly missed. If they are only in the owner's contract and not in the subcontract, enforcement becomes a conversation rather than a contractual right.

How does Scope Agent help with pre-buyout review?

Provision's Scope Agent generates trade-specific scope packages from digital project documents, flagging inferred items and coordination gaps before buyout. Every scope item is traced to the exact drawing or spec page. That gives the pre-buyout review a more complete starting point and reduces the time estimators spend on gap hunting versus decision-making.

Where can I find more on subcontract scope language?

The Scope Gap Playbook chapter on subcontract language covers how scope language creates or closes GC exposure, including readily inferable clauses, exclusion anti-patterns, and the five commercial terms that matter most at buyout. It is available at provision.com/ebooks/scope-gap-playbook/subcontract-language-scope.

Catch scope gaps before buyout, not after.

Scope Agent flags coordination items and inferred work before your subcontracts go out.

See Scope Agent

Share

Ask AI about Provision

Share

Ask AI about Provision