Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Sales Forecasting

Renewal Forecast Template: Every Contract Up for Renewal This Quarter

Pete Furseth 6 min read
renewalsretentionforecast templatescustomer successb2b saas
Renewal Forecast Template: Every Contract Up for Renewal This Quarter
Home/ Blog/ Renewal Forecast Template: Every Contract Up for Renewal This Quarter

What does a renewal forecast template need to track?

Expected dollars at renewal, not renewal dates. Most renewal trackers are calendars. They list which contracts come up when, get reviewed in a monthly meeting, and produce no number anyone can plan against until the renewal either happens or does not.

A renewal forecast attaches an expected value and a reason to every contract in the window. That turns a list into a forecast line that can be checked, and it exposes the difference between keeping a customer and keeping the revenue, which is the difference gross and net retention are built on.

ColumnWhat it holdsWhy it earns a slot
Account and current ARRThe value at stakeThe base for every calculation
Renewal dateContract endDrives the period it lands in
Notice periodDays before end that cancellation must be givenThe real deadline
OwnerOne name, CSM or AEPrevents shared ownership of nothing
Risk categorySecure, watch, at risk, or expected lossThe forecast category
Expected renewal valueDollars you expect to bookThe forecast itself
Change reasonWhy expected differs from currentMakes the number inspectable
Expansion attachedUplift being worked at renewalKeeps net retention visible
Last executive contactDateThe best proxy for relationship depth
The notice period column is the one teams add after being burned. A contract with 90-day notice and an auto-renew clause has a decision deadline three months before the date in the ARR schedule, and a tracker organized by renewal date puts that account in the wrong quarter.
Put this to work on your numbers
Run your own numbers with the free Forecast Accuracy Scorecard, then see how ORM builds it into a custom model.

How should renewal risk be scored?

Score on observable signals rather than on how the relationship feels to the person who owns it.
SignalHealthyElevated risk
Support case volume, trailing 12 months3 to 5 routine casesZero cases, or 7 and above
Executive contactWithin the last quarterNone in six months
Product usage trendFlat or growingDeclining for two consecutive months
Champion statusIn role, engagedDeparted or reassigned
Open escalationNoneAny unresolved severity one issue
The support signal is the one most teams read backwards. A silent account looks healthy on a dashboard and is often the most exposed, because nobody is using the product enough to file a ticket. Across ORM's customer base, accounts with no support cases carry elevated churn risk, accounts with seven or more in a year also carry elevated risk, and accounts filing three to five routine tickets churn less because they are engaged and getting help.

Score each account on the five signals and let two or more elevated flags move it out of secure. A rule beats a judgment call because it applies the same way to the account someone likes and the account nobody has called.

What are the renewal forecast categories?

Four, defined by dollars rather than by likelihood of keeping the logo.

Secure means the customer has confirmed renewal or the contract auto-renews with no cancellation signal and no risk flags. Watch means the renewal is expected at full value but at least one risk flag is open. At risk means you expect either a loss or a reduction, with the expected value written down. Expected loss means the customer has given notice or has made the decision internally.

Forecast the expected value in every category, including at risk. A customer moving from 200K to 140K belongs in the forecast at 140K with "reducing seat count after their reorganization" in the change reason column. Logging it at 200K until it happens produces a clean-looking forecast that misses by 60K with no warning.

How do you forecast renewal dollars rather than logos?

Model each contract's value movement, because retention is measured in dollars and logo counts hide contraction.

Break each renewal into the components that move ARR:

ComponentDirectionExample
Churned customer ARRContractionFull cancellation at renewal
Churned product ARRContractionDrops one module, keeps the rest
Product decrease ARRContractionReduces seats or usage tier
New product ARRExpansionAdds a module at renewal
Increased product ARRExpansionGrows seats or tier
Those components are what a monthly retention waterfall is built from, running from beginning ARR to ending ARR with each movement on its own line. Reconciling that waterfall every month is what makes gross and net retention trustworthy rather than a ratio someone calculates differently each quarter. The net revenue retention definition covers how the components combine.

A renewal tracker that only records renewed or lost cannot produce that waterfall, which is why the expected value and change reason columns matter more than the risk category.

How far ahead should renewals enter the template?

One full quarter before the renewal date at minimum, and notice period plus sixty days when the notice window is long.

Working a renewal in the final month means arriving after the customer's budget cycle has already made the decision. The tracker should carry a rolling two-quarter view, with the current quarter forecast at deal level and the following quarter scored for risk only.

That lead time also creates room for the expansion column to matter. Renewal conversations are the highest-probability expansion moment you get, and an account entering the window with a scoped uplift proposal converts at a different rate than one where the seller raises it three weeks out.

How do you measure renewal forecast accuracy?

Score it separately from new business, because the two miss for different reasons and mixing them hides both.

New business forecasting error comes from deals that do not exist yet or dates that move. Renewal forecasting error comes from value changes you did not see coming and from decisions made inside the customer that never surfaced. Reporting one blended number means a strong renewal quarter can mask a new business problem for a full period.

Track expected renewal value against booked renewal value by month, then split the variance into logo losses and value reductions. When the reductions turn out to be larger than the outright losses, the fix sits in the risk signals rather than in save plays. The scoring method is the same one used everywhere else, covered in forecast accuracy, and the overall structure of the number is in how to forecast revenue.

Frequently Asked Questions

What should a renewal forecast template track?

Contract value, renewal date, notice period, owner, risk category, expected value at renewal, and the reason for any expected change. Tracking renewal dates without expected values gives you a calendar rather than a forecast.

How far in advance should renewals enter the tracker?

At least one quarter before the renewal date, and earlier when the notice period is long. A contract with a 90-day notice requirement needs to be worked five months out, because by the time the renewal date arrives the decision was made months earlier.

How do you forecast renewal dollars instead of logos?

Forecast each contract at its expected renewal value, not its current value. A customer renewing at 70 percent of contract value is a retained logo and a 30 percent revenue loss, and only the dollar view shows up correctly in gross revenue retention.

What is the earliest signal that a renewal is at risk?

Support activity is one of the strongest. Accounts filing no support cases at all are at elevated churn risk, and so are accounts filing seven or more in a year. Accounts with three to five routine tickets churn less because they are engaged and getting help.

Should renewals be forecast in the same model as new business?

In the same reporting view, using different mechanics. A renewal has a known date and a known customer already paying you, so the forecasting question is retention probability and value change rather than whether a deal exists at all.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

See how ORM turns these insights into action

ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.

Schedule a Demo