How to Review Step-In Rights Triggers and Step-Out

Finance has said yes. Peak starts Monday. The warehouse-and-transport outsourcing MSA — a master services agreement the vendor hangs order forms on — has two sentences that let you step in if they “underperform,” and no way to hand the work back. Name the events, the access, who pays the extra cost, and how the rescue ends. Then keep, narrow, or walk.

On 4 September 2026, Theo — Ops at a 30-person UK logistics firm — has Finance’s yes on that packet — the exact file set that will be signed. Clause 19: if Supplier underperforms, Customer may step in; Supplier shall cooperate. No named SLA, insolvency, or security event, no notice, no emergency, no cure, no access list, no fee rule, no step-out. Sales: “standard continuity.” Typical mistake: treating the heading as a spare crew.

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

Which named triggers work — SLA miss, insolvency, security — not “underperformance”?

A step-in is a temporary continuity lever. It is not the exit-door comparison of convenience versus cause. Write events a third party can test: a critical SLA miss, a named insolvency procedure, a defined security incident. Strike “underperformance.” That adjective is a dispute while the warehouse is down.

The page that owns this job (ClearContract, 19 July 2026) is blunt: “poor performance” invites a fight at the worst moment. Workable triggers are objective — outage duration, a defined security category, financial-distress indicators. Theo’s two sentences fail on their face.

Do write three boxes. A critical SLA miss for a stated window — for example three failures in six months on a named service (Meyer colour, not a UK statute). Credit math lives on the SaaS SLA service-credits checklist. Vendor insolvency — Geldards : name the procedure. A security or safety emergency. Don’t keep “underperformance.” For-cause versus convenience as an exit is one sentence, then come back: termination for convenience versus for cause. This is not PRA “step-in risk.”

How do you write notice, an emergency exception, and a short cure?

Non-emergency step-in needs a written notice that names the trigger, the affected services, the start date, and any substitute operator. Give a short cure — practitioner colour is five to ten business days, not a second 30-day SLA. Emergency and insolvency skip that clock.

Do split the paths. Ordinary breach → Step-In Notice plus a short final chance. ContractKen colour uses five to ten business days; Mondaq / Logan uses about seven. Neither is a UK statute. Emergency — cyber, safety — → step in immediately, notice after. Insolvency: treat as immediate.

Don’t accept a 30-day consult lock as the only path. That burns peak. Invalid notice kills the rescue. In England and Wales counsel vague triggers invite a fight about whether step-in was valid.

What scope do you lock — systems, people, subcontractors, premises?

A right without access is theatre. Lock four lines for the affected slice only — not the vendor’s other customers. Add that you may perform the work yourself or through a substitute. Theo’s two sentences give him none of that.

Do write the four lines. Systems, data, runbooks, and credentials for the WMS or yard kit. People — key personnel cooperate; you may direct them on the affected services. Subcontractors — pre-agreed step-in terms. Premises — yard, floor, scanners. Plus yourself or a third party. The vendor may bar a competitor and demand an NDA — a non-disclosure agreement — (Tech Contracts).

Don’t count on a parachute into an offshore shared site. Morrison Foerster (structure-only) : steer the work to a substitute, override exclusivity, take remote access. A takeover that looks like a relevant transfer can pull TUPE in England and Wales — name it, then move on.

Who pays the extra cost, and do fees pause?

The High miss — an item scored high severity, so a human must verify it — is a monthly fee that keeps running while you also pay a 3PL substitute. You pay twice. Write who pays incremental step-in costs, and whether fees for the suspended slice pause.

Do three lines. Fees for the affected slice pause. The vendor reimburses reasonable incremental or excess costs. You may set off those sums. The Australian ClauseBank — official wording, not England-and-Wales statute — suspends the price for the ceased slice and lets the customer recover reasonable excess. TSA Advisory : do not pay twice.

Don’t leave the fee silent. Vendor default or insolvency → vendor pays incremental; no-fault emergency → negotiate. Silent fees plus incremental on you is a walk input.

How do you write step-out, max days, and convert to for-cause?

Theo’s paper has no step-out. Without an exit from the rescue he cannot hand the work back or convert a failed rescue into a for-cause exit. Write the handback, a max-day backstop, convert-to-for-cause, and a no-waiver sentence.

Do four lines. A Step-out or Withdrawal Notice when the trigger has ceased or the vendor shows it can resume — then a short transition-back. A maximum-day backstop — colour 60 to 180 days, or a window such as 90 then terminate the affected slice. If they cannot resume → convert to for-cause. Exercise does not waive terminate for cause.

Don’t accept silence, or step-in as the exclusive remedy. Those day-counts are not a UK statute. If the stack is still loose, use how to prepare a contract packet and return to Clause 19.

Checklist: keep, narrow, or walk

You are done when you can fill one page and point to one sentence that would pause signature. “We have a step-in” is not that sentence if the trigger is “underperformance” and there is no step-out. In practice: packet → not B31 convenience/cause → named triggers → notice / emergency / cure → scope + substitute → who pays → step-out / convert.

Keep named SLA / insolvency / security, emergency plus a short clock, four access items plus a substitute, fees pause plus vendor incremental on default, and step-out / max days / convert / no-waiver. Narrow the adjective, silent fees, or a 30-day consult lock. Walk when the trigger is an adjective and there is no step-out and fees keep running. Then counsel — a qualified lawyer, not a chatbot — reads every High sentence. A first-pass — the first machine pass that extracts clauses before a human reads every page — is not a green light.

After that log: upload the same MSA PDF to Checkory document analysis so flags land on that file. A human still opens every High gap.