What Is a Statement of Work (and Do Freelancers Need One)?

If you have worked with larger companies, you may have been asked for a "statement of work" or "SOW." It sounds formal, and for many freelancers it is a bit of a mystery. Is it a contract? Is it the same as a proposal? Do you need one?

Here is what it is, what it contains, and when it is worth writing.

This is general information, not legal advice. For large or high risk projects, have a lawyer review your documents.

The short answer

A statement of work is a document that describes exactly what work will be done, what will be delivered, when, and how it will be approved and paid for. It exists to make sure both sides agree on the details before the work starts.

It is about the work itself. Think of it as the detailed answer to "what, exactly, am I getting?"

Statement of work vs proposal vs contract

These three documents are often confused, because they overlap and some projects combine them.

In practice, the lines blur. A small project might need only one document: a proposal that includes clear scope, deliverables, a timeline, and payment terms, which the client then signs. A larger engagement might involve a proposal to win the work, then a separate statement of work and a contract, often from the client's side.

If you want to see how a proposal can carry most of this detail, our freelance proposal template includes scope, exclusions, timeline, payment, and a signature section.

What goes in a statement of work

A good statement of work answers the questions that cause disputes later.

Purpose and background. One or two sentences on why the project exists.

Scope. What is included. Be specific, with quantities and formats. "Design of five pages in Figma, desktop and mobile" is scope. "Website design" is not.

Out of scope. What is not included. This is just as important as the scope, because it stops the project from quietly growing.

Deliverables. The things you will hand over, in what format, and to whom.

Timeline and milestones. Key dates, and what has to happen on each one.

Acceptance criteria. How the client will decide the work is done. For example, "two rounds of consolidated feedback, with approval given in writing within five business days."

Responsibilities. What you will do, and what the client must provide, such as content, access, and timely feedback. Delays often come from the client side, so write this down.

Payment. The total, the schedule, and what triggers each payment. See how to ask for a deposit as a freelancer for how to structure this.

Assumptions. Anything you are counting on being true, such as "the client supplies final copy by October 30."

Change process. What happens when the client wants something outside the agreed scope: it is quoted, agreed in writing, then done.

A short example

Here is how a few of those sections might look for a small branding project.

Scope: Primary logo with two color variations, a color palette, a typeface recommendation, and a one page usage guide.

Out of scope: Stationery design, website design, packaging, and trademark registration.

Deliverables: Final logo files in SVG, PNG, and PDF. Usage guide as a PDF.

Acceptance: Up to two rounds of consolidated feedback. The project is complete when the client approves the final files in writing.

Change process: Requests outside this scope will be quoted separately before work begins.

Notice how little room this leaves for "I thought that was included."

When a freelancer needs one

You do not need a separate statement of work for every project. A clear proposal covers a lot.

Consider a standalone statement of work when:

• The project is large or runs for months. More moving parts means more room for disagreement.
• The client requires one. Larger companies often have a standard process.
• Several people or teams are involved. A shared document keeps everyone aligned.
• The work is technical or hard to describe. Precision matters more.
• You are working under a master agreement. Some clients sign one contract covering many projects, with a statement of work for each one.

For a typical freelance project of a few weeks, a proposal that includes these elements, signed by the client, usually does the job.

Common mistakes

Vague scope. The single biggest cause of trouble. If two people could read a line and picture different work, rewrite it.

No exclusions. If you do not say what is not included, clients may assume it is.

No acceptance criteria. Without a definition of "done," projects can drag on through endless revisions.

Forgetting the client's responsibilities. If a delay is the client's doing, the document should say so.

Never updating it. If the scope changes, record the change. An outdated statement of work is worse than none.

Does it replace a contract?

Not usually. A statement of work describes the work. A contract covers legal terms such as liability, intellectual property, confidentiality, and termination. They often work together, and sometimes the statement of work is attached to a contract as a schedule.

For smaller projects, many freelancers combine the essentials of both into a single signed proposal. For anything where a lot of money or risk is involved, get proper legal advice about the contract side.

The takeaway

A statement of work is the detailed description of what you will do, what you will deliver, and how everyone will know it is finished. It protects you and the client from misunderstandings.

If you are writing a proposal anyway, you can build most of a statement of work into it. A proposal that is specific about scope, exclusions, timeline, and acceptance wins more work, and, as we cover in why freelance proposals get rejected, vague proposals are one of the most common reasons they do not.

In Draftedly you can write scope, timeline, and payment into one proposal and have your client sign it and pay the deposit on the same page. The free plan includes 10 sent proposals.