Sovereign Records-Platform Separation Authority — Public Benefits

The mandate

A strategic technology provider invoked its exit clause after commercial renegotiation failed, creating a fixed fifteen-month window to move citizen records, processing history and operational controls into government-approved environments. Core services continue under transition terms, but encryption keys, metadata operations, support knowledge and several derived indexes remain provider-dependent. No existing executive has authority across legal exit, platform separation and benefit-cycle continuity.

The interim must begin in Delhi NCR within four weeks for the full fifteen months, from exit baseline through migration, service cutover and successor induction. A permanent search begins in month eight once the sovereign operating model is demonstrably viable. Eight weeks of overlap are reserved; the assignment cannot extend beyond the contractual exit, and an internal accountable officer will assume control if recruitment slips.

Handover requires all authorised records, audit histories, indexes, metadata and recovery copies to operate under client-controlled identity, keys, monitoring and support; the provider must lose privileged access without service interruption; and two benefit cycles plus a regional recovery exercise must reconcile. The successor will chair final exit certification and accept residual archive, legal-hold and decommission obligations.

The interim may stop migration waves, set evidence thresholds, direct the sanctioned ₹420 crore separation, approve temporary specialists and enforce contracted exit assistance. Changes to benefit policy, citizen-facing remedy, permanent appointments, destruction of held records and expenditure above budget require the chief executive or council. The authority cannot determine individual eligibility or waive government security and records requirements.

Benefit-policy redesign, replacement of departmental casework and broad cloud modernisation outside the exiting provider’s perimeter are outside this assignment. The leader may demand safe interfaces but does not own national identity policy, physical service centres or cleansing historic records without legal, operational or migration necessity. Scope discipline protects the non-negotiable exit and continuity dates.

Why this seat is open

The provider exit created an immediate, time-bound executive gap that ordinary programme governance cannot fill. Technology teams understand migration, records officers understand custody and public-service leaders understand benefit cycles, but none can arbitrate all three with independent signing authority. A temporary leader must remove provider dependence and leave permanent public-platform control after witnessed service continuity.

What you will own

• Establish an exit ledger covering records, derived assets, code, identity, keys, monitoring, licences, knowledge, recovery copies and contractual evidence.
• Decide migration waves using citizen consequence, benefit calendar, retention, recoverability, technical coupling and provider-dependency risk.
• Define sovereign control for identity, encryption, administration, provenance, audit, support and incident response across every target environment.
• Direct full-volume rehearsals covering in-flight cases, payment-cycle updates, corrections, legal holds, regional failure and rollback to safe service.
• Verify provider knowledge and privilege removal through observed client operation, credential revocation, residual-access testing and contractual attestation.
• Govern the ₹420 crore programme against retired dependency, reconciled records, continuity evidence and durable internal operating capability.
• Induct the successor through two benefit cycles, a regional recovery exercise and signed acceptance of archive and decommission debt.

Candidate qualifications

• Held executive authority for a sovereign, regulated or public-sector platform separation involving sensitive citizen or customer records.
• Completed provider exit across data, metadata, keys, privileged access, operating knowledge and recovery without interrupting essential service.
• Governed record retention, legal holds, audit history and derived indexes through migration into client-controlled environments.
• Directed full-volume cutover and rollback around financially consequential public or regulated processing cycles.
• Managed technology vendors and government stakeholders while keeping policy, security and individual-case authority correctly separated.
• Handed permanent leadership demonstrable operating control after revoking the former provider’s access and support dependence.

Non-negotiables

• Available within four weeks for an exclusive Delhi NCR assignment with travel to approved sovereign data-centre regions.
• Has personally signed provider-exit or platform-separation gates for sensitive records; generic cloud migration does not qualify.
• No undisclosed commercial, investment or advisory relationship with the exiting provider, replacement bidders or assurance firms.
• Will preserve service, legal-hold and citizen-evidence obligations even if doing so complicates the contractual exit timetable.

1. 49 words maximum. State your Delhi NCR availability and one provider exit where privileged access was demonstrably revoked without service loss.
2. 49 words maximum. Which derived records and operating dependencies are most often missed in a sovereign platform separation inventory?
3. 49 words maximum. What evidence would you require before final exit certification across a live public-benefit cycle?