Agency Scope of Work Template: A Free SOW That Prevents Scope Creep

If your SOW says “website redesign” and “ongoing support”, every new client request becomes a debate. This agency scope of work template is built to end that debate early. It sets deliverables with acceptance criteria, caps revisions, lists exclusions and defines a change request process, so an out-of-scope request is obvious when it shows up and easy to bill. Copy the template, fill in the [placeholders], then use the notes, clauses and examples below to tighten it.

What a Scope of Work Should Do for an Agency

After signing, a scope of work has one job: settle questions before they turn into arguments. When a client asks for a fourth social post, a new landing page or “a quick tweak to the logo”, anyone on your team should be able to open the SOW and answer “is this request included?” in under a minute. If it takes a meeting to decide, the document isn't doing its job.

That means writing for the person who will check requests six weeks from now, not for the sales call: quantities instead of adjectives, named exclusions, a revision limit with a definition, and one route for changes.

Scope of Work vs. Statement of Work vs. Proposal vs. Contract

These terms get mixed up, and “SOW” is used for both scope of work and statement of work. In practice:

• Proposal: the pitch: your approach and price, written to win the work.
• Scope of work: the description of the work itself: deliverables, quantities, revisions, exclusions and timeline.
• Statement of work: the scope plus the commercial and process terms: fees, payment schedule, responsibilities and sign-off. Agencies often sign one per project under a master agreement.
• Contract: the legal terms, such as liability, intellectual property, confidentiality and termination. It usually references one or more SOWs.

The template below works as a statement of work template in that sense: the scope, plus the sections that decide what happens when a request falls outside it. If you already have a master agreement, keep the legal terms there and use this document for each project.

Free Agency Scope of Work Template

Copy the block below into your own document and replace every [placeholder]. Delete what doesn't apply, but keep Revisions, Exclusions and Change request process: those three sections do most of the work when a client asks for more. This SOW template assumes a fixed-scope project. For a retainer, set deliverables per month and say whether unused capacity rolls over.

SCOPE OF WORK

Project: [project name]
Client: [client company] ("the Client")
Agency: [agency name] ("the Agency")
Related agreement: [master services agreement and date, if any]
Date: [date]    Version: [1.0]

1. PROJECT OVERVIEW
[Two or three sentences: what the project is, why the Client is doing it, and what will exist at the end.]

2. OBJECTIVES
- [Objective, e.g. "Launch the new website before (date)"]
- [Objective, e.g. "Let the Client's team publish blog posts without developer help"]
Objectives describe the purpose of the project. The Agency's obligations are the deliverables in Section 3.

3. DELIVERABLES
3.1 [Deliverable name]
Description: [what will be delivered, with quantities, e.g. "design and development of up to (number) page templates"]
Format: [e.g. Figma file, pages live on staging, PDF]
Acceptance criteria: [how both sides will know it's done, e.g. "pages match the approved designs and pass the agreed browser checks"]

3.2 [Deliverable name]
Description: [...]
Format: [...]
Acceptance criteria: [...]

A deliverable is accepted when the Client approves it in writing, or raises no documented issue within [number] business days of delivery.

4. REVISIONS
Each deliverable includes [number] rounds of revisions. A round is one consolidated set of written feedback from the Client's named approver.
A revision adjusts delivered work within the approved direction (copy edits, layout tweaks, bug fixes). Anything that adds a new page, feature, concept or channel, or changes an approved direction, is a new request under Section 9.
Additional revision rounds: [rate or fixed fee per round].

5. TIMELINE AND MILESTONES
- [Kickoff]: [date]
- [Milestone, e.g. design approved]: [deliverable], [date]
- [Final delivery or launch]: [deliverable], [date]
Dates assume the Client meets the responsibilities in Section 6. Client delays move dependent dates by at least the same number of business days.

6. CLIENT RESPONSIBILITIES
The Client will:
- Name one approver for feedback and sign-off: [name, role]
- Provide [content, brand assets, logins, product information] by [date]
- Return consolidated feedback within [number] business days of each delivery

7. ASSUMPTIONS
The scope and fee are based on these assumptions. If one proves wrong, either party may request a change under Section 9.
- [e.g. "The Client provides final copy for all pages"]
- [e.g. "The site is built on (platform), using the Client's existing hosting"]
- [e.g. "The project supports (number) languages"]

8. EXCLUSIONS (OUT OF SCOPE)
The following are not included:
- [e.g. "Copywriting, photography and video production"]
- [e.g. "Hosting, maintenance or support after (date)"]
- [e.g. "Paid media spend and ad account management"]
- [e.g. "Integrations with third-party tools not listed in Section 3"]
Any work not described in Section 3 is out of scope, whether or not it appears in this list.

9. CHANGE REQUEST PROCESS
Work outside Sections 3 and 4 requires a written change request before it starts.
1) The Client sends the request through an official channel (Section 11).
2) Within [number] business days, the Agency confirms whether it is in scope. If it isn't, the Agency sends a change request with a description, price and timeline impact.
3) Work begins only after the Client approves the change request in writing.
Approved change requests become part of this scope of work. All other terms stay the same.

