Pipeline Coverage Is a Lagging Indicator Dressed Up as a Leading One
3x coverage feels like safety. It isn't. By the time your coverage ratio looks healthy, the deals inside it are already decaying.
Every Monday morning, somewhere in a revenue org, a sales leader opens a dashboard, sees 3.2x pipeline coverage, exhales, and gets on with their week. By the end of the quarter, that same team misses by 35%. The pipeline was always there. The revenue was not. This is not a forecasting quirk. It is a systematic category error, and it is costing teams quarters they should have won.
Coverage ratio measures volume, not health
A pipeline coverage ratio tells you one thing: the total value of open opportunities divided by your quota. That is all. It says nothing about whether any given deal is moving, whether your champion still works there, whether the budget is real, or whether the "decision" that was supposed to happen in week two of last month has actually been deferred twice because procurement got involved and nobody updated the CRM stage.
The ratio counts deals. It does not weigh them. A £400k opportunity that has sat at "Proposal Sent" for 47 days contributes the same to your 3x as a £400k opportunity that had a product review last week, a legal call scheduled for Tuesday, and a champion who rang your AE unprompted on Friday afternoon. These are not equivalent objects. Treating them as equivalent is what produces the 40% miss.
The failure modes that hide inside a healthy coverage number
There are three patterns that recur, and they are worth naming precisely because most pipeline reviews are designed to miss them entirely.
The parked deal. It is at stage three. It has been at stage three for 34 days. Nobody has updated it because updating it would require either marking it at risk or explaining what happened, and neither conversation is one the rep wants to have on a Monday morning call. The manager sees it in the coverage count and moves on. The deal is not progressing; it is just not dead yet in the CRM.
The multi-threaded mirage. The deal has three contacts logged. It looks engaged. What the log does not show is that two of those contacts are the same person from two different companies who merged six months ago, and the third is a VP who attended one discovery call a month ago and has not responded to anything since. The deal counts as "multi-threaded" in the dashboard because someone ticked the fields.
The commit call time loop. Three weeks running, the forecast call features the same four deals in the commit column. The numbers are slightly different each time because someone adjusted close dates. The conversation is exactly the same: "still waiting on legal", "champion is aligning internally", "should close by end of month." Nobody says the quiet part out loud, which is that a deal that has been in commit for three consecutive weeks without a new buyer-initiated action is probably not closing this quarter.
None of these problems are visible in the coverage ratio. All of them are visible if you are measuring the right things.
What a genuinely leading signal looks like
If coverage is a lagging, volume-based metric, what actually predicts whether the pipeline closes? Three signals that are measurable, specific, and do not require expensive tooling.
| Signal | What it measures | Why it leads |
|---|---|---|
| Stage-velocity decay | Days spent in current stage vs. historical average for won deals | Stall is detectable before the deal dies |
| Days since last buyer-initiated contact | Last inbound email, call, or meeting request from the prospect side | Buyer silence is the earliest objective sign of disengagement |
| Champion access confirmed in 14 days | Has your rep spoken to the person who will advocate internally in the last fortnight | Champion loss is the most common unlogged reason deals slip |
None of these are exotic. You do not need a new platform. You need your managers asking different questions in the review. "When did they last reach out to you?" is a harder question than "what is your coverage?" and it is harder precisely because it has a concrete answer that cannot be dressed up.
The Deal Health / Risk Scorecard is a practical way to operationalise the third signal specifically. If your managers are doing champion access checks verbally and not recording the outcome, you will keep having the same three deals on the commit slide for three weeks running.
The right place for coverage in your operating rhythm
Coverage ratio is not a useless metric. It is the wrong metric in the wrong place. Here is the distinction:
Coverage belongs in the board pack. At the capacity planning level, coverage tells you whether you have built enough pipeline to give yourself a mathematical chance at quota. If you are running at 1.8x in week six of the quarter, that is a pipeline generation problem and the board should know. Coverage as a capacity signal is entirely legitimate.
Coverage does not belong in the weekly forecast call as a proxy for health. When it appears there, it substitutes for harder diagnostic work. Managers feel reassured by a healthy ratio and skip the deal-by-deal interrogation that would surface the parked deals, the silent buyers, and the phantom champions. The ratio performs health. It does not measure it.
The practical fix is simple: remove the aggregate coverage number from the weekly review slide deck entirely. Replace it with a stage-velocity exception report and a list of deals where the last buyer-initiated contact is more than 14 days ago. Both take five minutes to pull if your CRM data is halfway clean. Both will generate more useful conversation in the first ten minutes than 45 minutes of coverage-ratio discussion ever did.
If you want to understand where your pipeline capacity gaps actually sit before the quarter is too far gone, the Pipeline Coverage & Gap Calculator will give you the structural view without letting you mistake it for a health check. The distinction between those two uses is the whole point.
The real cost of confusing the two
A team that manages to coverage ratio instead of deal health systematically defers the difficult conversations. The rep who should be told "this deal is not real, go find another one" instead spends three more weeks nurturing a zombie opportunity while genuinely winnable deals in their territory go unpursued. The manager who should be escalating a champion problem instead reports the ratio to their VP and calls it a review. The VP who should be redeploying resource instead feels comfortable because the number looks fine.
By the time the ratio starts to look thin, you are already in trouble. Pipeline that decays for six weeks before anyone flags it cannot be replaced in the last four weeks of a quarter. That is not a forecasting problem. That is a diagnostic problem that was always going to produce a forecasting problem.
The coverage ratio is the number that makes everyone feel like they have done the work. The work is asking what is actually happening inside the number.