A pipeline health score combines the signals that predict conversion into one number, so a revenue team can tell the difference between pipeline that is large and pipeline that is capable. Coverage answers whether there is enough. A health score answers whether what exists behaves like pipeline that closes.
The reason to build one is that the individual signals are already sitting in the CRM and nobody reads them together. Aging looks fine in isolation. Silence looks fine in isolation. A pipeline where a quarter of the value is both old and owned by two reps looks fine on every dashboard that reports those facts separately.
The five inputs that carry the signal
| Input | What it measures | Why it belongs |
|---|---|---|
| Age against expected window | Time open relative to how long deals in this group take to close | Old deals close at lower rates than the record implies |
| Silence | Days since stage, close date, or amount last changed | The absence of a signal is the earliest warning a deal produces |
| Close date movement | Number and direction of date changes | A rep moving the date is the strongest slippage signal available |
| Concentration | Share of open value in the largest deals, accounts, or reps | One deal deciding the quarter is a forecast risk, not a pipeline strength |
| Amount realism | Recorded amounts against historical closed-won amounts | Most deals close for less than the value on the record |
Score by dollars and read the trend
Report the score weighted by value. A pipeline where 60% of deals are healthy but 70% of the dollars are not is a pipeline in trouble, and a count-based score will call it fine.
Read the trajectory rather than the level. A score that slides three weeks running means the team is creating pipeline faster than it resolves old pipeline, which shows up as rising pipeline coverage and falling quality at the same time. That combination is why the 3x coverage rule misleads.
Calibrate it, then leave it alone
Set the weights from your own closed history and rebuild them once a year. Changing the formula mid-year breaks every comparison against it and hides whether the pipeline improved or the scoring did. Stability is what turns the score into a signal that improves forecast accuracy instead of another dashboard nobody trusts.
Frequently Asked Questions
What should a pipeline health score include?
Five inputs cover most of the risk: age against the expected close window for that deal type, days of silence on the fields that matter, close date movement, concentration in a small number of deals, and the gap between recorded amounts and what deals historically close for. Coverage belongs alongside the score rather than inside it, because volume and quality are different questions.
Is a pipeline health score better than pipeline coverage?
It answers a different question. Coverage tells you whether there is enough pipeline. A health score tells you whether the pipeline you have behaves like pipeline that converts. A team can hold 4x coverage and still miss badly when the value is aged, concentrated, or priced above what deals actually close for.
How do you calibrate the weights?
Against your own closed history rather than against a template. Take four to eight quarters of closed opportunities, measure which signals separated wins from losses, and weight accordingly. A borrowed scoring model encodes another company's sales cycle and will flag the wrong deals in both directions.
Should the score be reported per deal or per pipeline?
Both, and weighted by value in each case. Deal level drives the action a manager takes this week. Pipeline level drives the conversation with the board. Scoring by deal count instead of dollars makes small opportunities look as important as the ones that decide the quarter.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline health score into prescriptive action for your team.
Schedule a Demo