Best ChatGPT Prompts for Project Managers (2026)

You are a senior project manager. Draft a project charter from the notes below. Include: the business problem, the objective stated as a measurable outcome, in-scope and explicitly out-of-scope items, key deliverables, the named stakeholders and their role in decisions, assumptions, constraints, and the success criteria we will be judged on at the end. Where the notes are silent, write the question I need to ask instead of inventing an answer. Notes: [paste].

Break the deliverable below into a work breakdown structure, three levels deep. For each leaf task give: a clear done-definition, the role that owns it, and the tasks it depends on. Flag any task that is larger than [duration, e.g. 5 days] as needing a split, and list the work that teams usually forget on projects like this (environments, access, data migration, training, handover). Deliverable and context: [paste].

Build a risk register for this project: [paste scope, timeline, team, and dependencies]. For each risk give: the risk stated as a cause-event-consequence sentence, likelihood and impact on a 1 to 5 scale with your reasoning, the early warning signal that would tell us it is materializing, a mitigation we can act on now, and a contingency if it lands anyway. Order by likelihood times impact and separate risks I own from risks I can only escalate.

Write a status report for [project] aimed at an executive sponsor who has 90 seconds. Structure: overall status (green, amber, or red) with the single reason for it, progress since [date], what is at risk and the impact if it slips, decisions I need from them with a deadline for each, and next milestones. Lead with the headline, no filler, and be honest about amber instead of managing it into green. Raw notes: [paste].

A stakeholder is requesting this change: [paste the request]. Given the current plan below, analyze the impact on schedule, budget, scope, quality, and team load. Give me three options: absorb it, trade it against something already planned (name what), or defer it, with the consequence of each. Then draft a short reply to the requester that says no to the free version without saying no to the person. Current plan: [paste].

Here is our estimate and plan: [paste tasks, durations, and assumptions]. Act as a skeptical delivery lead. Identify the assumptions holding this date together, the tasks most likely to be underestimated and why, the dependencies outside our control, and where the plan has no slack. Then give a realistic range with a best case, expected case, and the specific conditions that would produce the worst case. Do not just add a percentage buffer.

From the stakeholder list below, build a map by influence and interest, and a communication plan. For each stakeholder or group give: what they care about most, what they need from me, the format and frequency of updates, and the one thing that would make them block this project. Flag anyone whose expectations look misaligned with the current scope. Stakeholders: [paste names, roles, and what you know about them].

Build an agenda for a [length] meeting about [topic] with [attendees and roles]. For each item give: the purpose (decide, inform, or discuss), the time box, who leads, and the pre-read needed. Cut anything that could be an email and say so. After the meeting I will paste the notes back to you: turn them into decisions made with the reasoning, action items with a named owner and date, and open questions, and flag anything that was discussed but never actually decided.

From the task list with durations and dependencies below, identify the critical path, the tasks with the least slack, and the points where a single external dependency could stall multiple workstreams. Recommend what to re-sequence, what to start earlier, and what to fast-track or run in parallel, and state the risk each change introduces. Tasks: [paste].

Design a [length] retrospective for the team below after [milestone or project phase]. Give me: an opening that makes it safe to be honest, a structure for gathering what to keep, drop, and change, two prompts specifically aimed at surfacing the things people usually leave unsaid, and a way to close on a small number of committed improvements with owners. Then tell me how to handle it if the team stays quiet or if one person dominates. Team context: [paste].

Draft an escalation email about [the blocker, with dates and what has already been tried]. State the facts and the impact on the committed outcome, avoid blame and naming individuals, present the two or three resolution options with your recommendation, and ask for a specific decision by a specific date. Under 180 words, calm and factual.