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.
