Project Managers

Turn raw progress notes into a status-led update with a clear decision-needed flag.

Condense a detailed status into exactly 3 sentences that never hide a risk.

State a project risk plainly with mitigation trade-offs and one clear recommendation.

Escalate a blocker with a specific ask and deadline stated up front.

Turn stakeholder conversation notes into scoped must-haves and nice-to-haves.

Document a scope change with impact and required approval, even if impact is unconfirmed.

Structure retro notes into what went well, what to fix, and top takeaways.

Turn a retrospective into forward-looking, actionable guidance for future projects.

Categorize mixed project notes strictly into Risks, Assumptions, Issues, or Dependencies.