The seven blocks of a usable scope
- Location and boundaries — the exact areas the work covers.
- Work included — described as actions, in the order they happen.
- Materials and specifications — brand, grade, model, or equivalent standard.
- Standards and code references the work will meet.
- Responsibilities — who supplies power, water, access, parking, permits.
- Exclusions — everything a reasonable customer might assume is included but is not.
- Change handling — how additional work gets priced and approved.
Write actions, not nouns
'Bathroom remodel' is not a scope. 'Remove existing tub and surround, dispose of debris, install customer-selected 60-inch tub, waterproof to manufacturer specification, install tile surround to ceiling height' is a scope. Actions can be verified as complete; nouns cannot.
Exclusions are not defensive — they are informative
Customers do not experience exclusions as hostility unless they are discovered late. Listed up front, they read as professionalism and set up the change-order conversation before it becomes an argument. The exclusions that matter most are the ones specific to that site, not the generic paragraph copied onto every document.
The scope has two audiences
The customer reads it to decide. The crew reads it to execute. A scope that only satisfies the first audience produces jobs where the field improvises, and improvised work is unbilled work. Write it so the person doing the job could work from it without a phone call.
Reuse without copying blindly
Templates for repeated work types are the right approach, but every template needs a site-specific pass. The fastest way to create a dispute is to send a template with another job's assumptions still in it.