Scope creep: what it is and how to stop it
What scope creep is, why it happens on agency projects, and how to stop it with a clear scope, a change order and a fixed number of revision rounds.
Spodus team
Published 5 min read
On this page
Scope creep is work that grows beyond what the client agreed to pay for. It arrives as small requests: one more page, one more edit, one more meeting. None is worth a fight, so the agency absorbs them, and together they eat the margin. The fix is a clear scope, a change order and the habit of saying so.
Scope creep examples
Scope creep rarely looks like a big demand. It looks like these:
- A five-page website that becomes eight pages, because "we forgot the careers page".
- Two rounds of revisions that become five, because feedback arrives from three different people on three different days.
- A monthly report that grows a new section every month.
- A logo project that turns into business cards, a signature and a slide template.
- A "quick call" every week that nobody counts as billable time.
- A launch date that moves, so the team keeps supporting a project that was meant to be finished.
Each example has the same shape. The original scope was vague, or it was clear but nobody pointed to it when the request came in.
Why scope creep happens
There are three causes, and they are all fixable.
The scope was never written clearly. "Design and build a website" is not a scope. It does not say how many pages, how many revision rounds, who writes the copy, or what happens after launch. When the scope is a sentence, every request is inside it.
Nobody owns the boundary. The account lead wants the client to be happy. The designer wants the work to be good. Neither wants to send an awkward email. So the extra work gets done and nobody invoices it.
The agency does not measure it. If nobody compares hours worked to hours sold, scope creep is invisible until the project closes and the margin is gone.
How to prevent scope creep
Prevention happens before the price is agreed.
- Write the deliverables as a list. Number them. Say how many of each: pages, designs, posts, reports.
- Write the exclusions. A short list of what is not included prevents more disputes than the deliverables list does. "Copywriting, photography, hosting and ongoing changes after launch are not included."
- Fix the revision rounds. State the number, define what a round is, and price the extra ones.
- Add a change order clause. One sentence: "Work outside this scope will be quoted as a change order and starts after written approval."
- Name one client contact. Feedback from one person is a round. Feedback from five people is five rounds.
- Get a signature. A scope nobody signed is a suggestion.
A statement of work template covers all six.
How to handle scope creep when it appears
When the request comes in, act on the first one. If you wait until the fifth request, the client will expect the first four to stay free.
- Say it is outside the scope, in writing, in one plain sentence.
- Offer two options: a change order, or a swap for something of equal size that is already in scope.
- Keep the tone warm. The document does the hard part; you only have to point at it.
- If the request is small, you can choose to do it once. Say that you are doing it as a favour, and that the next one needs a change order.
Clients do not usually mind. Most scope creep is not a client trying to get free work. It is a client who does not know where the line is.
Change order template
A change order does not need to be long. Copy this into a document and fill in the blanks.
Change order [number] for [project name]
- Requested by: [client name], on [date].
- Description of the change: [what is being added, removed or changed].
- Why it is outside the current scope: [reference to the section of the statement of work].
- Additional cost: [amount], billed [with the next invoice / on approval].
- Effect on the timeline: [number of days added], new delivery date [date].
- Effect on other deliverables: [what moves, if anything].
- Approval: signed by [client name], [date].
Send it the same day the request arrives. A change order that takes a week to write is a change order the client has stopped waiting for.
Revision rounds: how many, and how to write them
The number matters less than the definition. Two rounds is a common default for design and content. Three is common for larger builds. The problem is never that a client used both rounds; it is that a round was never defined.
Write it like this: "Two rounds of revisions are included per deliverable. A round is one consolidated set of comments from [contact name], sent within five business days of delivery. Further rounds are charged at [amount] per round. A change of direction is a new deliverable, not a revision."
That sentence stops the three most common arguments at once: feedback arriving in pieces, feedback arriving late, and a redesign presented as a tweak.
Over-servicing: the scope creep you cause yourself
Over-servicing is when the agency gives more than it sold, without being asked. A designer polishes for an extra day. An account lead adds a report because it seemed useful. Nobody charges for it, and nobody knows.
It shows up on retainers most. A retainer sold at forty hours a month that regularly uses fifty is giving away a quarter more work than it was paid for. The fix is a monthly comparison of hours logged against hours sold, per client, and one person who tells the client when the budget is nearly used. A client profitability analysis makes the pattern easy to see.
Scope management for an agency
Scope management is not a big system. It is four habits:
- A signed scope document for every project, kept where the team can find it.
- A change order process that takes a day, not a week.
- A monthly look at hours against budget, per client.
- One person per account who is allowed to say "that is extra".
The tooling helps when the quote, the project board and the invoice sit on the same client record, so the team can see what was sold while they do the work. Spodus does that. But the habit comes first. A clear scope in a shared drive beats a vague scope in any tool.
Questions, answered
- What is scope creep?
- Scope creep is work that grows past what was agreed, without a change to the price or the deadline. It arrives in small pieces: one more page, one more round of edits, one more report. Each piece looks too small to charge for. Together they can turn a profitable project into a loss. The cause is almost always a scope that was never written down clearly enough to point at.
- How do you handle scope creep once it has started?
- Stop and name it. Say, in writing, that the request is outside the agreed scope, and offer two options: a change order with a price and a new date, or dropping something else of equal size. Do this on the first request, not the fifth. Clients rarely argue when the scope document is clear and you point to it politely. If you already did the extra work, say so once, then charge for the next piece.
- How do you prevent scope creep?
- Write the scope before you price it. List every deliverable, the number of revision rounds, and what is not included. Add a line that says any other work needs a change order. Get a signature. Then run the project against that document: check each new request against it, and treat the change order as normal, not as a fight. Most scope creep is prevented by the exclusions list alone.
- What is a change order process for an agency?
- A change order process is the fixed way you handle a request outside the scope. One person receives the request. They write a one-page change order: what is asked, what it costs, how long it adds, and what it moves. The client approves it in writing before any work starts. The approved change order is added to the project record and to the next invoice. The whole process should take a day, not a week.
- How many revision rounds should I offer?
- Two rounds is the common default for creative and content work, and three for larger deliverables such as a website. One round is often enough for small pieces. Whatever the number, write it into the contract and define a round: one set of consolidated feedback from one named person. Extra rounds are priced in the contract too, so asking for a third is a purchase, not a favour.
- What is agency over-servicing?
- Over-servicing is when an agency delivers more hours or more work than the client is paying for. It is scope creep the agency does to itself. It comes from wanting to please, from unclear scope, and from nobody comparing hours worked with hours sold. It is a common reason a retainer that looks fine on paper loses money every month.
- How do you stop scope creep with clients who keep asking for more?
- Make the boundary visible and repeatable. Send a short scope summary at the start of every month or phase. Answer each extra request with the same sentence: "That is outside the current scope. I can send a change order today." Keep the tone friendly and the answer identical. Clients learn the pattern fast. If they push back every time, the account is priced too low or the client is a bad fit.
- How should revision rounds be written into a contract?
- State the number of rounds per deliverable, what counts as a round, who gives feedback, and how long the client has to respond. Add the price of an extra round and say that a change of direction is a new deliverable, not a revision. Example: "Two rounds of revisions per deliverable. A round is one consolidated set of comments from the client's project lead within five business days."
- How do you stop over-servicing clients in an agency?
- Measure it first. Compare hours logged against hours sold for each client each month. Then set a rule: when a client reaches ninety percent of their hours, the account lead tells them, and the remaining work is prioritised or moved to a change order. Train the team that saying "that is extra" is part of the job. Over-servicing stops when it is visible and someone owns it.
- What does scope management look like in an agency?
- Scope management is the routine that keeps every project inside what was sold. It has four parts: a signed scope document, a change order process, a monthly check of hours against budget, and one person per account who is allowed to say no. It does not need a large system. A clear document and a weekly look at the numbers do most of the work.
