Handbook / Contracts and proposals

Scope creep: how to prevent it and handle it when it happens

Scope creep is the gradual growth of a project beyond what was agreed, without a matching change in time or price. It rarely arrives as one big request. It comes as "one more small thing", repeated until a profitable project becomes a loss and a good relationship becomes strained. This guide covers how to prevent it and what to do when it appears.

Why it happens

Scope creep usually has ordinary causes:

• the original scope was vague
• the client's needs changed as the project developed
• new people joined the client's side with new ideas
• the freelancer agreed to small requests without noting them
• nobody agreed how changes would be handled

None of these requires bad intent. Most clients do not realise how small requests add up.

Prevention starts with the scope

The best defence is a clear written scope before work starts. The guide on statements of work covers it in detail. Key elements:

• Deliverables: exactly what you will provide.
• Exclusions: what is not included. Listing them prevents assumptions.
• Revisions: how many rounds are included and what counts as a revision.
• Client responsibilities: content, feedback and approvals, with dates.
• Timeline: milestones that depend on client inputs.
• Change process: how new requests are handled and priced.

A simple change process

Write a short clause into your agreement:

1. The client describes the requested change.
2. You reply in writing with the effect on price and timeline.
3. Work on the change starts only after the client approves.

Contracts generally reflect an exchange of value between the parties; legal sources describe this as consideration. Agreeing changes in writing keeps that exchange clear when the work changes.

Spotting creep early

Watch for:

• "while you're at it" requests
• feedback that changes direction rather than refining
• new stakeholders with different goals
• revision rounds beyond what was agreed
• deadlines slipping because inputs arrive late

Keep a change log for each project: date, request, your response and the decision.

What to say

Respond quickly, warmly and in writing. A useful pattern:

1. Acknowledge the idea positively.
2. Clarify that it is outside the agreed scope.
3. Explain the effect on time or cost.
4. Offer options.

Example: "Adding an online booking page is a great idea. It is not part of the current scope, which covers the five informational pages. I can add it for an extra fee and four more working days, swap it for the blog page we planned, or schedule it as a second phase after launch. Which would you prefer?"

Options keep the conversation constructive.

Pricing changes

Price changes with the same method as the original work. The guide on project pricing covers estimates and contingency. For frequent small changes, an agreed hourly rate for extras can simplify things.

When you choose to give

Occasional generosity is fine if it is deliberate and visible. Say so: "This is outside scope, but I am happy to include it." That way the client understands the value and does not assume future requests will be free.

If the project fundamentally changes

Sometimes the client's needs change so much that the original agreement no longer fits. Pause and agree a new scope and price, or close the current phase and start a new one. If the client cancels instead, a kill fee clause protects you for work already done.

Learn from each project

After every project, compare the final work with the original scope. The SBA's finance guidance stresses knowing your numbers; tracking unpaid extra work shows where your scopes need tightening.

Wording that helps in your contract

A few clauses make scope conversations much easier later:

• Deliverables list: each item named, with quantities, such as three homepage concepts or two rounds of revisions.
• Exclusions: a short list of what is not included, such as copywriting, stock images or hosting.
• Revision definition: what counts as a revision versus a new request.
• Change requests: how changes are requested, priced and approved in writing before work starts.
• Client responsibilities: content, feedback and approvals due by set dates, with timelines moving if they are late.

Clear wording does not stop clients asking for more. It gives both of you a shared reference point, so the conversation is about the document rather than about who remembers what. Many disputes over extra work disappear once both sides can point to the same written scope.

Write a clear scope with exclusions and a change process, respond to new requests early with options, and keep a log of every change.