How to write a statement of work

The short answer

A statement of work (SOW) is a document that describes one piece of work in enough detail that a stranger could tell whether it was delivered. It lists the deliverables, what is included and what is not, the timeline and milestones, how the client reviews and approves, the price and payment schedule, and what each side has to provide. It sits under a contract: the contract sets the general rules of the relationship, the SOW sets the specifics of this job.

If you only take one thing from this page: write the exclusions and the acceptance criteria. Those two sections are where projects go wrong, and they are the two most people leave out.

SOW, proposal, quote and contract

The names overlap and clients use them loosely, so it helps to be clear about what each one does.

For a small job, one document often does all four. A short proposal with a scope section, a price, terms and a signature line is a perfectly good SOW and contract in one. For larger clients, the usual pattern is a master services agreement (the contract) signed once, and a new SOW for each project that refers back to it. My guide on invoices, quotes and proposals covers where each one fits in more detail.

The sections a statement of work needs

1. Parties and reference

Who the work is for, who is doing it, the date, and a reference number. If there is a master agreement, name it: "This SOW is issued under the Services Agreement dated 3 March 2026." That one sentence brings in all the legal terms without repeating them.

2. Background and objective

Two or three sentences on why the work exists. This is not filler. When a disagreement comes up halfway through, the objective is what both sides go back to: "The renders are for the product launch page and the retail catalogue" tells you a lot about resolution, format and how many angles make sense.

3. Deliverables

A numbered list of the things you will hand over, each with its format and specification. Specific beats generous here. "Product renders" is a problem. "Six still renders, 4000 by 4000 px, PNG with transparent background, plus one 3000 by 2000 px lifestyle scene in JPG" is a deliverable.

4. Out of scope

What is not included, written out. This is the section that protects your margin. Anything a client could reasonably assume is included but is not should be named: animation, extra angles, source files, model optimisation for web, copywriting, stock licences, printing. A line like "anything not listed under Deliverables is out of scope and will be quoted separately" helps, but named exclusions are much harder to argue with.

5. Timeline and milestones

Start date, the milestones with dates, and the delivery date. Tie each milestone to something both sides can see: "draft renders delivered for review", not "50% done". Say that the dates depend on the client's inputs arriving on time, and what happens to the schedule when they do not.

6. Client responsibilities

What you need from the client and by when: CAD files, brand guidelines, reference photos, access, a named person who approves. Most freelance delays I have seen were waiting for an input, not doing the work. Writing the dependency down makes it visible.

7. Review, revisions and acceptance

How many rounds of revisions are included, what counts as a revision (a change within the agreed brief) versus a change request (a new brief), how long the client has to review, and what happens if they do not reply. Acceptance criteria say when a deliverable is done. A common and fair rule is that a deliverable is accepted when the client approves it in writing or does not raise specific issues within a set number of working days.

8. Price and payment schedule

The fee, how it is split, and when each part is invoiced. Fixed price or time and materials, and if the latter, the rate and any cap. Currency. Expenses, and whether they need approval. If you take a deposit, say so here and say whether it is refundable. The payment terms guide has the common options.

9. Change requests

How new work gets added: in writing, quoted before it starts, and with the effect on the timeline stated. One short paragraph saves a lot of awkward conversations.

10. Sign-off

Names, roles, dates and signatures for both sides. A SOW nobody signed is a draft.

An example statement of work

Here is a full SOW for a typical 3D job, the kind I quote most weeks. Replace the details with your own.

STATEMENT OF WORK  SOW-2026-014
Issued under the Services Agreement dated 3 March 2026

Client:    Northwind Audio Ltd, 12 Harbour Street, Bristol BS1 4RT
Supplier:  Alex Morgan, 3D visualisation
Date:      5 October 2026

1. Objective
Product renders of the new NW-40 speaker for the launch page and the
2027 retail catalogue.

2. Deliverables
2.1 Six studio renders of the NW-40 (front, back, three-quarter left,
    three-quarter right, top, detail of the control panel).
    4000 x 4000 px, PNG, transparent background.
2.2 One lifestyle scene, living room setting, 3000 x 2000 px, JPG.
2.3 Colour variants of 2.1 in black and in oak: 12 additional files.

3. Out of scope
Animation or turntables. Additional angles. Delivery of 3D source
files or textures. Retouching of client photography. Model changes
after the CAD freeze. Stock image or font licences.

4. Timeline
- Start: on receipt of CAD files and the deposit.
- Draft renders (2.1, untextured lighting check): 5 working days
  after start.
- Final renders 2.1 to 2.3: 8 working days after draft approval.
Dates move by the length of any delay in client inputs or feedback.

5. Client provides
Final CAD (STEP or OBJ) by 12 October 2026, material and colour
references, one named approver (Sarah Kim, Product Manager).

6. Revisions and acceptance
Two rounds of revisions on the drafts and one on the finals are
included. A revision is a change within the brief above. Each
deliverable is accepted when approved in writing, or 5 working days
after delivery if no specific issues are raised.

7. Fee and payment
Fixed fee GBP 4,200.00, excluding VAT.
40% deposit (GBP 1,680.00) invoiced on signature, due before start.
60% balance (GBP 2,520.00) invoiced on final delivery, due in 14 days.

8. Changes
Work outside section 2 is quoted in writing before it starts, at
GBP 480 per day, with its effect on the timeline.

Signed for the client: ______________  Date: ________
Signed for the supplier: ____________  Date: ________

How to keep it short and still complete

A SOW does not need to be long. The example above fits on one page and covers everything that usually causes a dispute. Some habits that help:

• Write it from the quote, not from scratch. If your quote already lists the lines, the SOW is the quote plus exclusions, dependencies and acceptance. The quote generator gives you the line items and a PDF to attach.
• Use numbers wherever a word could be argued: pixel sizes, counts, days, rounds, amounts.
• Use the client's words for the objective, and yours for the deliverables.
• Keep the legal terms out. Ownership, liability, termination and confidentiality belong in the contract, so you do not have to renegotiate them every project. The guide on what to put in a freelance contract lists them.
• Price it before you write it. If you are not sure what the job is worth, work out your floor first with the day rate calculator, then estimate the days.

Getting it signed

Send the SOW as a PDF with the quote, and ask for a signature before you start. An email reply saying "approved" is better than nothing, but a signed document with a date is clearer for both of you when a question comes up three weeks later. Signing online is the fastest way to get it back; the guide on getting a proposal signed online covers how to make that quick for the client.

Then do the thing the SOW is for: when a request comes in that is not in section 2, point at section 8, quote it, and wait for a yes before you do it. That is the whole system.

Questions