Weekly status reports and stakeholder updates from raw notes
Writing the same weekly update in three registers — one for the exec sponsor, one for the delivery team, one for the client — is repetitive drudgery that always lands at the worst time. AI turns your rough notes into a clean, structured report in minutes. The discipline is keeping every claim tied to what you actually gave it, because a status report that quietly misstates percent-complete or a date does real damage.
You are a project communications assistant helping a project manager write a status report. Use ONLY the facts I provide below. Do not invent progress, percentages, dates, or risks I did not give you. Project: {{project_name}} Reporting period: {{reporting_period}} Raw updates and notes (source of truth): {{raw_updates}} Audience and what they care about: {{audience}} Produce, in this order: 1. Overall status as one word (On track / At risk / Off track) with a one-sentence justification drawn only from my notes. 2. "The short version" — three bullets a busy exec can read in 15 seconds. 3. Progress this period, upcoming this period, and any decisions or help needed. 4. Open risks and issues, each with current status. Rules: - Use only the facts in my notes. If something the audience will obviously ask about is missing, list it under "Gaps to confirm before sending" instead of guessing. - Do not state any percentage, date, or dollar figure unless it appears in my notes — mark anything uncertain as [VERIFY]. - Match the tone to the audience: concise and outcome-focused for execs, more detail for the delivery team. - Plain language, no filler, no false reassurance.
Fill in your details and the prompt updates live — then copy.
Overall status: At risk — UAT is progressing, but an ERP integration dependency has slipped. The short version: - Go-live still targeted for end of Q3, protected for now. - UAT is about 60% complete with no critical defects so far. - We are waiting on the vendor's API fix; a longer delay would put the date at risk. Decisions/help needed: Escalation contact at the vendor to unblock the API. Gaps to confirm before sending: Exact budget status this period — not in your notes; mark [VERIFY] before sending.
The full workflow
- Collect the real updates from your tracker, standups, and workstream leads as the source of truth
- Run the prompt and resolve every [VERIFY] and "Gaps to confirm" item against your actual data
- Adjust tone for each audience and cut anything the reader does not need
- Send from your normal channel and log the report in your PM tool
Watch out for
AI can misstate status by summarizing selectively — a confident update that overstates progress or hides a slip erodes stakeholder trust fast. Verify every percentage, date, and figure against your tracker before it goes out; you are accountable for the report, not the model.
Do not paste confidential client, contract, or financial detail into a consumer AI account that may retain and train on it. Describe the project generically, and use only an employer-approved enterprise tool for anything covered by an NDA or MSA.
Where this comes from
Every use case on this site is grounded in real reports from working project managers — not invented by us.