Individual exceptions are inevitable — plans will always have edge cases, data will occasionally break, and managers will sometimes need to approve a one-off correction. The exception pattern is what matters. When 8% of a cycle's payouts require an exception, you don't have 8% random incidents; you have a systemic issue pretending to be many small problems.
This tool categorizes your current cycle's exceptions across six standard types and surfaces the ones dominating the pattern. Categories that exceed healthy thresholds map to specific root causes — data pipeline issues, plan configuration drift, policy gaps, or process breakdowns — each with a concrete next-step recommendation.
The six exception categories — and what each tells you
1. Data corrections (healthy < 2% of deals)
Exceptions caused by incorrect deal data in the source system — wrong amount, missing rep, incorrect close date. If this category dominates, your data pipeline is the problem, not your plan. Investment should be in Data Readiness, not plan simplification.
2. Calculation corrections (healthy < 1%)
Exceptions caused by the engine producing a wrong number. Any notable rate here is a red flag — this is where reps lose trust fastest. Use the Calculation Accuracy Checker to validate the engine.
3. Crediting adjustments (healthy < 2%)
Exceptions resolving a crediting dispute (wrong rep, split disagreement, entity-of-record question). If dominant, plan crediting rules are too ambiguous — Crediting Complexity Scorer identifies what to simplify.
4. Policy exceptions (healthy < 1.5%)
Approved deviations from the plan document — manager overrides, retention SPIFFs, one-off rewards. If high, your plan is not supporting the business reality and managers are patching it with discretionary approvals. Fix by updating the plan, not by tightening approval gates.
5. Timing adjustments (healthy < 1%)
Corrections for out-of-period bookings, late contract amendments, or cycle-cutoff issues. If high, investigate the cut-off enforcement and data freshness in your cycle process.
6. Other / miscellaneous (healthy < 0.5%)
Exceptions that don't fit the other categories. A small amount is normal; a high rate means you need more specific categories because you're losing signal in a generic bucket.
Total exception rate is the wrong metric in isolation. A plan with 4% data corrections and 0% of everything else has a very different root cause than one with 0.5% in every category totaling 3%. The per-category thresholds reflect how much variance is "noise" vs "signal" for each type — data issues have high natural noise, calculation issues should be near-zero in a mature plan.
Exception Tracker
Enter one cycle's exception counts by category. Find the dominating pattern.
ℹ️ How this tool works +
The question it answers: Which category of exception is dominating my cycle, what's the root cause, and where should I invest to reduce the pattern?
What to enter:
- Total Deals This Cycle — closed-won deals processed in the cycle you're analyzing.
- One count per category: Data corrections, Calculation corrections, Crediting adjustments, Policy exceptions, Timing adjustments, and Other. Classify each exception into exactly one category.
Per-category healthy thresholds:
- Data corrections: <2% of deals
- Calculation corrections: <1%
- Crediting adjustments: <2%
- Policy exceptions: <1.5%
- Timing adjustments: <1%
- Other: <0.5%
What you'll get back:
- Overall exception rate with band (Lean <3% / Acceptable <6% / Concerning <10% / Critical ≥10%).
- Category breakdown bar chart with categories exceeding their healthy threshold flagged in red.
- Root-cause flags for flagged categories, with specific next-step recommendations and cross-links to relevant complementary tools.
Sample cycle pre-loaded. Run this tool monthly to see how the exception pattern evolves over time.
Benchmarks, ranges, and default values in this tool reflect Falcon's practitioner experience across consulting engagements. They are directional starting points, not substitutes for market survey data. For binding compensation decisions, validate key figures against Radford, Mercer, Carta, or WorldatWork survey data for your specific geography, industry, and company stage.
How to act on the pattern
Lean (<3%) — Operational excellence
You're running a well-controlled plan. Keep the exception log as a leading indicator of emerging issues — a sudden rise in any category deserves immediate investigation, even at this baseline.
Acceptable (3–6%) — Normal enterprise range
Most mature SalesOps teams live here. Focus on the highest category specifically rather than trying to reduce overall rate — category-specific investments pay back far more than broad cleanup.
Concerning (6–10%) — Active investment needed
Exception volume is costing meaningful SalesOps time and rep trust. The dominating category indicates the root cause. Pair this tool with the Dispute Cost Calculator to get a dollar figure to anchor the investment case.
Critical (≥10%) — Stop and redesign
You're running exceptions instead of a plan. Patch mode is no longer sustainable. Use the category mix to identify where the redesign focus should go — plan, data, or process.
Exception rates drift upward over time in almost every plan. A 3% rate in Q1 becomes 5% in Q3 as edge cases accumulate and managers learn which exceptions get approved. Without active monitoring, you don't notice until someone does a year-end audit and asks why half the cycle requires manual intervention. Run this tool every cycle, not annually.
Running too many exceptions?
We help SalesOps teams root-cause exception patterns and fix the underlying plan or process — not just the next ticket. Book a 20-minute review.
Book a 20-minute consultation →FAQ
No — count each exception once, in its root cause category. A data error that cascades into a calculation correction is a data exception, not two exceptions. Pick the earliest cause in the pipeline.
Any deal that required manual intervention beyond the normal calc and approval flow. If SalesOps, a manager, or the rep had to make a decision or correction outside the standard workflow, count it. Routine manager approvals of correctly-calculated statements don't count.
Exception Tracker tells you which category is dominating. The other tools tell you how to fix it: data corrections → Data Readiness Checklist; calculation corrections → Calculation Accuracy Checker; crediting adjustments → Crediting Complexity Scorer.
No. Zero exceptions indicates either (a) a trivially simple plan with no business nuance, or (b) nobody's logging exceptions. Some baseline is healthy. The goal is knowing why the exceptions you have exist, and preventing them from growing.