What It Actually Means
That is the whole mechanism. Its value is entirely in the ordering: priced first, built second. Reverse those and it stops being a change request and becomes an invoice you did not expect.
Why It Exists
Change requests protect both sides, which is worth saying because they are usually presented as protecting the supplier.
For the supplier, they prevent unpaid work accumulating from a series of small verbal asks.
For you, they do something more useful: they make the cost of your own decisions visible at the moment you make them. Asking for something in a status call feels free. Seeing that it adds four days and pushes launch into the following month changes the decision, and often you decide you did not want it that much. That information arriving before the work rather than after is the entire point.
What Good Looks Like
A change request worth its paperwork says four things: what is being added, what it costs, what it does to the timeline, and what it affects that already exists.
The fourth is the one usually missing and it is frequently the largest. Adding a field to a form is an hour. Adding a field to a form that appears in three exports, two reports and a client-facing PDF is a day and a half. A supplier who consistently surfaces knock-on effects is doing the job properly.
Turnaround matters too. Change requests that take a week to price will simply be bypassed, and everyone will go back to verbal agreements. Small changes should be priced in a day, and the process should be proportionate: a two-line email for a small item, something fuller for anything significant.
What To Ask
- What does this affect that already works? The knock-on cost is usually bigger than the direct cost.
- What does this delay? Time is the impact people forget to ask about.
- Can it wait until the next phase? Batching changes is nearly always cheaper than interleaving them.
- What is the running total of changes so far? This is the number that matters, and it should be available on request at any point.
When The Process Is Being Used Against You
Two patterns are worth watching.
The first is change requests for things a reasonable person would consider implied by the original scope. If the agreement said “customers can pay online” and the change request is for a receipt email, that is not a change, that is the thing you bought. Push back.
The second is the reverse and it is more common: no change requests at all, everything absorbed without comment, and a difficult conversation at the end about how much extra was done. A supplier who never raises changes is not being generous. They are accumulating a grievance, and you will hear about it during the final invoice or the renewal.
Where changes are frequent and small, a retainer is often the better commercial shape, because it removes the friction of pricing every individual item. Where they are the symptom of a scope that was never firm, the underlying issue is scope creep rather than the change process itself.
More terms are in the glossary.
