MS
Maya Program manager
If we keep every report in phase one, we miss the October 1 contract date.
Project Status & Recovery
Talk through what is true. Leave with a credible recovery path.
Evidence-based status, variance, hard tradeoffs, and recovery commitments replace optimistic reporting and vague escalation.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
Current status + contract date Tradeoff exposed
Scope or date must change Recovery tradeoff Full scope conflicts with October 1
AL
Ari Program sponsor
“Move custom reports to phase two. Noah owns the recovery plan tomorrow.”
Recovery path Confirmed by Ari ✓
Recovery plan ✓
Recovery path Recovery action Publish revised delivery plan Noah · Tomorrow
Deferred scope Custom reports Phase two
Current status + contract date→Confirmed by Ari
How the template helps
A status review that produces a decision, not a color.
The team establishes facts before diagnosing variance and choosing a recovery option.
What the team leaves with
A recovery plan with accepted tradeoffs.
Current evidence, the selected path, deferred scope, owners, risks, and checkpoints stay connected.
Run a project recovery sessionEnterprise rollout Recovery record
Path confirmedConfirmed outcome Protect October 1 by moving custom reports to phase two
Contract date retained · phase-one scope reduced · daily checkpoint
Recovery action Confirmed
Publish revised delivery plan Noah · Tomorrow
Linked to the scope decisionDeferred scope Reviewed
Custom reports Phase two
Decision rationale attached