The contract ends in months. The team that built the platform is leaving, and the organisation that inherits it is being assembled while the work continues. On paper the transition is under control: segments are scoped, sessions are scheduled, documents are being written.
In reality, the knowledge that operates the platform still lives with the people who are walking out of the door.
A transfer plan reports its own completeness, not the receiving team's capability. Documentation counts pages, not understanding. And the dependencies that matter most, the ones concentrated in one critical service or two irreplaceable engineers, rarely appear in a status report at all.
Handover risk is quiet. It becomes loud on the first night the departed team is no longer there to answer.
- Transfer readiness as evidence, not intent: which segments are actually executing, and which exist only as scope.
- Dependency concentration made explicit: which services and which people carry a disproportionate share of operational knowledge.
- Alternative routes and recovery capability held to proof. What has not been demonstrated stays visibly unproved instead of silently assumed.
Operability: whether the platform can be run and recovered without its current custodians.
Whether transition activity is becoming receiving-team capability, segment by segment.
What the unresolved dependency means for the commitment, in consequence language rather than topology.
The transition stops being defended with schedules and starts being defended with evidence. Where independence is demonstrated, the position says so. Where it is not, the gap is named while there is still time to act on it.
Know whether the receiving organisation can actually operate what it inherits.
Desired outcomeWhat this position looks like on paper: the Project Blue Executive Decision Brief →