Claude for Project Managers: Two Ways to Cut the Admin
Every project manager I have taught has the same two hours in their week that nobody ever scheduled. When people ask me about Claude for project managers, they usually want to know whether it can run the project. It cannot. What it can do is hand those two hours back to you.
The first hour goes to turning a week of scattered emails, chat messages and stand-up notes into a status report somebody will actually read. The second goes to a risk log that has not been touched since kickoff, and that everyone quietly agrees is fiction.
Here are the two things I demonstrate in class. Neither one needs a plugin, an integration, or a ticket to IT. You paste text into a chat window and you read what comes back.
Turn a Week of Messy Updates into a Status Report
Open a new chat. Paste in everything you have from the week: the raw text of five or six emails, your stand-up notes, the two paragraphs somebody sent you on Teams. Do not clean it up first. The mess is the point.
Then type a prompt shaped like this:
Below are my raw notes and emails from this week on the Contoso migration. Write a status report for a steering committee that has 5 minutes. Use these four headings: Progress this week, Slipping or at risk, Decisions I need from you, Next week. Under each heading use bullets, max 15 words per bullet. If something in my notes is ambiguous, list it at the bottom under "Questions for Tom" instead of guessing.
Two things make that prompt work. First, you told it the audience and the time budget, so it strips out the detail that only you care about. Second, that last sentence is the whole trick. Without it, an AI tool will quietly invent a plausible-sounding date or owner to fill a gap. With it, you get a short list at the bottom of exactly the things you were fuzzy about, which is usually the most useful part of the output.
The gotcha: the first draft will sound like a press release. Reply with Rewrite it plainer. No adjectives. If a date slipped, say the old date and the new date. That second pass takes ten seconds and is what makes it sound like you wrote it.
Claude for Project Managers: Build the Risk Register You Keep Postponing
Most risk registers die because the first blank row is the hardest thing in the world to fill in. So do not start with a blank row. Start with the project plan you already have.
Paste in your scope statement, your milestone list, or even just a plain description of the project in a few paragraphs. Then:
Based on this plan, list 12 risks to this project. For each one give me: the risk in one sentence, whether the likelihood is High/Medium/Low, whether the impact is High/Medium/Low, and one concrete mitigation I could start this month. Put it in a table. Include at least three risks that are about people or dependencies rather than technology.
That last sentence matters more than it looks. Left alone, these tools hand you twelve variations on “the server might be slow.” The risks that actually sink projects are a key person leaving, a vendor missing a date, or a department that never agreed to the scope in the first place. You have to ask for them.
You will keep maybe eight of the twelve. That is fine. Editing a list somebody else wrote takes fifteen minutes. Writing it from nothing takes an afternoon you will never schedule.
The gotcha: the likelihood and impact ratings are a starting point, not an assessment. It does not know your organization, your vendors or your history. Change the ratings yourself before anyone sees the register, or you are presenting a guess as a finding.
Plenty more on the calendar
If you want to see both of these done live, with real project documents and time for your own questions, I am running Using Claude to Be More Productive as a Project Manager on Thursday, October 29. We go further than the two tips above: building a project charter from a kickoff conversation, drafting stakeholder communications for three different audiences at once, and turning a two-hour meeting transcript into an action list with owners.
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 have a look through the others and find the session that fits what is on your desk right now.
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 teaching, I build real databases and reporting systems for clients in Excel, Access and Power BI, so the examples I use in class are the problems I ran into last week, not textbook exercises. I also publish free tutorials on YouTube and longer courses online.
If any of that sounds useful, come and see what is scheduled at PCWebinars.com.
