Preconstruction — Bidding & Procurement

Scope of Work (SOW)

The written definition of exactly what a contractor or trade is responsible for.

Quick Answer

A scope of work (SOW) is the written definition of the work a contractor or trade is responsible for on a project, including what's included and excluded. It translates drawings and specifications into a clear statement of deliverables and boundaries. A precise SOW is the reference every bid, contract, and change order is measured against, so ambiguity in it drives disputes.

The Full Picture

A scope of work exists to remove ambiguity about who does what. Drawings and specs describe the finished building, but they don't neatly say where one trade's responsibility ends and the next begins. The SOW makes those boundaries explicit — in writing — so that when it's time to bid, contract, and build, everyone is working from the same understanding of the work.

Mechanically, a good SOW lists the specific work included, the work explicitly excluded, the applicable specification sections and drawings, and the interfaces with adjacent trades. It's written at the seams: the electrical SOW says whether it includes low-voltage cabling; the concrete SOW says whether it includes embeds set for other trades. The exclusions are as important as the inclusions.

In practice, the SOW is the document everything else is measured against. A bid is a price for a scope; a change order is a change to a scope; a dispute is almost always an argument about scope. When a SOW is vague — 'furnish and install per drawings' with no boundaries — each party fills the gap with the interpretation that favors them, and the seams become claims.

For preconstruction, writing tight trade scopes is what makes bids comparable and contracts enforceable. A GC that hands subs a clear SOW per package gets back bids that cover the same work and levels them cleanly. A GC that leaves scope implicit gets bids built on divergent assumptions and spends the buyout untangling them. Scope definition is the quiet foundation of the whole bid phase.

Real Examples

→Explicit exclusions: The framing SOW states it excludes fire-caulking of penetrations, forcing that scope to be assigned elsewhere rather than assumed by everyone or no one.
→Trade interface: The mechanical SOW specifies that the electrical sub provides final power connections to equipment, defining the seam so neither trade double-carries or drops it.
→Vague scope dispute: A SOW reading only 'site work per civil drawings' triggers a claim when the sub argues that offsite utility work was never part of their price.

Common Misconceptions

People assume: The drawings and specs already define the scope of work.

Actually: They define the finished product, not the division of responsibility between trades. Two subs can read the same drawings and reasonably assume different boundaries. The SOW exists precisely to make those boundaries explicit where the documents leave them implied.

People assume: A scope of work only needs to say what's included.

Actually: Exclusions are just as important. The disputes come from the gray areas — work that could belong to either of two trades. A SOW that states what's excluded, and how it interfaces with adjacent trades, is what closes those gaps before they become claims.

Does MeltPlan Solve This?

Yes — direct fit

Writing scope of work for each trade is exactly what MeltPlan's document product automates. Its AI reads your construction drawings and specifications and identifies the scope of work per trade, drafting structured, package-ready scopes in place of days of manual writing. Because the scope is derived directly from the documents, the trade boundaries are defined up front rather than left for subs to assume.

Generate trade scopes from your drawings →

Frequently Asked Questions

What should a construction scope of work include?

The specific work included, the work explicitly excluded, the applicable drawings and specification sections, and the interfaces with adjacent trades. A strong SOW is written at the seams between trades, so no piece of work is double-assigned or dropped.

What's the difference between a scope of work and a specification?

A specification describes the quality and requirements of materials and workmanship; a scope of work defines who is responsible for which portions of the work. The spec says what good looks like; the SOW says whose job it is to deliver it.

Why do scope gaps cause disputes?

Because work that isn't clearly assigned to one trade is either priced by no one or claimed as extra later. When a SOW leaves a seam ambiguous, each party interprets it in their own favor, and the gap surfaces as a change order or a claim during construction.

Who writes the scope of work?

On the GC-to-subcontractor side, the general contractor's preconstruction team writes a scope of work for each trade package, derived from the design documents. The design team sets requirements through drawings and specs, but dividing that into trade responsibilities is the GC's job.

Related Terms

Bid PackageThe bundle of drawings, specs, and scope a GC sends a trade so subs can bid.Bid LevelingNormalizing subcontractor bids to the same scope so you compare equal numbers.Bidding Process (Construction)How work gets priced and awarded, from soliciting bids to signing a contract.Bid AnalysisEvaluating bids on scope, price, and risk to find the best value, not just the lowest.Subcontractor PrequalificationVetting a subcontractor's capacity, finances, and safety before they're allowed to bid.PreconstructionEverything a contractor does to plan, price, and de-risk a project before ground breaks.Quantity TakeoffMeasuring exactly how much of everything a project requires, straight from the drawings.

More Preconstruction — Bidding & Procurement Terms

Sources

  1. Construction Specifications Institute (CSI) — MasterFormat & SectionFormat standards
  2. AIA Contract Documents — Owner–Contractor and subcontract agreements
MELTPLAN