Project Management Prompts — Free AI Prompts (M365 Copilot)

Create a lessons learned document for [PROJECT]. Structure: (1) Project overview (scope, timeline, outcome), (2) What went well (5-7 items with impact), (3) What could improve (5-7 items with root cause), (4) What we would do differently, (5) Recommendations for future projects, (6) Key metrics vs plan. Get input from: [TEAM MEMBERS]. Tone: constructive and forward-looking.

Create a project notebook template for [PROJECT NAME] with these sections: (1) Project Charter — objective, scope, stakeholders, success criteria, (2) Meeting Notes — template for recurring meeting minutes, (3) Decision Log — table with Date, Decision, Rationale, Owner, (4) Action Item Tracker — Task, Owner, Due Date, Status, (5) Risk & Issue Log — structured risk register, (6) Key Contacts — stakeholder directory with roles and contact details, (7) Reference Documents — links to important files and resources, (8) Lessons Learned — ongoing capture of what went well and what to improve, (9) Status Dashboard — weekly RAG indicators template. Each section should have a brief description of what goes there.

Create a detailed project plan from this brief. Include: (1) Project Overview — objective, scope, success criteria, (2) Phases — break the project into 3-5 logical phases, (3) Tasks — list tasks within each phase with estimated duration, (4) Milestones — key checkpoints with dates, (5) Dependencies — which tasks depend on others, (6) Resource Requirements — roles needed for each phase, (7) Risk Register — top 5 risks with likelihood, impact, and mitigation, (8) Communication Plan — who gets updated, how often, through what channel. Present as a structured document with tables.

Write a project scope document for [PROJECT]. Include: (1) Project objectives and success criteria, (2) In-scope deliverables (be specific), (3) Out-of-scope items (explicitly stated), (4) Assumptions, (5) Constraints, (6) Dependencies on other teams, (7) Acceptance criteria, (8) Change control process. This document prevents scope creep — be precise.

Design a project status dashboard for [PROJECT/PORTFOLIO]. Include: (1) Overall status indicator (RAG), (2) Timeline progress with milestone markers, (3) Budget tracker (planned vs actual), (4) Risk summary with top 3 risks, (5) Key metrics and KPIs, (6) Recent accomplishments, (7) Upcoming milestones (next 2 weeks), (8) Decisions needed. One-page format for weekly reporting.

Write a resource request for [PROJECT] requesting [WHAT — additional headcount / budget / tools / time]. Include: (1) Current resource allocation, (2) Gap analysis showing what cannot be delivered without the resource, (3) Impact of not getting the resource (delays, quality, risk), (4) Options (full request, partial, alternative), (5) ROI or payback, (6) Timeline needed. Present for [APPROVER — PMO / director / finance].

Create a retrospective document for [PROJECT/SPRINT/QUARTER]. Structure it using the Start-Stop-Continue framework: (1) START — things we should begin doing (new practices, tools, habits), (2) STOP — things we should stop doing (wasteful activities, bad habits), (3) CONTINUE — things that are working well and should keep going. For each section, provide 5 thought-provoking questions the facilitator should ask. Then include: (4) Top 3 Action Items — specific improvements with owners and deadlines, (5) Celebration — highlight one team achievement to recognise.

Create a comprehensive risk register for [PROJECT/INITIATIVE]. For each risk provide: (1) Risk ID, (2) Risk Description — clear statement of what could go wrong, (3) Category — Technical, Resource, Schedule, Budget, External, (4) Likelihood — High/Medium/Low, (5) Impact — High/Medium/Low, (6) Risk Score — Likelihood × Impact, (7) Mitigation Strategy — specific actions to reduce the risk, (8) Contingency Plan — what to do if the risk materialises, (9) Owner — who monitors this risk. Identify at least 10 risks. Format as a table sorted by risk score (highest first).

Create a stakeholder map for [PROJECT]. For each stakeholder: (1) Name and role, (2) Interest level (High/Medium/Low), (3) Influence level (High/Medium/Low), (4) Current attitude (Supportive/Neutral/Resistant), (5) Engagement strategy, (6) Communication frequency. Categorise into quadrant: Manage Closely, Keep Satisfied, Keep Informed, Monitor.

Draft a stakeholder update for [PROJECT NAME] covering [TIME PERIOD]. Include: (1) RAG Status — Red, Amber, or Green with clear justification, (2) Executive Summary — 2-3 sentences on overall progress, (3) Key Accomplishments — what was delivered this period, (4) Upcoming Milestones — what is due next with dates, (5) Risks & Issues — any current blockers with mitigation actions, (6) Budget Status — on track / variance, (7) Decisions Needed — anything requiring stakeholder input, (8) Next Steps — priorities for the coming period. Keep it to one page. Tone: confident, transparent, concise.