Practical guide

How to Build a 12-Month Software Renewal Calendar for Budget Planning

Most software budgets start with last year's number plus a percentage. That is quick, and it hides the details that actually move the number: a big contract that renews in a month nobody planned for, a price increase written into the agreement, or a tool the team already decided to drop.

October 26, 2026 · 8 minute read

Why budget season needs a renewal calendar

A 12-month renewal calendar fixes that by putting every renewal on the month it lands, with its cost, its owner, and the date by which a decision has to be made. Finance sees when the money goes out. Owners see when they need to decide. Nobody learns about a renewal from the invoice.

This guide is for IT, ops, and finance teams building next year's budget. It covers what to collect, how to lay out the calendar, how to plan cost changes, and how to keep it current once the year starts.

Step 1: Build the list from more than one source

No single source has every renewal. Pull from several and merge them.

Your renewal register or license inventory, if you have one
Accounts payable: recurring vendors from the last 12 months
Company card statements: subscriptions that never went through procurement
Signed agreements and order forms: for term dates, notice periods, and price change clauses
Department owners: ask each team lead to confirm what they use and what they plan to add or drop

Expect the first pass to be incomplete. That is normal. Each review fills more gaps. For the fields worth keeping per tool, see software license inventory: what to record for every license.

Step 2: Capture the fields that drive the budget

For each renewal, record:

Vendor and product
Named owner and backup
Current annual cost:what you are committed to today, not one month's invoice
Billing cycle: annual, multi-year, quarterly, or monthly
Term end date
Auto-renewal terms and notice period
Notice date: the last day you can cancel or change terms
Decide-by date: a few weeks before the notice date, so there is time to act
Price change clause: what the agreement says about increases at renewal, if anything
Planned seat or plan change
Planned decision: keep, renegotiate, reduce, replace, cancel, or undecided
Budget owner or cost center

If a notice period is buried in the paperwork, see how to find the notice period in a software contract.

Step 3: Lay out the calendar two ways

The same list answers two different questions, so give it two views.

The spend view (for finance).Place each renewal's expected cost in the month the payment lands. Total each month, then roll the months up to your fiscal quarters. This shows which months are heavy and when cash goes out.

The action view (for owners). Sort the same list by decide-by date and notice date instead. This shows what needs a decision this month. A renewal that pays out in June may need a decision in February.

Keep both views tied to one list. If they live in separate files, they drift apart.

For why notice dates matter more than renewal dates, see how to avoid surprise SaaS auto-renewals.

Step 4: Plan cost changes line by line

The calendar is only as good as the cost on each line. Instead of applying one percentage to everything, adjust each renewal on its own terms:

Use the agreement's price change clause when it states one
Mark an assumption when it does not, and name who will confirm it with the vendor
Add planned seat changes: new hires, team changes, or seats you plan to remove
Subtract planned cuts: tools you intend to cancel, downgrade, or consolidate
Add new tools that teams have already asked for

Write the reason next to each change. When finance asks why a line went up, the answer should be on the row, not in someone's memory.

Step 5: Look for clusters and gaps

Once the calendar is laid out, scan it for patterns.

Heavy months: several large renewals landing together can strain cash and stretch the people who need to negotiate them. Consider starting those decisions earlier
Ownerless lines: any renewal without a named owner will not get a decision. Assign one now. For how, see who should own software renewals
Missing notice dates: treat these as urgent until confirmed
Owners who have left: reassign before the decide-by date arrives. See the offboarding handoff checklist for software renewals
Overlap: two tools doing the same job, both renewing this year

Step 6: Keep it rolling after the budget is approved

A calendar built once for budget season goes stale by spring. Keep it rolling.

Monthly (15 to 30 minutes): Add the newly visible month at the end so the view always covers the next 12 months. Record the actual cost of anything that renewed and compare it with the plan. Check decide-by dates in the next 60 days.

Quarterly: Review every renewal with a notice date in the next two quarters, confirm owners, and record decisions. The software renewal review checklist covers what to check on each one, and how to run a quarterly renewal review meeting covers the agenda and who to invite.

Between reviews: Make sure each renewal has reminders counted back from its notice date, sent to the owner and a backup. See the 90/60/30-day renewal reminder schedule.

Common mistakes

Plotting by invoice date and forgetting notice dates
Applying one blanket increase to every line
Leaving monthly subscriptions off because each one is small
Keeping the finance view and the owner view in separate files
Building it once for budget season and never updating it
Listing a team instead of a named person as owner

Spreadsheet version

A spreadsheet works for a modest number of renewals. Use one row per renewal with the fields above, add a column for payment month, and build a summary tab that totals expected cost by month and fiscal quarter. Add a second tab or filter sorted by decide-by date. Keep one master copy with one owner.

When the sheet starts to drift (costs that never get updated, owners who left, reminders living in one person's calendar) see how to move renewal tracking out of spreadsheets.

FAQ

When should we start building the renewal calendar for next year's budget?

A few months before your fiscal year begins, so there is time to collect costs, confirm owners, and make decisions on early renewals before the budget is locked.

Should the calendar be sorted by renewal date or notice date?

Both, for different people. Finance needs cost by payment month. Owners need renewals sorted by notice date and decide-by date, because that is when action is still possible.

How do we handle price increases we do not know yet?

Use the agreement's price change clause when it has one. When it does not, mark the line as an assumption, choose a figure your team agrees on, and assign someone to confirm it with the vendor before the decide-by date.

Do monthly subscriptions belong on a 12-month calendar?

Yes. Show them as a recurring monthly cost. They add up, and they are easy to forget when only annual contracts get attention.

Who should own the renewal calendar?

One person, usually in IT, ops, or finance, who keeps the list current and runs the monthly update. Each individual renewal still needs its own named owner.