Scope Creep: A Simple Change Request Process for Small Teams

Why small requests turn into big problems

Each request on its own is reasonable, and saying no to a client feels risky. So the extras get done quietly. The trouble shows up later, in three ways.

• The margin goes. The price was set for the agreed work. Everything beyond that is paid for out of your time.
• Other work slips. The hours come from somewhere, usually from the next client or the next deadline.
• Expectations reset. Once a client sees extras done for free, the next request arrives assuming the same.

None of this means the client is being unreasonable. Usually nobody told them where the line was.

The change request process in five steps

1. Write every request down in one place. Email, phone and chat requests all go into the same log, with the date and who asked. If it isn't logged, it isn't agreed.
2. Check it against the scope. Is it covered by what was agreed? Point to the line in the agreement or proposal. If the scope only says what's included, this is where you find out what's missing from it.
3. Price it and give the effect on timing. For anything outside scope, send a short reply: what it would cost, and whether it moves the deadline.
4. Get a written yes before starting. An email reply is enough. Don't start until you have it.
5. Review the log regularly. Once a month, or at each project check-in, look at what's come in. Several small requests from one client may be a sign the original scope was wrong, which is worth a conversation of its own.

Agree this process with the client at the start. The client onboarding process builds it into the kick-off meeting, which is the easiest time to raise it.

How to word the reply

A reply to an out-of-scope request has three jobs: welcome the idea, say plainly that it's outside what was agreed, and give the client a choice. Put the price in the same message, so they don't have to ask for it.

For a single extra, with made-up details:

Happy to add the new service page. It's outside the five pages we agreed, so it would be [price] and would move the launch back by three working days. Shall I go ahead? If you'd rather keep the date, we could add it the week after launch instead.

For requests that have quietly turned into a bigger job:

Thanks for this. Between this and the last two requests, the work has moved some way from the original brief. Rather than price each one separately, could we have a short call this week to agree a revised scope? I'll send a summary of what's come in so far beforehand.

Leave out long apologies and "unfortunately". You don't need to explain your costs or justify charging for extra work. A friendly, matter-of-fact tone tells the client this is normal, which it is.

When to say no

Pricing the extra is the usual answer. A plain no is better when:

• it's work you don't do, or don't do well. Say so, and suggest the kind of firm that does.
• the timing would put the agreed work at risk, or another client's, and the client won't move the deadline.
• it undoes something already signed off, late in the project. Offer it as a second stage after launch.
• the client keeps asking again after turning down the price, hoping it becomes free. Say no once, clearly, and point to the scope.

A no can still be helpful. Offer the nearest thing you can do, or a date when you could.

A change request form you can copy

One row per request is enough for a small team. Keep it in a spreadsheet, a Word table or your project tool, wherever the team already looks.

The "Why" column earns its place. A request that looks like a whim often has a reason behind it, such as a new service launching or a board meeting coming up, and knowing it helps you suggest a cheaper or faster way to get there.

Included, or a change?

Try it on a made-up project. The agreed scope is a five-page website, with two rounds of design changes and two weeks of support after launch to fix anything that isn't working. Sort each request, then compare your answers with ours.

Write the exclusions into the proposal

The sorter only works because the scope says five pages, two rounds and two weeks. A proposal that only lists what's included leaves the edges to be argued about later. Three habits help:

• Add a "Not included" heading under the scope, listing what clients often assume comes with the work. For a website, that might be writing the copy, photography, hosting, newsletter set-up and changes after the support period ends.
• Put a number on anything that can grow: pages, rounds of changes, meetings, hours a month, weeks of support. "Revisions" is open-ended. "Two rounds of changes" has a limit.
• Say what happens to extras. One line does it: "Anything outside this scope will be priced and agreed in writing before work starts." That's your change process, agreed before the first day.

Write the exclusions in plain words. The client should be able to read the list once and not be surprised by it later. The client intake form helps here: asking what's definitely in and out before you quote gives you most of the list.

A typical example

Take a made-up but familiar situation. A four-person marketing agency has a monthly arrangement with a client: four blog posts and a short report each month. Over two months the client starts asking for social media posts "while you're at it". Nobody logs them, and the account starts losing money.

The account manager starts a change log with the columns above. The next request, a set of posts for an event, goes in with a price and a note that it would push one blog post into the following week. The client approves the price for the event posts. A month later they ask to add social posts to the monthly arrangement permanently, at a new monthly fee. The log made that conversation easy, because both sides could see what had been asked for.

Common mistakes

Only logging the big requests. Small ones are where the time goes. Log everything, even the ones you decide to do for free.

Doing the work while waiting for approval. It feels efficient. Then the client says no to the price, or forgets they asked, and the work is unpaid.

Leaving it to whoever took the call. If three people talk to the client, requests arrive through three people. One person owns the log and the replies. A RACI chart helps if it's not clear who that should be.

A scope that only lists what's included. The clearer the exclusions, the easier every one of these conversations becomes. Add a "Not included" list to your proposal template, and take advice on the contract wording if you need it. This post isn't legal advice.

Treating every request as a battle. An extra request is often a sign the client values your work. A clear price lets them decide, and some of the best extra work starts that way.