Scope creep rarely starts with a bad client. It starts with a small, reasonable request, then another, each too small to mention. By the end the project is half again as large and nobody can point to the moment it happened. A clear statement of work (SOW) is the cheapest protection against that.
What a statement of work is for
A statement of work describes one project: what you will deliver, by when, for what fee, and how it will be approved. It sits under your service agreement, which covers the ongoing relationship. A good one is short, specific and readable by someone who was not in the room. Our statement of work template gives you the headings.
Describe the goal, then the deliverables
Start with two or three sentences on what the client wants to achieve, in their words. Then list the deliverables as nouns you could point to: a five-page website, a set of 20 edited photographs, a monthly report. Give each one an owner on your side. If a deliverable cannot be pointed to, it is a hope, not a deliverable.
Write what is out of scope
This section does the most work. Think about what a client could reasonably assume is included and is not: extra languages, additional pages, ongoing hosting, content writing, extra rounds of changes. Write each one down plainly. It is not unfriendly. It is the clearest way to say “we thought about this”.
Count the rounds, and the days
Say how many rounds of changes are included, and how many working days the client has to respond to each. Both numbers need to be real. “A couple of rounds” will be remembered as three. Say what happens if a response takes longer: usually the schedule moves by the same number of days.
Say what you need from the client
Most delays are caused by waiting for something: access, content, a decision. List what you need and by when, and name one person at the client who answers questions and one who approves. For the first days of a project, our onboarding checklist pairs well with it.
Agree how change works
Changes will come. A good SOW does not forbid them; it says how they are handled. For example: the client describes the change, you reply with the effect on cost and date, and nothing starts until they agree. The first time this happens it feels formal. The second time it feels like a relief, for both sides.
A quick check before you send
- Could someone new read this and know what is being delivered?
- Is there a number for rounds of changes, and for response days?
- Is every date a date, not “soon” or “ASAP”?
- Does the client know what you need from them, and when?
- Has someone qualified reviewed the contract wording that matters?
On that last point: our templates are plain outlines of topics, not legal advice. Have a professional review the agreements you rely on, especially around ownership, liability and payment.