Practical guide
How to Run a Quarterly Renewal Review Meeting: Agenda and Who to Invite
Most renewal surprises are not caused by a bad decision. They are caused by no decision. Once a quarter, the people who own renewals look at what is coming, confirm every item has an owner and a date, and make or schedule the decisions before the notice dates arrive.
October 21, 2026 · 8 minute read
Why a renewal review needs its own meeting
Most renewal surprises are not caused by a bad decision. They are caused by no decision. The notice date passed while the contract sat on a list that nobody looked at as a group.
A short, recurring renewal review fixes that. Once a quarter, the people who own renewals look at what is coming, confirm every item has an owner and a date, and make or schedule the decisions before the notice dates arrive.
This is an internal meeting, not a vendor business review. Vendors are not in the room. The goal is simple: leave with a decision or a dated next step for every renewal in the window.
This guide is for IT, ops, and finance teams who want a repeatable format. It covers who to invite, what to prepare, a timed agenda, and what to record when the meeting ends. For the checklist you run on each individual renewal, see the software renewal review checklist.
Pick the window: look two quarters ahead
A quarterly meeting that only looks at the next quarter is already late. Many software contracts need notice 30, 60, or 90 days before the term ends, and a real decision needs time for usage checks, budget conversations, and negotiation.
A practical window:
- Decide now: anything with a notice date in the next 90 days
- Prepare now: anything with a notice date 90 to 180 days out
- Watch: large or strategic contracts beyond 180 days that need a long runway
Build the window around notice dates, not renewal dates. A contract that renews in five months with a 90-day notice period belongs in "decide now." For why notice dates matter more than renewal dates, see how to avoid surprise SaaS auto-renewals. For turning a clause into a dated deadline, see how to find the notice period in a software contract.
Who to invite
Keep the core group small. Invite people who can make or unblock decisions, and bring everyone else in only for their items.
- Meeting owner: usually the person who maintains the renewal list in IT or ops. Runs the agenda, prepares the list, and sends the follow-up
- Finance: speaks to budget, spend changes, and payment timing, and can weigh in on which renewals are worth negotiating
- IT or security: flags access, data, or integration risk for tools up for renewal
- Procurement or a contracts contact, if you have one: handles negotiation and paperwork for larger contracts
- Business owners, for their items only: the person who owns each tool joins for the minutes their renewal is discussed, not the whole hour
- An escalation contact: someone who can make the call on high-value or blocked renewals. They do not need to attend every quarter
If you are not sure who owns a tool, that is itself an agenda item. For how to assign owners so this meeting has someone to ask, see who should own software renewals. If an owner has left or changed roles, run the offboarding handoff checklist for software renewals before the meeting.
Prep before the meeting
The meeting goes faster when the list is clean before anyone walks in. A week ahead, the meeting owner should:
- Pull every renewal in the window: vendor, product, term end date, notice date, decide-by date, and current cost
- Ask each owner to confirm their records: dates correct, owner still right, current usage noted
- Build an exception list: the items that need group attention
- Send the agenda and the exception list: so business owners know when they are needed
Good triggers for the exception list:
- Notice date inside the next 90 days with no decision yet
- No named owner, or an owner who has changed roles or left
- No confirmed notice date on the record
- A cost increase or a usage drop since last renewal
- A tool that overlaps with another tool you already pay for
- An open decision carried over from last quarter
Items that are healthy (owner confirmed, dates confirmed, decision on track) do not need discussion. They stay on the list but off the agenda.
If your records are missing basic fields like notice period or owner, start with software license inventory: what to record for every license.
The agenda (60 minutes)
A timed agenda keeps the meeting from turning into a tour of every tool. Adjust the minutes to your list size.
1. Open the window (5 minutes). The meeting owner shares the count of renewals in each bucket (decide now, prepare now, watch) and the number of exceptions. No discussion yet.
2. Close last quarter's open items (10 minutes). Go through decisions and actions carried over. For each: done, still open with a new date, or escalated.
3. Decide-now renewals (20 minutes). For each renewal with a notice date in the next 90 days, the business owner joins and the group picks one outcome:
- Renew as is
- Renew and renegotiate
- Downgrade or change seats
- Cancel and send notice
- Escalate, with a named person and a date
4. Owner and date gaps (10 minutes). Assign an owner and a backup to every item that has none. Assign someone to confirm the notice date for every item where it is missing or unclear.
5. Prepare-now renewals (10 minutes). For notice dates 90 to 180 days out, confirm the owner, agree what evidence the decision needs (usage, cost, alternatives already in use), and set the decide-by date.
6. Wrap up (5 minutes). Read back every decision and next step with its owner and date. Confirm the date of the next review.
What to record after the meeting
Write decisions down on the renewal record itself, not only in meeting notes. A decision that lives only in notes is lost by next quarter.
- The decision: renew, renegotiate, downgrade, cancel, or escalate
- Who decided and when
- The next step, its owner, and its due date
- Notice sent, if cancelling or changing terms: date sent, method, and where proof of delivery is saved
- Updated owner and backup
- Updated reminders: counted back from the notice date, not the renewal date
The meeting owner sends a short summary the same day: decisions made, items escalated, and gaps still open. For how to space reminders between meetings, see the 90/60/30-day renewal reminder schedule.
Common ways the meeting breaks down
- Reviewing every tool instead of only the exceptions
- Looking at renewal dates and missing notice dates
- Inviting every business owner for the full hour, so they stop coming
- Ending with "we will look into it" instead of a named owner and a date
- Recording decisions in notes but not on the renewal record
- Rotating the meeting owner, so nobody prepares the list
- Skipping a quarter because nothing felt urgent, which is when notice dates slip past
Between meetings: the weekly scan
A quarterly meeting does not replace a short weekly check. Once a week, the meeting owner spends 10 to 15 minutes scanning notice dates in the next 30 days and chasing anything without a decision. The quarterly meeting is for decisions and gaps. The weekly scan is for making sure nothing lands between meetings.
Spreadsheet version
A spreadsheet can run this meeting for a modest number of contracts. Add columns for notice date, decide-by date, bucket (decide now, prepare now, watch), decision, next step, next step owner, and next step due date. Sort by notice date and filter to the window before each meeting. Keep one master copy with one owner.
When the sheet starts to drift (decisions in a separate doc, owners who have left, reminders living in one person's calendar) see how to move renewal tracking out of spreadsheets.
FAQ
How often should we hold a renewal review meeting?
Quarterly works for most teams, with a short weekly scan between meetings. Teams with a large number of monthly or short-term contracts may prefer a monthly review with a shorter agenda.
How is this different from a vendor QBR?
A vendor QBR is a meeting with the vendor about their performance. A renewal review is internal. It covers every renewal in the window, focuses on notice dates and decisions, and does not include vendors.
Who should run the renewal review?
The person who maintains the renewal list, usually in IT, ops, or finance. They prepare the list, run the agenda, and send the summary. Keep the same owner from quarter to quarter.
Do business owners need to attend the whole meeting?
No. Invite them for the minutes when their renewal is discussed. The renewal record should carry the context so they do not need to sit through every item.
What if we do not know a contract's notice date?
Put it on the exception list and assign someone to find it in the signed paperwork before the next meeting. Until it is confirmed, treat the renewal as if the notice date is close.