Scope Creep & Revision Limits: How UK Freelancers Can Stop Free Work Before It Starts

A web developer quoted £3,500 for a five-page marketing site. Three months later, he'd built an e-commerce store, a blog, a member portal, and three integrations that "weren't explicitly excluded." He billed £3,500. The contract said "a professional website" with "revisions as needed to achieve client satisfaction." That was enough, legally, to trap him.

Scope creep is the silent killer of freelance profitability. It rarely arrives as a demand. It comes as a series of small, reasonable- sounding requests that individually seem fine, until you add them up and realise you've been working for free.

Why Scope Creep Is a Contract Problem, Not a Client Problem

It's tempting to blame difficult clients. But scope creep almost always starts with a vague contract. When your agreement doesn't define what's in scope, what counts as a revision, or how changes are requested and priced, there's no shared reference point. The client's interpretation will always expand, not contract.

Under the Supply of Goods and Services Act 1982, a service contract must be performed with "reasonable care and skill" within a "reasonable time." But "reasonable" is subjective and contested. If your contract doesn't define what you're delivering, a dispute about scope becomes a dispute about what's reasonable, which is expensive to resolve.

A clear contract doesn't just protect you legally. It also sets expectations upfront, so scope conversations are easier to have professionally without damaging the client relationship.

The Four Scope Creep Red Flags

1. Vague deliverables

"A website." "Design work." "Content for the campaign." These phrases describe categories, not deliverables. Without specifics, the client can always say more falls within scope. A strong scope clause lists exactly what you're delivering:

• Number of pages or screens
• File formats and final deliverable specifications
• Platforms or environments covered
• Languages, integrations, or features explicitly included

2. Unlimited revisions or "until satisfied"

"Revisions until the client is satisfied" is not a revision clause. It's an open-ended commitment to unlimited free work. Even "two rounds of revisions" is meaningless without defining what counts as a round and what counts as a revision. One round can easily become forty-seven individual email requests spread over six weeks.

3. No change request process

If your contract has no process for requesting changes (written request, written quote, written sign-off before work begins) there's nothing to stop scope from expanding informally. A WhatsApp message saying "could we also add X?" becomes a binding instruction if you act on it without pushing back.

4. Client has sole discretion to define scope

Watch for clauses like "the client may request additional work at any time" or "scope to be determined at the client's discretion." These shift total control of the project's size, and therefore your time and costs, to the client. Combined with a fixed fee, they're financially dangerous.

The Revision Clause Trap

Revision clauses are where scope creep most often hides. Vague language like "reasonable revisions" or "minor amendments" creates the illusion of a limit without actually creating one.

The key phrase to add to any revision clause is "based on the previously approved brief." This means that if the client changes direction after sign-off, that's a new instruction, not a revision. Without this language, a client can change the brief repeatedly and argue that each iteration is just a revision of the last.

For example, compare these two clauses:

• Weak: "The Contractor will make reasonable revisions until the Client is satisfied."
• Strong: "The Client is entitled to two rounds of revisions per deliverable, based on the approved brief. Each revision round consists of one consolidated set of written feedback. Additional rounds will be quoted and invoiced separately."

The strong version defines what a round is, limits the number, ties revisions to the approved brief, and creates a path to charge for extras, all in two sentences.

How to Define Scope Properly

Your scope clause should make it possible to answer "is this included?" with a clear yes or no. Include:

• Specific deliverables: List them. Not "branding" but "primary logo in SVG and PNG, colour palette document, and typography guide."
• File formats and specs: What do you deliver? In what format? At what resolution?
• Revision rounds: How many, and what counts as a round (one consolidated set of feedback, not drip-fed comments).
• Revision basis: "Based on the approved brief" to protect against direction changes being treated as revisions.
• Exclusions: What's explicitly not included. More on this below.

Even a short scope description is better than a vague one. The goal isn't to cover every edge case. It's to create a reference point both parties have agreed to.

The Change Order Process

Every freelance contract should include a short change order clause. This doesn't need to be complex. Just a clear process for what happens when the client wants something that falls outside the agreed scope:

1. Client submits a written request for additional work
2. Contractor provides a written quote (cost and timeline)
3. Client approves in writing before work begins
4. Additional work is invoiced separately

A short clause covering this, even just two or three sentences, transforms every out-of-scope conversation. Instead of feeling like you're being difficult, you're simply following the agreed process. Most clients respect this once they understand it's standard.

In practice, even an email trail that follows this process provides significant protection. "Here's a quote for the additional work. I'll start once you confirm." That's a change order.

Kill Fee and Scope Exclusions

Two underused clauses can do a lot of work here:

A kill fee (also called a cancellation fee) protects you if a project is cancelled partway through, especially useful when scope has already expanded before the cancellation. A typical kill fee is 25–50% of the remaining project fee, payable on cancellation. It also creates an incentive for clients to finalise scope before starting, not mid-project.

A scope exclusions clause lists what's explicitly not included in the project. This sounds obvious, but it's often the clearest way to prevent disputes:

"This agreement does not include: copywriting or content creation, third-party integrations not listed above, ongoing maintenance or support, SEO optimisation, or additional pages beyond those specified in Schedule A."

If a client later says "but I assumed that was included," you can point directly to the exclusions list. The conversation changes from an argument about intentions to a reference to an agreed document.

See our guide to freelance contract red flags for more on vague scope and revision warning signs, or download our 15-point contract checklist which covers scope, revisions, and change processes.

Frequently Asked Questions

What counts as a revision vs. a new request?

A revision refines or adjusts something within the agreed brief. A new request changes direction, adds functionality, or asks for something outside the original scope. The clearest test: if the client is asking you to change something because it doesn't match the brief, that's a revision. If they're asking you to change the brief itself, that's new work.

Can I charge for extra work even if my contract is vague?

Possibly, but it's harder. Under the Supply of Goods and Services Act 1982, if no price is specified for additional work, you're entitled to a "reasonable" fee. But what's reasonable is often disputed, and proving it without a clear change order is difficult. It's much easier to have the conversation upfront than to try to invoice retroactively for work you've already done.

What if my client keeps adding requirements verbally?

Start a paper trail. Summarise verbal conversations in email: "As discussed, you'd like to add X. I'll put together a quote for this as additional work. I'll send it over before starting." Even if your contract doesn't have a change order clause, this email exchange creates a clear record that the work was agreed as additional and separately quoted. Most clients will accept this without objection if you're professional about it.

What's a fair number of revision rounds to include?

It depends on the work, but two rounds per deliverable is standard for most creative and digital projects. Each round should consist of one consolidated set of written feedback, not rolling comments submitted over days. For technical projects (development, data work), you might structure this as a review and sign-off phase rather than numbered revision rounds. Whatever you choose, define it clearly and include "based on the approved brief" to protect against direction changes.