A client once challenged an agency invoice because the team had delivered more work than expected. The agency pointed to the agreed plan. The client pointed to the same document and said it never specified how much work was actually included. The dispute was not really about the invoice. It was about one sentence nobody had written.
An agency scope of work defines what an agency is responsible for delivering, in what quantity, over what period, through which process, and for what fee. It sits between the commercial promise made during the pitch process and the day-to-day work that follows. This guide explains the sections a modern scope needs and the three omissions that cause the most disputes: volume, turnaround, and what happens when something changes.
What the Document Is For
An agency scope of work gives both sides a shared reference point when memories start to differ.
That matters because agency relationships can run for months or years. People change roles, priorities move, campaigns evolve, and the original pitch can become distant history. A useful scope lets the agency and client look back and determine whether a particular piece of work was actually included.
It answers a practical question: Was this part of the agreed work, or is it additional?
That makes the scope particularly important for defining agency deliverables. Instead of saying an agency will “support social media,” for example, a useful scope might specify the number and type of posts, the planning involved, the approval process, and the reporting included.
But a scope is not everything.
It is not a contract. Legal terms such as liability, intellectual property ownership, confidentiality, termination and governing law generally belong in the wider agreement.
It is not a brief. A brief explains the problem, audience, creative direction and desired outcome. The scope explains what the agency has agreed to do in response.
It is not a wish list. If every possible future request is placed into the document, neither side can tell what the agency has actually committed to delivering.
The best scope is therefore specific enough to prevent ambiguity without becoming a document nobody wants to read.
The Sections That Belong in It
A practical scope should cover the following:
- Objectives
State what the work is intended to achieve. Objectives give the deliverables context without pretending that every outcome can be guaranteed. - Deliverables and quantities
List exactly what the agency will produce and how much. “Content support” is vague; “eight LinkedIn posts per month” is measurable. A deliverable without a quantity attached is one of the most common causes of scope disputes. - Team and allocated time
Identify the relevant roles and, where useful, the expected allocation. This helps prevent assumptions that every agency specialist is permanently available. - Process
Explain how work moves from request to production, review and final approval. Keep it practical rather than documenting every internal agency step. - Approval points
Identify who reviews the work and where client approval is required. One named decision-maker is often more useful than a long stakeholder list. - Timelines
Set out delivery windows, review periods and dependencies. This is where client response times need to be documented too. - Fee and what it covers
Connect the agreed work to the commercial model. The reader should be able to understand what the fee buys without turning the scope into a full remuneration schedule. - Reporting
State what reporting is included, how frequently it happens and what it covers. - Review cadence
Define when the scope itself is reviewed. Monthly, quarterly or campaign-based reviews can give both sides a chance to adjust before small changes become major disputes.
A good sow template marketing teams use should make these points easy to find rather than burying them in pages of boilerplate.
Omission One: Volume
The first major omission is volume.
Agencies often describe work using categories rather than quantities: social media management, content creation, campaign support, design, strategy or media planning.
The problem is that categories describe what kind of work is being bought, not how much.
A modern scope should answer three questions:
- How many deliverables are included?
- Over what period?
- What counts as one deliverable?
For example, “three social posts per week” is clearer than “social media content.” But even that may need definition. Three social posts are not necessarily three social campaigns. A campaign could include multiple posts, creative variations, landing-page work, reporting and coordination.
Volume also applies to revisions, meetings, reports and production rounds where those can materially affect workload.
Why is this so often left vague? Because specifying limits can feel restrictive at the beginning of a relationship. Agencies may worry about appearing inflexible, while clients may prefer to preserve room to request things later.
In practice, clarity protects flexibility. Both parties know where the agreed work ends, making it easier to discuss additional work without treating every new request as a negotiation.
Omission Two: Turnaround
The second omission is turnaround.
Agencies usually document when they will deliver something. They are much less likely to document how long the client has to review it.
That creates a predictable problem.
An agency sends creative on Monday. The client responds the following Friday. The agency then has to revise it, send it back, and somehow still hit the original launch date.
The scope should therefore describe both sides of the timeline.
It can specify:
- The expected agency delivery window.
- The client’s review period.
- The number or timing of approval rounds.
- What happens when required information arrives late.
- How launch dates are affected by delayed approvals.
There is no single correct number for every agency relationship. A social campaign, website project and monthly SEO engagement may need very different timelines.
The important thing is that the dependency is visible.
For example, a scope might establish that the agency delivers within an agreed working window, the client provides consolidated feedback within a defined review period, and any delay in receiving feedback may move subsequent milestones.
This is not about blaming the client for delays. It is about making the production chain visible.
A deadline cannot be genuinely shared if only one party has a deadline.
Omission Three: What Happens When Something Changes
The third omission is change management.
Something will change. A campaign will be expanded. A new stakeholder will appear. A product launch will move. A client will ask for another version. An internal priority will suddenly become urgent.
The question is not whether the scope will change. It is what happens when it does.
A useful scope should establish:
- What kind of request triggers a scope-change discussion.
- Who has authority to approve the change.
- Whether the change affects deliverables, timing, resources or all three.
- How any additional work will be priced.
- When the revised work can begin.
Without this mechanism, changes tend to become favours.
“Can you just add one more?” becomes “We thought that was included.”
Or the opposite happens: every adjustment becomes a confrontation over money.
Neither is healthy.
Unmanaged scope changes also create account churn. An agency that repeatedly absorbs extra work eventually becomes less profitable and more frustrated. A client that feels every request produces another unexpected charge may become equally frustrated.
Clear change management creates a third option: acknowledge the change, assess its impact, agree the adjustment, then proceed.
That is much healthier than relying on goodwill until goodwill runs out.
What to Leave Out
A scope becomes less useful when it tries to contain everything.
Legal terms should generally remain in the contract rather than being duplicated in operational documents. Intellectual property, liability, confidentiality, termination and other legal provisions need a proper contractual home.
Creative direction should generally live in the brief. The scope can reference the agreed brief, but it does not need to reproduce every audience insight, brand principle or creative thought.
Details that change frequently should also be treated carefully. If a scope contains dozens of operational details that become obsolete every few weeks, people will stop trusting it as a current source of truth.
The same applies to excessive process documentation. If an agency needs six pages to explain how a request moves between internal teams, the scope has probably gone too far.
The purpose is not to document everything anyone might ever need to know.
It is to make the commercial and operational boundaries of the work clear.
A scope that tries to become a contract eventually becomes too long to use. A scope that is too vague becomes too weak to settle disagreements. The useful middle ground is a short, readable document with enough precision to answer the questions people actually argue about.
Connecting It to the Fee Model
The scope and the fee model have to agree.
This sounds obvious, but mismatches are common.
Fixed fee + open scope = dispute waiting to happen.
If an agency receives a fixed monthly fee but the scope says it will provide unlimited support, the commercial model and operational commitment are pulling in opposite directions.
The reverse can also create problems.
Time-based fee + rigid deliverable list = another mismatch.
If the agency is fundamentally being paid for access to a defined amount of expertise or time, an excessively rigid output list may encourage the client to optimise for volume rather than the work that actually matters.
This is where agency remuneration and scope need to be considered together. The remuneration model establishes how the agency gets paid; the scope establishes what that payment covers. They should reinforce each other rather than operate as separate documents.
The same principle applies to media. If principal media or other commercial media arrangements sit alongside agency services, the scope should make clear which activities are included in the agency’s fee and which are outside it.
The distinction is also important with subscription models. Our [subscription pricing article] focuses on the pricing model itself; this article is about defining the work that sits inside that model. A subscription can still have a scope. In fact, clear boundaries become even more important when clients buy ongoing access through tiers.
The Read
Agency scopes are not necessarily becoming more precise. In some relationships, fee pressure is pushing them in the opposite direction.
When agencies compete heavily on price, both sides can become reluctant to specify exactly what is being bought. The scope is sketched during the pitch process, then rushed into place after the client chooses an agency.
That is backwards.
The pitch should establish the broad promise. The scope should turn that promise into an operational commitment.
The practical test is simple: could someone who was not in the original sales meeting read the scope six months later and understand what the agency owes, what the client owes, and what happens when either side needs something different?
If not, the scope is not finished.
The clause worth adding to your next scope: define the agreed volume, turnaround expectations for both parties, and the process for approving any change before that change becomes work.
