What to include in a statement of work (SOW), with a template outline

A statement of work (SOW) is the document that turns “yes, let’s do it” into a shared, specific understanding of the job. A good one prevents most scope disputes before they start.

What to include

1. Parties and background

Who the agreement is between, and a sentence or two on the purpose of the project.

2. Objectives

What the work is meant to achieve. This helps both sides judge whether a change request is in or out of scope.

3. Scope of work

The activities you’ll carry out, described specifically enough that a third party could tell whether they were done.

4. Deliverables

Each thing the client will receive, with format and quantity: “10 page templates in the agreed design system”, not “website pages”.

5. Out of scope

What isn’t included. Listing likely assumptions (copywriting, stock imagery, third-party licences) saves arguments later.

6. Timeline and milestones

Key dates, what triggers each milestone, and what you need from the client to meet them, such as content, access or feedback within a set number of days.

7. Acceptance

How deliverables are reviewed and approved, how many rounds of revisions are included, and what happens if feedback isn’t given in time.

8. Fees and payment schedule

The price, how it’s broken down, the deposit, milestone payments, payment terms and how extra work is charged. See how to get paid faster.

9. Change control

How changes are requested, estimated and approved before work starts on them.

10. Terms and signatures

Reference to your general terms (or the master agreement), and signatures from both sides.

Tips for a SOW that holds up

• Use numbers and names rather than adjectives.
• Tie payments to deliverables or dates, not to vague progress.
• Make client responsibilities explicit; delays often start there.
• Keep one signed version, and record any changes in writing.

Frequently asked questions