MSPs & IT: Document every change request before touching a ticket

An MSP owner in Durban told me once that his single largest source of revenue leakage was scope creep on support tickets. A client would call about a server issue. During the call, they'd mention — almost as an aside — that their VPN was also acting up and could they maybe take a look at that too. The technician would fix it, because the technician's instinct is to be helpful. That extra work wouldn't get billed because nobody documented it as a separate request. Over a year, across a team of twelve technicians, the owner estimated he was losing roughly R300,000 in unbilled out-of-scope work.

MSPs and IT service providers operate in a uniquely vulnerable position when it comes to scope creep. The work is technical, often urgent, frequently communicated through informal channels, and almost always involves trust — the client trusts you to fix things, and you trust the client to pay fairly. The problem is that trust doesn't generate invoices. Documentation does.

Here are the four documentation points that MSPs need to lock down.

First: change request approval. When a client asks for something beyond the managed services agreement — a new deployment, a configuration change, an additional integration — capture it as a receipt before work starts. Three bullet points: what the change is, what it costs, how long it'll take. Client confirms with a one-time code. The receipt becomes the billing trigger. No more "I thought this was included" conversations when the invoice arrives.

Second: incident documentation. When a major incident occurs — a ransomware recovery, a server failure, a data breach response — the work is urgent and the cost is unclear. You can't pause a disaster recovery to negotiate scope. But you can document what happened, what was done, and what it will cost as soon as the immediate crisis is resolved. A receipt sent within hours of incident resolution, while the client's memory of the emergency is still fresh, dramatically reduces subsequent billing disputes.

Third: budget confirmation. MSPs frequently operate on retainer or block-hour models, and scope changes that exceed the retainer are the most commonly disputed charges. When a client's request will push them beyond their contracted hours, a receipt confirming the overage — before the extra work happens — protects both sides. The client knows what they're committing to. The MSP knows they'll get paid.

Fourth: WhatsApp acknowledgment. Many MSP clients communicate primarily through WhatsApp, especially in South Africa where it's the dominant business messaging platform. A client WhatsApps their account manager about a server upgrade. The account manager says yes. The work gets done. The invoice goes out. The client disputes it because they don't remember the conversation. A receipt sent through WhatsApp, confirmed with a one-time code on the same thread, creates an instant, searchable record that prevents this cycle.

The Durban MSP owner implemented receipt documentation for all out-of-scope work about a year ago. Within three quarters, his recovered revenue from previously unbilled change requests exceeded R200,000. More importantly, his technicians stopped feeling resentful about doing free work, because the system now captured what they were actually delivering. For an MSP operating on thin margins — and most are — that's not a productivity improvement. It's a business model fix.