Templates / Statement of Work

Free statement of work (SOW) template

A statement of work turns a vague agreement into a clear plan both sides can hold each other to. This free SOW template spells out exactly what's being delivered, when, for how much — and just as importantly, what's out of scope.

Skip the copy-paste and fill it in visually.

Pair it with a contract

What to include

The parties and project overview
In-scope deliverables — and explicit out-of-scope items
Milestones and a timeline
Acceptance criteria (how "done" is defined)
Fees and a payment schedule
Assumptions and a change-request process
Signatures from both sides

The template

STATEMENT OF WORK (SOW)

Project: [Project name]
Between: [Provider] and [Client]
Date: [date]

1. OVERVIEW
[One paragraph on the project and its objective.]

2. DELIVERABLES (IN SCOPE)
- [Deliverable 1]
- [Deliverable 2]

3. OUT OF SCOPE
[List what is explicitly NOT included, to prevent scope creep.]

4. TIMELINE & MILESTONES
- [Milestone 1] — [date]
- [Milestone 2] — [date]

5. ACCEPTANCE CRITERIA
[How each deliverable is reviewed and approved, and the review
window — e.g. "Client has 5 business days to approve or request
changes."]

6. FEES & PAYMENT SCHEDULE
- [Amount] — [on signing / on milestone / on completion]
- [Amount] — [on ...]

7. ASSUMPTIONS
[What must be true for the timeline/price to hold — e.g. timely
feedback, access to accounts, content provided by Client.]

8. CHANGES
[Any change to scope will be agreed in writing and may adjust
timeline and fees.]

Provider: ____________________   Date: __________
Client:   ____________________   Date: __________

Send it and get paid — free

BuyerSuite turns these documents into the real thing: send invoices and get paid by card, get contracts e-signed, and give clients a branded portal — free to start.

Start free

FAQ

What's the difference between an SOW and a contract?

A contract sets the legal terms of the relationship; a statement of work defines the specific deliverables, timeline, and acceptance criteria for a project. They often go together — the contract references the SOW.

Why list out-of-scope items?

Naming what you won't do is the single best defense against scope creep. It sets expectations early and gives you a clear reference when new requests come up mid-project.

What to include

The parties and project overview

In-scope deliverables — and explicit out-of-scope items

Milestones and a timeline

Acceptance criteria (how "done" is defined)

Fees and a payment schedule

Assumptions and a change-request process

Signatures from both sides

The template

STATEMENT OF WORK (SOW) Project: [Project name] Between: [Provider] and [Client] Date: [date] 1. OVERVIEW [One paragraph on the project and its objective.] 2. DELIVERABLES (IN SCOPE) - [Deliverable 1] - [Deliverable 2] 3. OUT OF SCOPE [List what is explicitly NOT included, to prevent scope creep.] 4. TIMELINE & MILESTONES - [Milestone 1] — [date] - [Milestone 2] — [date] 5. ACCEPTANCE CRITERIA [How each deliverable is reviewed and approved, and the review window — e.g. "Client has 5 business days to approve or request changes."] 6. FEES & PAYMENT SCHEDULE - [Amount] — [on signing / on milestone / on completion] - [Amount] — [on ...] 7. ASSUMPTIONS [What must be true for the timeline/price to hold — e.g. timely feedback, access to accounts, content provided by Client.] 8. CHANGES [Any change to scope will be agreed in writing and may adjust timeline and fees.] Provider: ____________________ Date: __________ Client: ____________________ Date: __________

Send it and get paid — free

BuyerSuite turns these documents into the real thing: send invoices and get paid by card, get contracts e-signed, and give clients a branded portal — free to start.

Start free

FAQ

What's the difference between an SOW and a contract?

Why list out-of-scope items?

Naming what you won't do is the single best defense against scope creep. It sets expectations early and gives you a clear reference when new requests come up mid-project.