Why it matters for agencies
Most client disagreements are really disagreements about what was promised. A clear SOW turns "I thought that was included" into a short conversation with a document on the table.
How to do it or work it out
Cover the objective, the deliverables, the assumptions, the exclusions, the timeline, acceptance criteria, the client's responsibilities and how changes are handled. Write the exclusions as carefully as the deliverables.
Make acceptance measurable. "The site is approved" is vague; "all pages in the sitemap are live and pass the agreed checklist" is something both sides can verify.
Keep it short enough to be read. A few pages with plain headings are better than a long document nobody opens, and the opening summary should say what is being built and what is not.
A worked example
An SOW for a five-page website lists the five pages, states that copywriting is supplied by the client, allows two rounds of design feedback and sets acceptance as the pages being live and passing a checklist. A request for a sixth page is outside it and goes through a change request. The same SOW says the client will supply all copy by week 2 and give feedback within 5 working days. When copy arrives in week 4, the agency points to the SOW, the delivery date moves by two weeks and nobody is surprised.
Common mistakes
- Listing deliverables but not exclusions. What you will not do is what prevents most disputes.
- Vague acceptance such as client satisfied. The client can then withhold approval indefinitely.
- Leaving out the client's responsibilities. Late content and slow feedback are common reasons projects slip, so state what you need and by when.