Hybrid operations with staged handover
Hybrid operations place an experienced contractor in the seat at launch, then transfer authority to national operators through structured milestones. Done properly, handover is a technical event with pass/fail criteria, not a ceremony.
Why the first six months are not the right time to learn
A newly launched satellite is at its most demanding precisely when a new operations team is least experienced. The first weeks after separation involve initial acquisition, commissioning of every subsystem, propulsion burns for orbit raising or station-keeping, and the first payload calibration passes. Anomalies in this window are common, consequential and fast-moving. Placing an untrained national team in primary command authority at this moment is not a sovereignty statement; it is a risk transfer with no compensating benefit.
Hybrid operations resolve this by separating two things that are often conflated: operational authority and operational learning. The contractor holds authority and carries accountability during the highest-risk phases. The national team is present, active and accumulating hours from day one, but is not yet responsible for the spacecraft's health. Authority transfers in stages, each triggered by demonstrated competence rather than a calendar date. The distinction matters because it changes the incentive structure on both sides.
Milestone design: what a real handover gate looks like
A handover gate is a set of pass/fail criteria agreed before launch, not negotiated under time pressure after it. Typical gates are organised in three tiers. The first covers individual competencies: each national operator must demonstrate, on the actual flight system or a high-fidelity simulator, that they can execute nominal procedures, respond to defined off-nominal conditions and correctly escalate anomalies outside their authority. The second covers team competencies: the national team must complete a shadow operations period of defined duration, typically 90 to 180 days depending on mission complexity, during which they execute all procedures while the contractor observes and can intervene. The third covers organisational readiness: on-call rotas are staffed, escalation contacts are in place, and the operations data package including all procedures, contact schedules and anomaly histories is formally handed over and acknowledged.
The shadow period deserves particular attention. Shadow operations are not observation; the national operator executes every command, the contractor's hand is on a separate keyboard with override authority only. This distinction is psychologically and practically important. Operators who have spent months executing commands, even under supervision, have genuine muscle memory and situational awareness. Operators who have spent months watching do not. Programmes that skip or shorten shadow periods to reduce contractor costs consistently report longer post-handover anomaly recovery times.
The authority matrix and its evolution
At any point in a hybrid programme, every class of spacecraft command sits in one of three authority columns: contractor-only, joint (national executes, contractor concurs), or national-only. The authority matrix is a live document. It starts heavily weighted to the contractor column and migrates toward the national column as gates are passed. Routine contact scheduling and payload tasking typically migrate first. Propulsion authority and anomaly recovery authority migrate last.
Publishing the matrix at contract signature, with the migration schedule attached, does two things. It gives the national team a concrete progression to work toward, which sustains motivation across what can be a long programme. It also gives programme managers an objective measure of progress that does not depend on the contractor's self-assessment. A matrix that has not moved in six months is a programme management signal, not a technical one.
Where hybrid handover fails, and why
The most common failure mode is not technical. It is that the contractor has no commercial incentive to complete handover quickly, and the national team has no political incentive to accept accountability before they feel ready. Both pressures push in the same direction: extension. Contracts that do not include a defined end date for contractor primary authority, with financial consequences for overrun, routinely run long.
A second failure mode is documentation debt. Operators learn procedures by doing them, and informal knowledge accumulates in the contractor team that never makes it into the written operations data package. When handover finally occurs, the national team discovers that the procedures manual describes what the spacecraft is supposed to do, not what it actually does after eighteen months of on-orbit calibration drift and workarounds. Requiring the operations data package to be updated on a rolling quarterly basis, and audited by the national team, catches this early.
A third, less discussed failure is staffing continuity on the national side. Trained operators are attractive to other employers. A programme that trains twelve operators over two years and then loses four of them before handover is complete has a genuine capability gap. Retention planning is an operations architecture question, not an HR afterthought.
What sovereignty actually requires at handover completion
Handover is complete when the national team can operate the spacecraft through a full anomaly cycle without contractor assistance. That means detecting the anomaly in telemetry, correctly diagnosing it against the anomaly catalogue, executing the recovery procedure, and deciding independently whether to resume normal operations or escalate to the spacecraft manufacturer. Each of these steps requires different knowledge, and each should be tested explicitly before the contractor's primary authority is formally retired.
Post-handover, a residual contractor relationship is normal and sensible. Most programmes retain a defined technical support agreement covering anomalies outside the national team's experience envelope and major manoeuvre planning. The difference between this and hybrid operations is that the national team is now the customer requesting support, not the student receiving instruction. That inversion is the practical definition of sovereign operations capability.
Engineering parameters
| Shadow operations duration (typical) | 90 to 180 days for LEO Earth-observation missions; longer for GEO or multi-payload configurations |
| Minimum national operator cadre at handover | Generally 6 to 12 trained operators to sustain 24/7 on-call coverage with leave and attrition margin |
| Authority matrix migration checkpoints | Typically 4 to 8 formal gates across the hybrid period, each with documented pass/fail criteria |
| Operations data package update cadence | Quarterly updates recommended during hybrid period; full audit at each handover gate |
| Residual technical support agreement (post-handover) | Commonly 12 to 36 months; scope limited to out-of-envelope anomalies and major manoeuvre planning |
| Contractor primary authority end date | Must be contractually fixed before launch; open-ended arrangements consistently overrun |
| Simulator fidelity required for competency gates | High-fidelity hardware-in-the-loop or software-in-the-loop simulator tied to actual flight software build |
| Anomaly recovery test scope at final gate | National team must demonstrate unaided recovery from a defined set of representative fault scenarios |
One contract, one accountable engineer
Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Review our handover milestone framework.