A scope of work is the precise definition of what a contractor or subcontractor will do, what materials they will supply, what the quality standard is, and — critically — what is not included. The exclusions section is often more important than the inclusions: an explicit exclusion prevents a dispute. An undisclosed assumption creates one.
The scope of work is distinct from the contract (which governs the legal relationship) and the drawings and specifications (which describe the design intent). The scope ties them together — it identifies which drawings apply, which specification sections govern, and which elements are the contractor's responsibility versus someone else's. When written well, it makes the division of responsibility unambiguous before a single worker shows up on site.
Construction time tracking software connects to scope of work through cost codes: each defined scope element maps to a cost code in the construction timesheet app. When the scope is clearly defined, cost codes can be set up to match it — and labor tracked against each scope element reveals whether the work is progressing within the hours estimated for that element.
Scope of work = the written definition of what work is to be performed, by whom, to what standard, within what schedule, with what division of responsibility for materials, permits, and coordination.
Not the same as:
Who writes the scope:
When the owner or architect provides a scope that is vague, GCs have a choice: propose a more specific scope before contract execution, or carry the risk of scope ambiguity throughout the project. The better choice is always to resolve ambiguity before signing.
Explicit, specific description of every component of the work the contractor will perform.
Wrong (vague):
Contractor shall perform all mechanical work for the project.
Right (specific):
Contractor shall furnish all labor, materials, tools, equipment, and supervision to perform the following work in accordance with Mechanical Drawings M-001 through M-048 and Specification Sections 15000–15900:
- Furnish and install all HVAC equipment per the equipment schedule on drawing M-020
- Furnish and install all supply, return, and exhaust ductwork, including insulation, diffusers, registers, grilles, and accessories
- Furnish and install all hydronic piping, including insulation, valves, expansion tanks, and accessories
- Complete equipment startup and commissioning, including all required tests and balancing
- Provide all required penetrations, sleeves, and firestopping in GC-furnished structure
- Submit and obtain all required mechanical permits
- Provide as-built drawings and O&M manuals at project completion
Level of specificity: Each task is described clearly enough that a field superintendent can confirm whether it's done. "All mechanical work" requires interpretation. "All ductwork, insulation, diffusers, registers, grilles, and accessories" does not.
Reference the drawings: Every scope of work should include a specific drawing list or drawing revision reference. "Drawings M-001 through M-048, revision date [X]" is unambiguous. "The mechanical drawings" is not — there may be multiple revisions, and the sub needs to know which one governs.
The most important section most scopes of work omit or underwrite. Every ambiguous item — anything that could be interpreted as either party's responsibility — belongs in the exclusions.
Wrong: No exclusions section.
Right:
The following work is specifically excluded from this subcontract and is the responsibility of others:
- All electrical power supply to mechanical equipment (by electrical subcontractor)
- Building automation system (BAS) and controls wiring and programming (by controls subcontractor under separate contract)
- Concrete equipment pads and housekeeping pads (by general contractor)
- Chemical water treatment for hydronic systems (by owner's service vendor)
- Domestic cold and hot water supply connections to HVAC equipment (by plumbing subcontractor)
- Temporary heat during construction
- Any work related to plumbing fixtures or domestic water systems
Common scope boundary disputes — always address explicitly:
|
Scope Area |
Common Ambiguity |
Address With |
|---|---|---|
|
MEP rough-in |
Sleeves and penetrations — who provides? |
Explicit statement in each MEP sub's scope |
|
Electrical |
Power to equipment — HVAC, elevators, kitchen equipment |
"Electrical power supply to [equipment] by electrical sub" |
|
Painting |
Which surfaces? Ceilings, doors, frames? |
List by room type and surface |
|
Demolition |
What's included — hazmat abatement? |
Explicit inclusion or exclusion of abatement |
|
Site work |
Where does site work end and building work begin? |
Reference to a defined site boundary |
|
Roofing |
Gutters, downspouts, roof penetrations, flashing |
Item-by-item inclusion/exclusion |
|
Flooring |
Substrate preparation — who patches/levels? |
Explicit responsibility assignment |
|
Cleanup |
Debris removal — who hauls? |
Named responsible party |
Every document the contractor must comply with, organized by type.
Contract documents governing this scope:
Regulatory requirements:
Owner-provided documents:
The scope of work must state when the work must happen — not just what must be done.
Required schedule elements:
Float: Address float explicitly if the project schedule includes float in the sub's milestone. Does the float belong to the project or to the sub? AIA contracts give the project float to the project — not to any individual subcontractor.
The scope must specify the quality standard — what "correct" looks like.
For materials:
For workmanship:
For systems performance:
Specific quality standards prevent post-completion disputes about what "acceptable" means. A sub who argues their framing is workmanlike faces a very different conversation than one who argues their work meets Level 4 finish where Level 5 was specified.
Construction involves multiple trades working in the same space. The scope must assign coordination responsibility — who coordinates with whom for what.
Standard coordination requirements:
Owner-contractor coordination:
Who pulls the permits — and who pays for them.
Common permitting assignments:
State explicitly:
"Subcontractor shall obtain and pay for all permits required specifically for the mechanical work, including the mechanical permit and any required equipment permits. The GC shall hold the building permit. All permit fees are included in the subcontract price."
Permit inspection responsibility: Who calls for inspections, who is present during inspections, and what happens if work fails inspection. Typically the permit holder calls for inspection and is responsible for failed inspection corrections.
When scope is not yet fully defined at contract execution, allowances establish a budget for undefined items — with a defined process for adjusting when the scope is finalized.
Allowance format:
"The subcontract price includes an allowance of $[X] for [specific item, e.g., finish hardware, specialty lighting, tile pattern]. The actual cost of [item] will be determined by the owner's selection. If the actual cost is less than the allowance, the subcontract price is reduced by the difference. If the actual cost exceeds the allowance, the subcontract price is increased by the difference plus [markup percentage]."
What belongs in an allowance: Items where the owner hasn't made a selection yet, items with pricing contingent on field conditions, and items whose quantity isn't determinable until design is further developed.
What doesn't belong in an allowance: Work the contractor can price with reasonable certainty. Using allowances to defer pricing for defined scope transfers risk to the owner — who may not understand that's what's happening. Explain allowances clearly.
Included:
Excluded:
Included:
Excluded:
Included:
Excluded:
A well-written scope of work maps directly to the job cost code structure. Each major scope element becomes a cost code — and the construction time keeping app captures labor against each code.
Example mapping:
|
Scope Element |
Cost Code |
|---|---|
|
Concrete formwork |
03.100 |
|
Concrete reinforcing |
03.200 |
|
Concrete placement |
03.300 |
|
Concrete finishing |
03.400 |
When a worker clocks in via the construction time clock app and selects cost code 03.100, their hours track against the formwork budget — enabling the PM to compare actual vs. estimated hours for that specific scope element. The more precise the scope definition, the more useful the cost code data.
Scope changes and cost codes: When an approved change order adds scope, a new cost code is added for the change order scope — tracking the change order cost separately from the base contract. This keeps the base contract cost clean and the change order cost isolated.
Despite the best-written scope, gaps appear during construction — work that isn't clearly in anyone's scope, or work that falls between two scopes.
Step 1: Identify the gap early. The longer a scope gap goes unaddressed, the more expensive it is. A gap identified in design development is resolved with a drawing revision. The same gap identified mid-construction requires a change order, possible rework, and schedule impact.
Step 2: Determine responsibility. Review the contract documents — drawings, specs, and scope — to identify where the responsibility lies. Is it ambiguous? Does the prime contract language resolve it? Do local trade customs assign it?
Step 3: Resolve in writing before proceeding. Issue a directive or change order before the work is performed. "Figure it out and we'll deal with it later" creates cost disputes after the fact.
Step 4: Document the gap and resolution. RFI, meeting minute, or email chain documenting the gap discovery, the parties involved, and the resolution. If the gap required extra cost, that cost goes into a change order — not into a sub's scope as undocumented extra work.
Defining scope by reference to "all work shown on drawings" Drawings show design intent — not contractor responsibility. Two contractors can look at the same drawing and have different interpretations of who does what. Write out the responsibility explicitly.
No exclusions section Every experienced contractor writes their own mental exclusions list and prices accordingly. Without a written exclusions list, those mental exclusions are invisible — and disputes arise when the owner or GC assumed they were included.
Vague quality standards "Good quality" and "workmanlike manner" are the minimum — and they're minimum because they're vague. Specific finish levels, tolerances, and performance criteria eliminate interpretation.
No coordination responsibilities MEP coordination failures are among the most expensive field problems in construction. Assign coordination responsibility in the scope — who is responsible for resolving conflicts, by what deadline, in what format.
Missing permit assignments "Contractor shall obtain required permits" is ambiguous when multiple contractors are on site. Name who gets each permit.
Undefined scope boundaries for adjacent trades The boundary between the plumbing sub's scope and the mechanical sub's scope is often unclear — especially for domestic water connections to HVAC equipment, floor drains adjacent to mechanical equipment, and similar crossover items. Define the boundary explicitly in both scopes.
Before writing:
Scope document:
Before issuing:
TaskTag Features
Related Blog Posts