Deal exception rate is the share of closed deals that needed approval outside the standard price book, contract template, or deal structure. A rep quoting list price on standard paper is not an exception. A rep asking for thirty points off, net-90 payment terms, or a custom uptime commitment is.
How to calculate it
Count the deals in a period that went through an exception approval, divide by all deals closed in that period, and multiply by 100. Then run the same math weighted by contract value. The two numbers rarely match. A team can grant exceptions on a small share of deals and still concede on most of the revenue, which is the case that matters to finance.
What the number tells you
A rising exception rate points at the offer, not at the reps. If enterprise deals almost always need custom terms, the enterprise package is priced or scoped for a buyer who does not exist. Adding approval layers slows those deals down without changing the outcome, because the desk approves them anyway.
A rate near zero deserves the same scrutiny. Either the thresholds are too loose to catch anything, or deals are being structured to stay under them. Reps split a commitment into two order forms, or move value into a side letter, and the review never happens.
Read it by segment and by week
The aggregate hides where pressure sits. Break exceptions out by segment, product, region, and rep tenure, and the pattern usually resolves into a specific gap: one product that never sells at list, one region where the price book was never localized, or new reps who discount because they cannot defend the price.
Then break it out by week of the quarter. Exceptions cluster in the closing weeks, and each one granted then becomes the reference price for the next similar deal. Procurement teams share numbers. A quarter-end concession is a permanent one.
Why it belongs in the forecast
Exception data is a leading read on competitive pressure. More discount requests, longer payment terms, and shorter commitments show up in the desk queue weeks before they show up in average selling price. Tracking the queue gives you that warning early enough to reprice or requalify.
It also corrects the pipeline. ORM's customer data shows most deals close for less than the value recorded in the CRM, so a pipeline carried at list price is already optimistic before a single exception is approved. Feeding the historical exception pattern back into deal values makes forecast accuracy a function of what deals actually close for.
Track this alongside the volume of nonstandard terms your deal desk processes. Together they tell you whether the desk is protecting the price or documenting its decline.
Frequently Asked Questions
How do you calculate deal exception rate?
Divide the number of deals that required an approval outside standard pricing or terms by the total number of deals closed in the same period. Run the same calculation weighted by contract value, because ten small exceptions and one large one carry very different consequences for revenue.
Is a high deal exception rate bad?
It is a pricing signal before it is a discipline problem. When most deals in a segment need an exception, the standard offer for that segment does not match what those buyers will sign. The fix belongs in packaging and price levels, not in adding approval steps.
What counts as an exception?
Anything that leaves the standard path: a discount past the approved threshold, nonstandard payment terms, a custom SLA or security commitment, a ramped commitment, or an off price book SKU. Quoting list price on the standard order form is not an exception.
Can the exception rate be too low?
Yes. A rate near zero usually means thresholds are set so loosely that nothing trips them, or reps are structuring around the desk and booking terms nobody reviewed. Either case leaves the company exposed at renewal.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like deal exception rate into prescriptive action for your team.
Schedule a Demo