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.
What the contract renewal process flowchart (notice window to signed renewal) process is
Most contracts are not renewed. They roll over. The register alerts somebody sixty days before expiry, by which point a ninety-day notice period has closed; the person named as owner left eighteen months ago; and the decision announces itself as an invoice at a price nobody agreed, uplifted by an indexation clause that has been compounding since signature. That is the default outcome of a renewal process that exists as a date field in a spreadsheet and nothing else. The second failure is subtler and more expensive. The renewal happens on time, it is signed by someone entitled to sign it, and nobody asked whether the thing was used: licences bought for a headcount that has since halved, a minimum volume commitment the business never reached, a service level breached every quarter for two years without a credit ever being claimed. All of it renewed on an account manager's assurance that nothing much has changed. The notice window is the one point in the term when walking away costs nothing, the supplier knows exactly when it falls, and most organisations let it go past without noticing it was there.
This chart is drawn buy-side: your organisation is the customer, and the question is whether to keep paying a supplier. The sell-side mirror runs on the same calendar with the roles reversed, and the half of it that matters most (a customer who wants out) is at /templates/customer-cancellation-process. What this page is not is the review of the wording itself. Marking up terms, running redlines against a playbook and settling a liability cap belong to the contract review process at /templates/contract-review-process; this chart calls into that work at "Review the changed clauses" rather than repeating it. Nor is it the authority ladder. Who may bind the organisation, at what value, and how the executed copy is filed is set out in the contract approval process at /templates/contract-approval-process, and the renewal reuses that ladder instead of inventing a second one. And it is not the scorecard. Rating a supplier across everything they do for you, on a cycle that has nothing to do with any one agreement's dates, is the supplier evaluation process at /templates/supplier-evaluation-process; this chart reads that rating at "Review performance and future need" and asks the narrower question of whether this contract should continue past this deadline, on these terms.
Three decisions are drawn here that most renewal procedures leave implicit. "Notice window still open?" is asked before any review work begins, because once the deadline has gone the answer is already fixed, and the only honest outcome is "Term auto-renewed by default". Giving that a terminal box rather than a route back into the review is the point: what follows a missed deadline is diarising the next one, not deciding anything. "Which renewal route?" is a four-way rather than a yes or no: renew as is, renegotiate, re-tender, let it lapse. Renewing on unchanged terms is a decision that should still be valued and approved, and letting a contract lapse is an option that only exists if somebody asks the question out loud. And "Replacement ready before expiry?" catches the failure that turns a tidy re-tender into an emergency, where the sourcing exercise overruns, the incumbent knows it, and the business needs cover at any price. The chart routes that case to "Agree a short bridging extension" and sends it back through the approval lane, because a bridge is a renewal with a shorter term and exactly the same authority question.
What this flowchart covers
In this template
- Six role lanes (Contract owner, Procurement, Finance, Approval authority, Legal and Supplier) across six phases: Renewal horizon, Review and decision, Negotiation, Approval, Signature and update, and Exit and close.
- A horizon trigger with two pieces of housekeeping before any analysis starts: "Contract owner still in post?", whose Vacant branch runs "Reassign the contract to a new owner", and "Confirm the notice period and deadline", which reads the clause rather than trusting the register field.
- "Notice window still open?" asked before any review effort is spent, with the Missed branch ending the flow at "Term auto-renewed by default" rather than carrying on as though a choice remained.
- A four-way "Which renewal route?" (Renew as is, Renegotiate, Re-tender, Let it lapse) fed by "Pull spend, usage and price benchmarks" in the Finance lane and "Review performance and future need" in the Contract owner lane.
- A negotiation loop drawn across three lanes: Procurement makes the "Propose price and terms changes", the Supplier lane holds "Return counter-proposal and redlines", and Legal takes "Review the changed clauses"; "Position acceptable?" then closes it with three branches that accept, run another round, or abandon the renewal to a re-tender.
- Approval against the delegated-authority ladder at "Within delegated authority?", signature and "Update the register, ERP and budget"; plus an exit route that serves written notice, plans the handover and tests "Replacement ready before expiry?", looping a not-ready case into "Agree a short bridging extension".
When to use this template
- You have been caught by an automatic renewal, and you want the notice deadline rather than the expiry date to be the thing your register alerts on.
- Your contract register lists owners who left the organisation, and nobody can say who is entitled to decide whether a renewal goes ahead.
- Renewals get approved on the size of the increase rather than the value of the renewal, so a supplier asking for four per cent never reaches the tier the contract itself belongs in.
- You are re-tendering a category for the first time in years and need the notice, the exit and the transition drawn alongside the sourcing timetable.
- You are configuring a contract lifecycle tool or a renewal dashboard and want the process agreed before anyone builds reminders and approval routing into software.
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.
Where this process fits
In most operations this process follows Supplier evaluation process flowchart (ongoing performance).
It is one step in Contract lifecycle.
Step 1: Contract review process flowchart: intake to agreed terms
Step 3: Contract approval process flowchart (approve, sign, execute)
Step 4: E-signature routing process flowchart (package to signed record)
E-signature routing process flowchart template: lock the approved copy, verify signer authority and identity, set signing order, handle declines or expiry, validate the certificate and archive the record.
Step 5: Contract renewal process flowchart (notice window to signed renewal) You are here
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.