35 ChatGPT Prompts for Project Managers: Deliver Faster Without Working More Hours
Project managers live in a permanent state of translation. You translate strategy into tasks, tasks into timelines, problems into solutions, and all of it into communication that 12 different stakeholders can understand.
The overhead kills productivity. Status updates, meeting agendas, risk registers, budget summaries — necessary, time-consuming, and largely formulaic.
ChatGPT handles the formulaic parts. These 35 prompts are organized by the seven PM workflows that eat the most time. Each one is specific, ready to use, and built around real project scenarios.
1. Project Planning and Scope Definition
A clear scope at the start prevents 80% of project problems. These prompts help you define, document, and communicate boundaries before work begins.
Prompt 1 — Write a project charter
"Write a project charter for [Project Name]. Include: project purpose and business objective, scope statement (what's in and what's explicitly out), key deliverables, timeline milestones, budget estimate, project sponsor, and success criteria. Use a professional template format. The audience is [executive/client/team]."
Prompt 2 — Break down a project into phases
"Break down [Project Name] into 4-6 phases with clear entry and exit criteria for each. For each phase: name, objective, key activities, dependencies, and estimated duration. Assume the project involves [brief description]. Present as a table and include a note about risks at each phase transition."
Prompt 3 — Create a work breakdown structure
"Create a work breakdown structure (WBS) for [Project Name]. The project goal is [description]. Break it into: major deliverables (Level 1), sub-deliverables (Level 2), and tasks (Level 3). Use an indented outline format. Flag any tasks that are likely to be on the critical path."
Prompt 4 — Write a scope change request
"Write a formal scope change request for [Project Name]. The requested change is: [description]. Reason for the change: [client/internal request]. Impact on timeline: [X days/weeks]. Impact on budget: [dollar estimate]. Risks if approved: [list]. Risks if rejected: [list]. Recommended decision: [approve/reject/defer]."
Prompt 5 — Define project success metrics
"Write a success metrics framework for [Project Name]. For each key deliverable or phase: define what 'done' looks like, 2-3 measurable success criteria, how we will measure it, who is responsible for tracking, and what happens if we fall short. Avoid vague measures like 'client satisfaction' without specifying how it's measured."
2. Stakeholder Communication
Projects succeed when stakeholders stay informed and aligned. These prompts handle the communication load that keeps them there.
Prompt 6 — Write a project kickoff email
"Write a project kickoff email from [PM Name] to all project stakeholders for [Project Name] starting [date]. Include: project purpose and business goal, team roles and contacts, key milestones with dates, communication cadence (meetings, reports, channels), and what each stakeholder needs to do in the first 2 weeks."
Prompt 7 — Draft a stakeholder communication plan
"Create a stakeholder communication plan for [Project Name]. For each stakeholder group: [list groups]. Include: communication type, frequency, channel, owner, and content summary. Use a table format. Add a note about escalation triggers — when and how issues get raised above the normal reporting chain."
Prompt 8 — Write a status update email
"Write a concise project status update email for [Project Name] for the week of [date]. Include: overall status (Green/Yellow/Red with one-sentence reason), accomplishments this week, planned work next week, issues or risks (and owners), and any decisions needed from stakeholders. Under 300 words."
Prompt 9 — Handle a difficult stakeholder
"Write talking points for a conversation with [stakeholder type: sponsor, client, department head] who is [frustrated about delays / pushing for scope expansion / disengaged from the project]. My goal is to: [specific outcome]. Cover: acknowledging their concern, the factual situation, what I'm proposing to address it, and what I need from them."
Prompt 10 — Write a project steering committee update
"Write a 1-page steering committee update for [Project Name] for [month/quarter]. Include: executive summary (3 sentences), RAG status with explanations, major achievements, risks and issues escalated for committee attention, decisions needed, and a forward look to next period. Formal but scannable."
3. Risk Management and Mitigation
Risks ignored become issues. These prompts help you identify, document, and communicate risk before it becomes crisis.
Prompt 11 — Build a risk register
"Create a risk register for [Project Name]. Identify 8-10 realistic risks for a project of this type: [brief description]. For each risk: description, probability (High/Med/Low), impact (High/Med/Low), risk score, mitigation strategy, contingency plan, and risk owner. Use a table format."
Prompt 12 — Write a risk escalation memo
"Write a risk escalation memo from [PM Name] to [Sponsor/Executive] for [Project Name]. The risk is: [description]. Current status: [where things stand]. Potential impact if unmitigated: [timeline/budget/quality impact]. Options considered: [A, B, C]. Recommended action: [your recommendation]. Decision needed by: [date]."
Prompt 13 — Create a RAID log template
"Create a RAID log template (Risks, Assumptions, Issues, Dependencies) for a [type] project. For each category: define what should be logged there, provide 2 example entries, and specify the fields to track. Include columns for ID, description, date raised, owner, status, and resolution notes."
Prompt 14 — Write an issue resolution update
"Write an issue resolution update for [Issue Description] on [Project Name]. Include: original issue (date raised, impact), root cause identified, actions taken to resolve, current status, and any residual risk. For: [stakeholder audience]. Under 200 words. Factual and forward-looking."
Prompt 15 — Conduct a pre-mortem
"Facilitate a written pre-mortem for [Project Name]. Assume the project has failed spectacularly. Write 8 specific, plausible reasons why it failed — covering: scope, team, dependencies, client/stakeholder behavior, technology, budget, timeline, and external factors. For each: what the warning sign would have been and what we should do now to prevent it."
4. Team Coordination and Task Assignment
Projects stall when people don't know exactly what they're doing, by when, and why it matters. These prompts remove that ambiguity.
Prompt 16 — Write a task assignment email
"Write a clear task assignment email from [PM Name] to [Team Member Name] for [Task Description]. Include: what the task is (specific output, not activity), why it matters to the project, due date, resources available to them, any dependencies to know about, and how to flag if something blocks them."
Prompt 17 — Build a RACI matrix
"Create a RACI matrix for [Project Name]. Key activities: [list 8-10 major activities or decisions]. Roles involved: [list roles/team members]. For each activity, assign Responsible, Accountable, Consulted, and Informed. Use a table. Add a note where common RACI errors occur (multiple Accountables, too many Consulted)."
Prompt 18 — Write a team standup agenda
"Create a daily standup meeting structure for a [size] team working on [Project Name]. Keep it to 15 minutes maximum. Include: format (round-robin vs board-review), the 3 questions each person answers, how blockers are handled without derailing the standup, and how action items are captured."
Prompt 19 — Address a performance issue on the team
"Write talking points for a 1:1 with a team member who has [specific issue: missing deadlines / not communicating blockers / quality concerns]. My goal: address the issue directly, understand root cause, agree on a clear improvement plan. Not confrontational — problem-solving focused. 5-7 bullet points."
Prompt 20 — Write a new team member onboarding plan
"Create a 2-week onboarding plan for a new [role] joining [Project Name] at [phase of project]. Week 1: orientation, relationship-building, and context. Week 2: hands-on work with support. For each day: activities, meetings, and documents to review. Deliverable: the new member should be able to contribute independently by day 10."
5. Status Updates and Reporting
Reporting is the PM's most visible output. These prompts make it faster and clearer.
Prompt 21 — Write a project dashboard summary
"Write a project dashboard summary for [Project Name] as of [date]. Include: overall health (Red/Yellow/Green), timeline status (ahead/on track/behind by X days), budget status (spent vs. planned), scope status (changes logged), top 3 accomplishments, top 3 risks, and next milestone with date."
Prompt 22 — Write a monthly executive report
"Write a monthly project report for [Project Name] for [month]. Audience: [executives/board/client]. Format: half-page max. Include: RAG status with one-sentence rationale, key wins, key risks or issues, budget vs. actuals, what's coming next month, and any decisions needed. Professional and scannable."
Prompt 23 — Write a milestone completion notice
"Write a milestone completion notice for [Milestone Name] on [Project Name] completed on [date]. Include: what was delivered, how it compares to the original plan, any deviations and their causes, the next milestone and its target date, and a brief thank-you to the team. Under 200 words."
Prompt 24 — Communicate a schedule delay
"Write a schedule delay notification from [PM Name] to [stakeholders] for [Project Name]. The delay is [X days/weeks] affecting [milestone/deliverable]. Cause: [factual explanation]. Impact: [downstream effects]. Recovery plan: [specific actions and revised dates]. Tone: factual, accountable, solution-focused. Not apologetic beyond one sentence."
Prompt 25 — Write a budget overrun explanation
"Write a budget overrun explanation from [PM Name] to [sponsor/finance] for [Project Name]. Current spend: [amount]. Original budget: [amount]. Variance: [amount/%]. Root causes: [list]. Actions taken to date: [list]. Options to recover: [list with trade-offs]. Recommended path: [your recommendation with rationale]."
6. Budget and Resource Management
Budget conversations are uncomfortable. These prompts help you have them clearly and credibly.
Prompt 26 — Build a project budget template
"Create a project budget template for a [type of project] with an estimated budget of [range]. Categories to include: labor (by role), software/tools, external vendors, travel, contingency (specify %), and management reserve. Include a column for planned vs. actual tracking. Add 3 tips for tracking budget health weekly."
Prompt 27 — Write a resource request
"Write a formal resource request from [PM Name] to [Resource Manager/Sponsor] for [Project Name]. Resources needed: [role(s), hours/week, duration]. Why they're needed: [specific gap or deliverable]. Business impact if not provided: [timeline/quality risk]. Alternatives considered: [list]. Requested by: [date]."
Prompt 28 — Explain a vendor invoice discrepancy
"Write an email to [Vendor Name] regarding invoice [number] for [Project Name]. The invoice amount is [billed amount]; the contracted amount for this milestone/deliverable was [agreed amount]. The discrepancy is [difference]. Request a revised invoice or a written explanation of additional charges. Professional and specific."
Prompt 29 — Write a change order request
"Write a change order request for [Project Name] to [client/sponsor]. Change requested: [description]. Reason: [why needed]. Timeline impact: [X days]. Budget impact: [dollar amount]. Dependencies affected: [list]. Approval needed by: [date] to avoid further delay. Include a signature line for approval."
Prompt 30 — Build a resource utilization report
"Create a template for a weekly resource utilization report for a team of [size] on [Project Name]. Include: team member, planned hours, actual hours, utilization rate, tasks completed, and variance notes. Add a summary section: total team utilization %, any over/under-utilized individuals, and recommended adjustments."
7. Project Closure and Lessons Learned
How you close a project determines whether you learn from it. These prompts lock in the value before the team moves on.
Prompt 31 — Write a project closure report
"Write a project closure report for [Project Name], which completed on [date]. Include: project summary, original vs. actual timeline, original vs. actual budget, deliverables completed vs. planned, quality metrics, major risks that materialized, client/stakeholder satisfaction summary, and final disposition of all project assets."
Prompt 32 — Facilitate a lessons-learned session
"Create a lessons-learned facilitation guide for [Project Name]'s retrospective with [team size] people. Include: pre-session preparation (what data to pull), session agenda (60-90 min), 5 structured questions that surface honest insights without blame, method for prioritizing lessons, and output format for the written report."
Prompt 33 — Write a lessons-learned report
"Write a lessons-learned report for [Project Name]. Based on this project's experience: [brief notes]. Organize insights into: what worked well, what should be done differently, process improvements to implement, risks to watch on similar projects, and 3 specific recommendations for the next PM who runs a project like this."
Prompt 34 — Write a project team recognition email
"Write a project completion recognition email from [PM Name] to the full [Project Name] team. Reference 2-3 specific challenges the team overcame. Call out individual contributions if appropriate: [names and what they did]. Be specific — generic praise is forgettable. Under 200 words. Authentic, not corporate."
Prompt 35 — Write a client project close-out email
"Write a project close-out email from [PM Name] to [Client Contact] at [Client Company] for [Project Name]. Include: summary of what was delivered, comparison to original scope and timeline, confirmation of final deliverables handed over, any post-project support available, and a natural ask for a testimonial or case study."
The Complete PM Prompt System
These 35 prompts cover the 80% of project communication that follows a predictable formula. The remaining 20% — the judgment calls, negotiations, and crisis responses — is where your experience earns its value.
The Project Manager AI Prompt Pack includes 100+ tested prompts covering the full PM lifecycle, plus pre-built templates for status reports, risk registers, and stakeholder communications.
Use LAUNCH30 for 30% off — limited uses remaining.
Useful? Bookmark it or share it with a PM who's drowning in admin work.
Top comments (0)