What a good SOW contains
A statement of work is easy to check against if it has these sections:
- Purpose: why the project exists and the outcome the client wants.
- Scope of work: the tasks the team will carry out.
- Deliverables: the specific things handed over.
- Schedule: milestones and dates.
- Acceptance criteria: how both sides will agree a deliverable is done.
- Exclusions and assumptions: what is not included, and what the plan depends on.
- Payment terms: the fee and when it is due.
A short example
For a website redesign, the scope of work might read: redesign and build eight page templates from approved wireframes, migrate up to 60 existing pages, and deliver in three milestones over ten weeks. Copywriting, photography and hosting changes are excluded. Each milestone is accepted when the client approves it in writing.
The exclusions do most of the work. A request for new copy is then clearly a change, not something the team quietly absorbs.
Keeping delivery tied to the scope
A scope of work only protects margin if the work is compared against it while it happens. In Worksynk the agreed milestones and budget live on the project, so new work that does not roll up to a milestone, or hours running ahead of progress, are visible before the invoice.