Prompt: Write a Stakeholder Update Email

This prompt stakeholder update email generates concise updates that busy stakeholders actually read. The secret is structure and brevity. Nobody wants a 1,000-word email about project status.

The Prompt

You are a project communication specialist. Write a stakeholder update email.

Project/initiative: [what the update is about]
Stakeholder(s): [who is receiving this, their role and what they care about]
Update frequency: [weekly / biweekly / monthly / ad hoc]
Overall status: [on track / at risk / behind / ahead]

Key information to include:
- Progress since last update: [bullet points of what was accomplished]
- Metrics or data points: [relevant numbers]
- Issues or blockers: [anything slowing progress, if any]
- Decisions needed from stakeholder: [if any]
- Next steps: [what happens next and by when]
- Budget status: [on budget / over / under, if relevant]

Write the update email:

SUBJECT LINE:
Format: [Project Name] Update - [Date] - [Status: On Track / At Risk / Action Needed]

BODY:
1. STATUS LINE (1 sentence):
"[Project] is [on track/at risk/behind schedule]. Here is what happened and what is next."

2. PROGRESS (3-5 bullet points):
Each bullet: what was done + the result or impact. Not just "worked on X."

3. METRICS (2-4 numbers):
The key data points that show progress. In a simple inline format, not a full table.

4. ISSUES (if any):
What is blocked or at risk. For each: the issue, the impact, and the proposed solution.

5. DECISIONS NEEDED (if any):
Exactly what you need them to decide, the options, your recommendation, and the deadline for the decision.

6. NEXT STEPS (3-5 items):
What happens next, who owns it, and when it will be done.

Rules:
- Total email under 200 words (excluding subject line)
- Lead with status. They should know the headline before scrolling.
- Bold the decision items so they do not get missed
- No filler phrases: "I wanted to give you an update" or "hope this finds you well"
- If nothing is blocked, say so explicitly: "No blockers. On track."
- Match the detail level to the stakeholder: CEO gets high-level, project manager gets specifics

The Decision Section

Section 5 is what separates an update from an information dump. If you need something from them, make it impossible to miss. Bold it. State the deadline. Give your recommendation so they can approve quickly instead of starting from zero.

Consistency Beats Perfection

Send the update at the same time on the same day. Stakeholders learn to expect it. When they trust the cadence, they stop asking for ad hoc updates, which saves everyone time.

Build These Systems

Ready to implement? These step-by-step tutorials show you exactly how:

• How to Automate Contact Record Updates from Email - Update CRM contact records automatically based on email interactions.
• How to Create Automated Status Update Systems - Generate and distribute project status updates automatically.
• How to Automate Sales Playbook Updates - Keep sales playbooks current with automated updates from deal data.