A statement of work says what you'll do, by when, for how much, and how both sides will know it's done.
That last part is the one most people skip. It's also the one that saves the most fights.
This guide shows how to write a statement of work, one section at a time, with a short sample at the end.
What is a statement of work?
A statement of work, or SOW, is the plan for one project, in writing, agreed by you and the client.
People mix it up with a scope of work. They're not the same. Atlassian's guide to the SOW puts it well. The statement of work is the main file. The scope of work is one part inside it, the part that says what work gets done.
So the SOW holds the scope, plus the dates, the price, the roles and the rules for sign-off.
SOW vs proposal vs contract
These three get blurred. Each one has a different job.
- A proposal is a pitch. It says, here's the problem, here's how we'd solve it, here's the price. You send it before they say yes.
- A contract, such as a master services agreement, sets the legal terms. Payment, who owns the work, how either side can end the deal. You sign it once.
- A statement of work sits under that contract. It covers one project. Each new project gets a new SOW, and the terms in the contract still apply.
This setup saves time. You agree on the legal terms once. Then each new job is just a short SOW.
The sections of a statement of work
Keep the headings the same each time. Clients learn where to look.
- Overview: two or three lines on the project and why it matters to the client.
- Goals: what should be true when you're done? Make it something you can check.
- Scope: what's in. Then, just as clearly, what's out.
- Deliverables: the things you'll hand over. Files, pages, reports, each named on its own line.
- Timeline: key dates, and what each one depends on.
- Roles: who does what, on both sides. Name the one person who signs off for the client.
- Sign-off rules: how each item gets approved, and how long the client has to reply.
- Price and payment: the fee, when each part is due, and how you'll invoice.
- Changes: what happens when the client wants something new.
- Assumptions: the things you're counting on. Like the client sending copy by a set date.
Ten headings. Most SOWs fit on two or three pages.
How to write the scope so it holds
Scope is where projects go wrong. Be plain and be specific.
Say you're a designer building a booking site for a small yoga studio. A loose scope says, "Design and build a new website." A tight one says, "Design and build four pages: Home, Timetable, Book a Class and Contact, with class booking set up. Two rounds of changes per page. Copy, photos and the timetable come from the client."
Then list what's out. "Not included: online shop, logo design, ongoing upkeep." That one line can save you weeks.
Words to watch
Some words sound clear but mean different things to each side. Pin them down.
- "Support" needs a number. How many hours, and for how long?
- "Unlimited changes" is a trap. Name how many rounds.
- "Final" needs a name. Final for who?
- "As soon as you can" needs a date.
- "A website" needs a page count, and a list of what's on each page.
If a word could start an argument later, fix it now. It costs a minute.
Who should write the statement of work?
Most of the time, you should. You know the work best, and you know where it tends to go wrong.
Write a draft. Send it. Then walk through it on a short call. Ask the client to push back on anything that seems vague. A change now costs nothing. A change in week five costs a lot.
Sign-off rules, or acceptance criteria
Acceptance criteria are the tests that say a thing is done. Without them, "done" is a feeling. And feelings change.
Write them for each item you hand over:
- What it is, in plain words.
- What it must do or include.
- How many rounds of changes are in the price.
- Who approves it, and how.
- How many work days they have to reply.
Some teams add one more line. If there's no reply in that time, the item counts as approved. Talk this through with the client up front, so it isn't a surprise.
How to handle change requests
Clients will ask for more. That's normal. It's often a good sign.
The SOW should say how you'll handle it. Keep it short:
- The client asks for the change in writing.
- You reply with the cost and the effect on dates.
- They approve in writing before any work starts.
- You add it to the SOW as a dated change note.
This isn't about being strict. It's about keeping trust. Nobody likes a surprise bill.
A short statement of work example
Here's a sample, cut down, for a made-up project.
- Overview: New four-page site for a small yoga studio, so people can see the timetable and book a class.
- Goal: Site live by the end of week six, with booking working on phones and laptops.
- Scope: Design and build four pages and set up class booking, with two rounds of changes each. Not included: online shop, logo work, booking app fees.
- Timeline: Designs in week two, build in weeks three to five, launch in week six.
- Roles: The designer builds. The owner sends copy, photos and the class timetable by week two and signs off on each page.
- Sign-off: The owner has three work days to approve or ask for changes.
- Payment: Half at the start, half at launch.
- Changes: New requests are priced in writing and approved before work starts.
That's enough to start. Real ones add more detail. But the bones stay the same.
Quick SOW answers
What should a SOW include?
An overview, goals, scope, the items you'll hand over, a timeline, roles, sign-off rules, price and payment terms, and a change process. List what's out of scope too.
How do I start off a work statement?
Start with a short overview. Who the client is, what the project is, and why it matters to them. Two or three lines are enough.
What is an example of a statement of work?
Say a designer builds a four-page booking site for a yoga studio. The SOW names the pages, the booking setup, the rounds of changes, the dates, who signs off and when payment is due. The sample above shows the shape.
A clear SOW protects both sides
A good statement of work reads like a clear email, not a legal maze. If a client can't follow it, it won't protect either of you.
For the legal terms, have a lawyer look over your main contract once. Then reuse it.
To save the setup time, the Retainer Agreement Claude Skill pairs a main agreement with an SOW template, so each new job starts from the same base. For the wording, the HD24 prompt pack gives you 25 prompts for SOWs and proposals. Sitting on the client side of the table? Read how to hire a creative agency.