Craig Campbell
← All posts

21 November 2026

How to stop scope creep: handle unpaid extras without surprising clients

How to stop scope creep: handle unpaid extras without surprising clients

To stop scope creep, agree what the fee covers, make exclusions clear and discuss changes before doing the extra work. The aim is not to say no to every request. It is to give both sides a fair choice about the work, price and timetable.

This guide is for UK service businesses, consultants and small agencies, including Glasgow businesses agreeing their first client projects. The examples and reply templates are fictional teaching examples, not accounts of Craig’s clients. It focuses on controlling changes, rather than repeating the service-pricing guide.

What is scope creep?

Scope creep is work expanding beyond the agreement without a corresponding decision about cost, time or resources. A client asks for another page, another review round or a different report; the team quietly adds it, and the original project no longer describes the job being delivered.

An agreed change is not automatically scope creep. Nor is correcting your own mistake, finishing an agreed deliverable or meeting an obligation you already accepted. Check the original agreement before treating a request as an extra.

ACCA’s guidance identifies a common cause: clients assume their fee includes services that were never priced. It recommends explaining both what is included and what is not. The same principle is useful outside accountancy.

Write a scope a client can actually understand

The services catalogue helps visitors distinguish advice, website reviews and training. A service page is a starting point; the actual agreement still needs to define the individual project.

Before accepting a project, confirm:

  • The objective and named deliverables.
  • The quantity or extent of work, where relevant.
  • Who supplies information, approves work and makes decisions.
  • The feedback and revision process.
  • What is specifically excluded.
  • The timetable and dependencies.
  • How new requests will be assessed and approved.
  • The fee, payment terms and applicable tax treatment.

Spot the request before it becomes a promise

Watch for “while you are there”, “could we just add” and requests that change the audience, format or purpose of the original work. The wording is not evidence of bad intent. The client may genuinely think the task is included.

A team member replying “no problem” can create an expectation before anyone has checked the workload. Instead, acknowledge the request and say you will check the scope and implications. Make the accepted agreement easy for everyone on the project to find.

Use a simple change-request process

  1. Record the request: describe the new work in plain language and note who asked for it.
  2. Check the agreement: decide whether it is already included, an error to correct or additional work.
  3. Explain the impact: identify any extra fee, revised deadline or effect on existing deliverables.
  4. Offer choices: add it, replace another task by agreement, schedule it later or decline it.
  5. Get approval: retain a clear written decision from the person authorised to approve the change.
  6. Update delivery: revise the project record so the team works to the same version.

A conversation can settle the issue, but follow it with a written summary. Do not assume silence means the customer agreed to a new charge. Follow the contract and obtain professional advice where the legal position is unclear.

Example replies when clients ask for unpaid extras

Fictional templates: adapt these to the real agreement. Do not copy a price, date or promise you have not checked.

When you need to assess the request

Thanks, Alex. I can see why that would be useful. I will check it against the agreed work and confirm whether it changes the fee or delivery date before we go ahead.

When the request is outside the scope

The agreed review covers the existing service pages; writing an additional page is separate. I can send a quote for that work, or we can keep this project to the original review. Which would be more useful?

When the budget cannot increase

If the budget needs to stay the same, we could discuss replacing one of the planned tasks with this request. I will explain the trade-off first, so we do not accidentally remove something important.

When the request is actually included

You are right: that clarification is part of the agreed review. I will include it in the next update. Thanks for pointing out the gap.

When work has already drifted

The project has expanded beyond the original list, and I should have raised that earlier. Let us review what is complete, what remains and the options for the next stage. I will not assume an extra charge has been agreed.

The last reply matters. If you allowed the work to expand without explaining it, do not rewrite history or send a surprise invoice and call it good boundaries.

How to handle revisions without an argument

Define feedback before delivery. Is the client correcting factual errors, requesting changes within the agreed brief or changing the brief itself? Those are different situations. Ask for consolidated feedback from the agreed decision-maker so conflicting comments do not send the work in circles.

A stated number of review rounds is useful only when the agreement explains what a round means. It does not excuse unfinished work or override obligations you have already accepted. If the brief changes, explain the difference with a concrete example rather than simply declaring that the client has used their revisions.

When is a small goodwill extra sensible?

Sometimes a genuinely small task is worth including. Make that a deliberate decision, not a default caused by discomfort. Record that it is a one-off addition, explain any limits and avoid letting it delay the agreed deliverables.

Do not use goodwill to cover an unclear scope forever. If the same request keeps appearing, it may belong in the next package or agreement. Clear expectations can also support a better customer relationship; see the customer retention guide for onboarding and review conversations.

A weekly scope-creep checklist

  • Compare current tasks with the accepted scope.
  • Identify new requests without a recorded decision.
  • Check whether the team has promised unapproved work.
  • Tell clients about likely timetable changes promptly.
  • Update the agreed deliverables after approved changes.
  • Record recurring misunderstandings to improve future quotes.

Track the time spent on unplanned tasks if that helps you understand delivery costs. Separate client-approved additions, goodwill, internal mistakes and unclear original estimates. They need different responses; treating all of them as a difficult-client problem hides useful lessons.

How do I say no without losing the client?

Explain the agreed boundary and offer realistic options. A calm “that is separate, here are the choices” is more useful than blaming the customer. You cannot guarantee their response, but clarity gives them a decision instead of a surprise.

Should I charge for every extra question?

No blanket rule fits every service. Check whether the question is part of delivering the agreed work. Decide separately whether a new task needs a quote, a goodwill addition or a later project.

Can a contract stop scope creep on its own?

No. A clear agreement helps, but the people delivering the work must use it. Review new requests, communicate changes and retain approvals. Have a suitably qualified adviser review contractual terms where needed.

Sources and further reading

General business guidance, not legal advice. Examples are illustrative and do not establish the terms of any service.