Scope is the answer to a single question: what, exactly, are we being asked to deliver? Write the answer down and a job is manageable. Leave it as a feeling shared between two people, and you have built the conditions for every argument that will follow.
This lesson is about how scope behaves in practice — which is to say, how it grows.
Scope has two sides
People think of scope as a list of what is included. That is half of it. The other half, the one that protects you, is a list of what is not included.
| Scope IN | Scope OUT |
|---|---|
| Marble cladding to the feature wall, supply and install | The feature wall itself, which is others’ work |
| All joinery shown on drawing DRG-J-03, revision B | Joinery not shown on that drawing |
| Snagging of the work you carried out | Repairs to defects caused by others |
| Lighting fixtures as per the approved schedule | The lighting design, which the consultant owns |
A scope with only an “IN” column looks complete and is not. The “OUT” column is where the surprises live, because most disputes are not about what was included — they are about what each side assumed was included.
The “while you are here” request
This is how scope grows on a real job. Not through big dramatic changes, but through a stream of small requests that each feel too minor to refuse.
The danger is never one favour. It is the pattern. Free small work does not feel like scope change to anyone, so nobody flags it, and by the time the job is bigger than it was sold, there is no record of how it happened.
How to say yes properly
The answer to scope creep is not to say no to everything. Refusing every small request is how you lose a client. The answer is to say yes properly — which means treating the request as the change it actually is.
-
Record it
Write the request down, in words both sides would recognise. “Two extra downlights in the corridor, as discussed” — not “some extra lighting”.
-
Price it
Put a number on it. Material, labour, and a margin. Even a small number makes the request real instead of invisible.
-
Get it agreed
Send it to the client and get a yes before the work starts, not after. Agreement up front is what separates a paid change from an argument.
Done this way, yes is safe. The client gets their extra downlights. You get paid for them. And there is a paper trail, so at the end of the job the scope is what was actually built, not what two people remember differently.
There is a name for this practice once it is formalised: a variation, or a change order. We will come back to it in a later track. For now the principle is enough: nothing changes the scope without being recorded, priced, and agreed.
The hardest version of this lesson
The hardest “while you are here” to handle is the one from a client you like, on a job that is going well, for something genuinely small. Refusing feels petty. Recording and pricing it can feel petty too, in the moment.
It is not petty. It is the single discipline that separates contractors who finish jobs in profit from contractors who finish them bewildered. The client you like, on a job going well, is exactly the client who will respect a clear process — because clear process is also what protects them from surprises at the final account.
What this looks like in Taskity
Every extra request against a job lives as a recorded change, with a description, a price, and an approval. The running scope of the job is always the original agreement plus every agreed change — never a memory. Saying yes properly is built into the workflow, so the small favour stops being the thing that quietly sinks the margin.
Check what you learned
1. The client says, "While you are here, can you add two extra downlights in the corridor — it is a tiny thing." What is the real cost of just doing it?
Show the answer
Far more than two fittings, once ten such favours compound and none were tracked
A single extra downlight is genuinely cheap. The danger is never one favour — it is the pattern. Ten "while you are here" requests, each too small to price and none of them recorded, quietly change what the job is. By the time you notice, you are delivering a bigger job for the original price, and the client has no idea anything changed. The fitting is cheap; the untracked scope is not.
2. You want to agree to the client's extra request without poisoning the relationship. Which approach protects both sides?
Show the answer
Record it, price it, and get it agreed before the work starts
Saying yes properly is not the same as saying no. Recording the request, pricing it, and getting agreement up front turns a vague favour into a documented change. The client knows what they are getting and what it costs, you get paid for the work, and there is no dispute at valuation time. Done this way, yes is safe — and often the client decides the extra was not worth it after all, which is also a clean outcome.
Scored quizzes, progress tracking and certificates live inside Taskity.
Next: What a BOQ is, and why it rules everything downstream →