# AI Project Status Presentation: Show the Decision

A status deck should let a stakeholder decide what happens next without reading the entire project log. Build it from dated evidence and a small number of meaningful milestones. Use AI to organize the narrative, then check that the deck has not converted uncertain progress into confident completion.

## Your brief

1. Provide milestone names, planned dates, actual status and evidence links. Keep source completion, review, deployment and acceptance separate where they differ.

   ____________________

2. List current risks, unresolved dependencies and decisions with owners. Include a date for the snapshot so the deck is not mistaken for a live dashboard.

   ____________________

3. State who will attend and what decision is needed. Limit background detail to what changes that decision; keep a supporting appendix available.

   ____________________

## Prompt

Create a six-slide project status deck from [dated project facts]. Include objective, milestone table, delivered evidence, blockers, options and decisions needed. Preserve supplied status words and dates. Do not invent a percentage complete or hide overdue items. Put assumptions in notes. End each decision with an owner and requested response date, marking missing owners unknown.

## Illustrative example

Illustrative project: the new page is implemented, accessibility review is pending and production deployment awaits account access. The milestone slide shows three distinct states. A decision slide asks the account owner to provide approved access or move the launch date. The deck does not turn an implementation screenshot into proof that users can use the live service.

## Acceptance checks

- [ ] Do status labels and dates match the source facts, including delayed or unverified items?
- [ ] Does each risk or decision have an owner and a next action, without invented estimates?
- [ ] Can the exported milestone table be read on a small screen and in the meeting’s target language?

Avoid a decorative progress percentage calculated from the number of tasks. Five small completed items do not prove that half of a project is complete when the remaining dependency may determine the entire launch.

---

Brainbaby · https://brainbaby.ai/blog/ai-project-status-presentation

CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/