Statement of Work (SOW) Template Builder

What a statement of work template contains

A statement of work says what will be delivered, by when, how it will be judged complete, what it costs, and what happens when the work changes. A template earns its place only if it forces the four things people skip: acceptance criteria, exclusions, dependencies and change control.

• Header — project, client, start and end dates.
• Deliverables — numbered, each with a description, an acceptance criterion, a due date and an amount. A deliverable with no acceptance criterion is flagged.
• Acceptance review window — the business days the client has to accept or reject. Each deliverable's acceptance deadline is computed from its due date, skipping weekends and the holidays you list.
• Out of scope — the exclusions, written down. This is the section that ends the argument.
• Assumptions — what the price depends on being true.
• Client dependencies — what you need from them, and when.
• Change control — the threshold at which a change becomes a change order, and the rate it is billed at.
• Commercial terms — payment terms, alongside the deliverable total the builder adds up.

Statement of work vs scope of work

The scope of work is a section; the statement of work is the document that contains it. The scope says what will and will not be done. The SOW adds the parties, the dates, the acceptance test, the money and the change process that make the scope enforceable.

In practice the two names get used for the same file, and the harm in that is specific: a scope of work with no acceptance criterion and no change threshold is a description of work rather than an agreement about it, and the gap surfaces at the first disputed invoice.

Scope of work example

The dependency carries a date for the same reason the deliverable does — a dependency with no date cannot be shown to have been late.

One deliverable row, in the format the Deliverables field accepts:

Target-state architecture | Written architecture for the migrated estate, walked through with the client team | Client architecture lead accepts in writing, or returns comments | 2026-10-09 | 24000
Client dependency: read-only access to the production estate by 2026-09-15.
Acceptance review window: 5 business days — so the 9 October deliverable is accepted on 16 October unless it is rejected in writing before then.