Scope of Work Template

# Scope of Work

**Project:** [Project name]
**Client:** [Client name]
**Provider:** [Your name / Studio]
**Effective date:** [Date]
**Related agreement:** [e.g. Master Services Agreement dated [date], or this SOW stands alone]

---

## 1. Purpose

[One paragraph describing the project and the outcome it delivers. State the
business objective, not just the tasks.]

## 2. Deliverables

| # | Deliverable | Description | Format |
|---|---|---|---|
| 1 | [Name] | [What it is] | [PDF / repo / file] |
| 2 | [Name] | [What it is] | [Format] |
| 3 | [Name] | [What it is] | [Format] |

## 3. Out of scope

The following are explicitly excluded and, if required, will be handled as a
change request (Section 7):

- [Item not included]
- [Item not included]

## 4. Acceptance criteria

Each deliverable is considered accepted when:

- [It meets the description in Section 2 and any agreed spec.]
- [Client reviews within [5 business days] of delivery.]
- [Client provides written acceptance, or a list of specific defects to fix.]
- [If no response within [5 business days], the deliverable is deemed accepted.]

## 5. Timeline & milestones

| Milestone | Deliverable(s) | Target date |
|---|---|---|
| [M1] | [Deliverable 1] | [Date] |
| [M2] | [Deliverable 2] | [Date] |
| [Final] | [All remaining] | [Date] |

## 6. Assumptions & dependencies

- [Client provides [inputs / access / content] by [date].]
- [One named client contact is responsible for approvals.]
- [Provider is not responsible for delays caused by late client feedback.]

## 7. Change control

Any change to deliverables, timeline, or fees must be requested in writing.
The provider will respond with the impact on scope, schedule, and cost. Work on
the change begins only after both parties approve it in writing.

## 8. Fees & payment

| Item | Amount |
|---|---|
| [Fixed project fee] | [$0,000] |
| **Total** | **[$0,000]** |

[Payment schedule — e.g. [50%] on signature, [50%] on final acceptance.
Invoices due within [14 days].]

## 9. Sign-off

**Client:** ______________________  **Date:** ____________

**Provider:** ______________________  **Date:** ____________

How to use this template

1. 1

   Copy or download the template

   Grab the markdown with Copy markdown or Download .md.

2. 2

   Fill deliverables precisely

   Name each deliverable and its format. This section is what makes a SOW enforceable.

3. 3

   Write acceptance criteria

   State how each deliverable is judged complete and the review window, so 'done' isn't a matter of opinion.

4. 4

   List exclusions

   Spell out what's not included; anything else becomes a change request.

5. 5

   Set change control and fees

   Keep the written change-request rule and fill in the payment schedule.

6. 6

   Export a clean PDF for sign-off

   Paste into Markpdf, apply your brand, and export a PDF ready for signature.

What to include in a scope of work (and why)

Purpose

The objective in business terms. Mistake: jumping straight to tasks with no stated outcome.

Deliverables

Named outputs and formats. Mistake: listing effort instead of artifacts.

Acceptance criteria

How each deliverable is accepted, with a review window. Mistake: no criteria, so "done" is subjective.

Exclusions

What's not included. Mistake: leaving it implicit.

Change control

A written process for scope changes. Mistake: handling changes by email and forgetting to bill them.

Scope of work example

A filled-in snapshot for a small data project. Illustrative only.

FAQ

What is a scope of work?

A scope of work defines exactly what a project will deliver — objective, deliverables, acceptance criteria, exclusions, timeline, and terms — so both parties can point to it if there's a question later.

What's the difference between a scope of work and a statement of work?

They overlap. A statement of work is the broader engagement document (scope, schedule, payment, terms); the scope of work is the part describing the work and deliverables. Many small projects use one document for both. See our statement of work template for the fuller version.

What makes good acceptance criteria?

Criteria a stranger could check: what the deliverable must include, the review window, and what happens if there's no response. Vague acceptance ('client is happy') is the most common source of delivery disputes.

How do I handle changes after signing?

Use the change-control section: new or changed work is requested in writing, you respond with the impact on scope, schedule, and cost, and work starts only after both sides approve. It keeps 'small extras' from eroding the project.

Is a scope of work legally binding?

It depends on how it's executed and what agreement it sits under. Treat it as a business document, keep terms clear, and have a lawyer review contractual language for your situation. This is not legal advice.