Scope of work (SOW)

A scope of work (SOW) is the written description of exactly what a subcontractor is responsible for on a project — the boundary line everything else, including disputes, gets measured against.

Direct answer

What should a subcontractor scope of work include?

A subcontractor scope of work should identify the project and contract documents, define the trade's included work and deliverables, state exclusions and boundary responsibilities, specify materials, equipment, quality and safety requirements, set schedule and coordination duties, assign permits, testing and closeout, and describe pricing, payment, change, notice, and acceptance procedures. Referenced drawings and specifications should be revision-controlled.

Operational completeness check

01

Document basis

Project, parties, agreement, drawings, specifications, addenda, scope exhibits, and revision dates.

02

Included work

Tasks, locations, quantities, materials, labor, equipment, deliverables, and defined trade boundaries.

03

Requirements

Quality, codes, submittals, safety, logistics, protection, cleanup, testing, permits, and inspections.

04

Time and coordination

Milestones, sequence, lead times, access, predecessor work, interfaces, and reporting obligations.

05

Commercial controls

Exclusions, allowances, price basis, payment milestones, change procedure, notices, acceptance, and closeout.

Sources and verification

Official guide

Procore — defining subcontractor scope

Trade-specific tasks, deadlines, materials, resources, quality expectations, permits, inspections, safety, and change procedures in subcontractor agreements.

The governing subcontract controls risk allocation, flow-down terms, insurance, indemnity, payment, notice, and dispute rights. This is a completeness framework, not a substitute for project-specific legal review.

Published July 21, 2026 · Sources verified August 4, 2026 · Research methodology

A SOW is only useful if it's specific. 'Electrical per plans' isn't a scope; it's a placeholder that turns into an argument the first time a plan detail is ambiguous. A real scope of work names the trade's inclusions, exclusions, and the boundary where their work ends and the next trade's begins.

Verbal or emailed scope agreements are common on smaller jobs and are exactly where disputes come from later — one side remembers 'run wire for an outlet' as including the outlet, the other doesn't, and there's nothing written to settle it.

Example

A GC sends a painter a one-line scope: 'paint interior.' Three weeks in, the painter says trim isn't included; the GC says it obviously is. A written SOW naming rooms, surfaces, and finish level would have settled it before the first coat went on.

Next step

Where this shows up in Datumel:

Sub Scope LetterFree

Describe the project and what the sub owns. Get a formal pre-mobilization scope letter with a sign-off line.

Open →