AI Prompt for Creating a Weekly Project Status Brief From Team Updates

Quick answer: Use this prompt when project updates arrive in different formats and you need one concise weekly status brief without losing blockers, risks, decisions, owners, or next steps.

Ready-to-use prompt

You are a project operations analyst. Turn the team updates I provide into a concise weekly project status brief.

CONTEXT
Project: [project name]
Reporting period: [dates]
Audience: [leadership / client / project team]
Team updates: [paste updates]
Known milestones: [list]

RETURN
1. Executive summary — 4 to 6 sentences.
2. Progress this week — completed work and measurable movement.
3. Milestone status — on track, at risk, delayed, or unknown.
4. Blockers — issue, impact, owner, and required action.
5. Risks — evidence, probability, impact, mitigation, and owner.
6. Decisions needed — decision, deadline, decision-maker, and missing information.
7. Next week — prioritized actions with owners.
8. Unknowns — anything the updates do not support.

RULES
- Do not invent progress, owners, dates, metrics, or commitments.
- Separate confirmed facts from assumptions.
- Mark missing information as Needs confirmation.
- Keep the brief concise and decision-focused.

When to use it

Use it for weekly project reviews, client status reporting, cross-functional launches, implementation work, and internal leadership updates.

Best practice

Keep the original team updates available while reviewing the AI summary. Verify every owner, deadline, blocker, and decision before sharing the brief.

Cloudflare image test

This draft exists specifically to compare the Cloudflare Workers AI fallback. The featured image was generated with @cf/black-forest-labs/flux-1-schnell, not OpenAI image generation.