The customer exception nobody wrote down

Somewhere in most businesses there's a customer who gets something nobody else gets — extended payment terms, a discount off the standard rate, priority handling during busy periods. Ask why, and if you're lucky, someone remembers. If you're not, the answer is a shrug and a slightly awkward pause, because the exception has clearly outlived its explanation.

Exceptions are granted for reasons that make sense at the time

Nobody typically hands out special treatment arbitrarily. The customer was an early supporter who took a chance on the business. Or they had a genuine service failure that warranted compensation. Or they're simply a large enough account that the standard terms don't reflect the relationship's real value. Every one of these is a defensible reason, in the moment it's decided.

The trouble is that the exception, once granted, tends to run indefinitely with no natural trigger to revisit it, while the person who approved it — and the specific reasoning that made sense at the time — doesn't stick around nearly as long.

Why unexplained exceptions become a real problem

They look like favouritism to anyone who wasn't there. A team member handling this customer for the first time sees a discount with no documented reason and reasonably wonders whether it's fair, whether it's still deserved, or whether it's simply been forgotten and never revoked.

They can't be defended if questioned. If a different customer asks why they don't get the same treatment, "I'm not sure, it's just how it's always been for them" is not an answer that holds up, and it exposes the business to a fairness complaint that a documented, defensible reason would have avoided entirely.

They accumulate without anyone tracking the total exposure. Each individual exception feels small. A business can accumulate dozens of small special arrangements over years, and nobody has ever added up what they collectively cost, because no single person owns the full list.

Why this differs from a standard discount policy

A discount policy is a rule, applied consistently, that anyone can look up and understand. A customer exception is, by definition, outside the rule — a one-off judgement call for a specific situation. That's exactly what makes it valuable when it's genuinely warranted, and exactly what makes it vulnerable to being forgotten, since it doesn't live inside any system designed to track rules — see the exception that made sense once and confuses everyone now.

Making customer exceptions defensible

Record the reason at the moment the exception is granted, in specific, concrete language — not "loyal customer" but "founding client, has ordered continuously since 2019, extended terms agreed after a supply delay we caused in 2022." Specific reasons age better than vague ones, because vague reasons are indistinguishable from no reason at all a few years later.

Attach a review point, not necessarily an expiry. The exception doesn't need to end — it needs someone to periodically confirm it's still justified given current circumstances, rather than running forever on the strength of a decision nobody currently at the business witnessed being made.

Give one person visibility over the full list of active exceptions, even if different people manage individual customer relationships. Without a consolidated view, nobody can answer "how much of our pricing is actually non-standard right now," which is a question worth being able to answer.

What to do with the exceptions you already have

Pull together every customer currently on non-standard terms and, for each one, try to state the reason in one sentence. Where the sentence comes easily, you're fine — write it down properly and move on. Where it doesn't, that's the one worth a conversation before the last person who might remember moves on too.

Common questions

Why do customer exceptions lose their justification over time?

Because the exception itself — the discount, the extended terms, the priority handling — persists indefinitely in the system with no maintenance required, while the specific reasoning behind it lives only in the memory of whoever approved it. As that person moves roles or leaves, the reasoning disappears while the exception keeps running.

Why does an unexplained exception create a fairness risk?

Because if a different customer questions why they don't receive the same treatment, "it's just how it's always been" isn't a defensible answer. A documented, specific reason protects the business from a fairness complaint in a way an unexplained exception cannot.

How is a customer exception different from a discount policy?

A discount policy is a consistent, documented rule anyone can look up. An exception is by definition outside that rule — a one-off judgement call for specific circumstances. That's what makes it valuable when genuinely warranted, and what makes it easy to lose track of, since it isn't captured by any system built to track standard rules.

What's a practical way to audit existing customer exceptions?

List every customer currently receiving non-standard treatment and try to state the reason for each in one specific sentence. Where the reason comes easily, document it properly. Where it doesn't, that exception needs a conversation before the person who might still remember the original reasoning moves on as well.

Related: the exception that made sense once and confuses everyone now · configuration without a reason attached · what leaves with an employee that the erp never had