What a Good Vendor Renewal Process Actually Looks Like

Renewal process failures are almost never dramatic. There is no single moment where everything goes wrong. Instead, the failure is distributed across a hundred small gaps: a contract nobody knew about, an alert that fired too late, a review that did not happen because the owner was in a different city that week, a negotiation that started with seven days until the notice window closed.

Each gap is defensible. Taken together, they produce an outcome where 20-30% of contracts at a typical mid-market company auto-renew without any active decision. The spend continues. The value is not re-assessed. The seats are not rightsized. The uplift is not challenged.

The reason failures are quiet is that the cost lands in the budget as a line item that looks exactly like a deliberate renewal. There is no flag. There is no moment where someone says “that contract renewed without review.” The cost just appears, and the organisation moves on.

A benchmark-driven approach to renewal management makes the failures visible. When you know that 0% of contracts should auto-renew without a decision, and you can see that 24% did in the last 12 months, you have a concrete problem with a concrete fix.

Every vendor renewal passes through five moments. A good process has a defined action and a defined owner at each one. A weak process has some of these moments and skips others.

1. Discovery. The contract is added to the register with the correct dates - both the renewal date and the notice deadline, which are not the same. Discovery happens at signing, not at renewal. If you are discovering contracts when the vendor sends a notice, you are already behind.
2. Owner assignment. One named individual is responsible for the renewal decision. Not the team. Not the department. One person who has the context, the authority, and the accountability. This assignment is made at the time the contract is added to the register, and it is updated whenever that person changes roles or leaves.
3. Notice alert. The owner receives an alert before the notice window opens - not on the notice date, but with enough lead time to do something useful. The benchmark is 90 days before the notice deadline. That is the point at which a negotiation is still credible and alternatives can still be evaluated.
4. Review. The owner - or in some cases a small working group - reviews the contract against current usage, current need, and current market pricing. This is a structured conversation, not a rubber stamp. It should take between 30 minutes and a few hours depending on contract value.
5. Sign-off and log. A decision is made and recorded: renew at current terms, renegotiate, rightsize, or cancel. The log entry is one line. It exists so the next renewal cycle can see what was decided and why, and so the organisation has an audit trail that shows renewals were actively managed.

A process that covers all five moments consistently is a level 4 organisation. Most companies are operating at level 1 or 2.

Level 1: Spreadsheet and memory

The contract register is a shared spreadsheet, maintained by whoever has access, updated when someone remembers. Renewal reminders are calendar invites set by the person who signed the contract. There is no consistent ownership assignment. Review happens when someone notices the invoice. Auto-renewals are common and accepted as normal.

Who is here: most companies under 150 people and a significant number of companies between 150-500. The spreadsheet worked at 15 contracts and nobody replaced it as the stack grew.

Level 2: Better spreadsheet, same problems

The register is more complete. Someone owns the spreadsheet and tries to keep it current. There are columns for renewal date and owner. Alerts are still manual - calendar reminders, often at 30 days or less. Review happens for large contracts. Small contracts still auto-renew routinely. Ownership gaps exist when employees leave.

Who is here: companies that have felt the pain of a missed renewal and responded by improving the spreadsheet. The underlying issue - that a spreadsheet requires manual maintenance and does not survive employee turnover - is still present.

Level 3: Tracked dates, inconsistent ownership

Contracts are in a register with reliable dates. Alerts fire automatically. But ownership is inconsistently assigned - perhaps 60-70% of contracts have a named owner who is still current. Review happens for most contracts but is not uniform. Some auto-renewals still occur because the alert was acknowledged but no decision was made before the window closed.

Who is here: companies that have implemented a tool or process improvement but have not fully closed the ownership gap. Often the result of a good initiative that was partially executed.

Level 4: Every contract has a date, an owner, and a reminder before the window

The register is complete and current. Every contract has the notice deadline tracked (not just the renewal date). Every contract has a named owner who is still with the company. Alerts fire at 90 days before the notice deadline. Every renewal is reviewed and logged. Auto-renewals without a decision are tracked and expected to be zero.

