The Continuity Ledger: Keeping OKRs Coherent Through a UK TUPE Transfer

TUPE transfers are usually discussed in legal and HR language: consultation, liability, pension continuity and the protection of terms and conditions. For managers, they are also an OKR problem. A team moves from one owner to another, often with a client contract attached, and its objectives arrive in fragments. Some belong to the seller's final quarter. Some are written into the buyer's integration plan. Others exist only in the client's service-level expectations. If no one reconciles them, the team begins its new life with an objective set that is duplicated, contradictory or simply obsolete.

The Transfer of Undertakings (Protection of Employment) Regulations 2006 provide the legal frame, but they do not supply a management method. That gap is where a continuity ledger helps. It is a simple record of every live objective, its source, its owner, its evidence and its likely fate. The ledger does not replace legal advice or formal consultation. It gives managers a disciplined way to decide what should travel with the team, what needs rewriting, and what should be closed before it causes confusion.

Why a transfer disturbs the objective set

An OKR set is a statement of priorities, not a contract. That distinction matters during a transfer. Employees may understandably treat inherited objectives as promises about the future. Managers should avoid implying that an objective will survive simply because it was written down. The continuity question is narrower: which objectives still describe work that the team will be paid to do, and which were tied to a previous owner's strategy?

Three pressures typically appear at once. The seller wants a clean exit and may prefer that old objectives disappear quietly. The buyer wants integration and may impose new objectives before it understands the inherited work. The client wants continuity and may read any change of objective as a change of service. A manager who tries to satisfy all three without a written method will usually create a fourth problem: an objective set that no one trusts.

A handover objective in three movements

For the transfer quarter, managers can adopt a single handover objective with three key results: preserve, translate and retire. The objective might read: Establish a coherent OKR set for the transferred team within 30 days of transfer. The key results should be measurable and modest.

• Preserve: review every live objective and classify it as retain, rewrite or close by day 10.
• Translate: rewrite each retained objective in the language of the new organisation, with a named owner and a visible evidence source, by day 20.
• Retire: formally close obsolete objectives, with a short written note explaining why, by day 30.

This is not a growth objective. It is a maintenance objective, and it should be treated as legitimate work. A team that spends its first month under new ownership pretending that nothing has changed will pay for that pretence later.

Preserve: what must travel unchanged

Preservation is not sentimentality. An objective should travel unchanged only when three conditions hold: the work continues, the evidence remains available, and the new owner accepts the commitment. A client service objective often meets these conditions. A seller's internal efficiency objective usually does not.

The continuity ledger should record the original wording, the source document, the current owner, the current confidence level and the evidence used to track progress. Where an objective depends on a system that will not transfer, preservation is unlikely to be honest. Where it depends on a client relationship that remains in place, preservation may be essential.

Translate: what needs new language

Translation is the most delicate step. A retained objective may need new wording to fit the buyer's strategy, but the underlying commitment should remain recognisable. Managers should avoid two errors. The first is cosmetic translation: changing the wording while leaving the same unowned work in place. The second is over-translation: rewriting an objective so thoroughly that the team no longer recognises what it was asked to preserve.

A useful test is to ask whether the translated objective can be explained in one sentence to the client and in one sentence to the new finance director. If those two sentences contradict each other, the objective is not ready. The ledger should show both the original and the translated version, so that the change is auditable rather than invisible.

Retire: what should not survive

Retirement is a form of respect. Objectives that were tied to a seller's internal programme, a discontinued product or a departed sponsor should be closed openly. A short retirement note should state the original objective, the reason for closure and any residual work that has been transferred elsewhere. This prevents the quiet accumulation of zombie objectives that everyone knows are dead but no one feels authorised to remove.

Retirement also protects the new owner. A buyer who inherits an unexamined objective set may find itself accountable for commitments it never agreed to. A written closure record is a practical control, not a bureaucratic flourish.

A pre-transfer checklist for managers

Before the transfer date, managers should assemble the continuity ledger and test it against five questions.

• Source: where did each objective originate, and is that source still valid?
• Owner: who is accountable after the transfer, and have they accepted the role?
• Evidence: what will be measured, and will the data be available under the new owner?
• Capacity: does the team have the hours and skills to pursue the retained objectives?
• Consultation: has the objective set been discussed with employee representatives in a way that separates legal questions from priority questions?

During due diligence, OKRs should be treated with caution as evidence. They are management instruments, not audited accounts. If they are unreliable before the transfer, they should not be presented as a stable baseline afterwards. Managers should also avoid creating shadow objectives during the diligence period. A parallel set of informal goals undermines the ledger and makes consultation less honest.

The thirty-day review

Thirty days after transfer, the new manager should convene a short review with the transferee manager, the team lead and the client account lead where relevant. The review should examine the ledger, not the original slide deck. Five tests are enough: ownership, evidence, capacity, language and closure.

Ownership asks whether every retained objective has a named owner who has accepted it. Evidence asks whether the tracking method survived the transfer. Capacity asks whether the team is attempting more than it can deliver. Language asks whether the new wording is understood by both the team and the new sponsor. Closure asks whether retired objectives have been properly recorded.

The review should produce one output: a revised objective set for the next quarter, with no more than two or three objectives. A transfer is not a fresh start, but it is a legitimate moment to simplify. Teams that use the handover to preserve too much will begin their new ownership overloaded. Teams that retire too aggressively may lose the client confidence they need. The continuity ledger is the instrument that keeps both risks visible.

This article is not legal advice. TUPE obligations are specific and should be handled with qualified HR and legal support. The management case is simpler: objectives should travel with purpose, not by accident.