`Loss Reason Capture Rate = Closed Lost Deals With a Valid Code / All Closed Lost Deals`
Coverage is only half the test
The second test is whether the missing records look like the captured ones. Pull the uncoded losses and compare them against the coded set on the dimensions that would change a decision.
| Dimension | What a gap means |
|---|---|
| Average deal size | Large uncoded losses mean the expensive failures are invisible |
| Segment | Enterprise gaps distort the roadmap input most |
| Rep and manager | Concentrated gaps are a management problem rather than a tooling one |
| Competitor present | Systematic gaps here quietly deflate competitive loss counts |
Consistency beats cleanliness
ORM's position on revenue data is that everyone believes their data is uniquely bad, and it does not matter as much as teams think, since consistent errors still support accurate prediction. The same logic applies to loss codes. A team that always codes competitive losses as price is at least legible once you know it, and the pattern can be corrected for.
What breaks the analysis is inconsistency, where the same situation is coded three different ways depending on who owned the deal. That is why the audit matters more than the compliance percentage. Read a sample of closed lost records against the codes attached to them and see whether the same story produces the same code across reps.
Where the number belongs
Put capture rate on the same weekly data quality view as any other field completeness measure, split by manager, and treat it as a leading indicator for the credibility of the loss mix rather than as a scorecard for reps. When capture rate moves, every downstream conclusion about competitors and pricing moves with it. See win rate for what the coded losses are ultimately explaining, and sales forecasting for why a shifting loss mix belongs in the model rather than in a quarterly readout.
Frequently Asked Questions
What counts as a captured loss reason?
A code from the approved list, plus any second field that code requires, such as the competitor name on a competitive loss. An entry of other with no supporting note is a blank wearing a costume. Count it as missing, or the capture rate will read high while the loss mix stays unusable.
What capture rate do you need before the loss mix is trustworthy?
Coverage matters less than whether the gaps are random. Moderate capture with missing records spread evenly across reps and segments gives a directionally sound mix. High capture where reps skip the field on the losses that reflect worst on them gives a mix that is confidently wrong. Test the gap before you trust the total.
How do you raise capture without collecting noise?
Make the field required at the moment the stage is set to closed lost, keep the list short enough to read, and audit a sample of coded deals each quarter against the notes on the record. A required field with fourteen options produces compliance and no information, because reps pick whichever option is first or hardest to argue with.
Is it worth backfilling loss reasons on old deals?
Only with a label. Codes assigned weeks after the fact record what the rep remembers rather than what happened, so backfilled data belongs in its own series rather than blended with reasons captured at close. Use it for coverage of a specific question, and keep it out of the trend line.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like loss reason capture rate into prescriptive action for your team.
Schedule a Demo