Write a status update email for [RECIPIENT AND RELATIONSHIP] about [PROJECT OR WORKSTREAM]. The email should reflect this update: [PROGRESS, MILESTONES, AND EVIDENCE]. Include these open risks, blockers, or dependencies: [RISKS OR BLOCKERS]. I need the recipient to take or decide on this: [CLEAR ASK AND DEADLINE]. Use this tone: [TONE AND CONTEXT]. Write a ready-to-send email of 150–250 words with: 1. A subject line that names the project and the most important update. 2. A two-sentence opening stating overall status as on track, at risk, blocked, or complete, with the reason. 3. A short “Completed / since last update” section with only material progress.
4. A short “Next” section with owners or dates where I supplied them. 5. A “Needs from you” section that makes the requested action, decision, and deadline unmistakable. 6. A closing that matches the relationship; do not manufacture optimism, urgency, dates, owners, or commitments. Adapt the detail level to the recipient: executives need impact and decisions; project teammates need dependencies and handoffs; clients need outcomes and any needed action. Do not turn routine work into accomplishments or bury a blocker below a long progress list. Before answering, check that every claimed result, date, and owner comes from my input. Check that the ask can be answered with a concrete decision or action. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT AND RELATIONSHIP] | State who will receive the email and their relationship to the work. | Priya Shah, VP Product and executive sponsor |
| [PROJECT OR WORKSTREAM] | Enter the project, account, initiative, or workstream being updated. | September customer onboarding redesign |
| [PROGRESS, MILESTONES, AND EVIDENCE] | List completed work, measurable results, and important changes since the prior update. | Usability testing completed with 12 customers; 10 completed setup without support. Engineering finished the new checklist flow. |
| [RISKS OR BLOCKERS] | Describe unresolved dependencies, risks, delays, or decisions holding work up. | Legal has not approved the updated data-processing copy; this could delay the October 7 launch. |
| [CLEAR ASK AND DEADLINE] | State the action or decision needed, who should make it, and the deadline if one exists. | Please choose between launching without the copy change or moving launch to October 14 by Thursday. |
| [TONE AND CONTEXT] | Describe the desired tone and any relationship or sensitivity that affects wording. | Brief, candid, and calm; Priya prefers a direct recommendation. |
How to use
- Paste the prompt into ChatGPT, Claude, or Gemini and replace every bracketed field.
- Use real status evidence, not activity lists; include the exact decision or action you need.
- Check that the status label matches the facts and that the ask appears once in a skimmable section.
- Follow up with: “Make this half as long for an executive who reads email on mobile.”
Variations
Client update
Use when a client needs reassurance, visibility, and a specific approval.
Write a client project update for [CLIENT NAME] about [PROJECT]. Use these verified accomplishments: [COMPLETED WORK]. Explain this issue or dependency plainly: [ISSUE]. Request this approval, file, or decision by [DATE]: [CLIENT ACTION]. Produce a 120–180 word email with a subject line, progress, next steps, and one clearly labeled client action. Keep responsibility accurate; do not blame third parties or promise dates I did not provide. Check that every deliverable and deadline is supported by my notes.
Weekly team update
Use when teammates need handoffs, priorities, and blockers for the coming week.
Turn these weekly notes into an internal team update: [WEEKLY NOTES]. The audience is [TEAM AND ROLES], and the main objective is [OBJECTIVE]. Include these owners and deadlines exactly where supplied: [OWNERS AND DATES]. Write a concise Slack-ready update with Done, Next Week, Blockers, and Decisions Needed. Distinguish confirmed commitments from proposed work. Do not assign work to anyone not named in my notes. Before answering, check that each blocker names its impact or the action needed.
Leadership escalation
Use when an unresolved risk requires senior attention or a tradeoff decision.
Draft an escalation email to [LEADER] regarding [ISSUE]. The business impact is [IMPACT], the evidence is [FACTS], and the options are [OPTIONS]. I recommend [RECOMMENDATION] and need a decision by [DATE]. Write 130–200 words: subject line, one-sentence situation summary, impact, two or three options with tradeoffs, and a direct decision request. Do not exaggerate urgency or add financial, customer, or legal consequences not supplied. Check that the recommendation follows from the facts and the decision owner is clear.
Tips
- Lead with a truthful status label; “at risk” is more useful than a cheerful update that hides a dependency.
- Put decisions before background when the recipient can unblock the work.
- Separate completed outcomes from effort: “12 customers completed setup” says more than “ran usability testing.”
- If the ask involves a deadline, state the consequence of no response only when that consequence is confirmed.
FAQ
How long should a status update email be?
Most recurring updates work at 150–250 words. Add detail only when it changes a decision, a date, or a dependency.
Should I include every task I completed?
No. Include milestones, outcomes, and work that affects scope, timing, cost, quality, or a handoff.
Can AI write an update when the project is behind?
Yes, if you supply the facts. Keep the delay, cause, recovery options, and needed decision explicit rather than asking it to soften them away.