Scope of work: what to include

A scope of work (SOW) is the shared agreement of exactly what a project includes, excludes, and costs — the thing both sides point to when "was that part of it?" comes up. A vague one invites scope creep; a clear one prevents it. Here's what a strong one contains.

The seven sections every scope of work needs

1. Deliverables — the specific, enumerated things you're producing. "5 pages: home, about, services, contact, blog" — not "a website."
2. Exclusions — what's explicitly not included. This is the most-skipped and most-valuable section. If it isn't excluded, it's assumed included.
3. Timeline & dependencies — key dates, and what they depend on ("first draft Friday, assuming feedback within 48 hours").
4. Price & payment terms — total, deposit, and when each payment is due (e.g., 50% before work begins, 50% before final delivery).
5. Revisions — how many rounds are included and what happens beyond that ("2 rounds included; additional billed separately").
6. Change process — how a new request is handled: quoted and approved in writing before work continues.
7. Final acceptance — what "done" means, so a project can actually close.

The line that does the most work

Strong scope lines follow a pattern: concrete statement + boundary + future implication. "The total is $1,800; 50% is due before work begins; the remaining 50% before final delivery." A price alone protects nothing — the boundary is what holds.