The Pattern
Month 1: "We need a one-time exception for this unusual deal."
Month 6: "We have 200 exceptions this quarter."
Month 12: "Our exception queue IS the comp plan."
I've seen this movie a hundred times. It always ends the same way.
How It Starts
Exceptions start innocently:
- A strategic deal that doesn't fit the standard structure
- A rep transition that needs special handling
- A customer situation that requires flexibility
- A quota adjustment that "just makes sense"
Each one, individually, is reasonable. The problem is they compound.
The Compounding Effect
Exception #1 creates precedent.
Exception #2 references Exception #1.
Exception #47 references Exceptions #12, #23, and #31—none of which were documented properly.
Now you have:
- No standard process
- Inconsistent treatment across reps
- No way to forecast cost
- Legal exposure everywhere
- A comp team drowning in one-offs
The Root Cause
Exceptions explode when the plan doesn't fit reality. They're a symptom, not the disease.
Ask yourself:
- Why do we need so many exceptions?
- What scenarios does the plan not cover?
- Where are the gaps between policy and execution?
Usually, the plan was designed for an ideal world that doesn't exist.
Taking Back Control
Step 1: Categorize
Not all exceptions are equal. Create categories:
- Deal structure exceptions
- Territory/crediting exceptions
- Timing exceptions
- Quota exceptions
- Payout exceptions
Step 2: Define Approval Paths
Who can approve what? A $5K exception shouldn't need the CFO. A $500K exception shouldn't be approved by a sales manager.
Step 3: Document Everything
Every exception needs:
- Business rationale
- Financial impact
- Approval chain
- Expiration date
- Precedent implications
Step 4: Track Precedent
When someone requests an exception, you should be able to see: "We've handled similar situations X times, and here's what we did."
Step 5: Feed It Back
If you're approving the same exception type repeatedly, it shouldn't be an exception—it should be a plan rule.
The Goal
You'll never have zero exceptions. The goal is governed exceptions—predictable, documented, and defensible.
Tags