Pipeline Coverage: Ratio Formula, Denominators, Required Multiple and HubSpot Setup

Neither the 3x convention nor a threshold derived from win rate counts the pipeline that slips into a later quarter, so a team can open a quarter at 3.3 times pipeline coverage, clear the 3x threshold and still be on course for three-quarters of target. The denominator misleads separately: divided by the full target rather than the target still to close, coverage falls every week of a quarter that is going to plan. Both errors arise with every record in the CRM correct.

This article defines pipeline coverage and shows how to set the multiple it is judged against. It starts with the ratio and the calculations that share its name, derives the required multiple from win rate and slippage, applies the derivation to sample data and states the limits of that arithmetic. The HubSpot build comes next, then the business case for a derived multiple and the symptoms of a wrong figure.

Pipeline coverage is the value of open deals dated to close in a period, divided by the target still to be closed in it. The remaining target is the period's target less the value already closed won. Slippage is pipeline dated into a period that did not close in it, because its close date moved later or the period ended with the deal still open. Coverage feeds revenue forecasting without being a forecast: it states the pipeline per dollar still to close, and contains no conversion rate.

The Pipeline Coverage Ratio and Its Four Variants

HubSpot's forecast tool computes this ratio as Open pipeline coverage when its Forecast deal amount is Total amount, which step 6 confirms. Open pipeline adds up the amounts of open deals in the selected period that the viewer has access to, and coverage divides it by the gap to goal: the Goal less Closed Won.

The remaining target belongs in the denominator because a deal closed won leaves the numerator, and its value has to leave the denominator with it. The figure below models a team exactly on plan, starting at the 4.4x derived later, whose day-one pipeline resolves evenly over thirteen weeks with nothing added.

Coverage is a reading at a point in a period, so the multiple it is compared with has to come from the same point in earlier periods. The first day is simplest, because the remaining target then equals the full target. Once closed won reaches the target the ratio has no meaning; HubSpot's documentation does not say what the forecast tool displays then.

On 14 August the sample team, with a $1,200,000 quarterly target, has closed $450,000 and holds $2,250,000 of open pipeline dated into the third quarter.

Weighted pipeline is already an estimate of what will close, so a 3x threshold applied to it demands three times the target in expected value; weighted pipeline covers the probabilities behind it. Units must match too. HubSpot can compute Amount from line items as total contract value, annual contract value, annual recurring revenue or monthly recurring revenue, and a change of calculation leaves existing deals as they were. Coverage of total contract value against a target in annual contract value misstates by TCV ÷ ACV, the value-weighted term in years, overstating for multi-year terms.

The Required Multiple: Win Rate and Slippage

Setting aside amount changes, every dollar of pipeline dated into a period on its first day ends the period won, lost or pushed into a later one. Write w for the win rate on decided value, won ÷ (won + lost), and s for the push share, pushed ÷ (won + lost + pushed). A day-one dollar then yields w × (1 − s) in won value, and the required coverage is the reciprocal, 1 ÷ (w × (1 − s)). Multiplied out, the expression needs no rates at all: it is the period's won, lost and pushed value divided by its won value. Three times is that reciprocal for a team converting exactly a third of its pipeline, and for no other team.

The two terms weigh the same: a 25% push share raises the requirement by a third, exactly as a fall in win rate from 40% to 30% does.

One divided by win rate drops the push term, and the win rate it relies on cannot reveal the omission. A pushed deal is not decided in the period it slipped from, so that period's win rate omits it. A report filtered on close date excludes it a second way, because report date filters select records based on their property values, and a deal pushed into the next quarter is selected by its later date. The implied multiple, 1 ÷ w, therefore falls short of the requirement by a fraction equal to the push share. The shortfall is approximate, because HubSpot by default sets a deal's close date to the day it moves into a closed stage, so a later deal lost early joins the current quarter's decided value.

HubSpot sums pushed value in the deal pipeline waterfall, a sales analytics report (Sales Hub Starter, Professional and Enterprise) that splits a period's pipeline into Created, Pushed, Pulled, Decreased, Increased, Lost and Won amounts. Its Pushed amount includes deals still open with a close date inside the period when it ends. The Deal push rate report counts deals rather than value, so it cannot supply a share of value. The waterfall also counts deals created or pulled in after day one, so it approximates the day-one population in long sales cycles; the day-one export below measures it exactly.

Coverage on Sample Data

These figures are sample data constructed for this article and describe no client. The sample team has a quarterly target of $1,200,000, and for the second quarter its waterfall records $810,000 won, $1,890,000 lost and $900,000 pushed: $3,600,000 that was dated into the quarter and left it.

On 1 July the team holds $4,000,000 of open pipeline dated into the third quarter and has closed nothing, so coverage is 3.33x. That clears the 3x convention and sits exactly on the win-rate multiple. Against the required 4.44x it is $1,333,333 of pipeline short, and at a 22.5% yield it converts to $900,000, or 75% of target. The $300,000 miss is visible on the first day, and the $1,333,333 shortfall is a pipeline generation target whose deadline is set by the length of a sales cycle.

Boundaries of This Article

The derived multiple is an average over past periods. It assumes the next period converts and slips like the measured ones and holds enough deals for an average to describe it. With forty deals of equal value and a 22.5% yield, a pipeline at exactly 4.44x reaches target in 56% of quarters under a binomial model. Four quarters in five takes about 5.7x with forty larger deals, or 5.4x with 49 deals of the same size. A multiple fixes the expected outcome and says nothing about the spread around it, so any margin above it has to be chosen deliberately.

