Scope creep doesn't start with an unreasonable client — it starts with an ambiguous sentence. A good scope of work is specific enough that "is this included?" always has an answer written down before anyone asks it.

1. Project summary

{{Two sentences: what is being built/delivered and why. Reference the master agreement or proposal it attaches to.}}

2. Deliverables (what IS included)

3. Exclusions (what is NOT included)

The section that earns its keep. List the adjacent things clients commonly assume:

• {{e.g. Copywriting — client provides final text}}
• {{e.g. Stock photo / font licenses — billed at cost}}
• {{e.g. Post-launch maintenance beyond the {{N}}-day fix window}}
• {{e.g. Additional page templates, languages, or platforms}}

4. Assumptions

• Client provides {{materials}} by {{date}}; delays shift the timeline day-for-day.
• Feedback arrives consolidated, from one authorized person: {{Name}}.
• {{N}} revision rounds per deliverable are included; a "round" is one consolidated set of changes.

5. Standards and environment

{{Browser/device support, brand guidelines, accessibility target, tooling — whatever "done correctly" depends on.}}

6. Change requests

Anything outside sections 2–5 is a change. Changes are welcome: they're estimated in writing ({{rate or fixed quote}}), approved by the client, and appended to this SOW before work begins. Verbal requests aren't scope.

7. Schedule and fees

{{Milestone table with dates and amounts, matching the payment terms in your services agreement.}}

Writing rules

• Countable nouns beat adjectives: "3 concepts" not "several concepts".
• Every deliverable needs an acceptance test a stranger could apply.
• If you catch yourself writing "etc.", stop and list the items or exclude them.