Insights

What a marketing statement of work should actually include⁠

28 September 2026By Dan Chapman

A statement of work that’s just a list of deliverables invites disputes later — not because anyone acted in bad faith, but because “deliverables” alone never captures what’s excluded, who owns what, or what happens if something changes. Here’s what a proper one actually includes.

Beyond the deliverables list

  • Scope boundaries, stated as clearly as the deliverables themselves — what’s excluded, not just what’s included. See the “Not included” line on a fixed-scope audit for what this looks like when done properly.
  • Named ownership for each major deliverable, on both sides — one person, not a team, so accountability is never ambiguous.
  • Assumptions the price depends on — access, data, timely review and approval from the client side — stated explicitly, since a delay on these is one of the most common reasons projects run over.
  • A defined change process. How a scope change gets raised, priced and approved, agreed before it’s needed rather than negotiated mid-project.
  • The review and acceptance point. What “done” actually looks like, and who confirms it.

Why exclusions matter as much as inclusions

Most disputes over scope don’t come from disagreeing about what was promised — they come from one side assuming something was included that was never actually agreed. Writing the exclusions down explicitly, even the obvious ones, removes that ambiguity before it becomes a difficult conversation.

Where this fits into a wider operating model

A good statement of work is one piece of a working lead-to-billing process — the same discipline that makes pricing, delivery and invoicing predictable end to end. See marketing operations for how that fits together, and how pricing works here for how the price itself gets set before the statement of work is written.

A clear marketing brief makes the statement of work far easier to write.

Where to start

If scope keeps drifting on projects even with a statement of work in place, the document usually isn’t the problem — the process around change requests and ownership is. A Strategic Marketing and Operations Review will show you which.

FAQs

What’s the difference between a proposal and a statement of work?

A proposal sells the engagement — the problem, the approach, why you. A statement of work defines it — exact scope, deliverables, timeline, price and ownership. Treating the proposal as the contract is a common source of disputes once work is underway.

What should a statement of work exclude?

Anything a client might reasonably assume is included but isn’t — implementation after an audit, ongoing support after a project ends, work outside the agreed channels or scope. Stating exclusions clearly avoids the more difficult conversation later.

Who should own each deliverable in a statement of work?

One named person on each side for each major deliverable, not a team or a department. Shared ownership on paper tends to mean no real ownership in practice.

How should scope changes be handled once work has started?

With a defined change process agreed up front — how a change is raised, priced and approved — rather than absorbed silently or refused outright. Both erode trust; an agreed process protects the relationship.

Let’s talk

A 30-minute discovery call is free and there’s no pitch. Bring the situation as it is. If I’m not the right fit, I’ll say so, and suggest who might be.

Book a discovery call (opens Cal.com) or send an enquiry