Benchmarking clause: documents to prepare
A benchmarking clause lets either party compare current pricing or service levels against a defined market sample and demand an adjustment. Before the first benchmark request goes out, the file needs a fixed comparator methodology, current pricing and service schedules, and a record of any prior amendments. Without these three, the exercise stalls before it starts.
What changes once the clause is triggered
A benchmarking request is a contractual notice, not a conversation. It starts a clock defined by the contract itself: a period for the other side to respond, a period to select a comparator group, and usually a period to implement any adjustment. Missing the notice deadline or sending an incomplete request resets that clock or gives the other side grounds to reject the exercise outright.
The practical risk sits in documentation, not in the underlying commercial logic. A party that cannot produce its own pricing history or service records at the point of comparison loses leverage in the negotiation that follows, regardless of what the market data shows.
What to do
- Contract owner pulls the current signed version of the agreement, including all amendments and side letters that touch pricing or service levels.
- Finance or commercial lead assembles the pricing history: rate cards, invoiced amounts, and any discounts applied over the review period.
- Service owner compiles service-level reports for the same period — the raw data a benchmarker will need to compare like with like.
- Legal team checks the clause wording for the notice format, the comparator methodology it names, and any confidentiality carve-outs that apply to shared data.
- Commercial lead identifies or engages the benchmarking body named in the contract, or confirms the selection process if no body is named.
- Legal team drafts the benchmark request notice and sends it through the contractual notice channel, keeping proof of delivery.
Who decides
| Question | Who resolves it | Typical timing |
|---|---|---|
| Whether the trigger conditions are met | Contract managers on both sides, by correspondence | Within the notice period set by the contract |
| Selection of the comparator group | The named benchmarking body, or a jointly agreed expert | Set by the clause; commonly weeks, not days |
| Whether the adjustment is accepted | Commercial leads, escalating to senior management if unresolved | Within the implementation window in the clause |
| Unresolved disputes over methodology | The dispute mechanism named in the contract | Runs on its own separate timeline |
Documents to prepare
| Document | Why it is needed | Who holds it |
|---|---|---|
| Current signed agreement and amendments | Confirms the exact clause wording in force | Legal team |
| Pricing schedule and invoice history | Baseline for the comparison | Finance |
| Service-level reports for the review period | Comparator data must match the same service scope | Service owner |
| Prior benchmark reports, if any exist | Shows the pattern of past adjustments | Contract owner |
| Confidentiality undertakings for the benchmarker | Required before sharing pricing data externally | Legal team |
If the underlying agreement includes tokenised or usage-based licensing rather than flat pricing, the benchmark exercise also needs to define what licence scope is being compared. Overstated or ambiguous licence claims complicate that comparison; see When a token claims to carry a licence.
If your situation differs
If the clause names no benchmarking body, the parties must agree one before the notice period expires — do not send the request assuming a default exists. If the other side disputes the comparator group after data has already been shared, confidentiality undertakings signed earlier still bind them; check the undertaking's scope before assuming it covers a dispute. If pricing history is incomplete because records were lost in a prior transition, say so in the notice itself rather than waiting for the benchmarker to raise the gap.
What this page does not cover
This page does not set out the substantive comparator methodology, since that is defined clause by clause and varies by contract. It does not resolve disputes over whether a specific market sample is representative — that sits with the named benchmarking body or dispute mechanism. Where a benchmarking dispute turns on the counterparty's own standing, a report can confirm what is establishable in a given jurisdiction: see Counterparty in Malta and its limits in practice. Where the dispute traces back to an unsigned assignment in the licence chain, a separate report addresses that specific gap: see Document report when an assignment is unsigned step by. Where comparator data includes personal information about named individuals, a separate question arises about who can be identified in that data: see If you are named in a report and who.
Verified
Reviewed by Rasa Tumenaite. This page describes contractual procedure only and cites no statute or regulation, in line with the procedural scope of this material. No external legal source applies to a clause-driven internal process; the steps above reflect standard contract administration practice for benchmarking mechanisms in technology and outsourcing agreements.
Related reading
A comparable documentation exercise applies to IP indemnity negotiations: see IP indemnity negotiation: documents to prepare.
FAQ
How long does a benchmarking exercise take in practice?
The contract sets the notice period, the comparator selection period, and the implementation window. Add them together for a realistic estimate; most exercises run several months from notice to adjustment, longer if a dispute mechanism is engaged.
Which documents are needed to start?
At minimum: the current signed agreement with amendments, pricing history for the review period, and service-level reports covering the same period. Without these, the benchmarking body has nothing to compare against.
What happens if the other side does not respond?
Check the notice period in the clause first. Most clauses set a deadline after which the requesting party can proceed with a default comparator group or escalate through the named dispute mechanism. Keep proof of delivery of the original notice — it is the evidence that the deadline has run.