Pilot Control

Know What Must Be Tested Before The Pilot Clock Runs Out

The Checkpoint Runboard tracks the pilot cycle on the horizontal axis and only mandatory tests, evidence, and reviews on the vertical — no general project tasks. Each checkpoint shows Expected Evidence, Current State, and Decision Impact. Near-deadline untested scenarios expand; low-value work shrinks.

Phase 1 · Week 1 On Track · Closed
Kickoff & Goal Brief signed
OwnerTeam Lead
  • Expected EvidenceSigned Goal Brief + starter Criterion Tags
  • Current StateComplete — both on file
  • Decision ImpactUnlocks Threshold Ladder approval
Phase 1 · Week 2 On Track · Closed
Baseline frozen, Lockers 01–03 populated
OwnerIT
  • Expected EvidenceFrozen Baseline + Product Telemetry / Workflow Result / Support Issue clips
  • Current StateComplete — baselines frozen, three lockers populated
  • Decision ImpactRequired before Observed Results can enter scoring
Phase 1 · Week 3 At Risk · Expanding
Stakeholder review + failure-scenario test
OwnerSecurity
  • Expected EvidenceMargin Testimony from all six roles · failure-scenario evidence in Support Issue locker
  • Current StateAt risk — Security review open; failure scenario still untested
  • Decision ImpactBlocks Publish Decision Brief and any Go recommendation
Phase 2 · Week 1 Not Started · Collapsed
Contradiction review & scoring model publish
OwnerProduct User
  • Expected EvidenceResolved contradiction desk + published scoring model version
  • Current StateNot started — waiting on Phase 1 · Week 3
  • Decision ImpactRequired for confidence-adjusted score on the Decision Brief

Phase 2 · Week 1 stays Not Started until the Phase 1 · Week 3 checkpoint clears Security review.

Update Pilot Plan

Saves new Checkpoints, Owners, and dates, then notifies every affected participant. Missing evidence for the final decision updates immediately.