StructuredFor ProfessionalsWriting & Comms

Write a weekly status update that stakeholders actually read.

Every week for any ongoing project, programme, or client engagement

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~1100 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
write-a-weekly-status-update-that-stakeholders-actually-read.md Β· 1100 words
You are a senior {{role}} brought in to help a professional complete a {{use_case}} task.

# Context
- Category: Writing & Comms
- Use case: Write a weekly status update that stakeholders actually read
- Source task:
  - Write a weekly status update for {{project_name}} to be sent to {{audience}}. This week: {{summarise_what_happened_in_3_5_bullet_points}}. Current status: {{current_status}}. Key metric or milestone this week: {{one_number_or_achievement}}. Blockers or risks: {{list_any}}.
  - Format: RAG status badge (Red / Amber / Green) + 3-section structure: This Week | Next Week | Risks & Blockers. Total length: under 200 words. Skip anything that adds no new information.

# Goal
A scannable, under-200-word update with clear RAG status and no filler

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and corporate-sounding language.
- Make the output specific, practical, and ready to use.

# Output
A scannable, under-200-word update with clear RAG status and no filler

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleproject communications expert
{{project_name}}Project nameCRM migration
{{audience}}Audiencestartup founders
{{summarise_what_happened_in_3_5_bullet_points}}Summarise what happened in 3 5 bullet pointssummarise what happened in 3-5 bullet points
{{current_status}}Current statusOn Track
{{one_number_or_achievement}}One number or achievementone number
{{list_any}}List anyExample list any
{{use_case}}Your specific valuewrite a weekly status update that stakeholders actually read

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

Every week for any ongoing project, programme, or client engagement

PRO TIP

Stakeholders skim. Use bold for the RAG status and the single most important number. Everything else is context.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… EXPLORE MORE PROMPTS

More for Professionals

Browse all prompts built for Professionals β€” free and premium, ready to copy.

Browse more prompts β†’