ChatGPT for Project Managers: 40 Prompts to Plan Faster, Communicate Better & Ship on Time

Write a project charter one-pager for [project name]. Include: project purpose and
business objective, scope summary (in scope / out of scope), key deliverables,
target timeline ([start date] to [end date]), project sponsor: [name],
project manager: [name], key stakeholders: [list], success criteria: [list 2–3],
known constraints or assumptions: [list]. Format as a clean one-page executive document.
Tone: professional and direct.

Write a scope of work (SOW) definition for [project name]. Client/stakeholder: [name].
Deliverables: [list specific outputs]. Timeline: [start to end date].
What's explicitly OUT of scope: [list]. Assumptions: [list].
Acceptance criteria: [list]. Tone: formal, precise — this will be shared
with the client for sign-off. 400–600 words.

Create a work breakdown structure (WBS) outline for [project name].
Project goal: [one sentence]. Major phases: [list 3–5 phases].
For each phase, list 3–5 key tasks or work packages.
Format as an indented outline. Include a brief note on deliverable or owner
for each phase. Keep it practical and actionable — not theoretical.

Write a project kickoff meeting agenda for [project name].
Duration: [60 / 90 / 120 minutes]. Attendees: [list roles — PM, sponsor,
dev lead, design lead, client stakeholders, etc.].
Include: welcome and introductions, project objectives and success criteria,
scope overview, roles and responsibilities (RACI), timeline and key milestones,
risk overview, communication plan, Q&A, and next steps.
Format with time allocations. Tone: energizing and focused.

