DEV Community

ClawGear
ClawGear

Posted on

ChatGPT for Project Managers: Templates for Stakeholder Updates, Risk Logs, and Retrospectives

#projectmanagement #chatgpt #productivity #agile

Monday morning. Sprint review in two hours. Three stakeholder emails unread, a risk register that hasn't been touched since last week, and a retro to run this afternoon.

This is where most PMs fall behind — not because they lack skills, but because the communication overhead never stops. Status emails, charter drafts, risk escalations, go-live announcements. Each one takes 20–40 minutes to write well.

Here's how I cut that time by 70%: I stopped writing from scratch.

These 25 ChatGPT prompts handle the five communications every project manager deals with weekly. Copy them, fill in the brackets, and send. The prompt itself saves the thinking time.

1. Stakeholder Updates

Status emails are the tax every PM pays. These prompts write them fast, in the format stakeholders actually read.

Prompt 1 — Weekly Status Email

Write a weekly project status email for [project name]. Current status: [RAG: Green/Amber/Red].
Completed this week: [list 2-3 items]. Coming next week: [list 2-3 items]. One risk to flag:
[describe risk]. Audience: [executive sponsor / broader team / client]. Tone: direct and brief —
no more than 150 words.
Enter fullscreen mode Exit fullscreen mode

This prompt saved my Monday morning status meeting prep. I run it at 8 AM and have the email approved before standup.

Prompt 2 — Executive Summary (for non-technical stakeholders)

Write a 3-paragraph executive summary for [project name] to present to [C-suite / board /
steering committee]. Translate this technical progress into business impact: [describe what
was built]. Budget status: [on track / X% over / X% under]. Timeline: [on track / slipped
by X weeks]. Frame everything around business value, not features.
Enter fullscreen mode Exit fullscreen mode

Prompt 3 — Risk Escalation Message

