What a statement of work actually is
A statement of work, usually shortened to SOW, is not the document that wins the client. That is the proposal. It is not the document that gives them a price either; that is the quote. A statement of work comes after both of those, once the client has already said yes. Its only job is to say, in plain and specific language, exactly what you are delivering and exactly what you are not.
Most disputes between freelancers and clients do not come from bad work. They come from a mismatch between what the client assumed was included and what the freelancer thought they had agreed to. A clear statement of work closes that gap before it can open.
Be precise about what is included
Vague deliverables are the root of most scope disputes. “A new website” can mean almost anything to a client. “A five-page site with a homepage, about page, services page, contact form, and one round of content migration” cannot be misread. Write deliverables as concrete, countable things: how many pages, how many revisions, which formats, which platforms. If you catch yourself writing something a client could reasonably interpret two different ways, rewrite it until they could not.
Out of scope deserves equal attention
It is tempting to spend all your effort on the included list and leave the excluded list as an afterthought, or skip it entirely. Do not. The out-of-scope section is what protects you when a client assumes something is free that was never part of the deal: ongoing hosting, extra revision rounds, stock photography, content writing, or anything else common to your kind of work. State it with the same specificity you gave the deliverables. A short, generic line at the end covers whatever you did not think to list by name: anything not listed under deliverables is considered outside this scope.
Say how a change in scope gets handled
Clients ask for “just one more small thing” on almost every project. A good statement of work includes one general line for this, agreed up front rather than negotiated awkwardly in the moment: additional work outside this scope will be reviewed and quoted separately before it begins. You do not need to invent a specific change-order fee or process here, a plain statement of the principle is usually enough to make a later conversation much easier.
Common mistakes
- Writing deliverables in vague, feel-good language instead of specific, checkable statements.
- Skipping the out-of-scope section entirely, leaving boundaries to assumption.
- Promising a change-order process is free or automatic rather than agreeing it will be quoted separately.
- Sending a proposal or a quote and calling it a statement of work; each document has a different job.