Scope, and the Request That Is Not In It

How it arrives

Not as a demand and not unreasonably.

Somebody says while you are in there, could we also add a booking form, or asks whether the pages could have a testimonial section, or mentions that the manager would like a different photograph on each service page.

Each is a sensible request from somebody who wants a good outcome, and none was quoted.

The reason this causes so much damage is that neither party wants to have the conversation, so the first three requests are absorbed silently and the fourth produces a reaction out of proportion to what was asked.

Silent absorption is the failure

The supplier's instinct is to say yes to keep the relationship comfortable, particularly early.

That establishes a pattern: requests are free, so more arrive, and by the time somebody says no the client has reasonably concluded that this is how the project works.

The refusal then looks arbitrary rather than principled, and it usually happens when the supplier is already behind and irritated, which is the worst moment to raise it.

Naming the first small request as out of scope, while agreeing to do it anyway, costs nothing and prevents all of that.

The sentence that handles it

Three parts, in one reply, without apology.

Yes, that is a good idea and it can be done.

It is not in the current scope, and here is what it would take: roughly this much time, or this much cost.

Do you want it added now, which moves the date, or noted for after launch.

That framing is not a refusal and it is not a negotiation. It gives the client a choice with the consequences attached, which is what they needed in order to decide.

Most requests handled this way are deferred by the client themselves once the cost is visible, which is a better outcome than either party arguing.

Give away small things deliberately

Worth doing and worth naming when you do it.

A five-minute change is not worth a change order, and insisting on process for trivial requests makes a supplier tiresome to work with.

The distinction is between absorbing it silently and absorbing it visibly.

That one is quick, so I have done it, and it is outside the original scope, takes the same five minutes and buys goodwill rather than establishing a precedent.

The client learns that requests are tracked and that you are being generous, which is the impression you want rather than the impression that scope is meaningless.

Keep a list where both can see it

• What was asked, in the client's words.
• Whether it is in scope or not.
• Rough time or cost if it is not.
• The decision: now, later, or no.
• The date it was raised.

A shared document rather than a supplier's private notes, because the purpose is that neither party is surprised at the end.

It also becomes the phase two list, which is genuinely useful to both sides.

A worked example

A ten-week project accumulated eleven requests, all reasonable, none quoted.

The supplier absorbed the first seven, raised the eighth, and the client reacted badly because nothing had suggested a limit existed.

The project finished four weeks late with both parties unhappy and the final invoice disputed.

On the next project the same supplier logged every request in a shared document from week one, marked in or out of scope, with a rough figure against each.

Fourteen requests arrived. The client approved three, deferred nine to a later phase, and dropped two once the cost was visible.

The project finished on time, the deferred list became a second engagement six months later, and the same supplier had absorbed a comparable amount of small work without it becoming an issue.

The only change was that the requests were visible.

When the client is right that it should be included

Sometimes it should have been, and this is worth conceding quickly.

A request that is genuinely necessary for the deliverable to work, or that any competent supplier would have anticipated, is arguably part of the job even if the document does not name it.

A contact form that needs to send to two addresses, or a page that needs to work on a phone, is not a change request.

Where a client makes that argument reasonably, conceding it immediately costs less than defending a technicality and protects the relationship.

The reverse also applies: a client who hears the scope explanation and accepts it is doing their part, and that should be acknowledged rather than treated as expected.

Phase two is a real answer

The most underused option and usually the best one.

Most out-of-scope requests are not urgent. They are good ideas arriving at an inconvenient moment.

Deferring them protects the launch date, which is the thing most likely to be lost, and it gives the client a considered second stage rather than a set of additions bolted on under pressure.

It also produces a natural follow-on engagement, which suppliers under-propose because they feel it looks like upselling.

Presented as we can do this properly after launch rather than squeeze it in now, it is a service rather than a sale, and most clients recognise that.

The counter-case

Scope discipline can be taken too far and becomes its own problem.

A supplier who raises a change order for every minor adjustment is exhausting, and clients stop asking for things, which produces a worse site than one with a bit of give in it.

There is also a class of project where rigid scope is the wrong model entirely: exploratory work, where nobody knows the answer at the start, is better run on a time basis with a budget cap than on a fixed scope that will be wrong by week three.

And on a long relationship, the accounting matters less than the balance over time, which most good suppliers and clients settle informally.

The discipline exists to prevent surprise, not to prevent generosity.

How to handle it

1. Say yes to the idea before anything else.
2. Name it as out of scope in the same reply.
3. Attach a rough time or cost.
4. Offer now or later, with the consequence of each.
5. Log it in a shared list.
6. Absorb small things visibly, not silently.
7. Propose the deferred list as a second phase.

Step two on the first small request is what prevents the difficult conversation on the eighth.

Preparing before a project starts is covered in what to have ready before you start.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.