Clients and Scope

How to Stop Scope Creep in Your Creative Agency

By Danielle Stephanie · Published · 11 min read

Fig. 1Change request column
To do
Homepage design
In progress
About page copy
Client review
Services page
Done
Brand moodboard
Change requests
Add a blog pageNeeds quote
Extra logo optionOutside agreed rounds
getyouropstogether.co
Creative agency project board with a change request column for out-of-scope client requests
In this guide
  1. What is scope creep in a creative agency?
  2. Why does scope creep happen so often in creative agencies?
  3. What does scope creep actually cost your agency?
  4. How do you prevent scope creep before a project starts?
  5. How do you handle scope creep once a project is underway?
  6. Where should you start?
  7. Frequently asked questions
  8. Want help building this into your agency?

Scope creep in a creative agency is when a client project slowly grows beyond what was agreed at the start, through extra concepts, extra revision rounds and "quick" requests, while the timeline, your team's hours and the agreement stay the same. You stop it with operations: a clear scope written into your proposal, a set number of revision rounds for each service, a simple change-request process for anything new, one channel where client requests come in, a team that knows what's included, and a running record of every out-of-scope request. Each of those pieces is explained below in plain terms, so you can set them up in your own agency.

Most agency owners we work with are frustrated by the same things when it comes to scope. Projects run weeks past their end date, team members aren't sure whether they're allowed to say no to a client, and small favors keep landing on people who are already at full capacity. Those frustrations are signs of a scope problem, and scope problems can be fixed with clear systems.

What is scope creep in a creative agency?

Before getting into fixes, it helps to be clear on the words. The scope of a project is the agreed description of the work: what you'll deliver, how much of it, in which formats, how many chances the client has to request changes, and by when. Scope creep is what happens when that description quietly expands. Nobody sits down and decides to double the project. A client asks for one more logo concept, then a few social media graphics to go with the new brand, then the files in a format nobody mentioned at the start.

Each request feels too small to question on its own, which is exactly why scope creep is so common. It also rarely involves anyone acting in bad faith. From working with creative agencies, we've found that most clients ask for extra work because the line between what's included and what's extra was never made clear to them, so they have no way of knowing when they've crossed it. If you'd like to see what this looks like in different types of agencies, we've put together scope creep examples for design, social media, web, video and interior design agencies.

Why does scope creep happen so often in creative agencies?

Creative work is especially open to scope creep, because the deliverables are often subjective and the work happens in close, friendly collaboration with clients. From working with agencies, we see the same five causes come up again and again, and each one points to a gap in how the agency operates.

The first cause is unclear deliverables. A proposal that says "brand identity" or "social media management" leaves a lot open to interpretation. Does brand identity include business cards and a pattern library? Does social media management include replying to comments? When the scope describes a category of work instead of a specific list of what you'll hand over, the client fills the gaps with their own assumptions.

The second is unlimited or undefined revisions. A revision round is one chance for the client to review the work and send back a set of changes. If the number of rounds isn't set, or the word "revision" isn't defined, feedback can keep coming indefinitely, and a request to start over in a new direction gets treated the same way as a small adjustment.

The third is having no change-request process, meaning no agreed way to handle a request for something that wasn't in the original plan. Without one, every new request gets decided on the spot by whoever happens to receive it, and under pressure the default answer is usually yes.

The fourth is requests arriving through informal channels. When clients can message your designer in Slack, send a voice note to your account manager, reply to an old email thread and DM you on Instagram, nobody has the full picture of what's been asked. Small requests get done quietly by whoever saw them, and the extra hours never show up anywhere you can see them.

The fifth is the founder saying yes to keep clients happy. This one is understandable, because you built the relationship and you care about the client's experience. Each yes from you, though, sets the expectation for the next request, often lands on a team member who was already at capacity, and teaches your team that the real scope is whatever you agree to in the moment.

Fig. 2Change request process
S01Request comes inTeam does not start the work
S02Passed to the scope ownerOften the founder or account manager
S03Confirmed as new workShared with the client
S04Agreed separatelyPrice and timing
S05Added to the planThen the work begins
getyouropstogether.co
Change request process for a creative agency from client request to approval

What does scope creep actually cost your agency?

Once you can see where scope creep comes from, it's easier to see why it matters. The first cost is capacity, which simply means how much work your team can realistically handle compared with what's already booked. Every hour spent on unplanned work is taken from something that was planned, so when a designer spends an afternoon on an extra round for one client, another client's project slips or that designer works late to catch up.

The second cost is deadlines. Extra work rarely gets added to the project plan, so timelines stretch quietly. Projects that should have wrapped stay open, the next projects start late, and your team ends up juggling more active work than anyone planned for.

The third cost is margin, and the clearest way to see it is in time. Compare the hours your team planned to spend on a project with the hours they actually spent. When scope creep is happening, that gap keeps growing, which means the same project is taking far more of your team's week than it was meant to. We focus on the time side because that's what systems can fix. If those numbers raise questions about your pricing, that's a conversation for your accountant or financial advisor.

How do you prevent scope creep before a project starts?

The best time to stop scope creep is before any work begins, because it's much easier to agree on boundaries when nothing has been delivered yet. Two pieces do most of the work here: a clearly documented scope and clearly defined revision rounds.

How do you document a clear scope in your proposal?

Your proposal is the document a potential client reviews before deciding to work with you. It's part of your lead inquiry system, which covers everything from the moment someone submits an inquiry to the moment they become a paying client. In the proposal, describe each deliverable as specifically as you can: how many concepts, how many pages, how many posts per month, which platforms, which file formats, and what the client is responsible for providing, such as copy, photos or brand files. It's just as helpful to list what isn't included, because a written exclusion answers the question before it turns into a debate halfway through the project. Tools like HoneyBook and Dubsado let you send a smart proposal, which puts the proposal, contract and invoice in one place so the client can review, sign and pay at once.

