What Is a Statement of Work (SOW) and When Do You Need One?

A statement of work stops scope creep before it starts. Here's what goes in one, when to use it, and how to write it in minutes.

A statement of work (SOW) is a document that defines exactly what you will deliver for a client, when you will deliver it, and how much they will pay. It's the written agreement that separates a professional service engagement from a handshake deal. Freelancers who skip it tend to find themselves doing extra work for free because the client "assumed" something was included. Those who use one have a clear reference point every time a project tries to expand. The Contract / SOW Generator creates a professional document in minutes without needing a lawyer.

## SOW vs. Contract: What's the Difference?

The difference between a statement of work and a general contract is scope. A contract covers the legal framework — payment terms, dispute resolution, intellectual property ownership, liability. A SOW covers the project specifics — what deliverables will be provided, what's excluded, what the timeline looks like, and what the revision process is. For longer engagements, you might have a master services agreement (the contract) and individual SOWs for each project under it. For single projects, many freelancers combine both into one document.

## Deliverables: Specificity Prevents Disputes

Every SOW should clearly define the deliverables. Not "design work" but "three logo concepts in vector format, one round of revisions per concept, final files delivered as .AI, .EPS, .SVG, and .PNG in both color and monochrome variants." Vagueness is where scope creep hides. The more specific you are, the harder it is for a client to argue that something extra was implied.

## Timeline and Milestones

Timeline is the second critical element. Don't just state the final delivery date — break it into milestones. "Initial concepts delivered by April 15. Client feedback by April 18. Revisions completed by April 22. Final files delivered by April 25." Milestones create accountability on both sides. When a project runs late because a client took three weeks to give feedback, your milestone log shows whose schedule slipped. Without milestones, everything compresses onto you at the end.

## Revision Policy and Exclusions

The revision policy needs to be explicit. "Two rounds of revisions are included. Additional revision rounds are billed at $150/hour" is unambiguous. "Revisions as needed" is not a policy — it's an open invitation. Specify what constitutes a revision versus a new direction. Changing a headline is a revision. Deciding to pivot from a minimalist style to a maximalist one after delivery is a new scope item.

Exclusions are as important as inclusions. If you're building a website but not doing copywriting, state it explicitly. If you're designing a logo but not printing or applying it anywhere, say so. Exclusions prevent the "I thought that was included" conversation that ends with you either doing free work or souring a client relationship. List three to five things that are clearly out of scope for your specific project.

## Payment Terms Tied to Milestones

Payment terms should mirror the timeline. A common structure for project work is 50% upfront before any work begins, 50% on delivery of final assets. For longer projects with multiple milestones, consider tying payments to milestone completion: 30% at kickoff, 30% at first deliverable, 40% at final delivery. This aligns your cash flow with your workload and gives the client clear expectations about when invoices will arrive. The Invoice Maker makes it easy to issue these milestone invoices when they're due.

## When to Use a SOW vs. a Simpler Agreement

When should you use a SOW versus a simpler email agreement? The threshold is roughly proportional to project size and complexity. For a quick one-hour task billed at your hourly rate, an email confirmation is fine. For anything that spans multiple weeks, involves multiple deliverables, or costs more than a few hundred dollars, a formal SOW protects you. The time to write it (fifteen minutes with the Contract / SOW Generator) is trivially small compared to the time you'd spend arguing about scope without one.

Clients rarely push back on SOWs. Most appreciate them — it demonstrates that you're organised and have done this before. The freelancers who skip formal agreements often do so because they're worried a document will make things feel too formal or scare clients off. The opposite tends to be true: clients who plan to pay you fairly are happy to sign a clear agreement. The ones who want to avoid a written agreement are often the ones you'll later wish you'd had one with.

← More articles | Free SMB Tools