Documenting Exceptions: What Happens When the Rule Does Not Fit

Forty-two exceptions were granted in one quarter against a policy with eleven written rules, and 31 of them were granted for the same three situations. The policy was not being broken. It was being supplemented in a place nobody could see.

The policy governed how a support team handled refunds and credits. Fourteen agents applied it, and the escalation path ran to a team lead who approved exceptions by message.

The invisible rulebook

Exceptions were approved in direct messages, which meant the reasoning lived in a private thread between an agent and a lead. A new agent facing the same situation had no way to know that a precedent existed, so the request was made again from the beginning.

The team lead estimated she answered the same three questions about twice a week for a year.

Logging the exceptions

For one quarter every exception was logged with four fields: the situation in one sentence, the rule that did not fit, the outcome, and the lead’s reason. Nothing else was captured, and nothing was published until the quarter ended.

Forty-two entries accumulated. Reading them took forty minutes and produced a clear pattern.

The three recurring situations

The first was a delivery that had been late by more than the policy allowed but where the customer had reordered before complaining. The second was a duplicate charge under 15 euros, where the cost of investigation exceeded the refund. The third was a business customer whose contract overrode the consumer policy, which everyone knew and nobody had written down.

Thirty-one of 42 exceptions fell into those three groups. The other eleven were genuinely individual cases, and several were generous decisions rather than applications of a rule.

The rewrite

Three rules were added to the policy, each written as a condition rather than a principle. The policy went from eleven rules to fourteen and stopped being a document agents had to work around.

The business customer case became a separate short page, because it applied to a different set of accounts.

What was deliberately left out

The eleven individual exceptions were not turned into rules. The lead argued, and the team agreed, that some of them were judgement calls made once and should stay that way. Writing them down would have created an entitlement that nobody intended to grant.

That decision required a note in the policy saying that exceptions exist and are not precedents, which is the kind of sentence that only makes sense after you have needed it.

The effect

In the following quarter exceptions fell from 42 to 17. The lead’s time on repeated questions dropped to roughly one message a week. Two agents said the policy had become longer and easier at the same time, which is the correct outcome of a rewrite driven by cases.

The exceptions nobody wanted to write down

Four of the eleven individual cases involved a customer who had been with the company for more than five years and had a single late delivery. The lead granted a credit each time, for reasons that were consistent and not codified, because codifying them would have created an expectation the business could not afford.

That tension is permanent for any policy that meets real customers. The written rule covers the repeatable case, and a named person covers the rest, and the two have to sit beside each other without either pretending to be the other.

What the rewrite changed for new agents

Two agents joined the team after the rewrite. Neither had seen the private threads and neither knew that the three added rules had once been exceptions, which is the point. A rule that has absorbed its own history reads as ordinary, and ordinary rules get followed.

The team kept the exception log as a reference, though nobody reads it now. Keeping it costs nothing and it is the only record of how the policy acquired its current shape.

Forty-two exceptions once hid in private messages, 31 of them for the same three situations. The rules now name those situations, and the private thread is shorter because the policy answers first.