Stage probabilities, forecast accuracy, capacity planning and revenue recognition are outside the scope of this article. Product behaviour is as documented in October 2026, and the linked HubSpot pages take precedence as the product changes. The arithmetic above is CRM-neutral; HubSpot is the platform this practice implements, and only the procedure that follows depends on it.

Coverage in HubSpot: Forecast Tool, Goals and the Day-One Export

The forecast tool requires Sales Hub or Service Hub Professional or Enterprise, Forecast permissions and an assigned Sales or Service seat, though Super Admins can open it regardless of seat. Setup requires a Super Admin, per the forecast setup guide.

1. In Settings > Objects > Forecast, set the forecast period, monthly or quarterly, to the target's period; changing it later resets every forecastable revenue goal and submission. Note the Forecast deal amount: Weighted amount (Amount × Deal probability) is the default, and Total amount is the full Amount.
2. In Sales > Forecast, click Create goal and use the Forecastable Revenue template to set each user's or team's target on the pipelines coverage should include. The tool shows only goals associated to one or all pipelines.
3. Read Goal, Closed Won and Gap in the Team table, and Open pipeline and Open pipeline coverage in the Pipeline table. Open pipeline is documented only as "the sum of amounts for all open deals", but the Forecast deal amount "determines how deal amounts are displayed in the forecast tool", so on the Weighted default the tool's coverage may be weighted; step 6 settles it.
4. On each period's first day, filter the deals index to the pipeline, a Close date (closedate) inside the period, and Is Closed Won and Is closed lost both false. Export the view with Record ID, Amount (amount) and Close date, because a later report filtered on Close date misses the deals that moved out. Rebuilding the population later needs property history exports for Close date, Amount and Deal stage, each limited to 20 revisions per deal property.
5. After the period, re-export the step 4 Record IDs with Is Closed Won, Is closed lost, Close date and Amount. Won and lost mean closed in that state with a Close date inside the period; the rest are pushed. The next period's multiple is the day-one exported value divided by the won deals' closed Amount.
6. Verify as a user who can see every deal, such as a Super Admin, since Open pipeline sums only deals the viewer can access. Build a deals report with the step 4 filters on the tool's pipeline, with Deal owner limited to the users the tool lists for the team being viewed, since only seated users appear. Sum Amount, divide by the Gap, and confirm the quotient equals Open pipeline coverage. A match with the Weighted amount sum instead means the coverage is weighted; set Total amount in step 1 and repeat the check.

A dashboard can set a goal report (Marketing, Sales or Service Hub Professional or Enterprise) beside a deals report of open pipeline. Formula fields cannot divide one sum by the other, because they do row-level math; that takes summary functions, documented for Data Hub Professional and Enterprise, though the formula fields page limits the Functions tool to Data Hub Enterprise.

The Business Case for a Derived Multiple

A derived multiple turns coverage from a threshold into a measurement. The day-one reading states a shortfall in dollars of pipeline while there is time to create it, and the argument over whether 3x is enough becomes a quotient anyone can recompute.

It costs a day-one export and a re-derivation each period, as win rate and push share move, plus the forecast tool's subscription. The larger cost is close-date discipline: coverage is a sum over close dates, so an unmaintained date enters the ratio at full value and reaches the multiple through the push share.

The case is strongest in long sales cycles, where a period's pipeline exists before the period begins and holds many deals of comparable size. It is weakest in short cycles, where much of a period's won value comes from deals created inside it. Day-one coverage then sees only part of what will close, and the derived multiple overstates the day-one need. A requirement above the pipeline the sellers can work is a capacity problem, a distinction drawn in go-to-market antipatterns.

Coverage Symptoms and Their Sources

Coverage clears 3x on the first day and the period misses by a quarter. The threshold came from convention or from one divided by win rate, and neither contains the push share. Derive the multiple from the last completed period's waterfall instead.

Coverage falls every week of a period that is on plan. The figure divides by the full target, so closed won value leaves the numerator and stays in the denominator. Divide by the forecast tool's Gap, which subtracts Closed Won from the Goal.

Current-period coverage rises whenever deals are created, though the new deals sit in the first stage. HubSpot dates a new deal to the last day of the month it was created unless the default is changed, so new deals count in the current period at full value. Set Time from deal creation under Settings > Data Management > Objects > Deals to the length of a sales cycle; imported, mobile-created and workflow-created deals ignore the default.

Coverage holds steady while the deals behind it show no activity. Open deals whose close date has passed still count in the period, and the waterfall moves them to Pushed only when the period ends. A saved view of open deals dated before today lists them while they can still be redated or closed.

In Summary

Pipeline coverage divides open pipeline dated into a period by the target still to close in it, which HubSpot's forecast tool reports as Open pipeline coverage when its Forecast deal amount is Total amount. The multiple it is judged against is a reciprocal: the period's won, lost and pushed value divided by its won value. One divided by win rate omits the push share, and the period's win rate cannot reveal the omission, because a pushed deal is not decided in that period.

Deriving the multiple costs a day-one export and maintained close dates, and returns the shortfall in pipeline dollars while it can still be made up: in the sample, a requirement of 4.44x replaces a reassuring 3.33x and moves a $300,000 miss from the end of the quarter to its first day. Day-one coverage is held to a quotient recomputed every period: the sum of last period's Won, Lost and Pushed amounts in the deal pipeline waterfall, divided by its Won amount.