Write a risk escalation email to [recipient's role]. Risk: [describe risk]. Likelihood:
[high/medium/low]. Impact if it hits: [describe impact]. What we need from them: [specific
decision or resource]. We need a response by [date]. Keep it under 100 words and make the
ask clear.
Enter fullscreen mode Exit fullscreen mode

Prompt 4 — RAG Status Change Notification

We need to change the project RAG status from [previous] to [new status]. Reason: [explain
cause]. Write a message to the steering committee that explains what changed, what we're
doing about it, and what we need from them. Do not sugarcoat, but do not panic either.
Enter fullscreen mode Exit fullscreen mode

Prompt 5 — End-of-Phase Milestone Announcement

Write a milestone announcement for [project name] completing [phase name]. What was
delivered: [list]. Who contributed: [team names or roles]. What happens next: [next phase
or next milestone]. Audience: [internal team / all company / external stakeholders]. Keep
it celebratory but factual.
Enter fullscreen mode Exit fullscreen mode

2. Project Kickoff

The documents no one wants to write but everyone needs to have.

Prompt 6 — Project Charter Draft

Write a project charter for [project name]. Objective: [what this project achieves in one
sentence]. Scope: [what's in scope]. Out of scope: [what's explicitly excluded]. Key
stakeholders: [names/roles]. Constraints: [budget / timeline / resources]. Success criteria:
[how we'll know it worked]. Format as a clean one-page document.
Enter fullscreen mode Exit fullscreen mode

Prompt 7 — RACI Matrix Explanation Email

Write an email to the project team explaining the RACI matrix for [project name]. Attach
the matrix (I'll add it separately). Explain what R, A, C, and I mean in practice — not
in theory. Tell them exactly what they're expected to do when they see their name in each
column. Keep it under 200 words.
Enter fullscreen mode Exit fullscreen mode

Prompt 8 — Scope Statement

Write a scope statement for [project name]. In-scope deliverables: [list]. Out-of-scope
items: [list]. Assumptions: [list 3-4]. Dependencies: [what we need from others]. This
should be specific enough that if a stakeholder asks 'does this project include X?',
we can point to this document for the answer.
Enter fullscreen mode Exit fullscreen mode

Prompt 9 — Kickoff Meeting Agenda

Create a 60-minute kickoff meeting agenda for [project name]. Attendees: [roles].
Objectives of the meeting: introduce the team, align on scope, review RACI, identify
early risks. End with a clear action list. Include time allocations for each section.
Don't pad it with unnecessary slides or welcomes.
Enter fullscreen mode Exit fullscreen mode

Prompt 10 — Assumptions and Constraints Register

Turn these raw notes into a clean assumptions and constraints register for [project name].
Notes: [paste your raw notes]. Format: two columns — Assumption/Constraint | Impact if
wrong/violated. Sort by impact level: high, medium, low.
Enter fullscreen mode Exit fullscreen mode

3. Risk and Issue Management

Risk registers get ignored when they're vague. These prompts write entries specific enough to act on.

Prompt 11 — Risk Register Entry

Write a risk register entry for this risk: [describe the risk in plain English]. Include:
risk description, likelihood (H/M/L), impact (H/M/L), risk score (likelihood × impact),
owner ([name or role]), mitigation plan (3 specific actions), and contingency plan (what we
do if mitigation fails). Be specific — "monitor closely" is not a mitigation plan.
Enter fullscreen mode Exit fullscreen mode

Prompt 12 — Mitigation Plan

Write a detailed mitigation plan for this project risk: [risk description]. The plan should
include: (1) preventative actions we can take now, (2) early warning indicators to watch,
(3) who owns each action, and (4) the trigger point for escalating to the steering committee.
Output as a numbered list.
Enter fullscreen mode Exit fullscreen mode

Prompt 13 — Issue Log Update

Update this issue log entry: [paste current entry]. New status: [resolved / in progress /
escalated]. What happened: [describe what changed]. Next action: [who does what by when].
If resolved, add a root cause note so we don't repeat it.
Enter fullscreen mode Exit fullscreen mode

Prompt 14 — Risk Review Meeting Notes

Convert these messy meeting notes into a clean risk review summary: [paste notes]. Format:
top 3 risks discussed, decisions made, new risks identified, actions assigned (name + action
+ due date). Keep it under one page.
Enter fullscreen mode Exit fullscreen mode

Prompt 15 — Stakeholder Risk Briefing

Write a risk briefing email to [stakeholder name/role] covering the top 3 risks on the
project right now. For each risk: what it is, the current mitigation, and what you're
monitoring. Do not alarm them unnecessarily. Do flag that risk #[X] requires their
input. Be direct.
Enter fullscreen mode Exit fullscreen mode

4. Retrospectives

Retros fail when they're vague or when action items die in a Confluence page nobody checks. These prompts fix both problems.

Prompt 16 — Retro Facilitation Script

Write a 45-minute sprint retrospective facilitation script for a team of [X] people.
Sprint: [sprint name or number]. Use the Start/Stop/Continue format. Include specific
discussion questions for each section that push the team past surface-level answers.
Add a 10-minute action item assignment session at the end.
Enter fullscreen mode Exit fullscreen mode

Prompt 17 — Action Item Tracker Email

Convert these retro action items into a follow-up email to the team: [paste raw action
items]. For each item include: owner, action, success criterion, and due date. Add a
note that these will be reviewed at the start of next sprint. Keep the tone accountable,
not punishing.
Enter fullscreen mode Exit fullscreen mode

Prompt 18 — Improvement Proposal

Write a short improvement proposal based on this recurring retro theme: [describe the
issue — e.g., 'sprint planning takes too long', 'QA always gets squeezed at the end'].
Include: current state, proposed change, expected outcome, who needs to approve, and
how we'll measure success. One page max.
Enter fullscreen mode Exit fullscreen mode

Prompt 19 — Sprint Health Summary

Write a sprint health summary for sprint [X]. Velocity: [story points completed / planned].
Bugs introduced: [X]. Bugs resolved: [X]. Team capacity: [X% of planned]. Key learnings:
[paste 2-3 bullet points]. Format as a short internal document the team can review in
under 3 minutes.
Enter fullscreen mode Exit fullscreen mode

Prompt 20 — Retro Anti-Patterns Debrief

Our last retrospective had these problems: [describe — e.g., no one spoke honestly,
action items from last retro were ignored, the same issues keep coming up]. Write a
brief debrief I can share with the team that names the problems directly and proposes
one concrete change to how we run retros. Do not be diplomatic at the expense of being
useful.
Enter fullscreen mode Exit fullscreen mode

5. Client Communications

The messages where tone matters most — and where most PMs spend too long getting the words right.

Prompt 21 — Timeline Slip Email

Write an email to [client contact name/role] informing them that [project name] has slipped
by [X weeks]. Reason: [honest explanation — don't hide it]. New target date: [date]. What
we're doing to prevent further slippage: [2-3 actions]. What we need from the client, if
anything: [describe or say 'nothing at this time']. Do not over-apologize. Be direct and
solution-focused.
Enter fullscreen mode Exit fullscreen mode

Prompt 22 — Change Request Explanation

Write a change request explanation for this scope change: [describe the change]. Why it's
needed: [reason]. Time impact: [+X days or 'no impact']. Cost impact: [$X or 'no impact'].
Risk if we don't do it: [describe]. Format this so a client can read it in under 2 minutes
and make a decision. End with a clear yes/no ask.
Enter fullscreen mode Exit fullscreen mode

Prompt 23 — Go-Live Announcement

Write a go-live announcement for [project/product name] launching on [date]. Audience:
[client team / end users / both]. Include: what's going live, what users can expect,
known limitations or issues we're aware of, support contact, and next steps. Keep the
tone confident but not hype-driven.
Enter fullscreen mode Exit fullscreen mode

Prompt 24 — Meeting Recap for Client

Convert these meeting notes into a clean client-facing recap: [paste notes]. Include:
key decisions made, action items (owner + due date), open questions still to resolve,
and next meeting date. Remove internal comments. Format for someone who was in the
meeting but will skim this in 90 seconds.
Enter fullscreen mode Exit fullscreen mode

Prompt 25 — Project Close-Out Summary

Write a project close-out summary for [project name] to share with the client. Include:
original objectives vs. what was delivered, key milestones hit, any scope changes and
why, final budget vs. estimate, and lessons learned (keep it honest). End with a clear
statement of project completion and next steps (warranty period, support handover, etc.).
Enter fullscreen mode Exit fullscreen mode

How to Use These in Practice

Don't run them raw. Add context before you hit enter:

  1. Name the audience — "executive sponsor" reads differently than "junior dev."
  2. Give the RAG / status first — the model needs to know the tone before it writes.
  3. Paste your real data — prompts are 10× better with actual numbers and names.
  4. Edit the output — treat the first draft as a 70% draft. Tighten it.

I keep these in a Notion page and run them through ChatGPT 4 or Claude. The whole set takes about 90 minutes to set up once, then pays back daily.

Want the Full PM Prompt System?

If you run sprints, manage clients, or just spend too much time writing project updates, the Project Manager AI Workflow Toolkit has 100+ prompts, templates, and frameworks organized by workflow — kickoff through close-out.

Use code LAUNCH30 at checkout for 30% off. Currently $14.99 → $10.49 with the code.

If you manage multiple professional contexts, the Complete AI Prompt Pack Library bundles the PM toolkit with packs for HR, Real Estate, Healthcare, and Sales — better value if you wear more than one hat.

25 prompts. 5 workflow categories. Zero filler.

Save this for when your boss asks why the project is running late and you have 20 minutes to write a stakeholder update.

Top comments (0)