Write a SMART goal statement for [project name]. Context: [2–3 sentences about
the project and its business purpose].
Specific: [what exactly will be achieved], Measurable: [how success is measured],
Achievable: [why it's realistic], Relevant: [why it matters to the organization],
Time-bound: [deadline or target date].
Format as a single clear SMART goal statement followed by a brief breakdown of each
component. Use confident, outcome-oriented language.

Write a resource allocation plan summary for [project name].
Team: [list roles and % allocation — e.g., Lead Developer: 80%, UX Designer: 50%].
Timeline: [start to end]. Key phases: [list].
Flag any resource conflicts or gaps: [describe if applicable].
Include a recommended approach to address any gaps.
Format as a concise summary with a resource table. Max 300 words.

Write a sprint planning brief for [team name], Sprint [number].
Duration: [1 week / 2 weeks — Sprint [start date] to [end date]].
Sprint goal: [one sentence].
Stories/tasks committed this sprint: [list 4–8 items with story point estimates].
Team capacity: [X points total].
Dependencies to resolve: [list].
Definition of done: [list acceptance criteria].
Tone: clear and action-oriented — this goes to the dev team before the sprint starts.

Generate a risk register seed for [project name].
Project type: [software development / construction / marketing campaign / other].
Key constraints: [timeline / budget / resource / technical].
For each of the top 5 risks, provide: Risk description, Likelihood (High/Medium/Low),
Impact (High/Medium/Low), Risk score (H/M/L × H/M/L), Mitigation strategy,
Owner (suggest a role). Format as a table. Flag the top 2 risks that require
immediate attention.

Write a weekly status report for [project name], covering [reporting period].
Overall status: [Green / Yellow / Red].
Milestones completed this week: [list].
Milestones coming up (next 2 weeks): [list].
Blockers / issues: [list each with owner and resolution plan].
Budget status: [on track / X% variance — reason].
Key decisions needed from leadership: [list if any].
Audience: exec team. Tone: confident, concise, no unnecessary hedging.
Lead with a one-sentence bottom line. Max 350 words.

Write a stakeholder update email for [project name] addressing a delay to
[specific milestone or deliverable]. Original due date: [date].
New projected date: [date]. Root cause: [brief explanation].
Impact on overall timeline: [describe]. Steps being taken to recover: [list].
What you need from the stakeholder (if anything): [specify or "no action required"].
Recipient: [stakeholder name and role]. Tone: transparent, professional, solution-focused —
acknowledge the delay without over-apologizing. Max 250 words.

Write an escalation email for [project name] to [leadership name/role].
Issue: [describe the blocker or critical risk in 1–2 sentences].
Impact if unresolved: [timeline / budget / scope / quality — be specific].
Steps already taken: [list what the PM has already attempted].
Decision or action needed from leadership: [specific ask].
Timeline for response needed: [date].
Tone: urgent but professional — this is a request for help, not a complaint.
Max 200 words.

Write a project dashboard summary for [project name] as of [date].
Use RAG (Red/Amber/Green) status for each category:
- Schedule: [status] — [one-sentence explanation]
- Budget: [status] — [one-sentence explanation]
- Scope: [status] — [one-sentence explanation]
- Resources: [status] — [one-sentence explanation]
- Risks: [status] — [one-sentence explanation]
Overall project status: [RAG].
Top priority action this week: [one sentence].
Format as a clean summary suitable for a leadership dashboard. Tone: factual, no spin.

Write a steering committee review one-pager for [project name].
Date: [date]. Reporting period: [period].
Executive summary: [2–3 sentences on project status].
Key accomplishments this period: [list 3–5].
Issues and risks requiring committee attention: [list with recommended decisions].
Upcoming milestones: [list with dates].
Budget snapshot: [spent to date vs. budget].
Decisions requested from the committee: [list specific asks].
Format as a structured one-page document. Tone: executive-ready, precise.

Write a milestone completion announcement for [project name].
Milestone achieved: [name and description].
Date completed: [date].
What this means for the project: [significance — are we on track, ahead, etc.].
Team members to recognize: [names and contributions].
What comes next: [next milestone, timeline].
Audience: [full project team / broader organization].
Tone: celebratory but professional — acknowledge effort, build momentum.
Max 200 words.

Write a change request summary for [project name].
Change requested: [describe the change].
Requested by: [name/role]. Date: [date].
Reason for request: [business justification].
Impact on scope: [describe]. Impact on timeline: [describe delta — e.g., +2 weeks].
Impact on budget: [describe delta — e.g., +$15,000].
Recommended decision: [Approve / Reject / Defer — with rationale].
Next step: [who needs to approve and by when].
Format as a formal change request document. Tone: neutral, analytical, decision-ready.

Write an end-of-phase summary memo for [project name], [phase name — e.g., Discovery /
Design / Development Phase 1].
Phase dates: [start to end].
Planned vs. actual delivery: [on time / X days late — reason].
Key deliverables completed: [list].
Issues encountered and how they were resolved: [list].
Lessons learned to apply to next phase: [list 2–3].
What's next: [next phase overview and start date].
Audience: project team and sponsor. Tone: reflective, forward-looking, concise.
Max 400 words.

Write a sprint retrospective facilitation guide for [team name], Sprint [number].
Duration: [45 / 60 / 90 minutes]. Facilitator: [PM / Scrum Master / team lead].
Format: [Start/Stop/Continue / 4Ls / Mad-Sad-Glad — choose one].
Context for this sprint: [brief — what went unusually well or poorly].
Include: icebreaker (2 min), data review (5 min), individual reflection (5 min),
group discussion (20 min), action item identification (10 min), close (5 min).
For each section, include facilitator prompts and what to watch for.
Tone: psychologically safe, improvement-focused — not a blame session.

Write a detailed meeting agenda for the [project name] project kickoff.
Date: [date]. Time: [time and timezone]. Location/link: [in-person / Zoom / Teams].
Duration: [90 minutes].
Attendees: [list roles].
Prework required: [list anything attendees should review beforehand].
Include time-boxed agenda items: objectives, introductions, project overview,
scope and timeline walkthrough, roles and responsibilities, communication plan,
risk overview, open Q&A, next steps.
Assign a discussion lead to each item. Tone: structured, energizing, sets the tone
for the whole project.

Write an action item follow-up email after the [project name] daily standup on [date].
Action items captured:
- [Action 1] — Owner: [name] — Due: [date]
- [Action 2] — Owner: [name] — Due: [date]
- [Action 3] — Owner: [name] — Due: [date]
Blockers flagged: [list any items that need PM support].
Next standup: [date and time].
Tone: clear, accountable, brief — this is a quick reference, not a lecture.
Max 150 words. Reply-to is optional.

Write a decision log entry for [project name].
Decision made: [describe the decision clearly].
Date: [date].
Decision made by: [name(s) and role(s)].
Options considered: [list 2–3 alternatives that were evaluated].
Rationale for decision: [why this option was chosen].
Impact on project: [scope / timeline / budget / approach].
Who was notified: [list].
Next action required (if any): [describe].
Format as a formal log entry suitable for project documentation. Tone: factual, precise.

Write a RACI matrix description for the task: [task name] in [project name].
Task description: [1–2 sentences].
Define the RACI for each of the following roles: [list 4–6 roles — e.g., PM,
Tech Lead, UX Designer, Business Analyst, QA, Sponsor].
For each role, assign R (Responsible), A (Accountable), C (Consulted), or I (Informed)
and provide a 1-sentence explanation of why.
Flag any roles where RACI overlap could create confusion.
Format as a table followed by brief explanatory notes.

Write a cross-functional alignment email for [project name].
Sending from: [PM name], to: [list team leads / department heads].
Purpose: [align on [specific decision / timeline change / dependency / handoff]].
Context: [2–3 sentences of background — what's happening and why this email matters].
What each team needs to know: [list team-specific points if applicable].
What you need from each team by [date]: [specific asks].
Next touchpoint: [meeting / check-in date].
Tone: collaborative, direct — assumes smart people who are busy. Max 250 words.

Write a 5-minute all-hands project update script for [project name].
Audience: [full team — cross-functional, including people not on the project daily].
Current project phase: [planning / development / testing / launch].
Overall status: [on track / at risk — brief context].
Key wins to celebrate: [list 2–3].
Challenges being worked through: [list 1–2 — be honest, not alarming].
What the team needs to know about the next 30 days: [list key milestones].
Call to action or ask: [what you need from the broader team].
Tone: energizing, transparent, builds trust. Include natural speaking transitions.

Write a conflict resolution message for a situation on [project name] between
[Team Member A — role] and [Team Member B — role] regarding [nature of conflict —
e.g., ownership of a deliverable / communication breakdown / differing technical approaches].
This message is from the PM to both parties.
Acknowledge both perspectives. Propose a path forward: [brief description].
Set clear expectations going forward.
Tone: calm, professional, solution-focused — no blame, no drama. Max 200 words.

Write a RAID log entry for [project name] covering [specific item — e.g.,
third-party API availability].
Type: [Risk / Assumption / Issue / Dependency].
Description: [clear 2–3 sentence description].
Date identified: [date].
Owner: [role].
Impact if unresolved: [High / Medium / Low — explain].
Mitigation or action: [specific steps and timeline].
Status: [Open / In Progress / Resolved].
Related items: [link to other RAID entries if applicable].
Format as a clean log entry ready to paste into a RAID register.

Write an email responding to a scope creep request on [project name].
Request: [stakeholder name/role] has asked to add [describe the new request].
This was not in the original scope approved on [date].
Acknowledge the request professionally.
Explain the impact: [timeline delta / budget delta / resource impact].
Offer the path forward: [change request process / trade-off options / defer to Phase 2].
Tone: professional, firm but collaborative — protect the scope without damaging
the relationship. Max 250 words.

Write an issue escalation brief for [project name].
Issue: [describe clearly in 2–3 sentences].
Date identified: [date]. Severity: [Critical / High / Medium].
Impact on project: [schedule / budget / scope / quality — be specific].
Root cause (if known): [explain or note "under investigation"].
Actions taken so far: [list what the team has already done].
What is needed to resolve: [specific resources / decisions / approvals].
Escalating to: [name/role]. Response needed by: [date].
Format as a brief suitable for leadership review. Tone: urgent, factual,
solution-oriented.

Write a lessons learned summary for [project name], covering [phase or full project].
Date: [date]. Compiled by: [PM name].
For each category, provide 2–3 specific, actionable lessons (not generic advice):
- Project planning and scoping
- Stakeholder management
- Team and resource management
- Risk and issue management
- Communication and reporting
For each lesson: what happened, what we'd do differently, and what to implement
on the next project. Tone: honest, constructive, forward-looking.

Write a dependency map description for [project name].
List all key external and internal dependencies: [list what the project depends on
to proceed]. For each dependency:
- Dependency name: [name]
- Type: [internal team / external vendor / system / regulatory]
- Owner: [name or team]
- Required by: [date or project milestone]
- Current status: [on track / at risk / blocked]
- Risk if delayed: [describe impact]
Flag the top 2 dependencies most likely to jeopardize the timeline and recommend
mitigation. Format as a structured table with narrative summary.

Write a budget overrun explanation memo for [project name].
Current spend: $[X] vs. approved budget: $[X] — variance: $[X] ([X]% over).
Primary causes of overrun: [list 2–4 specific reasons with dollar amounts].
Impact on project completion: [describe].
Options for resolution: [list 2–3 options with trade-offs — e.g., reduce scope,
request additional budget, extend timeline].
Recommended path forward: [your recommendation with rationale].
Audience: [project sponsor / finance / exec team].
Tone: transparent, analytical, focused on solutions not excuses. Max 400 words.

Write a post-mortem report outline for [project name].
Project dates: [start to end]. Final status: [delivered on time / late by X /
over budget by X / under budget by X].
Include sections for: Executive Summary, Timeline Analysis (planned vs. actual),
Budget Analysis (planned vs. actual), Scope Changes (list all approved changes),
What Went Well (list 4–6 specifics), What Didn't Go Well (list 4–6 specifics —
be direct), Root Cause Analysis for top 3 issues, Recommendations for Future
Projects, Appendix (key documents, decision log, risk register).
Tone: honest, constructive — this document should actually improve the next project.

Write a vendor brief for [deliverable name] on [project name].
Vendor/contractor: [name or "TBD"].
Deliverable description: [what exactly is being produced].
Scope boundaries: [what's included and what's explicitly excluded].
Timeline: [start date] to [due date]. Key checkpoints: [list].
Quality and acceptance criteria: [list specific standards or sign-off process].
Communication expectations: [frequency of updates, format, escalation path].
Key contacts: PM ([name]), Technical Lead ([name]).
Tone: professional and precise — this sets expectations before work begins.
Max 400 words.

Write a PMP exam study plan outline for someone with [X years] of PM experience.
Target exam date: [date — approximately [X weeks] from now].
Available study time: [X hours per week].
Primary study resource: [PMBOK / Agile Practice Guide / prep course / other].
Include: weekly study schedule with topics, milestone checkpoints (practice exams),
focus areas based on current exam format (predictive vs. agile/hybrid content split),
and a 2-week pre-exam sprint. Tone: practical, structured — assume a working PM
with limited time.

Write a LinkedIn post about a project win for [project name].
What was achieved: [describe the deliverable or result].
Why it mattered: [business impact — quantify if possible: time saved,
revenue generated, cost reduced, etc.].
What made it hard: [the real challenge — be specific, not humble-braggy].
What I/the team did that worked: [key approach or decision].
Optional: tag team members or stakeholders [names if desired].
Tone: confident, human, credibility-building — not a press release.
150–250 words. Include 3–5 relevant hashtags.

Write a performance self-review narrative for a project manager covering
[review period — e.g., Q1–Q2 2026].
Key projects managed: [list with brief outcomes].
Achievements to highlight: [list 3–5 specific accomplishments with impact metrics].
Skills developed or demonstrated: [list — e.g., stakeholder management,
risk mitigation, cross-functional leadership].
Challenges navigated: [list 1–2 — show self-awareness and growth].
Goals for next period: [list 3 specific, measurable goals].
Tone: confident, specific, outcome-oriented — not generic or self-deprecating.
400–500 words.

Write a cover letter for a project manager applying to [company name] for
the role of [job title].
Applicant background: [X years PM experience], [industries — e.g., tech /
construction / healthcare], [certifications — PMP / CSM / PRINCE2].
Key projects to reference: [list 2 with brief outcomes].
Why this company / role: [specific reason — research the company].
Tone: confident, direct, specific — no generic "I'm passionate about project management"
openings. Max 350 words. Format as a professional cover letter.

Write a STAR-format interview answer for the question "Tell me about a time you managed
a particularly difficult project" for a [senior / mid-level] PM role at a
[company type — e.g., tech startup / enterprise / consulting firm].
Situation: [project type, stakes, and what made it difficult — e.g., aggressive timeline,
unclear scope, difficult stakeholder].
Task: [your specific responsibility].
Action: [what you did — focus on PM decisions, not team actions].
Result: [quantified outcome — delivered on time, saved X, launched Y].
Tone: confident, specific, demonstrates seniority. 250–350 words.
Feel free to make reasonable assumptions about the project details.

Write a methodology comparison brief for a decision between Agile and Waterfall
for [project name].
Project type: [describe — software / construction / marketing / product launch].
Key factors: [fixed scope or flexible / clear requirements or evolving /
timeline flexibility / team experience with each methodology].
For each methodology, cover: core approach, best fit, risks, and
team requirements. Recommend the better fit for this specific project with rationale.
Audience: [PM + project sponsor / leadership team].
Tone: analytical, opinionated — recommend clearly, don't sit on the fence.
Max 400 words.

Write a 90-day mentorship plan for a junior PM being mentored by [senior PM name].
Junior PM background: [brief — new to role / career changer / recent grad].
Focus areas for development: [list 3–4 — e.g., stakeholder communication,
risk management, running effective meetings, writing status reports].
For each month (30/60/90 days), include: learning objectives, specific activities
(shadowing, leading a deliverable, reading/resources), and a milestone or check-in.
Include a recommended meeting cadence. Tone: supportive, structured,
growth-oriented — this should actually develop someone.

Write annual professional goals for a senior project manager for [year].
Current role: [title] at [company type].
Career direction: [aspiring to director / program manager / VP / PMO lead /
staying IC but deepening expertise].
Areas to develop: [list 2–3 — e.g., executive presence, portfolio-level thinking,
mentoring, AI tools adoption, stakeholder influence].
For each goal: specific objective, measurable success criteria,
key activities to achieve it, and target timeline.
Tone: ambitious but achievable — these should stretch, not overwhelm.
3–5 goals, formatted clearly.