What to Include in a Statement of Work

Scope disputes, indefinite revision loops, and unpaid final invoices are predictable results of specific SOW failures — vague deliverables, no acceptance criteria, relative milestone dates, no named client authority. Every failure has a corresponding clause that prevents it. The problem is that most people writing a SOW for the first time do not know which sections are the dangerous ones until the dispute is already happening.

What a SOW does that nothing else can

A contract governs the relationship — IP, liability, termination. A SOW governs the engagement — what specifically is delivered, when, in what format, and how you know it is complete. On Upwork, Fiverr, and every other freelance platform, the platform handles payments and basic dispute resolution. It does not provide a SOW. Every scope dispute on those platforms traces back to the absence of a written, signed statement of what was to be delivered and how completion would be determined.

The eight sections — and where each one fails

1. Project description

One paragraph establishing shared context. Failure mode: skipping it because it seems obvious. When a deliverable is ambiguous in a dispute, the project description is where interpretation starts. "Obviously understood" at the start becomes "we had different understandings" when there is money at stake.

2. Scope of work

Every deliverable by name, quantity, format, and definition of done. Vague language does not just create ambiguity — it actively enables the client to claim more than you intended to deliver.

3. Out of scope

An explicit list of what you will not do. Failure mode: omitting it because it seems obvious. Anything not excluded is implicitly included in the client's expectation. By the time the dispute is happening, "that was never included" is your position against "I naturally assumed it was" — and assumptions are hard to beat without documentation.

4. Deliverables and milestones

Each deliverable with a calendar due date tied to payment. Failure mode: relative dates. "Week three" becomes unenforceable the moment kickoff is delayed — and the client who caused the delay now controls whether you are behind schedule. Calendar dates remove this argument entirely.

5. Acceptance criteria

The review period, how feedback must be delivered, the number of revision rounds, and a deemed-acceptance provision. This is the most consequential section in the document for collecting your final invoice. Without a review period and deemed-acceptance clause, the client can be "unavailable to review" indefinitely. With it, silence within the review window is contractual acceptance — and your invoice is due.

6. Payment terms

Total fee, milestone schedule, net terms, and explicit statement that final deliverables are withheld until final payment is received. Failure mode: releasing finals before payment. Once the client has the files, your leverage is gone and your only option is collections or court.

7. Change order process

Any work outside the scope section requires a signed change order before it begins. Failure mode: acting on verbal requests. Every "just one more thing" agreed verbally creates an obligation with no record, no fee, and no timeline adjustment — and no way to prove what was agreed when the client cannot remember authorising payment for it.

8. Assumptions and dependencies

What the client must deliver, and by when. Failure mode: omitting it. When the client delivers assets three weeks late, the project is behind schedule — but without a dependency clause, you cannot demonstrate the delay was theirs. With it, timeline adjustments are automatic and documented from the contract itself.

The coherence problem generic templates cannot solve

Each section must reference the others precisely. Acceptance criteria that reference deliverables must match the scope section exactly. Milestone dates must account for review periods plus revision rounds. The out-of-scope list must anticipate what this client, in this industry, is likely to assume is included. A SOW produced by filling in a generic template has sections that do not reference each other coherently — and the disputes it fails to prevent are the expensive ones.