- Kicking off a project and pinning down scope
- Planning the work: breakdowns, milestones and dependencies
- Spotting risks and handling issues early
- Status updates and stakeholder emails that get read
- Meetings: agendas, notes and next actions
- Retrospectives and lessons learned
- How to get better results from these project prompts
- Frequently asked questions
These ChatGPT prompts for project managers help you scope a project, plan milestones, log risks, write status updates, run tighter meetings and hold useful retrospectives. Copy a prompt, paste it into ChatGPT (it works in Claude or Gemini too) and swap every [bracket] for your own details. My key tip: paste in real context, such as the brief or your notes, because the answer is only as good as what you give it.
Most small business owners I work with never set out to be project managers. A client says yes, the website needs rebuilding, a new service has to launch, and suddenly you're the one keeping a dozen moving parts in line while doing your day job too.
These are the prompts I'd hand anyone in that seat. They're grouped by the job you're doing, from the first conversation about scope to the final retrospective, and each one leaves [brackets] for your own details. If you'd like a refresher on the basics first, here's my plain guide to the key project management processes.
Kicking off a project and pinning down scope
Turn a messy brief into a project charter
Copy this prompt
Here's a rough project brief: [paste notes].
Turn it into a one-page project charter with the goal, what success looks like, who's involved, key dates and the questions I still need answered before we start.
Draw a clear line around scope
Copy this prompt
I'm starting a project to [describe project] for [client or team].
List what's in scope and what's out of scope, then flag the grey areas most likely to cause arguments later, with a suggested way to settle each one.
Plan the kickoff meeting
Copy this prompt
Plan a kickoff meeting for [project name] with [who's attending].
Give me a timed agenda for [length], the decisions we need to leave with, and three questions that will surface hidden assumptions early.
Map your stakeholders
Copy this prompt
List the stakeholders likely to care about [project], from these people and roles: [list them].
For each, note what they want, how much influence they have, and how often I should keep them informed.
Questions to ask before you commit
Copy this prompt
A client has asked us to [describe request].
Write the clarifying questions I should ask before I commit to a delivery date, grouped by goals, content, approvals and available people.
Planning the work: breakdowns, milestones and dependencies
Break a goal into tasks
Copy this prompt
Break the project [describe project and end result] into phases, then into tasks small enough for one person to finish in a day or two.
Present it as a nested list I can paste into [tool].
Milestones that mean something
Copy this prompt
Suggest five to seven milestones for [project] that each mark a real, checkable outcome rather than just a date.
For each one, describe what done looks like and who signs it off.
Find the dependencies
Copy this prompt
Here's my task list: [paste tasks].
Identify which tasks depend on others, which can run in parallel, and the chain of tasks that will decide our finish date. Show it as a simple table.
Reality-check a timeline
Copy this prompt
Our team of [number] people has [timeframe] to deliver [project] alongside normal work. Review this draft plan: [paste plan].
Point out where it's too optimistic and suggest where to add slack or trim scope.
Share the work out fairly
Copy this prompt
Here are the tasks [paste tasks] and the people available, with their strengths and current workload: [paste details].
Suggest who should own each task and flag anyone who looks overloaded.
Spotting risks and handling issues early
Small teams rarely have time for a formal risk process, which is exactly why a quick prompt helps. If your team feels stretched, you'll recognise a lot of what's in why project management is so hard for small teams.
Run a pre-mortem
Copy this prompt
Imagine it's the end of [project] and it has gone badly wrong.
Write the most likely reasons it failed, then turn each reason into a risk with an early warning sign and a way to prevent it.
Start a risk register
Copy this prompt
Create a risk register for [project] as a table with columns for risk, likelihood, impact, owner, warning sign and response.
Fill in eight realistic risks for a small team working on [type of project].
Triage a new issue
Copy this prompt
This problem has come up on [project]: [describe issue].
Help me judge how serious this is, who needs to know today, what my options are, and write a short message I can send the team.
Recover from a missed deadline
Copy this prompt
We've missed the deadline for [deliverable] by [length of delay] because [reason].
Give me three recovery options with the trade-offs of each, and a calm, honest note to the client explaining the new plan.
Catch scope creep politely
Copy this prompt
The client has asked for these extras: [list requests]. Here's the agreed scope: [paste scope].
For each extra, tell me if it's in scope, how much time it might add, and a polite way to say yes, no or later.Work with meWant AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Status updates and stakeholder emails that get read
Weekly status update
Copy this prompt
Turn these notes [paste notes] into a weekly status update for [audience].
Use the headings done, next, blocked and decisions needed. Keep it short and lead with anything they must act on.
Traffic light summary
Copy this prompt
Using this project information [paste details], give each workstream a red, amber or green status with one line explaining why.
Then write a two-sentence overall summary a busy director can read in seconds.
Deliver bad news well
Copy this prompt
Write an email to [stakeholder] telling them [bad news].
Be direct in the first line, explain the cause briefly without blaming anyone, give the new plan and say what I need from them.
Chase an approval
Copy this prompt
I've been waiting [time] for [person] to approve [item], and it's holding up [what's blocked].
Write a short, friendly follow-up that makes the impact clear and makes it easy for them to reply.
Bring someone new up to speed
Copy this prompt
Summarise where [project] stands for [new team member or stakeholder] who's joining today, using these notes: [paste notes].
Cover the goal, progress so far, open decisions and who to ask about what.
Meetings: agendas, notes and next actions
An agenda with a purpose
Copy this prompt
Write an agenda for a [length] meeting about [topic].
Start each item with the decision or outcome we need, give it a time slot and name who leads it. Add any reading people should do beforehand.
Messy notes into clear actions
Copy this prompt
Here are my rough meeting notes: [paste notes].
Pull out every decision, every action with an owner and a due date, and any open questions. Format it as a short follow-up email to the attendees.
Should this be a meeting at all?
Copy this prompt
I'm planning a meeting about [topic] with [attendees].
Tell me honestly whether it could be an email or a shared document instead, and if so, draft that message for me.
A daily check-in that surfaces blockers
Copy this prompt
Suggest a quick daily check-in format for a team of [number] working on [project], with three questions that surface blockers early.
Then write a short message introducing it to the team.
Retrospectives and lessons learned
Retro questions that get people talking
Copy this prompt
Write questions for a retrospective on [project or sprint] that get a small team talking openly about what helped, what got in the way and what we'd change, without anyone feeling blamed.
Turn retro comments into changes
Copy this prompt
Here's what the team said in our retrospective: [paste comments].
Group them into themes, pick the three that matter most, and turn each into a specific change we can try on the next project.
Write the lessons learned summary
Copy this prompt
Write a lessons learned summary for [project] using these notes: [paste notes].
Include what we planned, what happened, why it differed and what we'll do differently. Keep it short enough that people will read it.
Close the project cleanly
Copy this prompt
Create a close-out checklist for [type of project] covering handover to the client, files and logins, final sign-off, thanking the team, and anything we should save as a template for next time.
How to get better results from these project prompts
- Paste the real material. The brief, the task list, the meeting notes. ChatGPT can't plan what it can't see, and generic input gets generic plans.
- Say who'll read it. A status update for a client reads very differently from one for your own team, so name the audience every time.
- Ask it to question you first. Add "ask me any questions you need before you start" and you'll catch gaps before they become rework.
- Keep one project in one place. ChatGPT has projects, so you can keep a client's brief, notes and drafts together rather than starting from scratch each time.
- Check every date and name yourself. It doesn't know your calendar or the promises you've already made.
- Leave out anything confidential that your client hasn't agreed you can share.
If you'd like your team to build prompts like these together around your own projects, this is how my AI workshops run.
Frequently asked questions
Can ChatGPT replace a project manager?
No. It's very good at the writing and structuring side of the job, such as plans, updates and meeting notes, but it can't hold people to account, read the room or make judgement calls about your client.
What's a good ChatGPT prompt for a project plan?
Give it the goal, the deadline, the team and any fixed constraints, then ask it to break the work into phases and tasks small enough for one person to finish in a day or two. Ask it to flag dependencies and anything that looks too optimistic.
How do I use ChatGPT for project status reports?
Paste your rough notes and ask for an update under the headings done, next, blocked and decisions needed. Tell it who the reader is and ask it to put anything they must act on at the top.
Is it safe to paste project details into ChatGPT?
Treat it like any other online tool. Leave out confidential client information, passwords and anything you've agreed to keep private, and describe sensitive situations in general terms instead.
Do these prompts work in Claude or Gemini?
Yes. They're written in plain language, so you can paste them into ChatGPT, Claude or Gemini and get a useful first draft from any of them.