Who is here: a minority of mid-market companies. Usually those that have been through a painful spend review or have a RevOps or procurement function with clear ownership of the renewal process.

Apply these five benchmarks to your current process. Score yourself honestly. The gaps are where the money is.

1. Percentage of contracts with a named, current owner

Good: 100%. Typical: under 40%.

This is the most common failure point and the hardest to maintain. Ownership erodes every time someone leaves or changes roles. A register that was 90% owned six months ago can be at 60% today if three people with contract ownership have moved on. Audit the owner column quarterly, not annually.

2. Percentage of contracts with the notice deadline tracked

Good: 100%. Typical: under 30%.

Most registers track the renewal date. Very few track the notice deadline - the date by which you must notify the vendor of non-renewal or changes. These are not the same. A contract that renews on 1 October may require 60 days notice, making the actual deadline 1 August. Managing to the renewal date instead of the notice deadline costs you 60 days of lead time on every contract. For a 60-vendor portfolio, that is the equivalent of starting every negotiation two months late.

Read more about how vendors design their notice windows to make this error expensive.

3. Lead time before the notice window when alerts fire

Good: 90 or more days before the notice deadline. Bad: 7 days or fewer, or after the deadline.

Ninety days is the minimum lead time to evaluate alternatives, pull usage data, and have a negotiation with the vendor where you have credible options. At 30 days, you can still negotiate but you have almost no time to switch. At 7 days, you are choosing between accepting the vendor's terms and operational disruption. Most calendar reminders fail because they are set at the renewal date, not the notice deadline, and often at 14-30 days rather than 90.

4. Days of review runway actually used

Good: 45 or more days between alert and decision. Bad: under 7 days.

Getting an alert at 90 days is only useful if the review actually starts. Many organisations receive a 90-day alert and begin the review at 20 days because other priorities intervene. The benchmark here is the actual time between the alert firing and the renewal decision being logged - not the theoretical lead time.

5. Share of renewals that auto-rolled without a decision

Good: 0%. Typical: 20-35%.

This is the single most honest measure of a renewal process. An auto-renewal is not inherently bad - sometimes the right decision is to renew at standard terms without a negotiation. But it should be a decision, not an accident. If 25% of your renewals are auto-rolling without anyone making an active choice, that is 25% of your SaaS spend that is not being managed. Read the detailed case for why auto-renewals without review are costly.

If you can only do one thing, it is this: track the notice deadline, not the renewal date, and assign one named owner to each contract.

Those are technically two things, but they are inseparable. An alert on the notice deadline with no owner is an alert that nobody acts on. An owner with no notice-deadline alert is an owner who only hears about the renewal when the vendor calls.

Everything else in the process - the review framework, the negotiation approach, the decision log, the RACI for who approves what - builds on top of these two. If you do not have reliable notice-deadline dates and current ownership on every contract, the rest of the process does not matter, because the alerts are firing at the wrong time and landing in the wrong inbox.

The companies that move from level 2 to level 3 almost always do it by solving these two problems first. The companies that stall at level 2 are usually the ones that invest in the review framework before they have fixed the data underneath it.

If you want to go deeper on the ownership question specifically, the RACI for SaaS renewals is a useful starting point. For a detailed look at why spreadsheets fail as the register grows, that post covers the mechanics in detail.

Renewly is built around the two things that move organisations from level 2 to level 3: notice deadlines and ownership. Upload your vendor contracts. Renewly extracts the vendor name, contract value, category, and notice deadline - the actual deadline, not just the renewal date. Assign an owner per contract. Alerts fire at 90 days before the notice deadline. Every renewal decision is logged. The percentage of auto-renewals without a decision is tracked and visible.

It is not a CLM system. It is not designed for contract drafting or e-signature workflows. It is a vendor renewal register that solves the specific problem of knowing what you have, when it expires, who owns it, and whether you acted before the window closed.

Free for up to five vendor contracts.