The Difference Between a Full Pipeline and an Active One
Pipeline coverage is often tracked as a ratio: total open pipeline value against quota or target. A 3x or 4x coverage ratio is generally considered a healthy sign. But coverage ratios measure what is present in the pipeline — they do not measure whether what is present is still actively progressing toward a decision.
A deal that entered "Proposal Sent" three months ago and has not had a logged interaction since carries the same weight in a coverage calculation as a deal that was moved to "Proposal Sent" last week with an active conversation underway. The coverage ratio is the same. The commercial reality is not.
This distinction — between apparent pipeline health and structural pipeline health — is at the center of why deals stall, why they persist in CRM systems long after they have practically expired, and why the pipeline often contains significantly less recoverable value than it appears to on paper.
What "Stuck" Actually Looks Like in CRM Data
A deal that is structurally stalled does not always look different from an active deal in a standard pipeline view. The stage name is set. The amount is populated. It appears in the forecast. What distinguishes a stalled deal at the data level is a combination of two conditions: extended time in the current stage relative to typical progression velocity, and an absence of recent activity that would indicate ongoing buyer engagement.
Neither condition alone is necessarily alarming. Some deals move slowly through specific stages. Some activity gaps are explained by buyer-side processes. But the combination — sustained stage residence and sustained activity absence — is a consistent structural signal. It indicates that the deal has not advanced, that no meaningful commercial event has occurred, and that its continued presence in the pipeline reflects data inertia rather than active selling.
In a representative CRM export, a meaningful share of open deals in late-stage categories (Negotiation, Proposal, Commit) show no activity in 30 or more days, with stated close dates that have already passed. These deals remain in coverage calculations and forecast views without any structural differentiation from active opportunities.
Why This Happens: Three Structural Causes
The three causes that drive accumulation in most pipelines each trace back to a structural gap in how CRM systems are designed:
- Stage movement asymmetry — advancement is an explicit action; stagnation leaves no record
- Close date defaults — dates set at deal creation and never revised as timelines shift
- Removal friction — formally closing a deal requires acknowledging a loss, which creates both effort and quota implications
Stage Movement Is Manual, Inactivity Is Invisible
In most CRM systems, stage progression requires a deliberate action by a sales representative — moving the deal forward is an explicit operation. There is no equivalent mechanism for marking inactivity. A deal that stops moving simply stays where it is. There is no CRM alert that surfaces after 30 days of no activity in "Proposal Sent." The stage remains. The deal remains. The forecast includes it.
This asymmetry — where advancement is recorded but stagnation is invisible — means that pipeline bloat develops as a natural consequence of CRM structure, not exclusively as a result of individual behavior.
The extent of that accumulation is typically only quantifiable through record-level analysis of a CRM export, where activity gaps and stage residency durations appear as measurable data rather than as invisible conditions within a pipeline label.
Close Date Defaults Are Not Buyer Signals
Close dates in CRM records are typically entered when a deal is created or moved to a meaningful stage. In many organizations, these dates are created as estimates or targets — not derived from a specific buyer commitment or conversation. As deals age, the close date is rarely updated to reflect that the original estimate was incorrect.
The result is a pipeline populated with close dates that reflect when a rep expected to close, not when a buyer has indicated they will decide. Those dates continue to appear in near-term forecast windows long after they have passed, inflating the apparent immediacy of pipeline that is, structurally, much less immediate.
Removal Requires Judgment, Not Just Data
Removing a deal from an active pipeline requires a rep to acknowledge, in the CRM, that the deal is lost, dead, or deferred. This is a friction point — both in terms of effort and in terms of its implication for quota tracking and pipeline metrics. The path of least resistance is to leave the deal in place and focus on newer opportunities. Over time, the accumulation of these decisions compounds into substantial stale pipeline inventory that no one has formally closed.
The Structural Signals That Indicate Accumulation
Number of days since the most recent logged activity on an open deal. Extended gaps relative to stage position indicate disengagement.
Days elapsed in the current stage compared to typical progression velocity for deals at that stage. Outliers signal structural stall.
Open deals whose stated close date has passed without movement to won, lost, or a future close date. Indicates forecast dates are not being maintained.
When last activity predates the current stage entry by a meaningful margin, the stage assignment reflects a past action, not current engagement.
How Stalled Deals Distort Planning
Stalled pipeline affects planning in two ways that compound each other. First, it inflates coverage ratios — the ratio looks healthy, which reduces pressure to generate new pipeline, which means the underlying health problem is not addressed. Second, it creates false forecast confidence — deals that appear near-term are included in planning assumptions, and when they do not close, the miss is attributed to execution rather than to the structural data condition that made those deals look more advanced than they were.
The compounding effect is that the longer stalled deals remain in the system, the more planning cycles they distort. A deal that should have been removed in Q1 will affect Q1, Q2, and Q3 forecasts before it is finally addressed — or before it ages out through natural attrition when a rep eventually marks it lost.
If you want to know what proportion of your pipeline is structurally stalled, the Revenue Risk Score identifies activity gap concentrations and stage residency outliers from a standard CRM export.
What Structural Evaluation Identifies
Structural evaluation of deal velocity, as applied in the Revenue Risk Framework™, examines the underlying record data across the pipeline — not the stage labels and amounts in the forecast view. It identifies the proportion of open pipeline that exhibits the structural signals of stagnation: activity gaps, stage residency outliers, close date lapse concentrations. The result is a characterization of how much of the apparent pipeline is structurally active versus structurally idle.
That distinction is the basis for a more accurate assessment of commercial position than coverage ratios alone can provide — and it identifies the specific structural controls (activity minimums by stage, close date maintenance requirements, deal review cadences) that would prevent the accumulation from recurring.
In representative pipeline exports examined through structural analysis, 30–50% of open pipeline by value shows at least one stall or expiry signal at the record level — a proportion that reported coverage ratios treat as equivalent to active pipeline value. The headline ratio reflects what is present. Structural evaluation distinguishes what is present and advancing from what is present and stalled.
A free Revenue Risk Score evaluates these structural signals in a standard CRM export. The analysis identifies activity gaps, close date lapse concentrations, and the proportion of open pipeline that exhibits structural stall characteristics.