AI for Project Manager
Status reporting alone costs you 2–4 hours every week — the same data reformatted for different audiences, pulled from five different tools, translated into executive language under deadline. Add 45–90 minutes of meeting notes after every major call, and a significant chunk of your week is going to documentation that follows predictable patterns. These guides show you how to draft status reports, meeting summaries, risk registers, and stakeholder communications in minutes instead of hours.
Try right now
Copy a prompt, paste into ChatGPT, Claude, or Gemini
Works with any free AI chatbot, no signup needed
An immediate analysis of your team's allocation data identifying over-allocations, the specific weeks affected, and suggested rebalancing options.
Here is my team's resource allocation for the next [X] weeks: [paste table or list of person, task, % allocation per week]. Identify over-allocations (>100%), flag which weeks are affected for each person, and suggest rebalancing options — either by shifting tasks or flagging work to deprioritize.
View full prompt →Tip: Paste the allocation data as a table — person, task, and % per week — rather than describing it in prose. The AI's rebalancing suggestions are starting points; factor in skill requirements and client preferences before acting on any recommendation.
A structured stakeholder map with influence and interest ratings, each stakeholder's likely concerns, and a recommended engagement approach — organized as a table.
Create a stakeholder analysis for a [project type] project. Stakeholders: [list names/roles]. For each: rate influence (H/M/L), interest (H/M/L), likely concerns, current attitude (supportive/neutral/resistant), and recommended engagement approach. Format as a table.
View full prompt →Tip: Update the "attitude" column based on your actual read of each person — the AI defaults to "neutral" and your real knowledge matters most here. The engagement approach column is worth reviewing carefully; it surfaces options you might not have considered for resistant stakeholders.
A timed, outcome-focused agenda for any meeting type — standup, steering committee, kickoff, or retrospective — that keeps discussions on track.
Create a [duration]-minute [meeting type] agenda. Attendees: [roles]. Context: [1-2 sentences on project status]. Goal: [specific decision or outcome needed]. Include timed sections, owner for each item, and a pre-read recommendation if relevant.
View full prompt →Tip: State the specific decision or outcome needed — "align on go/live date" produces a tighter agenda than "project update." Ask for a parking lot section if your meetings tend to drift; it gives you a structured way to defer scope-expanding questions.
A fully planned retrospective session with a fresh format, timed sections, facilitation prompts, and an action capture method — ready to run without additional prep.
Design a [duration]-minute retrospective for a [team size]-person team struggling with [specific issue, e.g. scope creep / unclear requirements]. Make it engaging, not the standard Start/Stop/Continue. Include: warm-up, main format with prompts, action capture method, timing for each section.
View full prompt →Tip: Name the specific issue your team is struggling with (not just "the last sprint") — that's what drives the AI toward a format that actually addresses it. Ask for three format options if you're unsure, then choose based on your team's maturity and how much psychological safety exists.
A formal change request document with scope, schedule, and budget impact clearly articulated — ready for sponsor review and sign-off.
Draft a formal change request. Original scope excluded: [item]. Client now requests: [change]. Reason: [business driver]. Impact: +[X weeks], +$[amount], requires [resources]. Format: CR title, description, justification, scope/schedule/budget impact, options considered, recommendation.
View full prompt →Tip: If budget or schedule figures are estimates, add that caveat yourself before sending — the AI presents numbers with false precision unless you flag the uncertainty. List the options you've actually considered rather than leaving that section generic.
A structured 2–3 page project charter draft covering executive summary, scope, out-of-scope items, assumptions, constraints, risks, and success criteria.
Generate a project charter. Client: [type]. Objective: [goal]. Timeline: [X months]. Budget: [$amount]. Key stakeholders: [list roles]. Deliverables: [list]. Include: executive summary, scope, out-of-scope, assumptions, constraints, top 3 risks, success criteria.
View full prompt →Tip: Always have delivery leadership review commercial or contractual language before sign-off — the AI fills in standard language for assumptions and constraints, but those sections often need project-specific adjustments. Add out-of-scope items explicitly to avoid scope creep later.
A professionally worded email informing a stakeholder of a schedule delay — empathetic in tone, solutions-focused, and ready to personalize before sending.
Draft a professional email to [stakeholder title] notifying them the [deliverable] is delayed by [X weeks] due to [reason]. Be empathetic but confident. Propose a revised date, outline next steps, and request a brief call this week. Tone: direct, solutions-oriented.
View full prompt →Tip: Review the output for accuracy and add any relationship context the AI can't know — the delay reason and proposed path forward are placeholders until you validate them. Add "make this warmer" or "make this more concise" to tune the tone for the specific stakeholder.
A formatted RAG (Red/Amber/Green) status report ready for your project sponsor or client, drafted from your raw project notes.
You are an experienced PM. Write a weekly status report for a non-technical executive. Format: Overall Status (RAG + 1-line reason), 3 Accomplishments, 3 Upcoming Milestones, 2 Risks with mitigations, Decisions Needed. Project: [name]. Notes: [paste notes]
View full prompt →Tip: Paste your raw notes exactly as you have them — bullet points, partial sentences, whatever you've got. If the status color feels off, add "set overall status to Amber — here's why: [reason]" and it will adjust the framing accordingly.
A table of 15 project-specific risks with probability, impact, and suggested mitigations — ready to bring to your team for review.
I'm managing a [X-month] [project type] for a [company size/type]. Key dependencies: [list 2-3]. Generate a risk register: 15 risks, each with probability (H/M/L), impact (H/M/L), risk owner role, and a 1-sentence mitigation. Format as a table.
View full prompt →Tip: List your 2-3 key dependencies explicitly — those are where the most project-specific risks live and the AI will focus there. Follow up with "add 5 more risks specific to [constraint]" to go deeper on any category that matters most for your project.
A populated RAID log — Risks, Assumptions, Issues, Dependencies — with initial entries across all four categories, ready for team review.
Generate a RAID log for a [X-month] [project type] engagement. Client: [industry/size]. Key workstreams: [list 2-3]. For each category (Risks, Assumptions, Issues, Dependencies) provide 4-5 entries with description, owner role, and status. Format as 4 separate tables.
View full prompt →Tip: Add the project-specific constraints the AI can't know — known personnel limitations, client system restrictions, or hard deadlines — after generating the initial log. Use this in your project initiation meeting so the team reacts to existing entries rather than generating from scratch.
A concise 1-page summary of a long report, email thread, or document — formatted for meeting attendees who need to be prepared without reading the full source.
Summarize the following document into a 1-page pre-read brief for a [audience type, e.g. executive steering committee]. Include: key findings (3-5 bullets), open decisions needed, and recommended reading time. [Paste document text]
View full prompt →Tip: If a critical nuance gets lost in the summary, paste that specific section back in and ask the AI to expand on it. Specify the audience (e.g., "executive steering committee") so the level of detail and terminology match who will actually read it.
A clear, professional escalation memo documenting a project issue with impact analysis, options, and a recommended decision — ready for sponsor or steering committee review.
Draft a project escalation memo. Issue: [describe the problem]. Impact if unresolved: [timeline/budget/quality effect]. Options: [list 2-3 options]. Recommended decision: [your recommendation]. Audience: [sponsor/steering committee]. Format: Issue Summary, Impact, Options Considered, Recommendation, Decision Requested.
View full prompt →Tip: Fill in the Options section with choices you've actually considered — the AI presents them neutrally, which is useful when the situation is politically sensitive. State your recommendation explicitly even if you're uncertain; a hedged recommendation is still better than no recommendation for a sponsor who needs to act quickly.
Use AI in your tools
AI features built into tools you already have
No new subscriptions, just features you may not have noticed
Set up an AI assistant
Step-by-step guides for dedicated AI tools
10 to 30 minute setup, then ongoing time savings
Go further
Advanced workflows, automation, and custom AI setups
For when you’re ready to connect tools and automate
Recommended Tools
5Ranked by relevance for project manager
- 1
ChatGPT
Weekly Status Report Generation, Project Risk Register Population + 6 more
- 2
Fireflies.ai
Meeting Notes & Action Item Extraction
- 3
Atlassian Rovo
Jira Backlog Refinement & Ticket Writing
- 4
Smartsheet AI
Automated Project Dashboard Summary
- 5
Gamma.app
Presentation Deck Building (Kickoff / Steering Committee)
Common questions
- What is the best AI tool for a project manager?
- 1. ChatGPT: Weekly Status Report Generation, Project Risk Register Population + 6 more. 2. Fireflies.ai: Meeting Notes & Action Item Extraction. 3. Atlassian Rovo: Jira Backlog Refinement & Ticket Writing.
- How can a project manager use ChatGPT or another AI chatbot?
- Start with copy-paste prompts that work in any free chatbot. For example: An immediate analysis of your team's allocation data identifying over-allocations, the specific weeks affected, and suggested rebalancing options. A structured stakeholder map with influence and interest ratings, each stakeholder's likely concerns, and a recommended engagement approach — organized as a table. A timed, outcome-focused agenda for any meeting type — standup, steering committee, kickoff, or retrospective — that keeps discussions on track.
- Do I need technical skills to start?
- No. Level 1 prompts work in any free AI chatbot with no signup beyond the chatbot itself: copy the prompt, fill in the bracketed details, and paste it in. Later levels add AI features in tools you already use, then dedicated AI tools and automation.
New to AI?
The Big Four AI Assistants
ChatGPT, Claude, Gemini, and Grok do roughly the same thing. Pick one and start.
Four Levels of AI Skill
From your first prompt to building automated workflows. Where are you now?
How to Keep Up with AI
The landscape changes fast. A low-effort system to stay informed without drowning.
We update this guide when the tools change. See what's changed →