The Exception You Approved Once Is Now Company Policy

"We always do free next-day delivery for Hartley & Co."

Your new warehouse supervisor mentions it in passing. You stop.

Always? Since when?

You remember. Back in October, Hartley's buyer called in a panic. They'd miscounted stock for a product launch. Could you expedite shipping just this once? You said yes. Good client, long relationship, seemed like the right call.

That was the exception. Somewhere between then and now, it became the rule.

No one wrote it down as policy. No one asked if it should apply to every Hartley order going forward. But the person who handled that October shipment remembered. They told the next person. Now it's baked in. Free next-day delivery, every order, eating into your margin on one of your biggest accounts.

The Exception Creep Problem

This happens more than most founders realise. You make a one-time call — a discount, a custom term, an extra service — and it calcifies into permanent practice without ever passing through an actual decision.

The mechanism is simple. Someone on your team sees you approve something. They don't know it was a one-off judgment call based on context they weren't privy to. They just know: the boss said yes. So next time a similar situation comes up, they don't ask. They just do what you did.

Rinse, repeat. Six months later, you've got a patchwork of unofficial policies you never approved, based on exceptions you barely remember granting.

A few examples I've seen in real businesses:

• A 10% discount given once to close a deal, now automatically applied to every quote for that client
• A custom payment term (net 60 instead of net 30) that spread from one account to the entire sales team's playbook
• A free add-on service offered during a difficult project, now expected by every client who heard about it
• A rush turnaround granted once, now the assumed standard for an entire product category

None of these were decisions. They were moments. But your team, reasonably, treated them as precedent.

Why This Keeps Happening

The root cause isn't your team being sloppy. It's the absence of a clear line between "exception" and "policy."

When you approve something in the moment — on a call, in Slack, walking past someone's desk — there's no flag that says "this is a one-time thing." The approval looks identical to a policy change. Your team can't tell the difference because you didn't make one visible.

And frankly, neither did you. In the moment, you were solving a problem. You weren't thinking about what happens the next fifty times that situation arises.

This is how exception creep works. It doesn't announce itself. It just accumulates, one reasonable-seeming repetition at a time, until you're subsidising shipping costs you never agreed to or honouring terms that made sense exactly once.

How to Stop Granting Policies by Accident

The fix isn't complicated, but it requires a small habit change.

Make the exception explicit. When you approve something non-standard, say so out loud. "Yes, we'll do it this time, but this isn't standard — next time they need to pay for express." That single sentence gives your team a frame. They know this was a judgment call, not a new rule.

Write down your actual policies. This sounds obvious, but most businesses have vague or incomplete documentation on pricing, terms, and service levels. If there's no written policy, your team will infer one from behaviour. Usually yours.

Create a way to flag exceptions. Some teams use a tag in their CRM or project notes: "ONE-TIME" or "EXCEPTION — DO NOT REPEAT." Low-tech, but effective. It creates a record that this wasn't supposed to be permanent.

Review the exceptions that stuck. Audit your client accounts for non-standard terms. Ask your team: "Is there anything we do for specific clients that's different from our standard?" You'll find policies you didn't know you'd created. Some of them might be worth keeping. Many won't be.

The goal isn't to stop being flexible. Flexibility is often the right move. The goal is to stop accidentally converting flexibility into permanent margin erosion.

The Real Cost

Exception creep doesn't just cost money — though it does that. It also costs clarity. Your team ends up navigating a maze of unofficial rules, unsure what's actually standard and what's a ghost policy from some long-forgotten favour.

That uncertainty slows everything down. People ask more questions, or worse, they guess wrong.

If you've been running a business for more than a couple of years, you almost certainly have exceptions that became policy without a decision ever being made. Might be worth a look.

If this kind of operational archaeology sounds useful, it's something we dig into with clients regularly.