One important note: we aren't lawyers, and we don't give advice on how contract clauses should be worded. Use your proposal to describe the work clearly, and have a lawyer check the wording of your contract.

How many revision rounds should you include, and what counts as a revision?

Next, decide how many revision rounds each service includes. There's no universal number, so choose one that fits the service and keep it the same for every client who buys it. Then define what a revision is. A useful rule is that a revision changes something within the agreed direction, like adjusting spacing, swapping a color within the approved palette or tightening a caption. A request that changes an approved direction, adds a new deliverable or reopens something the client already signed off on is a new request, and it goes through your change-request process.

Ask the client to send one combined set of feedback per round, by a set date, from the one person who has the final say on their side. When three people on the client's team send separate notes at different times, you end up running several rounds while only counting one. Then repeat the revision rules during client onboarding, whether that's in your welcome packet, on a kickoff call or both, depending on how your onboarding runs. What matters is that the client hears them before the first draft arrives.

Fig. 3Revision vs new request
ARevisionA change within the agreed directionPart of the included roundsHandled by the team
BNew requestA new direction or new deliverableReopens approved workGoes through the change-request process
getyouropstogether.co
Difference between a revision and a new request in a creative agency project

How do you handle scope creep once a project is underway?

Even with a clear scope, clients will ask for new things, often because they're happy with the work and want more of it. The goal is to handle those requests the same way every time, so nobody on your team has to make it up on the spot.

What should a change-request process include?

A change-request process is a short, agreed set of steps for anything outside the original scope. Every agency's version looks a little different depending on team size and tools, but the purpose is the same: every new request gets checked against the scope and decided in writing before anyone works on it. One simple version: the request is logged in your project tool, the person responsible for the client compares it with the scope, and then they reply. If the request is included, they confirm the timing. If it isn't, they say so plainly and kindly and give the client options, such as adding it as additional work under the terms your agreement sets out, swapping it for something already in the scope, or planning it as a separate phase after the current project. Work starts only after the client confirms in writing, and once it's approved, the project plan and deadlines are updated so everyone is working from the same picture.

A reply could be as simple as: "Thanks for sending this over. That's outside what's included in this project, and we'd be glad to help with it. I'll send you what it would involve so you can decide whether to add it now or plan it for later." Saying this before any work begins keeps the conversation friendly and keeps your team from spending hours on work nobody agreed to.

Why should client requests come through one channel?

Scope creep grows fastest when requests are scattered across Slack, email, texts and voice notes, so choose one place where client requests live. That could be a request form, your project management tool or a single shared Slack channel for each client. Tell clients where to send requests during onboarding, and give your team a simple way to redirect anything that arrives elsewhere, such as "Thanks, I've added this to your project board so the team can review it." When every request lands in one place, nothing gets done quietly and everything can be checked against the scope.

How do you train your team on what's in scope?

Your team can only hold the line on scope if they know where it is. Give everyone working on an account access to that client's scope, including the deliverables, the number of revision rounds and the exclusions. Then write an SOP, short for standard operating procedure, which is a step-by-step guide for a task, that explains how to handle a client request and includes the reply wording you're comfortable with. That way a designer doesn't have to message you every time a client asks for something extra. Our Template Shop has free SOP Starter Kits for different types of creative agencies to help you write these, and our guide to client delivery workflows covers how review rounds and approvals fit into the rest of a project.

Why should you track out-of-scope requests?

Finally, keep a record of every out-of-scope request, including the ones you choose to do as a favor. A simple log in your project tool or a spreadsheet works: the date, the client, what was asked and what was decided. Reviewing it once a month shows you patterns. If several clients ask for the same extra item, your proposal may need to describe that area more clearly. This kind of record is part of data tracking, which is how your agency collects the information it needs to make decisions without guessing. Scope connects to almost every part of how an agency runs, which is why we cover it alongside the other core systems in our guide to the systems a creative agency needs to scale without burnout.

Where should you start?

If scope creep is one of several things pulling you back into client work, start with the free Baggage Check. It's a short self-assessment that shows where your agency still depends on you and what to hand off first.

Frequently asked questions

Is every extra client request scope creep?

No. A client asking for more often means they're happy with the work. It becomes scope creep when extra work happens without being checked against the scope, agreed in writing and added to the project plan.

What's the difference between scope creep and gold plating?

Scope creep comes from client requests. Gold plating is when your own team adds extra work nobody asked for, often to impress the client. Both use hours that weren't planned, so a clear scope and a log of extra work help with each.

What should you do if a project has already gone past its scope?

Compare what's been delivered and what's still open against the original scope, then talk with the client about the remaining requests using your change-request process. Agree in writing what's included from here, and have a lawyer check any contract wording.

Can project management software stop scope creep?

It helps you see scope creep, but it won't stop it by itself. A project tool can hold the scope, log requests and show planned versus actual hours, while your revision rounds and change-request process keep the project in line.

Want help building this into your agency?

If you'd like to start on your own, the free SOP Starter Kits in our Template Shop give your team policies and SOP templates to work from. If you'd rather have it built for you, Ops Concierge is our done-for-you system build, set up around how your agency already works. And RESORT Mode is our group program for creatives who want to scale to $30k+ months without the burnout. You get all the systems your agency needs, grow as a founder, and get real-time coaching as you scale.

Keep reading

Back to the blogRead the main guide: how to systemize your creative agency

Find out how much of your creative business is riding on you

Check Your Bags