ChatGPT for Project Management: From Notes to a Real Plan

Most project managers I meet are not short on tools. They are short on time between the tools. The plan sits in one file, the kickoff notes sit in a notebook, the status update is an email you rewrite every Friday, and the risks live in somebody’s head until the week they finally bite.

That gap is where ChatGPT for project management actually earns its keep. Not for writing a project charter nobody reads, but for the plumbing work between meetings that quietly eats an hour at a time. I have taught this to teams who were certain AI had nothing to offer a project manager, and the two tasks below are the ones that change their minds inside the first twenty minutes.

Both work in the free version, neither needs a connection to a company system, and you can try them this afternoon on a project you are already running.

ChatGPT for Project Management: Turn a Brain Dump Into a Real Work Breakdown

After a kickoff call you usually have a page of fragments: half a scope, three deadlines somebody said out loud, two names, and a vague worry about a vendor. Turning that into a task list is an hour of staring at a blank screen. Hand it over instead.

Open ChatGPT, start a new chat, and type this, then paste your raw notes underneath:

You are helping me plan a project. Below are my unedited notes from the kickoff call. Turn them into a work breakdown structure with no more than four phases. Under each phase, list the tasks. For every task give me: task name, a one-line description, the role that should own it, a duration estimate in business days, and what has to finish before it can start. Return it as a table. If something in my notes is too vague to estimate, flag it in a separate list instead of guessing. Notes:

What comes back is a table you can paste straight into Excel, Project, or Planner, with the dependency column already filled in. The part people do not expect is the second list, the one that says “these four items cannot be estimated yet.” That is your agenda for the next sponsor call, written for you.

Two follow-ups are worth knowing: Now give me the same table sorted by earliest possible start date gets you a draft schedule, and Which three tasks are on the critical path and why gets you a defensible answer to the question your boss asks first.

The gotcha: without that “flag anything too vague” instruction, the tool will happily invent a five-day estimate for work it knows nothing about, and those numbers look exactly as confident as the real ones. Keep the instruction in, and read every duration before it reaches a stakeholder. The estimates are a starting proposal for your team to argue with, not a plan.

Run a Ten-Minute Pre-Mortem Before the Slippage Starts

Risk registers get built once, at the start, when nobody knows anything yet, and then never touched again. A pre-mortem fixes that in ten minutes. Instead of asking what might go wrong, you assume it already did and work backwards.

Paste in your task list or timeline, then ask:

Act as a skeptical project reviewer. Here is my plan and timeline. Imagine it is six months from now and this project finished three weeks late and over budget. Give me the twelve most likely reasons that happened, ranked by likelihood. For each one give me: the risk in one sentence, the earliest warning sign I would actually notice, the role best placed to spot it, and one thing I can do this month to make it less likely. Do not give me generic risks like "poor communication" unless you can tie it to something specific in my plan.

The ranked list is useful, but the warning-sign column is what pays for itself. “Vendor is slow” is not actionable; “the vendor misses the first weekly check-in and reschedules” is something you can watch for. That column turns a document nobody reads into four or five things you are actively monitoring.

Drop the result into your risk register, put real names in the owner column, and bring the top five to your next steering meeting.

The gotcha: the tool only knows what you paste. It has never seen your organization or your vendors, so treat the output as a list of good questions for the people who have, not as findings. And check your company’s policy before pasting client names or contract terms into a public AI tool. Strip the identifying details first; the advice is just as good.

Plenty more on the calendar

If you would rather see this live, with the prompts typed out and the results picked apart as we go, I am running How to Use ChatGPT & Microsoft Copilot for Project Management on Wednesday, October 7. We cover the prompts above, where Microsoft Copilot fits in when your project data already lives in Microsoft 365, and how to pick which of the two tools to reach for on a given task.

If that date does not work, the full current schedule is on the front page of PCWebinars.com, and new dates go up as they are confirmed. Register for this one, or browse the list and find the session that fits what you are working on right now.

About your trainer

I’m Tom Fragale. I have been a computer trainer and consultant for more than 30 years, and I have taught well over 30,000 people how to get more out of the software they already own: Excel, Access, Power BI, Word, Outlook, and now the AI tools that sit on top of all of it, including Claude, ChatGPT, and Microsoft Copilot. My background is applied, not theoretical. Alongside the teaching I build real databases and reporting systems for clients in Excel, Access, and Power BI, so the examples I bring to class are the problems I ran into last week, not textbook exercises. I also publish free tutorials on YouTube and longer courses online.

If this was useful, there is a lot more where it came from at PCWebinars.com.