RevOps Architecture, CPQ & Billing Systems IntegrationPlaybook3 min readUpdated September 2026

Building a Pipeline Coverage Dashboard Leadership Trusts

A pipeline coverage number is meant to answer one question: is there enough open pipeline to hit the target. It's a useful number right up until stale deals, ones that haven't moved in months but never got marked closed-lost, start padding it, and a coverage ratio that looks healthy on the dashboard stops meaning what leadership thinks it means.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What coverage is supposed to measure

Pipeline coverage compares open pipeline value against the revenue target for a given period, usually expressed as a multiple: three times the target in open pipeline is a common rule of thumb, though the right multiple depends heavily on your typical win rate and deal cycle. The number exists to give leadership an early warning if there isn't enough in the pipeline to plausibly hit the number, well before the period ends and it's too late to do anything about a shortfall.

Why does stale pipeline inflate the coverage ratio?

A deal that hasn't had a real update in two months but is still sitting open in "negotiation" counts toward coverage exactly the same as a deal that's moving fast toward close. Reps have little incentive to mark a stalled deal closed-lost, since doing so removes it from their active pipeline and their personal numbers, so it lingers, inflating the coverage ratio without representing any real chance of closing.

The more stale deals accumulate, the more the coverage number diverges from reality, until leadership is making decisions off a ratio that looks comfortable but doesn't reflect what's actually likely to close.

Building the dashboard with a deal-age filter

Segment coverage by how recently each deal was actually updated, not just by stage. A deal in negotiation with an update in the last week is a very different signal from one in the same stage with no update in six weeks. Showing coverage both with and without stale deals included, side by side, makes the gap between the optimistic and realistic number visible at a glance, rather than requiring someone to dig for it.

To build a coverage dashboard leadership can trust:

  1. Calculate coverage as open pipeline value against the period's revenue target, using a multiple based on your own win rate and deal cycle.
  2. Segment every open deal by how recently it was actually updated, not only by stage.
  3. Show coverage with stale deals included and excluded side by side, so the gap between the optimistic and realistic number is visible at a glance.
  4. Give reps a low-friction way to mark stalled deals closed-lost, and avoid penalizing a high closed-lost count on its own.
  5. When the ratio looks healthy, ask what share sits in deals with recent activity before treating it as good news.

What should leadership ask when coverage looks healthy?

A coverage ratio that clears the target multiple isn't automatically good news. The follow-up question that matters is what share of that coverage is in deals with recent activity versus deals that have gone quiet, and whether the ratio would still clear the bar with stale deals excluded entirely. A number that only looks healthy because of deals that are effectively dead isn't actually healthy.

Keeping the dashboard from becoming a gaming target

Once reps know coverage is a number leadership watches closely, some will find ways to keep deals technically open rather than mark them closed-lost, precisely because it helps a number that isn't really about them individually. Pair the dashboard with a clear, low-friction process for marking deals closed-lost, and don't penalize reps for a high closed-lost count on its own, since punishing honest loss-marking is exactly what pushes deals into stale-but-open limbo in the first place.

A worked example: the coverage ratio that told two different stories

A team's quarterly coverage ratio came in at a level that looked comfortably above target going into the final six weeks of the quarter. When a sales leader filtered the dashboard to exclude deals with no activity in the last month, the ratio dropped meaningfully, closer to a level that would have prompted real concern and a pipeline-generation push weeks earlier.

The gap wasn't fraud or manipulation. It was accumulated stale deals that nobody had gotten around to marking closed-lost, each individually reasonable to leave open a little longer, collectively distorting the number leadership was relying on. Rebuilding the dashboard to show both figures side by side, permanently, meant the next quarter's coverage conversation started from the realistic number instead of the optimistic one.

The rep-level conversations that followed were more specific too. Instead of a generic reminder to "keep pipeline current," managers could point to named deals sitting untouched for weeks and ask directly whether they were still real, which is a much easier conversation to have than a vague appeal to good hygiene that everyone nods along to and nobody actually acts on.

Executive Capability Standard

What Good Looks Like

A trustworthy coverage dashboard segments pipeline by deal recency, shows the ratio both with and without stale deals included, and pairs with a low-friction closed-lost process so reps aren't incentivized to keep dead deals open.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Filter your current pipeline by last-activity date and see how much of your open coverage is sitting in deals with no recent movement.
2. Do Manually:Manually review every deal older than a set threshold each week and get a real answer on whether it's actually still active.
3. Delegate:Give a sales manager ownership of enforcing timely closed-lost marking as part of the regular pipeline review, not a separate cleanup project.
4. Automate:Build the deal-age filter into your coverage dashboard in your CRM, such as Pipedrive or Close, so the realistic number is always visible alongside the raw one.
5. Buy:Bring in a RevOps consultant to rebuild your coverage methodology if leadership has been making forecast decisions off an inflated number for a while.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Pipedrive

Fits a team that wants a visual pipeline view where stale deals are easy to spot by how long they've sat in a stage.

Visit Pipedrive→
Close

Fits a high-velocity team where a deal going quiet for even a short window is a meaningful signal worth flagging fast.

Visit Close→

Frequently Asked Questions

What's a good pipeline coverage ratio?

It depends on your typical win rate and sales cycle, but three times the target in open pipeline is a common starting benchmark. The right number for your team should be calculated from your own historical win rate rather than borrowed from a generic industry rule, since a lower win rate needs proportionally more coverage to hit the same target.

Why does pipeline coverage often look healthier than it actually is?

Stale deals, ones that haven't had a real update in weeks or months but never got marked closed-lost, count toward coverage the same as active, moving deals. Reps have little incentive to close them out since doing so removes them from personal pipeline numbers, so they accumulate and quietly inflate the leadership-facing ratio.

How do you build a coverage dashboard that accounts for stale deals?

Segment by how recently each deal was actually updated, not just by stage, and show coverage both with and without stale deals included. Seeing both numbers side by side makes the gap between the optimistic and realistic picture visible without anyone having to dig for it.

How do you stop reps from gaming a coverage dashboard?

Pair it with a low-friction process for marking deals closed-lost, and avoid penalizing a high closed-lost count on its own. If marking a deal lost feels like a personal black mark, reps will keep dead deals open instead, which is exactly the behavior that distorts the coverage number in the first place.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides