Renewal Forecast: Plan the Next 12 Months of Renewals

A renewal forecast is a month-by-month list of every contract and licence that ends or auto-renews in the next 12 months, with the notice deadline, the annual cost and the seats actually used next to each line. To build one, list every vendor you pay, copy the term end and notice period from each contract, compute the deadline (term end minus notice period), sort by that deadline and total the cost per month. The deadline month, not the renewal month, is when the decision is made, so that is the month to plan for.

What is a renewal forecast, and what does it answer?

A renewal forecast is a month-by-month view of every contract and licence that will end or renew automatically in the next 12 months. For each line it shows the term end, the notice deadline, the annual cost and the seats in use. It answers three questions: what is coming, by when must someone decide, and how much money moves if nobody does.

A calendar reminder gives you one date at a time. A forecast lets you see that October holds four decisions and January holds none, so you can spread the work and the cash before the month arrives. It is the renewal side of the contract renewal reminder: the reminder fires on one contract, the forecast shows all of them together.

Which fields does each line of the forecast need?

Seven fields are enough. Most are copied from the contract, one is computed, and one is a decision about who owns the line.

The notice deadline is the field most lists miss, because it is computed and not read. A term ending on 30 November with a 60-day notice period has to be decided by 1 October, two months before the date on the calendar. Our 90/60/30 rule counts back from that deadline for the same reason.

How do you build the 12-month view in an afternoon?

1. List every vendor you pay: start from card statements, the accounting export and the single sign-on app list, then add what the team confirms.
2. Open each contract or order form and copy the term end, the notice period and whether it renews by itself.
3. Compute the notice deadline for each line.
4. Sort by notice deadline, not by term end, and group the lines by month.
5. Add the annual cost of each month's lines and total it.
6. Mark each line keep, renegotiate or cancel as a first guess, and revise it at the 90-day checkpoint.

Expect gaps: some contracts have no notice period written down, and some vendors only bill by card. Put those at the top of a separate list and chase them first, because an unknown deadline is the one that passes unnoticed. Where several contracts end in the same month, see multi-year discounts before you accept a longer term just to simplify the calendar.

What does a forecast look like with real figures?

The sample licence panel on the InventorIA home page holds four lines. Read as a forecast, it looks like this:

The arithmetic is plain. Zoom costs $15 a seat and 20 seats are idle, so about $300 a month or $3,600 over a year goes to seats nobody uses. Figma costs $18 a seat with 18 idle, about $324 a month. The four lines add up to $1,745 a month, or $20,940 a year, and all four renew within 89 days.

That is what the forecast adds. It turns four numbers into a calendar: Zoom and Figma are decisions this month, Slack comes in about six weeks, Notion at the three-month mark. The money still open to negotiation is whatever has not yet passed its notice deadline.

How do you keep the forecast true after day one?

A forecast that is built once and never touched is a snapshot, and it goes stale within a quarter. Three habits keep it true:

• Once a month, spend 15 minutes adding new vendors and removing cancelled ones.
• After each renewal, replace the term end with the new one so the line moves to its next year, and add the month that has just entered the 12-month window.
• At the 90-day checkpoint, refresh seats used from the vendor console before you decide.

The FinOps Foundation's forecasting capability lists the length of the forecast and its variance thresholds among the parameters to define up front. For renewals the length is 12 months and the threshold is simple: any line whose cost or seat count moved by more than you expected gets a second look.

When is a spreadsheet enough, and when do you need a register?

A spreadsheet with the seven columns works for roughly fifteen contracts and one person who owns it. Beyond that, the seat counts stop being refreshed and the deadlines depend on someone remembering to recompute them. A contract register stores the term end and the notice period, computes the deadline, and sends alerts 90, 60 and 30 days before it, which is how InventorIA handles it. You can open the live demo to see the contract records and alerts, or start with your own contracts.

Frequently asked questions

What is a renewal forecast?

A month-by-month list of every contract and licence that ends or auto-renews in the next 12 months, with the notice deadline, annual cost and seats used for each. It shows what to decide and when.

How far ahead should a renewal forecast look?

Twelve months is the usual window, because most SaaS terms run a year. Add the next month at the end each time you review it so the window always stays 12 months long.

Should I sort the forecast by renewal date or notice deadline?

By notice deadline. The renewal date is when the money leaves, the deadline is the last day you can change it, and every decision has to be made before the deadline.

How often should I update a renewal forecast?

Monthly, for about 15 minutes, and again after every renewal. Refresh the seats used at the 90-day checkpoint of each contract.

What if a contract has no notice period?

Treat it as unknown and ask the vendor in writing. Until you have an answer, assume the deadline is 30 days before term end and keep that line at the top of the list.