How to Write a Freelance Statement of Work

The project ended. Or you thought it did. The client had different ideas. "Can you take a look at those last few pages while you're wrapping up? Shouldn't take long." It wasn't discussed. The brief was a three-sentence email. Nothing said it was out of scope, because nothing said what the scope was.

This is scope creepThe gradual expansion of a project beyond what was agreed. Almost always starts before the work does, in the gap between what both parties assumed was included.. It starts before the project does, in the gap between what you meant and what they heard. The Project Management Institute found that 52% of projects experience scope creep — not during execution, but because expectations were never written down.

An SOWA per-project document that defines what you're building, when it's due, and what it costs. It's what you point to when a client asks for more than you agreed. (Statement of Work, or engagement agreement) turns what you both think you agreed to into a document you both actually signed. Deliverables, timeline, what's not included. When someone asks for those extra pages six weeks in, you don't need to argue about what was implied. You look at the document.

What an SOW actually is

An SOW is a written agreement that defines the scope, deliverables, timeline, and payment terms for a specific project. Federal contracting law defines it as a description of work to be performed. For freelancers, it's the document you pull out when there's a disagreement about what was agreed.

Unlike a general services contract (which covers liabilityLegal responsibility if something goes wrong. A contract's liability clause limits how much you can be held accountable for. Without one, exposure is uncapped., confidentialityA mutual agreement to keep certain information private. Covers client plans, proprietary processes, and unreleased work. Often formalized as an NDA., and how disputes get resolved), an SOW is project-specific. You write a new one each time. It answers: what are we building, what does "done" look like, and what aren't we building?

An SOW is also where you figure out what you haven't thought through yet. Writing the acceptance criteriaThe specific conditions that define "done." Work is complete when it meets these — not when the client simply likes the direction. Vague acceptance criteria is how revision cycles never end. feels uncomfortable? That usually means you haven't defined what you're actually handing over. Better to find that out before the kickoff call than three weeks in.

Five sections every SOW needs

1. Scope of work

What you're doing. Specific. Not "website redesign" — "redesign of the five pages listed below, developed in Webflow and handed off as a published, live site." Name every deliverableA specific, named output you've committed to produce. Not "design work" — the five pages in the SOW, in Webflow, as a live site. If it isn't named, it isn't a deliverable.. If there's a list, write the list.

2. Out of scope

The section most freelancers skip and then regret. Name what you're not doing. "Content writing is not included. SEO configuration is not included. Ongoing maintenance is not included." Every line here is a conversation you won't need to have later.

3. Timeline

Start date, milestone dates, delivery date, client review windows, and what happens when the client is late with feedback. "If client feedback is delayed by more than three business days, the delivery date shifts by the same number of days." That clause does more work than most of the rest of the document.

4. Revision policy

How many revision rounds are included, and what counts as a revision. "Two rounds of revisions are included. A revision round is a consolidated set of feedback delivered in a single document within five business days of delivery. Additional rounds are billed at $[X]/hour."

5. Payment terms

DepositUpfront payment before work begins. Standard is 50% for project work. Commits the client before you've spent an hour — and means you have something in hand before delivering anything. amount (50% upfront is standard for project work). Final payment timing: on delivery or on approval, but be specific. Late fees. Kill feeA payment owed if a client cancels after work has begun. Typically 25–50% of the remaining balance. It compensates you for time blocked and work already done — not a penalty. if the project gets cancelled mid-work. Cover this here or in your invoice, but cover it before the work starts.

Is an SOW legally binding?

Yes — if it meets the standard requirements for a contract: offer, acceptance, and something of value exchanged on both sides. A signed SOW is enforceable. Under basic contract law, many freelancers already have a binding agreement without realizing it, just from exchanging signed documents that define the work and payment.

An SOW works best alongside a master services agreement (MSAA standing contract covering the rules of your working relationship — liability, IP ownership, and how disputes get resolved. Signed once, applies to every project with that client.), a standing contract that covers liability, IPOwnership rights to creative work. The key question: who can use, sell, or modify the deliverables? Standard freelance practice: IP transfers to the client on final payment. ownership, and dispute resolution, and holds constant across every project you do with that client. If you only have time for one document, start with the SOW. It covers what matters right now.

Why this matters before you start

Scope creep is expensive. The PMI estimates that organizations waste $1 million every 20 seconds due to poor project performance, most of it from unclear requirements at the start. One scope-crept project can erase a month of margin.

The SOW closes that gap before it opens. Once you and the client agree in writing on what "done" looks like, every additional request is clearly outside that line. You can still say yes. But now you're choosing to say yes, and you can charge for it.

---

Written by Robin Kelmen with AI assistance. Sources linked inline. Last reviewed February 2026.