What is a Statement of Work?

A Statement of Work (SOW) is a document that defines exactly what a project will deliver, when, and on what terms. It typically sits under a master services agreement and covers scope, deliverables, milestones, payment, assumptions, and how changes are handled. It turns a vague engagement into a clear, agreed plan.

What is the difference between scope and deliverables?

Scope describes the boundaries of the work — what is and isn't included overall. Deliverables are the specific tangible outputs the client receives, such as a design file, a deployed app, or a report. Listing both prevents scope creep and disputes about what was promised.

Why include an out-of-scope section?

Stating what is explicitly NOT included is the single most effective way to prevent scope creep. It sets clear expectations and gives you a reference point when the client requests extra work, which then flows through the change-order process.

How should I tie payments to milestones?

Linking each payment to an accepted deliverable or milestone protects both sides: the client pays for progress they can verify, and you get paid as you go rather than only at the end. Common patterns are a deposit, progress payments, and a final balance on acceptance.

Is my SOW stored anywhere?

No. The document is assembled in your browser and your draft stays on your device only. Nothing is uploaded or shared.

Statement of Work (SOW) Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Turn a fuzzy engagement into a clear, agreed plan

A Statement of Work is what separates a professional engagement from a misunderstanding waiting to happen. It pins down the scope, the exact deliverables, the timeline, who pays what and when, the assumptions everyone is relying on, and how changes get handled. This builder walks you through each section and assembles a complete, well-structured SOW you can copy or print and attach to your agreement.

How it works

The tool collects the standard sections of a SOW and renders them in a conventional order:

Background — the context and objective of the project.
Scope — what’s included, plus an explicit out-of-scope list.
Deliverables — the concrete outputs the client receives.
Milestones — each with a target date, building the timeline.
Payment schedule — amounts tied to milestones or percentages.
Assumptions — the conditions the plan depends on.
Change-order process — how additional work is requested, priced, and approved.

Each list (deliverables, milestones, payments) is editable, and the milestone dates form the project timeline. Everything is concatenated into one clean document.

Tips and notes

Be specific in deliverables: “Responsive marketing site, 6 pages, deployed to production” beats “a website”.
Always fill the out-of-scope section — it’s your best defence against scope creep.
Tie at least the final payment to acceptance of the last deliverable, and define what acceptance means.
Keep the change-order process simple: any change is documented, estimated, and approved in writing before work starts.