Scope creep: how to handle it without losing the client

Scope creep is the slow growth of a project beyond what the client signed for: one more page, a third round of feedback, a "quick" integration. You handle it without losing the client in three moves. Write down what the price covers before you start. Sort every new request against that the day it arrives. Then answer with a price and a date, not with a bare yes or no.

Why requests grow, and what it costs

Requests grow for ordinary reasons. The client sees the first designs and has new ideas. A new stakeholder joins and adds their wishes. Something you both assumed turns out to be wrong, such as content that was meant to be ready by the second week.

It is common. PMI's PM Network reported that 52% of projects in PMI's 2018 Pulse of the Profession survey experienced scope creep or uncontrolled changes, up from 43% five years earlier.

On a fixed price, every unpriced hour comes out of your margin. On time and materials the client carries that risk instead, though they still expect to hear before the estimate runs out. The bigger cost is trust. A team that says yes to everything and then sends a surprise invoice, or lets the deadline slip without a word, damages the relationship far more than one that said "that's extra, here is what it costs" on the day it was asked.

Prevention starts in the proposal

You cannot call something extra if nobody wrote down what was included. The full method is in how to write a scope of work clients understand. Four parts of it do the work when extra requests arrive:

• Counted deliverables. "Up to eight page templates" and "two rounds of consolidated feedback per design", not "a website" and "revisions".
• An out-of-scope list. Name the things clients often assume are included: copywriting, photography, translations, data migration, training.
• Assumptions. What must be true for the price and the date to hold, such as "you supply all page texts by the end of week three".
• A change process and a rate. How a change is asked for, priced and approved, and what an hour of extra work costs.

I want a client to feel that everything they need is included, and I am just as clear about what is not. I also put my hourly rate for work outside the proposal in the proposal itself. Extra requests will come, and the client should know their price before they ask.

You can go one step further and price the likely extras in advance as optional lines. If you expect the client to want a second language or a team page later, list it with its price. Then "can we also have…" has an answer they have already seen. Options and extras in a proposal shows how to lay them out.

Sort every request: a decision table

When a request arrives, decide which of four kinds it is before you reply.

Two questions decide the row. First: would someone who was never on your calls read the signed scope and say this is included? Second: does it fit within the buffer you agreed for small requests, such as "requests up to two hours in total are included"?

The buffer matters more than it looks. It lets you be generous without being vague: the client gets quick help with small things, and you have a clear point at which a favour becomes paid work.

Run a change request in five steps

1. Acknowledge it the same day. "Good idea. It isn't in the current scope, so I'll send you the price and what it does to the timeline by Thursday." You have neither refused nor agreed.
2. Write it down. What is asked, why, and which deliverable or milestone it touches.
3. Price it. Hours times your rate for extra work, or a fixed price for the change. Add its effect on the timeline. If you have no rate yet, start from a freelance day rate that covers your costs.
4. Get written approval before you start. A reply saying "approved" works, or a signature, the same way you got the proposal signed in the first place.
5. Update the scope and invoice it. Add the change to the scope, the timeline and the next invoice, so the documents match the project.

There is a quieter option too: swap rather than add. If the client wants the new item within the same budget, offer to drop something of the same size.

Worked example: a change request on a fixed-price website

The studio, the client and the amounts below are made up. Replace them with your own.

Example

The project. Studio Noord builds a website for a garden design firm for a fixed €14,400 excluding VAT: up to eight page templates, two rounds of consolidated feedback per design, page texts supplied by the client by 3 November, launch on 15 December. Extra work costs €95 an hour excluding VAT. Small requests up to two hours in total are included.

Four requests arrive in week five.

Request	Kind	Hours	What happens
Swap the photo on the home page	Small favour	0.5	Done, logged: 1.5 of 2 hours left
A team page with bios	Change request	9	Priced below
A third feedback round on the home page	Change request	4	Priced below
A webshop with 40 products	New project	–	Separate proposal after launch

Change request 1, sent two days later.

Item	Hours	Rate	Amount (excl. VAT)
Team page template: design	4	€95	€380
Team page template: build and test	5	€95	€475
Third feedback round, home page	4	€95	€380
Total	13		€1,235

Effect on the timeline: three working days, so launch moves from 15 to 18 December. If the client approves it in writing by Friday, design starts on Monday.

The project after approval.

	Amount (excl. VAT)
Original fixed price	€14,400
Change request 1	€1,235
Total	€15,635

Look at what the client gets: a decision on each request within two days, a price they can say yes or no to, and an honest new date. The webshop does not disappear. It becomes the next project, with its own proposal.

Replies you can copy

Template

A change request Hi [name], thanks, a [team page] is a good idea. It isn't part of the scope we agreed, so I've written it up as a change request: [what], [hours] hours at [rate] excluding VAT, [amount] in total. It moves the launch from [date] to [date]. If you approve it in writing by [day], we'll start on [day]. If you'd rather keep the launch date, we can add it in the first week after launch.

A small favour within the buffer Hi [name], done. That took [time], which comes out of the [two hours] of small requests included in the project. There are [time] left.

A new project Hi [name], a [webshop] is a project in its own right, and adding it now would push the launch back by weeks. Let's launch on [date] as planned, and I'll send you a separate proposal for the [webshop] by [date].

Swap instead of add Hi [name], we can fit the [team page] into the current budget if we drop the [FAQ page], which is about the same amount of work. Or we keep both for [amount] extra. Which do you prefer?

When the client pushes back

• "I thought that was included." Quote the line from the scope, calmly. If the wording really can be read both ways, that is on you: consider doing it this once, and tighten the line in your next proposal. It is one of the misunderstandings listed in the difference between a proposal, a quote and an estimate.
• "It's only a small change." Small changes add up. The log shows the total, and the buffer shows where the line is.
• "We have no budget left." Offer the swap, or move the request to a second phase after launch.
• Requests that never stop after launch. That is ongoing work, not a project. Propose a monthly arrangement with hours included: see how to write a retainer proposal.

Checklist

• The scope counts every deliverable and every feedback round, and has an out-of-scope list.
• The proposal states your rate for extra work.
• A buffer for small requests is agreed, and you keep a log against it.
• Every request gets a reply within two working days: its kind, its price and its effect on the date.
• No change starts without written approval.
• Approved changes go into the scope, the timeline and the next invoice.

This is general information, not legal or tax advice. For your situation, ask a lawyer or accountant.

How Propozit helps

In Propozit you set your rate for extra work in the proposal, and the terms state it for you, so the price of extra requests is agreed before the project starts. Extras you expect can go in as optional lines that the client ticks themselves, with the totals updating as they choose: see how optional lines and live totals work.

Before you send, Propozit checks for a team or a length that does not match the prices and the timeline. Your client signs in the deck, drawn or typed, and both sides get a signed PDF of what was agreed. Propozit does not track hours or send invoices; your change log and your accounting tool still do that.

Propozit is in early access and free to start.