Phases, not tasks
Organize the SOW into 3–5 phases with named outputs. Tasks-level scoping invites scope creep — phase-level scoping invites change orders, which is what you want.
Assumptions are pricing levers
Every assumption in the SOW is a hedge. List them explicitly: client provides X, decisions made in Y days, access granted to Z. When one breaks, you have a documented basis to re-price.
The template outline
Engagement Objectives
- Business outcome (not deliverable)
- Success metric
- Decision-maker named
Phases & Deliverables
- Phase 1: Discover (output: findings memo)
- Phase 2: Design (output: target operating model)
- Phase 3: Implement (output: go-live)
- Phase 4: Stabilize (output: handover pack)
Assumptions
- Client provides SMEs at X hrs/week
- Decisions made within 3 business days
- Existing tooling remains in place
Change Control
- What triggers a change order
- Pricing basis (T&M rate card)
- Approval path
Frequently asked questions
Should a consulting SOW include pricing?
Include total fee and phase-level fee breakdown. Hide the daily rate unless the client explicitly asks.
How do I protect against scope creep?
Tight phase definitions, explicit assumptions, and a documented change-order process triggered by any deviation.