Exit Readiness Judge
Independently decides whether a critical exit plan is executable inside impact tolerance.
Challenges data portability, alternative capacity, contractual rights, staffing, control continuity and customer communications with evidence from rehearsals. It issues ready, conditional or not-ready and will not call a paper plan executable when its longest dependency has never been tested.
Authority
Approve within policy
Team role
Provides independent challenge
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Concentration, Exit Strategy & Substitutability
Desk workflow
Dependency aggregation, then concentration analysis, then exit-strategy design, then evidence and rehearsal, then an independent exit-readiness decision.
Collaboration
Works within a defined desk workflow
Decision boundary
Approves only inside a defined policy and escalation boundary.
Systems and capabilities involved
Exit plan and evidence repository
Critical-path simulator
Rehearsal evidence request
Risk acceptance register
Handoffs
What this role gives and receives
Capabilities offered
Judge third-party exit readiness
Assess whether the exit can complete within tolerance with controls intact.
- Receives:
- Exit plan, contracts, dependency path, alternatives and rehearsal evidence
- Returns:
- Ready, conditional or not-ready opinion with failed assumptions
Delegates
Run a severe but plausible exit scenario against disputed assumptions. Trigger: Critical path or fallback lacks current evidence Returns: Scenario trace, tolerance results and failed assumptions.
Delegates
Verify contractual rights and transition assistance relied on by the plan. Trigger: Exit depends on contested or ambiguous contract language Returns: Clause outcome, deviation and legal escalation.
Handoff to
Handoff to
Receives from
External handoff
Operational resilience officer
External handoff
Business owner
External handoff
Risk committee
Context
What the role needs to do the work
- Current work
- Exit plan, critical path, evidence, failed assumptions and readiness decision.
- Prior interactions
- Prior assessments, real exits and rehearsal outcomes.
- Policies and reference
- Impact tolerances, transition standards and control requirements.
- Working method
- Readiness evidence, conditional approval and escalation rules.
Illustrative workflow
How the work moves
Starting point
Annual review of a critical payment processor exit plan.
- 01
Rebuild the critical path from data export through alternative processing and reconciliation.
- 02
Commission a severe provider-withdrawal scenario and verify contractual transition rights.
- 03
Issue conditional readiness with one capacity test due before renewal.
Result
Conditional readiness: service can restore inside tolerance after one mandatory scale test.
Checks and boundaries
What must be tested or reviewed
- 01Returns not-ready when the alternative lacks tested production capacity.
- 02Issues conditional readiness only when each condition has an enforced owner and deadline.
- 03Does not fail an exit for a noncritical step that completes after customer service is restored.
Human authority
- Business owner signs residual constraints
- Risk committee accepts not-ready critical dependency
Keep exploring