What is pipeline coverage?
Pipeline coverage is the ratio of open pipeline value to the revenue target for the same period. If a team needs $1 million this quarter and has $3 million of open deals due to close in it, coverage is 3x.
The ratio exists because not every deal closes. Coverage asks a single question: is there enough in play that a normal win rate gets us to the number? It is a sufficiency check on the top of the funnel, run early enough that something can still be done about the answer.
How to calculate pipeline coverage
Divide the total value of open opportunities with a close date inside the period by the target for that period. Three million divided by one million is 3x coverage.
Two decisions determine whether the number means anything. The first is which deals count: only those with a close date in the period, and only those still genuinely open, not the ones nobody has touched in two months and nobody has had the nerve to close as lost. The second is whether to use full value or weighted value. Full value against the target is the conventional coverage ratio and the one most benchmarks assume. Weighted value, where each deal is multiplied by its stage probability, is a forecast rather than a coverage figure, and comparing a weighted number against an unweighted benchmark is the most common way this metric gets misread.
What coverage ratio should you aim for?
Three to four times the target is the benchmark most sales organisations work to, on the reasoning that a team closing roughly a quarter to a third of qualified opportunities needs three to four times the number in play to land on it.
The benchmark is only a starting point, because the right ratio is a function of your own win rate rather than a rule. A team that closes half of its qualified deals needs closer to 2x. A team that closes one in eight needs 8x and should probably be asking why qualification is letting so much through. Calculate the ratio your own history implies before adopting anyone else’s.
A very high ratio is not reassurance. Coverage of 10x usually means the pipeline is full of deals that were never qualified, close dates that have been rolled forward repeatedly, or opportunities created to make a dashboard look healthy. Unusually high coverage is a prompt to audit, not to relax.
Pipeline coverage and activity coverage are different things
Pipeline coverage tells you whether enough value exists. It says nothing about whether anyone is working it. A team can hold 4x coverage while half those deals have had no contact in three weeks, and the ratio will look healthy right up to the point the quarter closes short.
Activity coverage is the second question: what proportion of open deals have had a meaningful interaction recently, and who owns the ones that have not. The two metrics fail in opposite directions. Thin pipeline coverage with strong activity means the team is working hard on too little. Strong pipeline coverage with thin activity means the value is there and nobody is touching it. Only reading both together tells you which problem you actually have.
Where pipeline coverage misleads
Coverage is an average, and averages hide concentration. A team at 3x where a single deal is 60 per cent of the pipeline does not have 3x coverage in any useful sense, because one procurement delay takes the quarter with it.
Coverage also assumes the close dates are real. Pipelines accumulate deals whose dates have been pushed three times and are now sitting in the current quarter because nobody moved them out, which inflates the numerator with revenue that was never going to arrive. Recalculating coverage after clearing stale close dates usually produces a very different and much less comfortable number.
Finally, coverage is a point-in-time reading, so the trend matters more than the level. Coverage falling from 4x to 3x over six weeks is a worse sign than a flat 3x, because it means deals are leaving the pipeline faster than new ones are entering it.
Pipeline coverage in Empiraa Signal
Empiraa Signal tracks coverage against the targets set for each person and territory, and deliberately separates pipeline coverage from activity coverage so the two are never read as one number.
Because targets, deals and activity history live in the same system, coverage is calculated from the pipeline as it actually is rather than from an export that was accurate on Monday. ANI, the AI built into Empiraa Signal, flags the gap between the coverage a team has and the coverage its own win rate says it needs.
