I used to love a co-termination clause. It was sold to the customer as administrative tidiness, and it was, but it also pulled every line onto a single date I controlled, removed their ability to shop each module on its own clock, and gave me one big renewal to anchor high. Anniversary-date clauses did the same for uplifts: they made sure the increase landed on my calendar, not theirs. This is part of our ITSM contract clause library of 40 terms every buyer should know.
What is a co-termination clause and how does it work?
Co-termination aligns the end dates of everything you buy to a single master contract end date. Add a module in month seven of a three-year deal, and instead of getting its own term, it co-terminates to the master date, so you pay a short stub period and then it folds into the next full renewal. On paper it simplifies billing. In practice it consolidates every line into one renewal event the vendor can anchor against.
The cost shows up in two places. First, mid-term additions often get priced at a fresh rate for the stub rather than your existing discounted rate, so you pay more per seat for the months until alignment. Second, you lose the ability to renegotiate each component on its own timeline, which is one of the few structural levers a buyer has against a large vendor.
What is an anniversary-date clause?
An anniversary-date clause fixes a single annual date on which things happen: the uplift applies, the user count is trued-up, the additional licences are billed. The vendor frames it as predictability, and for the vendor it is. The increase and the measurement land on a known date, on the vendor's revenue calendar.
The buyer risk is timing. If your true-up is measured on a fixed anniversary that falls just after a hiring wave or a project ramp, you are measured at your peak and billed accordingly. The clause does not change the rate, it changes when the meter reads, and when the meter reads can be worth real money.
Where do these clauses cost buyers the most?
| Clause | Vendor benefit | Buyer cost if unprotected |
|---|---|---|
| Co-termination | One renewal event to anchor, consolidated leverage | Stub periods at non-discounted rates, loss of per-line timing |
| Anniversary-date true-up | Measurement on the vendor calendar | Counted at peak usage just after a ramp |
| Anniversary-date uplift | Predictable annual increase | Uplift compounds on a date you did not choose |
| Combined | Everything renews and increases together | A single large event where the vendor holds the clock |
What should you negotiate on these clauses?
- Pro-rata at your existing rate. Insist that mid-term additions co-terminate at your current discounted per-unit price, not a fresh stub rate. This removes the penalty for growing during the term.
- Protect the uplift cap. Make clear that co-termination does not reset or re-baseline your annual uplift cap. The cap should survive the alignment. The mechanics are in our guide to price-hold and rate-card clauses in ITSM contracts.
- Choose the anniversary date. Set the true-up and uplift date to your low point in the year, not the vendor default. Measure when usage is lowest, not after a ramp.
- No silent term extension. Confirm that co-terminating an add-on does not extend your overall commitment without a matching concession in price or terms.
- Keep an exit on each material line. Where a module is large enough to matter, preserve a right to drop or re-scope it at the master renewal rather than carrying it by default.
Get these right and co-termination genuinely is tidy, on your terms. Get them wrong and it is a consolidation of the vendor's leverage dressed as a convenience. Across our engagements the firm averages a 30% reduction, and protecting the timing clauses is part of making sure that reduction does not erode at the next renewal.
Our gated ITSM Contract Terms and True Forward Guide covers co-termination, anniversary dates and the uplift mechanics that decide your year-two price.
Book a contract negotiation review.
We read the timing clauses for the leverage they move and rewrite them so the clock stays on your side. Fixed fee or gainshare, no savings no fee.
Book a contract negotiation review →What to do next
Before you sign or renew, find the co-termination and anniversary-date language and ask one question of each: does this move the clock toward me or the vendor? Then negotiate pro-rata pricing, a protected uplift cap, and a true-up date set to your low point. A sibling term worth reading alongside this is our renewal-notice and non-renewal-window clauses guide, because the dates interact. When you want the contract read line by line, the engagement goes through our contract negotiation service on fixed fee or gainshare.
Frequently asked questions
- What is a co-termination clause in an ITSM contract?
- It aligns the end dates of add-ons and expansions to one master contract date so everything renews together. It simplifies billing but consolidates the vendor's leverage and can price mid-term additions at a stub rate.
- What is an anniversary-date clause?
- It fixes a single annual date on which uplifts apply and true-ups are measured. The risk is being measured at peak usage on the vendor calendar rather than yours.
- Should I agree to co-termination?
- Only with protections: pro-rata pricing at your existing rate, a protected uplift cap, a true-up date set to your low point, and no silent term extension.