Pipeline coverage review with comparable stages
Review pipeline coverage with stage comparisons, supported amounts, and consistent definitions instead of a single coverage ratio.
Pipeline coverage review with comparable stages
A pipeline coverage review compares the amount the team needs with what it can realistically close. That comparison only works when stages, amounts, and the observation window use the same definitions.
A single coverage ratio can hide weakness in a specific stage. Review coverage by stage and source so the team sees where the pipeline is thin, not just a total.
Define what counts
Publish which opportunities enter the coverage population and which stay outside, such as proposals, renewals, or channel deals. A consistent population keeps the ratio explainable.
Record the definition version and the snapshot time. Live pipelines change during review, so a frozen snapshot lets every reviewer see the same numbers.
Use supported amounts
Base the coverage math on the most recent supported opportunity values rather than an unsupported upside figure. State whether amounts are list, discounted, or forecast values.
Treat kept open opportunities with visible uncertainty separately from confirmed stages. Do not let one optimistic close value inflate the whole ratio.
Compare across stages
Review coverage at each pipeline stage and source so weakness in one stage does not get hidden by strength in another. A healthy total can still hide a broken conversion point.
Publish the stage definitions and the expected conversion range. Investigate a stage with striking coverage or a gap rather than assuming the total tells the story.
Assign review owners
Name the owner who reviews each segment, confirms the amounts, and records decisions about disputed opportunities. Lead a short review that produces an accountable next action per segment.
Route a disputed value through the accountable owner with evidence. Do not let the reviewer silently reclassify opportunities to improve the ratio.
Close and compare
Retain the snapshot, the definition, the amounts, and the review decisions. Compare later outcomes against the same definition to see whether coverage predicted the close.
Version the definition when it changes and preserve the old values. Avoid tuning the definition to make the current number look better.
Sources
- How to Build a Sales Forecast, Salesforce Trailhead. Explains forecasting stages and the comparison of pipeline against stated targets.
Related GTM guides
Frequently asked questions
Is total pipeline coverage enough?
No. Review coverage by stage and source so weakness in one stage does not hide behind a healthy total.
What amounts should the ratio use?
Use the most recent supported opportunity values and state whether they are list, discounted, or forecast amounts.