Claude for Project Managers: Spot Risks Before Dates Slip
Every project manager I have taught has a version of the same Thursday afternoon. The plan looked fine on Monday. Then one vendor slips three days, and the rest of the week goes to working out what else just moved, and explaining it to six people who each want a different level of detail. That is the part of the job nobody puts in the job description, and it is exactly where Claude for project managers starts to pay for itself.
Let me be clear about what I mean, because there is a lot of noise on this subject. Claude is not going to run your project. It does not know your stakeholders, it cannot see inside your scheduling tool, and it will cheerfully agree with a bad plan if you let it. What it is good at is the reading-and-reasoning work that sits around the schedule: looking at a plan you already built and telling you where it is thin, and working out what a date change actually costs you.
Here are two things you can do with it this afternoon. Both assume you already have a plan written down somewhere, whether that is a task list in Excel, an export from Project or Smartsheet, or a decent bulleted outline.
Claude for Project Managers, Tip One: Stress-Test the Plan Before Someone Else Does
Paste your task list into Claude as plain text, or paste the sheet straight in. You want at minimum one row per task with the owner, the duration, and what it depends on. Then give it a job, not a question:
You are a skeptical program manager reviewing this plan for the first time. For each risk you find, give me: (1) the exact task row it attaches to, (2) what goes wrong, (3) the earliest signal I would see if it were happening, and (4) one thing I could do this week to reduce it. Only list risks you can anchor to a specific row. If a risk applies to the plan as a whole, say so explicitly rather than attaching it to a random task.
What comes back is a risk register you can paste into a status deck. The useful part is not the obvious items. It is the sequencing ones: two tasks assigned to the same person in the same week, a dependency on a team that has not been told yet, a testing window that assumes nothing fails. Those are visible in the plan but invisible to the person who wrote it.
The gotcha: Claude will produce confident, professional-sounding risks that have nothing to do with your plan. That is why the prompt forces it to name the row. Anything it cannot anchor, delete without reading twice. Six risks that point at real rows beat twenty that read like a textbook chapter.
Tip Two: Work Out What a Slipped Date Actually Costs
This is the one that saves the afternoon. When something slips, give Claude the dependency chain and the slip, and ask for the cascade rather than an opinion:
Task 14 finishes 4 working days later than planned. Using the dependencies below, tell me: which downstream tasks move and by how much, which ones have enough float to absorb it, what the new project end date is, and the two cheapest options to recover the time. Show your date arithmetic for each task you move so I can check it. Treat Monday to Friday as working days and ignore holidays.
Ask for the answer as a table. You can paste that straight into Excel, and paste the recovery options straight into the email you were dreading. The value is speed: the same reasoning done by hand across thirty tasks is an hour of squinting at a Gantt chart.
The gotcha, and it is a real one: Claude is not a scheduling engine. Date arithmetic across weekends is the single thing I see it get wrong most often in class. That is why the prompt tells it to show its work per task and to state its working-day assumption. Spot-check three rows against your actual calendar before anything goes to a stakeholder. If your organization has holidays or a four-day week, say so in the prompt, because it will not guess.
Plenty more on the calendar
If you want to see this done live, I am running Using Claude to Be More Productive as a Project Manager on Thursday, October 29. We build a risk register from a real plan, replan after a slip, turn a messy stakeholder thread into a decision log, and write status updates that different audiences will actually read. You can ask questions as we go.
The full current schedule is on the front page of PCWebinars.com, with new dates going up as they are confirmed. Register for this one if the topic fits, or browse the others, because there is usually something on Excel, Power BI, Copilot, or one of the AI tools running within the next week or two.
About your trainer
I am 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 rather than textbook exercises. I also publish free tutorials on YouTube and longer courses online.
If that sounds useful, the schedule, the recordings, and the free material are all at PCWebinars.com.
