A transition assistance clause commits a supplier to help move service responsibility to a recipient, or to close it down in a controlled way. Its value is decided at drafting, because it is invoked at the moment cooperation is least reliable.
What the clause has to name
A federal continuity-of-services model shows the shape: transition training, cooperation obligations, an approved responsibility-transfer plan, a post-expiry service period contingent on written notice, and a cost provision covering reasonable transition costs and a bounded fee.
The generalisable content is a schedule naming, for each deliverable, the accountable parties, the release authority, the access dependency, the assistance commitment and its rate, the completion evidence, and the dispute route.
That schedule has to be maintained during operation. An exit request that begins with an unknown inventory has already failed, because the first weeks go to discovering what exists rather than moving it.
Delivery is not transfer
The characteristic failure is a supplier delivering the repository on time while the recipient cannot deploy, because a required account remains inaccessible.
Nothing was breached. The deliverable was delivered. The access dependency was simply never anyone’s obligation, and it is the kind of item that lives outside the artifact list — a cloud tenancy, a registry credential, a third-party consent, an API subscription in the supplier’s name.
So the schedule records access dependencies as first-class items with a named party able to resolve each one, and the acceptance test is a rehearsal: the recipient performs the permitted activities using the agreed artifacts and support, and unresolved third-party permissions are recorded separately. What remains, and who funds it, gets written down while the supplier is still engaged.
Termination for convenience is priced
Ending work without alleging breach requires that the applicable arrangement grants the route. No general private-contract right exists, and the federal fixed-price model is an example rather than a default.
That model permits whole or partial termination through a notice specifying scope and date, distinguishes stopping specified work from completing work that continues, and directs preservation and delivery of defined property and information.
The settlement provisions are the substance. They address completed work, incurred costs, subcontract settlements, deductions, and non-duplication, and the unilateral calculation includes a loss adjustment where the contract as a whole would have lost money. A convenience exit is a route to stop, not a route to stop for nothing.
The practical stop plan identifies the authority and notice requirements, freezes new commitments only as far as directed, identifies services that must continue, inventories completed and in-progress work with subcontract commitments and prepaid amounts, and reconciles delivery, retention, and deletion against the applicable rights. Payable items and substantiated entitlements are different categories, and the same work must not be counted as both an earned fee and a settlement cost.
People are not deliverables
Personnel arrangements are where transfer plans contradict themselves, because staff have rights and preferences that the artifact list does not.
Four things get conflated and are separate: restrictions on recruitment, voluntary hiring, statutory employment transfer, and knowledge transfer through training and documentation.
Canadian competition law addresses certain wage-fixing and reciprocal no-solicitation or no-hire agreements between unaffiliated employers, with a conditional ancillary-restraints defence that requires a broader agreement between the same parties, a restraint directly related and reasonably necessary to it, and a broader agreement that does not itself contravene the provision. Those conditions are cumulative.
UK guidance identifies business transfers and service-provision changes as possible protected transfers carrying continuity of employment, while stating exclusions — so a contractor change is a question rather than an answer.
And the federal continuity clause conditions release of selected employees on those employees agreeing to the change and on a mutually agreeable date, with earned benefits negotiated.
An agreement that promises unrestricted recruitment of the supplier’s project team alongside a broad reciprocal no-hire restriction has committed to two incompatible things. The review surfaces the contradiction, obtains the applicable legal analysis, and asks the employees. A training fallback is evaluated on its own evidence rather than presumed to replace expertise that walks out.
The rule
What stays fixed is that exit obligations have to be executable when cooperation has deteriorated. What changes is which dependency binds — rights, accounts, people, or money — and the schedule exists to make each one visible before it is urgent.
Not to be confused with
An escrow promise. A deposit is not demonstrated continuity, and neither is source delivery.
A universal entitlement. The federal clauses are drafting sources with their own notice, fee, and duration conditions. Whether an equivalent right exists in a given contract is a question about that contract.