Statement of Work: What It Is and How Agencies Use It

What a statement of work is

A statement of work (SOW) is a signed document that defines the work your agency will deliver, the timeline for delivery, the cost, and the criteria for acceptance. It is the single reference point both sides use when someone asks "Is this included?" or "When is this due?"

The SOW sits between the proposal and the kickoff. The proposal sells the work. The SOW defines it precisely enough that both parties know what "done" looks like. If the proposal says "redesign the website," the SOW says "design and build 12 pages in Webflow, deliver by June 15, with two rounds of revisions per page."

Both the agency and the client sign the SOW before any work begins. This is not a formality. A signed SOW is a written agreement on scope, cost, and timeline. Without it, you are relying on email threads and verbal conversations to define the engagement. Those do not hold up when disputes arise.

What goes in a statement of work (for agencies)

A complete SOW covers nine areas. Skip any of these and you create a gap that will surface mid-project, usually at the worst possible moment.

SOW sections

Project overview and objectives

What the project is, why the client is doing it, and what success looks like
Keep this to 2-3 sentences: it sets the context for everything below

Deliverables

A complete list of what the agency will produce
Be specific: "12-page Webflow website" not "a website"
Ambiguous deliverables are the primary source of scope disputes

Timeline and milestones

Key dates for drafts, reviews, and final delivery
Tie milestones to payment where possible
If the project runs in phases, define each phase separately

Revision rounds and acceptance criteria

How many revision rounds are included per deliverable
What counts as "approved" (written sign-off, not verbal)
Two rounds per page is a common agency standard

Fees and payment schedule

Total project cost, deposit amount, and milestone payments
State when invoices are issued and how many days the client has to pay
Late payment terms and any interest or pause clauses

Roles and responsibilities

Name the client's point of contact and the agency's project lead
Define client obligations: content delivery deadlines, feedback turnaround, system access
A delay caused by the client is still a delay; document who owns what

Out-of-scope exclusions

What is explicitly not included in this engagement
List common assumptions: copywriting, photography, stock images, hosting fees, ongoing maintenance
This section prevents "I assumed that was part of the project" conversations

Change order clause

How changes to the agreed scope will be handled
Any work outside the SOW requires a signed change order with its own timeline and cost
Reference your change order process so the client knows the mechanism exists

Termination and kill fee clause

What happens if either party cancels mid-project
Define the notice period and what the client owes for work completed to date
A kill fee (typically 25-50% of remaining project value) protects your lost capacity

Statement of work vs scope of work

These terms get used interchangeably across the industry. They are related but not identical, and the distinction is practical, not academic.

A scope of work defines the boundaries of the work itself: what will be delivered, what is excluded, and how revisions are handled. It answers the question "What are we building?"

A statement of work is broader. It includes the scope of work plus payment terms, timeline, roles, termination clauses, and change order processes. It answers "What are we building, and on what terms?"

Most agency SOWs contain a scope section inside them. If you write a scope of work as a standalone document, you still need a separate agreement covering payment and legal terms. A statement of work combines both, which is why it is the more common format for agency-client agreements. Read more about the distinction in our scope of work handbook entry.

Statement of work for retainers vs projects

The billing model drives the SOW structure. A project SOW and a retainer SOW cover the same ground, but the details differ in ways that matter for billing, renewals, and capacity planning.

Project SOW

Fixed deliverables tied to a defined outcome
Timeline runs from kickoff to delivery date
Payments tied to milestones (deposit, midpoint, final)
Scope changes handled through change orders
Project closes after sign-off and final invoice

Retainer SOW

Monthly deliverable budget or hours allocation
Rolls forward each month with renewal terms defined
Monthly invoicing on a fixed schedule
Unused hours: define whether they roll over or expire
Cancellation requires a defined notice period (30-60 days typical)

The key difference: A project SOW protects against scope creep by defining everything up front. A retainer SOW protects against ambiguity by defining what "a month of work" includes and what happens when the client asks for more. Both need a change order clause, but for retainers the more common issue is capacity overages, not scope changes.

When a SOW needs to change: amendments vs change orders

Client requirements shift. Timelines move. A SOW is not a document you sign and forget. The question is how you handle changes without renegotiating the entire engagement every time.

For changes to a single deliverable (adding a page, changing a feature, extending a deadline), issue a change order. A change order is a short, signed addendum that modifies one part of the SOW without reopening the whole agreement. It has its own cost and timeline.

For changes that affect the overall engagement (doubling the project scope, replacing the project lead, shifting from fixed-fee to retainer), amend the SOW itself. Both parties sign the amendment. This is more involved than a change order but less disruptive than starting from scratch.

The rule of thumb: If it changes one line item, use a change order. If it changes the nature of the engagement, amend the SOW. Having both options defined in the original document makes this process faster when it comes up. And it will come up. See our full guide on change orders for the mechanics. For context on how this fits into the broader website project delivery process, start there.

Frequently Asked Questions

What is a statement of work?

A statement of work is a formal document that defines the scope, timeline, deliverables, costs, and responsibilities for a project. Both the agency and client sign it before work begins.

What is the difference between a statement of work and a scope of work?

A statement of work is the broader document: it includes payment terms, timeline, and responsibilities. A scope of work focuses specifically on deliverables and exclusions. In practice, agencies often use the terms interchangeably.

Does a statement of work need to be a legal contract?

No, but it should be signed. A clear, plain-English SOW signed by both parties is enforceable as a contract in most jurisdictions. Have a lawyer review your template once, then use it repeatedly.

How do I update a statement of work mid-project?

For small changes to a single deliverable, issue a change order. For significant changes to the overall engagement, amend the original SOW with both parties signing the amendment.

What should I include in a retainer statement of work?

Define the monthly deliverable budget or hours, what is included each month, the renewal terms, how unused capacity is handled, and the notice period for cancellation.

Related Terms

Website Project Delivery

The structured process of running a client walkthrough, collecting formal sign-off, and handing off a completed website — covering pre-launch checks, the delivery call, and post-launch documentation.