How to Calculate Renewal Pipeline Coverage

What is renewal pipeline coverage?

Renewal pipeline coverage divides the ARR of renewal opportunities with an active motion behind them by the retention target for the period. It answers a narrow question: of the contracts coming up for renewal, how much is actually being worked, and does that cover what the plan expects retention to deliver.

The metric exists because renewal revenue gets assumed rather than managed. New business gets a pipeline, a forecast call, and a coverage ratio. Renewals get a date in a spreadsheet and an assumption that most will land. That assumption holds until it does not, and by then the contract has already expired. Renewal coverage forces the same discipline onto the base that new business already receives.

Why does renewal coverage use a lower target than new business?

Because coverage multiples compensate for loss rates, and renewals lose at a fraction of the rate new deals do. New business carries a 3x to 5x ratio because most open opportunities never close. Across ORM customer data, most companies run near 3.5x on new business. Renewals invert that. Most contracts renew, so renewal coverage gets read against 1.0x of the retention target rather than as a multiple. The retention goal has already priced the expected churn and downgrade, so nothing needs to be layered on top of it.

Applying a new business multiple to renewals produces nonsense. A team with $4,000,000 of contracts up for renewal cannot manufacture $14,000,000 of renewal pipeline, because the base is fixed by contracts that were signed a year ago. The only variables are how much of that base gets worked and how much of it survives.

What is the formula?

Divide covered renewal ARR by the retention target, where the target is the ARR up for renewal multiplied by the gross retention goal.

``` Retention target = ARR up for renewal x Gross retention goal Renewal coverage = Covered renewal ARR / Retention target ```

Covered means a renewal opportunity exists, an owner is assigned, and a conversation has happened inside the last 60 days. ARR sitting in the base with no owner and no contact is uncovered regardless of how confident anyone feels about the account.

How do you build the renewal base?

Pull every contract with an end date inside the period, group by renewal month, then split each month into covered and uncovered ARR. The quarter reads 0.89x, which is already short. The month view shows where the shortfall lives and how much time remains to fix it. Month three has nearly half its base uncovered, and those conversations should start now rather than in the week the contracts expire.

Which signals move a renewal into the uncovered column?

Support case volume at either extreme, and the absence of any account activity at all. Across ORM customers, an account that has filed zero support cases in the past year is at risk, because nobody is using the product enough to hit a problem. An account with seven or more cases is also at risk. Accounts filing three to five tickets, usually tier two or tier three rather than severe, are engaged and less likely to churn.

The other reliable signal is silence. A renewal with no meaningful change in the record and no response to outreach is a worse position than one with an active objection. An objection is a conversation. Silence is a decision that has already been made somewhere you cannot see.

Does expansion belong in the same calculation?

No. Run expansion as its own pipeline with its own coverage ratio. Expansion behaves like new business. It has a conversion rate well under 100%, it needs a multiple to cover losses, and it moves for different reasons than renewals do.

Blending them hides the problem the metric exists to find. A base with $810,000 uncovered and $900,000 of expansion pipeline nets out to a comfortable-looking number while a fifth of the contract base has nobody working it. Report the two separately and combine them only where they belong, at the net revenue retention line. Track the monthly waterfall alongside it: beginning ARR, churned customer ARR, churned product ARR, product decreases, new customer ARR, new product ARR, product increases, and ending ARR. That reconciliation shows which component moved rather than reporting a single blended percentage.

Why does renewal forecasting need its own model?

Renewal revenue follows different mechanics than new business, so accuracy on one says nothing about accuracy on the other. ORM measures forecast accuracy on new and expansion business separately from renewals for exactly this reason. Renewals are driven by product usage, support engagement, and contract structure. New business is driven by pipeline creation, conversion, and deal size.

A single model covering both will fit whichever component dominates the revenue base and misprice the other. Build the renewal forecast from the contract base and the usage signals, then hand the result to the consolidated view. The broader approach to splitting a forecast by revenue source is covered in how to forecast revenue.

How often should renewal coverage be recalculated?

Monthly, on a base that extends at least two quarters forward. A renewal read taken 30 days out reports an outcome that has already been decided by the previous eleven months of the customer relationship.

Watch the uncovered column rather than the ratio. Uncovered ARR is directly actionable: assign an owner, open a conversation, and it moves. The ratio is a summary of that work, and it improves only after the work happens. The base version of this metric for new business is defined in pipeline coverage.