How detailed should deliverables be?

As detailed as you need to be unambiguous. "Logo design" is too vague; "Logo design: 3 concepts presented in week 4, refined to 1 final by week 6, delivered as vector + PNG + JPG in light and dark variants by week 8" is enforceable.

What if scope changes mid-project?

Issue a Change Order — a short amendment to the SOW that adds the new work and any fee/timeline impact. Both parties sign before the new work starts. Without Change Orders, scope creep eats your margin.

Scope of Work (SOW)

Detailed work specification — usually attached to a Master Services Agreement or contract.

Customise

SOW number

Date

Parent MSA reference

Client

Provider

Project name

Project objectives

Deliverables (numbered list)

Milestones + dates

Project fee (USD)

Payment schedule

Assumptions + exclusions

Live preview

STATEMENT OF WORK (SOW)

SOW #: SOW-2026-001                    Date: May 4, 2026

This Statement of Work is issued under and incorporates by reference the following parent agreement:
  Master Services Agreement dated 2026-01-15 between Acme Inc. and Beta Consulting LLC

Between:
  CLIENT:   Acme Inc.
  PROVIDER: Beta Consulting LLC

──────────────────────────────────────────────────────────────────────

1. PROJECT NAME
Q3 Brand Identity Refresh

2. OBJECTIVES
1. Refresh Acme's visual identity to support the modernised positioning.
2. Deliver brand guidelines that internal teams can use without further consulting input.
3. Equip the marketing team with templates ready to deploy at launch.

3. DELIVERABLES
1. Discovery report from stakeholder interviews (~20 pages, week 2)
2. Three logo concept directions, each with rationale (week 4)
3. Refined logo with full color/typography system (week 6)
4. Brand guidelines PDF, 30 pages (week 7)
5. Social media template kit, 5 templates (week 8)
6. Email signature template (week 8)

4. MILESTONES & TIMELINE
Week 0:  SOW signed, kickoff meeting
Week 2:  Discovery report delivered
Week 4:  Three concepts presented
Week 6:  Final design approved
Week 8:  All deliverables shipped

5. PROJECT FEE
Total: $18,500.00

Payment schedule:
30% on SOW signing
30% on concept approval (week 4)
40% on final delivery (week 8)

6. ASSUMPTIONS AND EXCLUSIONS
Assumptions: Client lead is available for weekly 30-min check-ins; existing brand assets accessible within 1 week of kickoff; up to 2 rounds of revisions per phase included.
Exclusions: Photography, video, paid ads, post-launch maintenance.

7. CHANGE REQUESTS
Any changes to scope, deliverables, or timeline must be agreed in a written Change Order signed by both parties before work on the change begins. Change Orders may include revised fees and revised deadlines.

8. ACCEPTANCE
Each Deliverable will be reviewed by Client and either accepted, or rejected with specific written feedback, within 5 business days of submission. Failure to respond within 5 business days constitutes deemed acceptance. Provider has 5 business days to address rejections; this cycle may repeat for the number of revision rounds specified in Section 6.

9. INCORPORATION
This SOW is governed by the terms of the parent Agreement referenced above. In the event of conflict between this SOW and the parent Agreement, this SOW controls for matters specific to the project described herein.

CLIENT                                         PROVIDER

By: _____________________________     By: _____________________________
Name: Acme Inc.           Name: Beta Consulting LLC
Title: ___________________________     Title: ___________________________
Date: ____________________________     Date: ____________________________

About this template

A Statement of Work is the project-specific document attached to a Master Services Agreement (MSA). The MSA covers the relationship terms (payment, IP, confidentiality, liability) once; each new project gets its own SOW with deliverables, dates, and fees. This pattern is standard for consulting and agency relationships because it lets clients add projects without renegotiating the legal terms each time. The single most-skipped section is "Acceptance" (Section 8) — without an explicit acceptance/rejection cycle and a deemed-acceptance default, projects drag indefinitely while you wait for sign-off. Five business days with deemed-acceptance after silence is the industry standard. The "Assumptions and Exclusions" section is the second-most important — it limits scope-creep arguments by being explicit about what's NOT included.

When to use it

Each project under an existing MSA with a service provider.
Defining a specific scope inside an ongoing consulting engagement.
Agency-client relationships where projects vary widely.
Multi-phase implementation projects where each phase needs its own SOW.

What to include

Reference to the parent MSA.
Project name + business objectives.
Numbered list of deliverables.
Milestone schedule with target dates.
Project fee + payment schedule.
Assumptions and exclusions.
Change request process.
Acceptance / rejection cycle.

Frequently asked

Yes — but then the SOW needs to include the legal terms an MSA would normally cover (IP, confidentiality, liability, governing law). Many consultants do this for one-off projects. The downside: you re-negotiate those terms for every project.

⚠ Legal disclaimer. This template is provided for informational purposes only and is not a substitute for legal advice from a qualified attorney. Always consult a licensed professional before using this document for any binding agreement.