10. FEES AND PAYMENT TERMS
Project fee: [fixed fee] or [hourly rate, estimate and cap]
- [Deposit amount] due on signing
- [Amount] due on [milestone]
- [Amount] due on final delivery
Invoices are due within [number] days. Approved change requests are invoiced [on approval / with the next milestone].

11. COMMUNICATION CHANNELS
Official channels for requests, feedback and approvals: [email to (address)] and [shared Slack channel #(name)].
Requests made anywhere else (calls, meetings, direct messages) are not official until confirmed in writing in an official channel.
Agency contact: [name, role]    Client contact: [name, role]

12. APPROVAL AND SIGN-OFF
By signing below, both parties agree to this scope of work.

For the Client: ____________________   Name and title: [name, title]   Date: ________
For the Agency: ____________________   Name and title: [name, title]   Date: ________

This template is sample wording written for this guide, not legal advice. Have a lawyer review the contract terms before you use it.

How to Fill In Each Section

These six sections cause most scope creep when they're vague, so give each one an extra ten minutes.

Deliverables

Write each deliverable as a noun with a number: what it is, how many, in what format, and how you'll both know it's done. Acceptance criteria are the part most often skipped, and they're what stops “can you just…” requests after delivery.

• Weak: “Website design and development.”
• Strong: “Design and development of up to eight page templates on [platform], accepted when pages match the approved designs and pass the agreed browser checks.”

Revisions

State the number of rounds per deliverable, define a round, and say what isn't a revision. Without that last part, “revision” stretches to cover new pages, new concepts and changes of direction.

• Weak: “Revisions included until the client is satisfied.”
• Strong: “Two rounds of consolidated revisions per deliverable. Requests that add new pages, features or concepts follow the change request process.”

Assumptions

Assumptions are the conditions your price depends on: who writes the copy, which platform, how many languages, how many people give feedback. When one breaks, the conversation is about the assumption, not about whether you're being difficult.

• Weak: “Client will provide content.”
• Strong: “The Client provides final, approved copy for all pages by [date]. Copywriting and editing beyond typo fixes are not included.”

Exclusions

Name what a reasonable client might assume is included: adjacent services, the next phase, ongoing work. Then add a catch-all line. A clear exclusion list is the simplest out-of-scope clause you can write, because it turns a negotiation into pointing at a line.

• Weak: No exclusions section at all.
• Strong: “Not included: copywriting, photography and maintenance after launch. Any work not described in Section 3 is out of scope.”

Change Request Process

Say how a change is requested, how quickly you'll respond with a price, and that work starts only after written approval. For the reply itself, use these email templates for telling a client a request is out of scope.

• Weak: “Changes will be discussed as needed.”
• Strong: “Work outside Section 3 requires a written change request with a description, price and timeline impact, approved by the Client before work starts.”

Communication Channels

Name the channels that count as official requests, usually email and one shared Slack channel, and say that anything raised elsewhere must be confirmed there in writing. Requests made on calls are the ones most likely to get done without anyone checking the SOW.

• Weak: “The teams will stay in close contact.”
• Strong: “Requests and approvals are official only when sent to [email address] or posted in #[client-channel]. Requests made on calls are confirmed in writing within one business day.”

Out-of-Scope Clause Examples (Copy and Paste)

An out-of-scope clause says what happens when a request falls outside the agreement. Use the general clause in every SOW, then add the ones that match your work. Section numbers refer to the template above.

Any work, deliverable or service not expressly described in Section 3 (Deliverables) is outside the scope of this agreement. Out-of-scope work is performed only under a change request approved in writing by the Client, at the rates in Section 10 or as quoted in the change request.

Each deliverable includes [number] rounds of revisions. A round is one consolidated set of written feedback from the Client's named approver. Additional rounds are billed at [fee per round]. Requests that add new elements or change an approved direction are not revisions and follow the change request process.

This scope covers [number] pages and the features listed in Section 3. Additional pages, templates, features or integrations are new work, quoted separately through a change request, and may affect the timeline.

Requests the Client needs completed in fewer than [number] business days, or outside the Agency's working hours ([hours, time zone]), are rush work. Rush work requires written approval and is billed at [rush rate]. Before starting, the Agency will name any scheduled deliverables that move as a result.

This scope covers work on [named platforms and tools]. Work on other platforms, migrations between platforms, and integrations with tools not listed in Section 3 are out of scope. The Client is responsible for third-party licenses, subscriptions and fees.

The Agency provides [number] days of post-launch support, limited to fixing defects in delivered work. Content updates, new features, platform updates, hosting and maintenance after that period are not included and can be provided under a separate support agreement.

Scope of Work Examples by Agency Type

The template fits any agency, but deliverables and the likely extra requests differ by service. Each scope of work example below gives typical deliverables, common out-of-scope requests and a revision rule to adapt for Sections 3, 4 and 8. To see how requests like these play out mid-project, read these scope creep examples from client projects.

SOW Mistakes That Lead to Scope Creep

1. Vague verbs like “support” or “optimize”. “Support the launch” has no end point. Say what you'll do, how much and for how long: “fix defects reported within 14 days of launch”.
2. Unlimited revisions. “Revisions until approved” sounds generous at signing and turns every deliverable into an open-ended project.
3. No exclusions. If the SOW only lists what's included, every adjacent request becomes a debate about intent.
4. No change process. Extra requests get a yes in a meeting and an awkward invoice later, or no invoice at all.
5. No official request channel. Requests scattered across email, DMs and calls never all get checked against the SOW.
6. Deliverables without acceptance criteria. If “done” isn't defined, the client can keep asking for changes to delivered work, and each one feels reasonable.

After Signing: Check Every Request Against Your SOW

A strong SOW only helps if someone reads it when a request comes in. Make it a habit: before anyone says yes, open the SOW, find the deliverable, revision limit or exclusion the request touches, and decide whether it's in scope, out of scope or unclear. Small requests matter most: they get the reflexive yes.

When a request is out of scope, reply the same day, quote the clause and offer options: a change request, a later phase or a swap. This guide on how to tell a client something is out of scope covers the wording, including requests that arrive in Slack.

Scovara is built for that check. You import your SOW or contract, then paste client requests in or pull them from mapped Slack channels. Each request is classified as in scope, needs review or potential out of scope, with the relevant SOW or contract clause cited.

Common Questions About Writing a SOW

What should an agency scope of work include?

A project overview, deliverables with acceptance criteria, a revision limit, a timeline, client responsibilities, assumptions, exclusions, a change request process, fees and payment terms, official communication channels and a sign-off. The scope of work template above covers all twelve.

What's the difference between a scope of work and a statement of work?

A scope of work describes the work: deliverables, quantities, revisions and exclusions. A statement of work usually adds the commercial and process terms, such as fees, payment schedule and approvals. Both are shortened to “SOW”, and many agencies use the terms interchangeably.

How detailed should a SOW be?

Detailed enough that someone who wasn't on the sales call can tell whether a request is included in about a minute. That means quantities for every deliverable, a defined revision round and named exclusions.

What's an out-of-scope clause?

A clause stating that work not described in the SOW isn't included and is handled through a change request. It turns “is this included?” into a check against the document instead of a negotiation.

How many revisions should a SOW include?

There's no standard number; two or three rounds per deliverable is a reasonable starting point for design and content work. Defining what a round is, and what happens after the last one, matters more than the number.

Can I change the SOW after signing?

Yes, with both sides' written agreement. Most changes go through a change request that adds to the original SOW. For larger changes, such as a new phase or budget, issue an amended SOW with a new version number and date.