Contract renewal process flowchart (notice window to signed renewal)
Contract renewal process flowchart: horizon alert, owner check, notice deadline, spend and performance review, renew, renegotiate, re-tender or lapse, approval against delegated authority, signature and register update.
How it works
Rename the lanes to your own organisation
Replace Contract owner, Procurement, Finance, Approval authority, Legal and Supplier with the roles you actually have. Keep the contract owner separate from procurement: one holds the business need, the other runs the process, and merging them is why renewals get decided by whoever answers the supplier's email. Smaller organisations fold Legal into an external adviser and Approval authority into a director; merge the lanes rather than leaving one in the chart that never acts. Use one lane per decision-maker rather than per person, so the diagram survives a reorganisation.
Set the alert on the notice deadline, not expiry
Work backwards from the notice deadline. Take the expiry date, subtract the notice period, then subtract the time a review and an approval genuinely take in your organisation — for most that is another six to twelve weeks. That figure, not ninety days before expiry, is when "Renewal horizon alert raised" should fire. Store the notice deadline as its own field in the register rather than deriving it in someone's head, and give high-value or auto-renewing contracts a longer lead time than the rest.
Define the renewal pack the review has to produce
Decide what "Pull spend, usage and price benchmarks" must return before anyone talks to the supplier: actual spend against contracted value, consumption against what was bought, the indexation applied in each year of the term and the index it was supposed to track, service credits earned and claimed, open issues, and a current market comparator. Name the owner of each figure. If the review is assembled during the meeting it will be assembled from the supplier's numbers, which is the position you are trying to avoid.
Write your real thresholds onto the authority decision
"Within delegated authority?" is inert until your written tiers are attached to it in figures, with a named role at each. State the value basis at "Confirm renewal value and budget cover" too: the whole renewal term including any options it creates, known variable spend and the compounded uplift — not the difference from last year, which is how a large contract gets waved through on a small increase. Add the triggers that escalate regardless of size: uncapped liability, personal data processing, exclusivity, a term longer than your standard, or a supplier already on a corrective plan.
Agree how notice is served and what exit involves
Write the mechanics onto "Serve termination notice in writing": the form the contract requires, the legal entity and address it must go to, who signs it, and how proof of delivery is kept. Then fill in "Plan exit, data return and transition" with your real obligations — data export in a usable format and its deletion afterwards, return of equipment or keys, knowledge transfer, any termination assistance the contract already obliges the supplier to give, and final invoicing. Both sit on the routes that leave, and both are easier to settle while the supplier still wants the renewal than once they know they have lost it.
Walk it through with the people who run it, then publish
Take the finished chart to a contract owner, a buyer, whoever holds the register and the person who actually signs, and walk one live renewal through it end to end. Ask where the chart is wrong rather than whether it looks right; the disagreements will land on the notice deadline, the value basis and who may say no to a supplier. Correct it, add the thresholds and the register fields, then publish that revision and keep the earlier ones, so anyone opening it later can tell which version they are reading.
Frequently asked questions
What are the steps in a contract renewal process?
A workable sequence is: raise a renewal alert against the notice deadline rather than the expiry date; confirm the contract still has a named owner and reassign it if not; read the term, notice period and renewal mechanism out of the contract itself; check the notice window is still open; pull spend, usage, indexation and benchmark data; review performance and whether the need still exists; decide the route — renew as is, renegotiate, re-tender or let it lapse; propose and negotiate the price and terms changes; have legal review only what has changed; value the renewal on a whole-life basis and confirm budget; test it against the delegation of authority and escalate if it is above tier; sign and exchange; then update the register, the purchasing system and the budget, and reset the reminder against the new notice deadline. The exit routes add two steps: serve written notice, and plan the data return and transition.
What is the difference between contract renewal and contract approval?
Contract approval is one stage inside a renewal, not an alternative to it. The approval process at /templates/contract-approval-process answers a governance question about a contract whose terms are already settled: is this person authorised to commit the organisation at this value, has it been signed correctly, and is the executed copy filed with its key dates? Renewal is the wider cycle that produces something to approve. It starts before expiry with an alert, a named owner and a notice deadline, spends most of its effort on whether the contract should continue at all, and can end without any approval being sought — a served termination notice is a perfectly good outcome. If you already know you are renewing and only need the sign-off path, use the approval template. If the question is whether to renew, and on what terms, use this one; it hands the agreed renewal to the same authority ladder at "Within delegated authority?".
How far in advance should a contract renewal process start?
Count backwards from the notice deadline, not the expiry date, and add the time your own process takes. If the contract carries a ninety-day notice period and a review plus approval realistically takes eight weeks, the process has to begin roughly five months before expiry — and if a re-tender is on the table, longer again, because a sourcing exercise for anything substantial rarely runs in under three months. There is no universal figure, which is why the useful move is to store the notice deadline as a field in the register and set the lead time by contract type: longest for high-value, auto-renewing or hard-to-replace suppliers, shortest for small contracts on your own template that expire cleanly. A renewal calendar built on expiry dates alone will be late on every contract with a notice period in it.
What is an auto-renewal clause, and how do you stop one?
An auto-renewal or evergreen clause extends the contract for a further term unless one party gives notice by a stated deadline. The effect is that the decision point is the notice deadline, not the expiry date, and silence counts as agreement. To stop one, serve notice in the form the contract specifies — usually in writing, to a named entity and address, sometimes by recorded delivery — before that deadline, and keep proof of delivery; an email to your account manager is not notice under most agreements. Serve it even if you might still renew, because notice can be withdrawn by agreement and a missed deadline cannot be undone. In this chart the trap is drawn rather than assumed: "Notice window still open?" is asked before any review effort is spent, and a missed window ends the flow at "Term auto-renewed by default" with the next window diarised.
Should you renegotiate or re-tender a contract at renewal?
Renegotiate when the requirement is stable, the supplier is performing, and what has drifted is price, volumes or service levels — a renewal conversation with real usage data and a credible alternative usually recovers more than a tender costs. Re-tender when you cannot answer whether the price is competitive, when the specification has changed enough that the original award no longer describes what you buy, or when the incumbent has held the work long enough that nobody has tested the market. Two practical constraints decide it more often than principle. A tender has a cost in time and internal effort that only pays back above a certain contract value, and a re-tender that cannot finish before expiry needs either an early notice or a bridging extension, which is why this chart routes a not-ready replacement to "Agree a short bridging extension" rather than letting the deadline pass.