Why it matters for agencies
Change requests are the pressure valve for scope creep. They let a client change their mind without the agency absorbing the cost, and they leave a record that explains why a project ended up different from its SOW.
How to do it or work it out
Use one form for every change: what is being asked, who asked, the estimated hours, the effect on the delivery date and a space for approval. Keep the estimate in hours so it is easy to compare with the budget.
Do not start the work until it is approved, and log the approved hours against the same project so the original budget and the changes can be told apart.
Set a response time on both sides, for example the agency estimates within two working days and the client decides within five. A request that sits unanswered while work is paused costs both parties.
A worked example
Midway through a build, a client asks for a new login option. The developer estimates 9 hours and one extra day. The change request goes to the client, who approves it. The project's total moves from 120 to 129 hours, and the delivery date moves by a day. Had the developer started without approval, the 9 hours would have shown as an overrun against the original 120, with nothing on record to say the client asked for them.
Common mistakes
- Starting before approval. Work done to keep things moving becomes work you cannot charge for.
- Estimating in vague terms such as a small change. Give hours, because hours are what the budget is measured in.
- Forgetting the effect on dates. A change that adds 9 hours may also move a launch, and the client needs to know both.