Renewal and price review: stages and deadlines
Renewal and price review runs in four stages: notice, data exchange, negotiation and signing. Each stage carries a deadline drawn from the original contract, not from statute. Missing a renewal notice date is usually irreversible: the contract lapses or auto-renews on the incumbent's terms. The whole cycle typically takes six to twelve weeks.
What renewal and price review actually change
A technology contract rarely renews itself on the same terms without a trigger. Most master service agreements and licence schedules carry a notice window: a fixed number of days before expiry, inside which either side must speak, or the contract either lapses, rolls over automatically, or opens for renegotiation. Price review usually sits inside the same window, but it is a separate clock. A vendor can accept renewal and still reject the proposed price, or accept the price and refuse renewal on volume terms.
The practical effect is that a client who does nothing during the notice window loses the ability to negotiate price and is left with whatever default the contract specifies: continuation at the old rate, an indexed increase, or termination. None of these outcomes is decided by a court. They are decided by the calendar written into the contract itself.
Stages, documents and deadlines
| Stage | What happens | Typical duration | Document produced |
|---|---|---|---|
| Notice | Either side triggers the renewal or price-review clause in writing | 1–3 days to draft and send | Notice letter or notice email referencing the clause |
| Data exchange | Usage volumes, service levels and cost baseline are shared | 1–2 weeks | Usage report, cost breakdown, current schedule |
| Negotiation | Terms, price and duration are proposed and countered | 2–6 weeks | Redlined schedule, term sheet |
| Signing | Amendment or new schedule is executed by authorised signatories | 3–10 days | Signed amendment or renewal schedule |
These durations assume a cooperative counterparty. A dispute over benchmarking data, or a change of authorised signatory on the other side, extends every stage that follows.
What to do
- Calendar the notice window as soon as the contract is signed. The person responsible should be named, not left to whoever notices the date.
- Send the notice inside the window, in the form the contract requires. An email to the wrong address or the wrong role does not stop the clock.
- Assemble usage and cost data before negotiation opens. Whoever brings numbers first sets the frame for the discussion.
- Fix a response deadline for the counterparty and put it in writing. Silence is a scenario the process must plan for, not react to.
- Route the final terms through the same signatory chain as the original contract. A schedule signed by the wrong person is not binding.
- Keep the amendment and the correspondence trail together. The next renewal cycle starts from wherever this one ends.
Who decides
There is no external forum for a renewal or price-review dispute at this stage. The decision sits with whoever holds signing authority on each side, guided by the escalation clause in the contract, if one exists. Where the contract names a specific manager or committee for pricing disputes, that body decides first; litigation or arbitration is a later, separate track and is outside the scope of this page.
Some framework agreements tie price review to an indexation formula rather than open negotiation. Where the underlying calculation is expressed as executable logic rather than a manual benchmark, the way the outcome is proved resembles the mechanism described in Smart contract in tokenised rights and its limits. The comparison is useful for spotting where a dispute over the formula's output, rather than its wording, may arise.
Common forks
If the contract is silent on notice periods, treat the general termination notice as the default and confirm it in writing with the counterparty before relying on it.
If the vendor proposes a price increase without supporting usage or cost data, request the breakdown before responding on price; a counter-offer made without data weakens the client's position later.
If the corporate structure on either side has changed since signing — a merger, a transfer of the contracting entity — check whether renewal is even the right track, or whether the contract instead needs a novation; see Novation on a corporate change technology contract for that separate process.
What this page does not cover
This page does not cover the substantive drafting of a price-review clause, the choice of benchmark, or the tax treatment of an amendment. It does not decide whether a given increase is commercially reasonable — that is a negotiation question, not a procedural one. It does not cover disputes that have already moved to litigation or arbitration.
Sources and limits
This description follows standard contract-management practice for technology and outsourcing agreements and does not rely on a specific statute or regulation; the applicable deadlines come from the contract itself, and readers should check their own document rather than a general rule. Last reviewed: this page reflects our internal process notes and is not a substitute for reading the current schedule.
Before a renewal decision commits budget, a structured check on the counterparty's standing is often the missing step; see Counterparty report before appointing a developer for how and when that check runs.
Where the renewed schedule needs to be filed with an office or registry as part of the amendment, the document-level check follows a separate track, described in Document report before filing with an office explained.
For the scope and limits of our advisory role on technology contracts generally, see About the firm and its scope and its limits.
Related publications
A related procedure, triggered by a different event, covers what happens when the contracting entity itself changes: Novation on a corporate change technology contract.
FAQ
How long does renewal and price review take in practice?
Six to twelve weeks from notice to signature, assuming both sides respond within the deadlines they set. A dispute over data or authority adds weeks, not days.
Which documents are needed to start?
The current schedule, a usage or cost report covering the review period, and the written notice referencing the renewal or price-review clause. Without these three, negotiation has nothing to work from.
What happens if the other side does not respond?
The contract's default applies: continuation on existing terms, automatic renewal, or lapse, depending on what the clause specifies. A written reminder before the deadline expires is the only practical safeguard.