Scope of work template: Deliverables, timeline & change control

SOW vs Proposal vs Contract: The Critical Distinction

These three documents serve different purposes at different stages of the engagement. Confusing them is one of the most common operational mistakes in agencies.

Document	Purpose	Tone	When Used	Binding
Proposal	Sells the work, demonstrates approach	Persuasive	Pre-signing, sales conversation	Indicative only
Statement of Work	Defines exactly what, when, how	Operational, specific	At signing, references the contract	Yes
Contract	Sets legal terms	Legal, formal	At signing, frames the SOW	Yes

The proposal answers 'what will you do and why.' The SOW answers 'exactly what, when, and how.' The contract answers 'what are the legal terms.' In practice, you send a proposal. The client says yes. The SOW translates the agreement into specifics. The contract references the SOW and binds both parties.

For agencies, the rule of thumb: a one-page proposal at sales stage, a 4 to 8 page SOW at signing, and a 2 to 6 page master services agreement (MSA) covering legal terms. See our MSA vs SOW guide for how these interact.

The ten required sections

A statement of work template for agencies must contain these ten sections. Skipping any of them creates ambiguity that costs you time, money, or both.

1. Project overview

A brief summary of what the project is, why it exists, and the agreed outcome. Two to four sentences. This is the only section that overlaps with proposal language, so keep it tight.

Sample language:

'This Statement of Work covers the design and development of a new marketing website for [Client]. The project will replace the current site (built in 2020) with a responsive, content-managed site optimized for lead generation. The engagement runs from [Start Date] through [Target Launch Date].'

2. Scope of work

The core description of what you will do. Break into workstreams or phases. Be specific enough that a third party reading it could understand the boundaries.

Sample language:

'The scope includes: (1) Discovery and strategy: 4 stakeholder interviews, competitive review of 5 named competitors, content audit of existing site; (2) UX and design: sitemap, wireframes for 8 page templates, visual design for homepage plus 3 sub-page templates; (3) Development: build in Webflow with responsive implementation and on-page SEO setup per the SEO specification; (4) Content migration: migration of 18 existing pages per the attached content matrix; (5) QA and launch: testing across 4 named browsers and 3 device types, bug remediation, go-live execution.'

The specificity in 'review of 5 named competitors' or 'wireframes for 8 page templates' is what makes this section enforceable later. Vague descriptions like 'comprehensive design phase' invite disputes.

3. Deliverables

A numbered, concrete list of what the client will receive. Treat this like a packing list: if something is not on it, it is not in.

Sample language:

'Deliverables include: (1) Discovery report and content matrix (PDF); (2) Sitemap and wireframes (Figma file, view access); (3) High-fidelity designs for homepage, 3 sub-pages, and 1 blog template (Figma); (4) Fully functional website in staging and production environments; (5) Migrated content for 18 pages per the content matrix; (6) QA report and launch handoff document including credentials, training video, and support contacts.'

Avoid vague entries like 'support' or 'consultation' unless you define them precisely with hours or frequency.

4. Timeline and milestones

When work happens and when key approvals or payments are due. Tie milestones to deliverable handoffs and to payment events.

Sample language:

'Milestone 1 (Week 2): Discovery complete and report delivered. Milestone 2 (Week 4): Wireframes approved. Milestone 3 (Week 6): Visual design approved. Milestone 4 (Week 10): Development complete in staging. Milestone 5 (Week 12): Production launch. Client feedback at each approval gate is due within 5 business days. Delays in feedback shift the project timeline day-for-day.'

5. Acceptance criteria

How you and the client agree that a deliverable is 'done.' Without this, 'it's not quite right' can stretch indefinitely.

Sample language:

'Designs are considered approved when Client provides written sign-off via email or the client portal approval mechanism, or does not request revisions within 5 business days of delivery. Development is considered complete when all items in the attached QA checklist pass and Client signs the staging approval. Launch is considered complete when the site is live on the production domain and Client confirms go-live within 2 business days.'

Tie approval to a specific action (a signature, a portal click, a written confirmation) and a specific timeframe. Silence-equals-approval clauses prevent indefinite review windows.

6. Out of scope (critical section)

Agencies often leave this section out, and it is the one that prevents the most disputes. It states what you will not do. When a client asks for something later, you point here: 'That is out of scope. We can handle it via a change request.'

Sample language:

'Out of scope and not included in this engagement: (1) Copywriting or original content creation beyond migration of existing content; (2) E-commerce functionality, membership areas, or user accounts; (3) Third-party integrations including CRM, marketing automation, and analytics platforms beyond standard GA4 setup; (4) Ongoing maintenance, hosting, or post-launch support beyond the 30-day stabilization window; (5) Design revisions beyond 2 rounds per deliverable; (6) Work on pages or features not listed in the content matrix; (7) Translation or multi-language implementation; (8) Custom CMS development.'

Scope disputes usually start where the SOW was silent. The more specific your Out of Scope section, the fewer disputes you will have. See our scope creep prevention guide for a deeper playbook.

7. Change request process

How scope changes are handled. Every addition should follow the same path: written request, then estimate, then approval, then work.

Sample language:

