Renewal and price review: documents to prepare
A technology contract renewal rarely arrives as a single event. Price review clauses, service credit resets and licence scope changes tend to surface together, and each one needs its own paper trail. This page sets out the stages, the documents a technology or procurement team should gather, and the point after which renegotiation becomes far harder to reverse.
What renewal and price review actually cover
Renewal is the decision to extend a contract past its current term. Price review is a separate mechanism inside that contract, usually triggered by a fixed date, an index, or a volume threshold. The two often coincide, but a contract can allow one without the other. Reading the trigger clause first avoids preparing the wrong file.
In practice, three questions decide how much preparation is needed: is the renewal automatic unless one side objects, does the price review require a formal notice, and does either mechanism depend on a benchmark such as usage volume or an external index. Answering these three questions before collecting documents saves time later.
Stages of the process
| Stage | What happens | Typical duration |
|---|---|---|
| Trigger check | Confirm whether renewal is automatic, and whether a price review window has opened | Days |
| Notice | Send or receive the formal notice required by the contract, if any | Set by the contract, often 30 to 90 days before term end |
| Data gathering | Collect usage figures, service reports, and prior correspondence | One to three weeks |
| Position paper | Draft the internal rationale for the target price or terms | One week |
| Negotiation | Exchange proposals with the counterparty | Two to eight weeks |
| Sign-off | Execute the amendment or renewal instrument | Days once terms are agreed |
The stages above are typical, not fixed. A contract with a short notice window compresses everything into the notice period, and a missed notice can mean the contract renews on the old terms whether either side wants that or not.
Documents to prepare
- The current contract, including all amendments and side letters, read as one document rather than in isolation.
- The renewal or price review clause itself, highlighted, with the trigger date and notice period marked.
- Usage and consumption records for the review period, from whichever system tracks them.
- Service level reports covering the same period, including any credits claimed or disputed.
- Prior correspondence about pricing, scope, or performance, even informal emails.
- A benchmark reference if the clause ties price to an index, market rate, or comparable deal.
- A short internal memo stating the target outcome and the fallback position.
Where the contract involves software licensing terms that predate the current supplier relationship, it helps to check whether the original licence scope has changed through use, since scope creep is a common source of price review disputes.
Where personal data flows through the service being renewed, the renewal file should also confirm what the data processing terms require going forward. What a privacy notice needs to cover when personal data is involved is set out separately: Privacy notice overview and what to prepare.
The point of no return
Most technology contracts fix a date after which silence counts as acceptance of renewal on existing terms. This date is the point of no return for that cycle. Once it passes, a party that wanted a price review typically has to wait for the next cycle, unless the contract allows an out-of-cycle review.
A second point of no return sits inside the negotiation itself: once an amendment is signed, the prior price review window closes for good. Verbal agreements reached during negotiation do not replace the signed instrument, and a team that treats an email confirmation as final risks having no enforceable change at all.
Who decides, and on what basis
Inside most organisations, the decision sits with whoever holds contract authority for spend at that level, informed by the technology or procurement lead who ran the review. On the counterparty side, the same split usually applies: an account manager gathers the position, but sign-off sits higher up. Knowing who signs on the other side, and confirming they have that authority, avoids agreeing terms that later need re-approval.
Common forks
If the contract is silent on renewal mechanics, treat it as requiring active agreement rather than assuming automatic continuation, and send notice early to protect the review window.
If the counterparty does not respond to a price review notice within the period the contract allows, check the default outcome written into the clause. Some contracts continue at the old price if no agreement is reached; others allow termination for non-agreement. The file should record the date the notice was sent and any proof of delivery.
If usage has materially changed since the last agreed price, gather the consumption data before opening negotiation rather than during it. A position built on numbers agreed in advance moves faster than one built on numbers challenged mid-discussion.
What this page does not cover
This page describes the renewal and price review procedure and the documents it typically requires. It does not set out what a given jurisdiction's default rules say about silent renewal, since that depends on the governing law chosen in the contract and on facts specific to each file. It also does not cover novation, which is a different process triggered by a change in the contracting party rather than by a review date.
Sources and the limit of this file
This page reflects common contractual mechanics observed across technology and outsourcing agreements, not a single statutory scheme. Where a contract sits under a jurisdiction with counterparty registers, checking what can be verified about the other party before signing a renewal is a separate step. What can be established about a counterparty in Luxembourg, and the limits of that check, is set out here: Counterparty in Luxembourg and its limits in practice.
Where the supplier or the contracting entity sits in the United States, document-level verification follows a different register and a different set of limits, explained separately: Document in United States explained.
Last reviewed: this page is checked against current internal procedure records and updated when the underlying process changes.
Related process
A related but distinct scenario is a change in the contracting party itself. The document set for that scenario differs from a renewal file: Novation on a corporate change: documents to prepare.
FAQ
How long does renewal and price review take in practice?
Simple renewals with no price dispute can close within the notice period, often two to four weeks. A contested price review typically runs six to ten weeks once negotiation starts, longer if a benchmark dispute needs external data.
Which documents are needed to start?
At minimum: the current contract with amendments, the specific renewal or price clause highlighted, recent usage and service data, and a short internal statement of the target outcome. Everything else supports these four.
What happens if the other side does not respond?
Check the default outcome written into the clause first. Some contracts continue on prior terms if no agreement is reached in time; others allow either side to treat non-response as grounds for termination. Keep proof that notice was sent and received.
Next step
If the renewal question is tangled with a custody arrangement on a technology platform, start with the immediate steps for that situation: When custody is held by a platform and the.