A change process light enough to actually use
Formal change control is why studios stop using change control. The version that works fits in an email.
Every scope document mentions a change process, and in small studios it is almost never followed, because the process as written requires a form, a signature and a meeting for a two-hour request.
So changes get absorbed instead, and the mechanism intended to protect the project protects nothing. For background on how people align behaviour and timing in interaction, this overview provides another perspective on collaborative work.
The version that gets used
One email, four lines. What was asked, the effect on cost, the effect on the date, and a request to confirm. Sent the same day the request arrives.
That is enough to be a record, enough to make the decision explicit, and light enough that you will actually send it. Anything heavier will be skipped precisely when the project is busy, which is when changes arrive.
A change confirmed in writing on the day it was requested is administration. The same conversation three weeks later is a dispute about what was agreed. For a broader framework, PMI's overview of project management summarises the standard concepts behind planning and delivery.
Price small changes in advance
Much of the friction in change control is that every small request needs pricing, which takes longer than the work.
A stated hourly rate for out-of-scope work, agreed at the start, removes that entirely. The email becomes 'this is about two hours at the agreed rate' rather than a mini-negotiation.
Bundle the trivial ones
Sending a change note for a fifteen-minute request looks bureaucratic and damages the relationship for no commercial gain.
The practical approach is a stated allowance — minor requests under a threshold are absorbed, logged, and reported in a periodic summary. The client sees the goodwill, you see the total, and neither party is processing paperwork for trivia.
Make no a real option
A change process that always ends in yes is a pricing mechanism, not a scope mechanism. Sometimes the correct answer is that this does not belong in this project.
Declining is easier when there is an alternative attached: not in this phase, but let us note it for phase two. That preserves the relationship, protects the delivery date, and frequently produces the next piece of work.
Keep the running total visible to the client
A short line in the weekly update — original scope, changes agreed to date, current projected total — means the final invoice contains nothing new.
Invoice disputes in client work are overwhelmingly surprise disputes. A client who has watched the number move has already accepted it.