Benchmarking clause: stages and deadlines
A benchmarking clause lets one party compare price or service levels against a market sample and demand an adjustment. The clause runs on its own timetable, separate from renewal or termination notices. Miss a step and the right usually lapses until the next contractual window. Below is the sequence most technology and outsourcing agreements follow, the documents each stage needs, and where the process can quietly close.
Basis: the clause, not a statute
A benchmarking right comes from the contract itself. It is not a statutory entitlement, so there is no external law to check for a deadline or a formula. Everything — the trigger, the comparator pool, the adjustment formula — sits in the clause as drafted. Read that clause first. Any general description, including this one, is secondary to its exact wording.
Practical consequence
Two consequences follow from this contractual nature. First, the deadlines are whatever the parties wrote, and courts rarely extend them by implication. Second, silence in the clause is filled by whatever general contract-interpretation rules apply to the agreement, not by a benchmarking-specific rule. That makes the drafting quality of the clause the single biggest factor in how the process actually runs.
| Stage | What happens | Typical window | Who acts |
|---|---|---|---|
| Trigger notice | The party invoking the clause sends written notice naming the intended benchmark date | Set out in the clause, often tied to an anniversary | Requesting party |
| Benchmarker selection | Parties agree an independent benchmarker or use one named in the contract | Shortly after the notice | Both parties, jointly |
| Data submission | Pricing, volumes and service data are handed to the benchmarker | A fixed number of days from selection | Supplier, sometimes both sides |
| Comparison report | The benchmarker issues a report comparing terms against the market sample | A fixed period from the data being complete | Independent benchmarker |
| Negotiation window | Parties negotiate an adjustment based on the report's findings | A short, defined period after the report | Both parties |
| Escalation | An unresolved gap moves to named senior contacts or an escalation forum | As set in the escalation clause | Named escalation contacts |
| Lapse | The right closes for the cycle if a step is missed | End of the contractual window | Automatic, under the clause wording |
What to do
- Locate the clause and read the trigger wording exactly as drafted. Do this before any conversation with the other side.
- Calendar every deadline in the sequence, not just the first one. A missed second-stage deadline is as final as a missed first one.
- Assign one named owner on your side. Benchmarking exercises that drift between departments miss windows.
- Confirm the comparator pool and methodology with the other side in writing before data goes out.
- Keep a dated record of every notice sent and received. This record is what settles a later dispute about timing.
- If a step depends on the other side's cooperation, send a written reminder before the deadline, not after.
Who decides
The benchmarker decides the comparison, not the adjustment. The adjustment itself is a negotiation between the parties, guided by the report but not dictated by it. If negotiation fails, the contract's escalation clause names the forum — often senior management from both sides, sometimes a named mediator. Only if the contract provides for it does the matter move to formal dispute resolution. Absent that provision, an unresolved benchmark simply expires for the cycle.
Where this splits
If the clause names a specific benchmarker and that benchmarker is unavailable, check the fallback wording before assuming the process stalls. Many clauses name a backup mechanism.
If the underlying platform also touches tokenised assets, a parallel deadline logic can apply to custody obligations, and the trigger points do not always align. See Custody expectations in tokenised rights and the deadline for how that separate clock runs.
If the other side is silent through the negotiation window rather than actively refusing, most clauses treat that as a failure to agree, triggering escalation rather than automatic acceptance of the requesting party's proposed adjustment.
Limit
This page describes the sequence a benchmarking clause typically follows. It does not draft or interpret a specific clause, and it does not calculate what a fair adjustment should be — that depends on the market sample and the contract's own formula. Two related situations sit outside its scope but inside our reports.
If the counterparty's legal identity changes mid-cycle, the notice obligations can shift. See Counterparty report when the counterparty changes name who decides.
If a related assignment document is left unsigned when the benchmarking window closes, a separate deadline logic applies. See Document report when an assignment is unsigned explained.
Verified
This description reflects how benchmarking clauses are typically structured and administered in technology and outsourcing agreements, checked against contract-management practice rather than any single statute. It is not a substitute for the exact clause in your agreement. Working with this team in detail is described separately: Working with this team in detail.
Related
The same stage-and-deadline structure recurs in other negotiated clauses. See IP indemnity negotiation: stages and deadlines for a comparable sequence in indemnity terms.
FAQ
How long does benchmarking clause take in practice?
Most cycles run three to six months from the trigger notice to a settled adjustment, longer if escalation is needed. The exact figure depends entirely on the deadlines written into your clause.
Which documents are needed to start?
The clause text itself, current pricing and volume data, and the trigger notice. Keep dated copies of all three from the outset.
What happens if the other side does not respond?
Silence through a deadline is usually treated as a failure to agree at that stage, not as acceptance. Check whether the clause moves silent non-response straight to escalation or lets the window lapse.
Need this reviewed against a live subprocessor change instead? See When personal data flows to a new subprocessor and what it costs to get wrong.