Every agency has tried the change request form. Every client has ignored it. The requests keep arriving as one-liners in chat, the form gathers dust, and the "process" becomes whatever mood the PM is in that day.
The flaw isn't discipline. The flaw is that the classic process puts the paperwork on the client — the person with the least motivation to fill it in. They don't think their ask is a change. They think it's small.
Photo: Nelizaj, CC BY 4.0
Invert the flow
A process clients follow is one they don't notice. Let them ask the way they already ask — chat, email, a comment on a ticket. Then your side runs the classification:
- Capture — every ask becomes a tracked item, automatically. Nothing lives only in a chat scrollback.
- Classify — compare it against the scope of work: in scope, partial, or out.
- Route — in scope proceeds with a status answer; out of scope gets an estimate and a yes/no put in front of the client, in writing, in the same thread they asked in.
The client experiences none of this as "process". They asked; they got an answer with a price. That's just good service.
The two sentences that make it work
For the client, when something's out of scope:
Happy to do that — it's outside the current scope, so it'd be ~3 days at our standard rate. Want me to schedule it for the next sprint?
For your team, in the SOW:
Requests outside the listed scope items are quoted separately before work begins.
No forms, no committees. The hard part — noticing, classifying, estimating consistently at 9pm on a Friday — is exactly the part software should own.
← All posts