How to Review Exit Assistance and Transition-Services Rates

Kit, Ops at an 18-person UK SaaS, is about to treat “reasonable assistance to transition to a successor” as an exit plan because Finance said they have to help. Knowing how to review exit assistance and transition-services rates is a 25-minute hunt: people and runbooks, not a zip; days after any termination including for cause; a rate card signed now; a no-withhold sentence; named knowledge transfer and successor access; then days, rate cap, or walk.

September 2026. English law; exclusive courts of England and Wales. The MSA — master services agreement, the frame vendors hang order forms on — clause 14.4: “Provider shall provide reasonable assistance to transition to a successor.” No days. No cause survival. No exhibit — attached rate schedule — of exit day rates. Clause 8.3 suspends termination assistance until disputed and undisputed fees are paid. Successor booked Friday. The rush is the problem.

Hunton (11 August 2026) names the disease: generic reasonable-assistance language provides little protection, because by exit you depend on their people and know-how. Tech Contracts (7 January 2026) publishes the provider-friendly draft almost as Kit’s paper — then-standard policies, not in breach, pre-pay standard fees. In practice, Friday is when that pressure is costly.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Which help is people and runbooks, not only a file dump?

A zip is not a runbook, named hours, or a person who will sit with the successor. Circle “reasonable assistance.” Demand hours per week, a runbook of configurations and integrations, knowledge-transfer sessions, and a named contact. Kit’s 14.4 names none of those.

Freeze the packet — MSA, order form, professional-services schedule, and DPA (data processing agreement) dated today. Open 14.4 and the fees block. If the fight is the file dump or export window, that is a different hunt (SaaS data-export exit rights); stay here for people, runbooks, and day rates. Membersimple (20 February 2026): data alone is not enough. Their sample — 90 days, 40 hours per week, four 60-minute sessions — is an ask, not statute. Typical mistake: treating the export as the exit. Do: name the hours.

What does a day count after any termination, including for cause, require?

Write a number of days that starts on termination or on notice, and that applies on expiry, convenience, and cause — including if they terminate. Kit’s paper has no days — fail. Do not treat “assistance” as a calendar. Log the blank before Friday.

Bindlegal (16 June 2026) balanced sample: on any termination, up to ninety (90) days, at rates in that exhibit. That 90 is drafting colour, not a statute. CCS Call-Off Schedule 10 (Crown 2025) allows Termination Assistance up to twelve (12) months after the End Date — public-sector colour, not Kit’s default. Papers that drop help if they terminate you for non-pay are the Friday trap. If the fight is convenience versus cause as a walk-right, that is a different hunt: termination for convenience versus cause. Stay here for whether assistance survives cause.

Why does then-standard pricing fail as a rate card?

Then-standard and then-current fees are priced when leverage is gone. Demand named day or hour rates in this agreement or an exhibit, or a capped estimate. Circle then-standard, then-current, time-and-materials at exit, and subject to availability. Kit has no card — fail.

Hunton: price exit services up front; if left to future agreement, costs escalate. The hidden cost is then-current pricing at exit. ABA (November 2021) still lists a rate card for transition assistance fees as a customer ask. CCS charges from Framework Prices with a capped estimate. For example, Bindlegal flags “if any” at then-current rates as the aggressive close. Do: put the card on the paper now. Don’t: wait until Friday “to be fair.”

When to treat a fee fight as a freeze of the handover?

Treat a fee fight as a freeze when the paper lets them suspend termination assistance until disputed and undisputed fees are paid. Kit’s 8.3 = withhold — fail. Require help to continue; withhold only against an advance for this assistance after written notice of a described breach.

Tracking Contracts (25 March 2026): the supplier shall not make transition cooperation conditional on disputed invoices. Tech Contracts’ customer-friendly sample: they may not refuse or delay, including for customer breach; withhold only against an advance for this assistance after written notice. Do: strike 8.3’s freeze. Pause Friday if 8.3 stays.

How do you lock knowledge transfer and successor access?

Name the incumbent’s duty to cooperate with the successor under a reasonable NDA (non-disclosure agreement), deliver the runbook, and make named people available for stated hours. Kit’s Friday booking without this block is a smile and a zip. Do not assume they can just read the docs.

Morgan Lewis (25 February 2026): successor cooperation must be express, not aspirational. CCS colour: an Exit Plan within three (3) months of start, including training of Replacement Supplier staff, plus access for the buyer and/or successor. Do: write hours, runbook, successor under NDA. Don’t: book Friday on a vibe.

How do you choose days, a rate cap, or a walk?

Keep days only if the log shows a number that survives cause, a signed rate card or cap, a no-withhold sentence, and named knowledge transfer plus successor access. Rate cap means redline those four before Friday. Walk — do not sign Friday — if “reasonable assistance” plus no days plus no rate card plus withhold-until-fee-fight remain as a package.

Success bar: a one-page log plus one sentence that would pause Friday. Kit has three: no days; no rate card; 8.3 withhold. Workflow: people+runbooks vs dump → days including cause → rate card now → no withhold → KT + successor → days / rate cap / walk. Spend counsel — the England-and-Wales solicitor who opens 14.4 and 8.3 — on that package. Escalate the AE’s “we’ll be reasonable” line. Optional: upload the same PDF to document analysis for a first-pass — a machine extract of clauses before a human reads every page — then open 14.4 and 8.3.