'Any work outside the defined scope requires a written Change Request. Agency will provide an estimate (incremental timeline and cost) within 5 business days of request. Work will not begin on the change until Client approves the Change Request in writing or via the client portal. Approved changes may extend the project timeline. Small changes (under 2 billable hours) may be handled via email approval; larger changes require a formal Change Request form. All Change Requests are billed at $X per hour or as agreed in the request.'

This clause is what lets you bill for extra work instead of absorbing it.

8. Payment schedule

When and how much the client pays. Tie payments to milestones when possible.

Sample language:

'Total project fee: $X. Payment schedule: 40% upon SOW signing ($X), 30% upon design approval ($X), 30% upon launch ($X). Invoices are payable net 15 from invoice date via the AgencyPro client portal. Late payments after net 30 incur a 1.5% per month service fee. Work on the next phase will not begin until the corresponding payment is received and confirmed.'

For retainer engagements, see the retainer SOW structure below. Many agencies use recurring billing for retainers.

9. Assumptions

What you assume to be true. When those assumptions break, you have a basis to re-scope.

Sample language:

'This SOW is based on the following assumptions: (1) Client will provide all necessary brand assets, copy, and platform access within 5 business days of project start; (2) Client will designate one primary approver per the Roles section; (3) Staging and production hosting environments will be available no later than Week 4; (4) Scope is based on the attached content matrix totaling 18 pages; additional pages require a Change Request at $X per page; (5) Site will be built on the latest stable version of Webflow as of the project start date.'

10. Roles and responsibilities

Who does what, on both sides. Client delays (slow feedback, missing assets) are a common cause of project slips. Document the client's obligations to give yourself a basis to push back.

Sample language:

'Agency responsibilities: project management, design, development, QA, content migration, and launch execution per the scope. Client responsibilities: (1) providing content, assets, and platform access by specified dates; (2) designating [Name] as primary approver with sign-off authority; (3) providing feedback within 5 business days at each milestone; (4) final sign-off for launch; (5) timely payment per the schedule above.'

SOW for retainer vs project work

Retainers have a different structure than fixed-scope projects. Instead of a fixed deliverable list, you define capacity and expectations per period.

Project SOW vs retainer SOW: Side-by-side

Element	Project SOW	Retainer SOW
Scope description	Fixed deliverables to project completion	Ongoing services within defined boundaries
Capacity definition	Total project hours or fixed-fee total	Hours or deliverables per period
Timeline	Start date to launch date	Term length with notice provisions
Payment	Milestone-based	Recurring (monthly typical)
Acceptance	Per-deliverable sign-off	Monthly utilization review
Out of scope	What is not in the project	What is not included per period
Change process	Change Request adds to scope	Overage hours, separate SOW for new work
Rollover	N/A	Hours roll, expire, or credit (specify)

Retainer-specific sections

A retainer SOW needs these elements that a project SOW does not:

Term and notice: Length of engagement (typical agency retainer is 6 to 12 months with auto-renew) and how either party can modify or end. Common pattern: 90-day initial commit, then month-to-month with 30-day notice.

Hour or deliverable capacity: Be explicit. '40 hours per month' or '8 blog posts, 4 social graphics, 2 email sequences per month.' For hour-based retainers, time tracking becomes critical to manage the boundary.

Rollover policy: Do unused hours roll over to next month, expire at month-end, or credit to the next period? Many agencies use 'unused hours expire at month-end' to prevent stacking, though some allow 25 to 50% rollover for client flexibility.

Overage handling: What happens when the client needs more than the retainer allocates? Options: bill overage at $X per hour, require a Change Request for any work above the retainer, or pause and discuss tier upgrade. Specify the trigger and the rate.

Reporting cadence: Monthly utilization report showing hours used, deliverables completed, work remaining. Most agencies surface this through their client portal.

Sample retainer scope language

'Agency will provide ongoing content marketing services per the following monthly allocation: (a) 40 hours of strategy, production, and account management time; (b) 8 blog posts averaging 1,500 words; (c) 1 monthly performance review with the Client team. Hours and deliverables are allocated per calendar month and do not roll over. Work exceeding the monthly allocation requires either a Change Request (for one-time scope) or a written agreement to increase the monthly retainer (for sustained higher capacity).'

See our retainer agreements guide for deeper retainer structure detail.

The sample master SOW template

For an agency creating a standardized template, the recommended structure:

[Agency Letterhead]
STATEMENT OF WORK No. [SOW Number]
This SOW is issued under the Master Services Agreement
dated [MSA Date] between [Agency] and [Client].

1. Project Overview
2. Scope of Work
   2.1 Phase 1: Discovery
   2.2 Phase 2: Design
   2.3 Phase 3: Build
   2.4 Phase 4: Launch
3. Deliverables
4. Timeline and Milestones
5. Acceptance Criteria
6. Out of Scope
7. Change Request Process
8. Payment Schedule and Terms
9. Assumptions
10. Roles and Responsibilities

Signed for Agency: ____________________ Date: _______
Signed for Client: ____________________ Date: _______

Keep the template in a system where you can quickly populate per-engagement variables (client name, dates, deliverables, prices) without retyping the structure. Most agencies build this into their CRM or project management tool.