Claude for Project Management: Two Ways to Cut Status Work

Every project manager I have taught has the same two hours sitting in their week that they would like back. One goes to the status report — digging through a chat channel, three email threads, and a task board to work out what actually moved. The other goes to the follow-up questions that arrive because the status report left something out. The work is not hard. It is reconstruction, every week, from scraps. That is exactly the gap where Claude for project management pays off, and it is narrower and more practical than the hype around AI suggests.

I am not suggesting you let an AI decide whether your project is green or red. The useful version is the opposite: you hand it the raw material you already have — last week’s notes, the exported task list, the meeting transcript — and make it do the sorting, while you keep the judgment. That is the difference between a draft you have to rewrite and a draft you can send.

Here are the two setups I would build first. Each takes about ten minutes to try.

Claude for project management, part one: turn the week’s mess into a status update

Start a Project in Claude rather than a plain chat. In the left sidebar, click Projects, then New project, and name it after the project you are running. A Project holds files and instructions that stay loaded for every conversation inside it, so you are not re-explaining your world every Monday morning.

Into the project knowledge, upload the things that do not change much: the charter, the milestone list, and one status report you were happy with. That last file is the important one — it teaches the format far better than any description can.

Then each week, upload the raw material and use a prompt shaped like this:

Here are this week's raw inputs: my meeting notes, the task export, and the client email thread. Write the weekly status report in the same format as the example in project knowledge. For each workstream give me: what moved, what did not, and what is now at risk. Only use what is in the material I just gave you. If something in the format has no supporting information, write "no update this week" instead of filling it in.

That last sentence is the whole trick. Without it you get a confident, tidy report with invented progress in the thin spots. With it, the blank spaces stay blank, and the blanks are usually the most useful thing on the page — they are the workstreams nobody reported on.

The gotcha: dates. Claude will happily restate a deadline it inferred rather than one it read. Before you send anything, add List every date you used and quote the line it came from. That has caught a wrong milestone date for me more than once.

Part two: build a real risk and blocker list from the same material

Most risk registers go stale because updating one means re-reading everything. That is the job to hand over.

Paste in your last two status reports and ask:

Compare these two status reports. List anything that was flagged as a risk or blocker in the earlier one and is not resolved in the later one. For each, quote the sentence from each report that shows it is still open, and say how many weeks it has been carried.

What comes back is the list you cannot get from a task board: the items that keep getting mentioned and never get closed. The week count is what makes it land in a steering meeting. “Open five weeks” is a different conversation from “still in progress.”

You can push it one step further:

• Group these open items by who owns them. — the real bottleneck is usually one person with six items.
• Draft a three-sentence escalation note for the two oldest items, written for an executive who has not been following the detail.

The gotcha: require the quotes. If you ask for a risk list without quote the sentence, you will get plausible, generic project risks — scope creep, resource constraints — that have nothing to do with your project. The quote requirement forces it to stay inside your documents, and anything it cannot quote simply does not appear.

Plenty more on the calendar

If you want to see this done live, with real files and the mistakes handled as they happen, I am running a session on Claude for Project Management on Thursday, October 22 at 1:00 PM Eastern. We cover setting up a project workspace, the status report workflow above, risk and blocker tracking, and how to keep the whole thing honest about what it does and does not know. You can register for Claude for Project Management here.

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, or browse the others — there is usually something on Excel, Copilot, Power BI, or Claude within the next week or two.

About your trainer

I’m Tom Fragale. I’ve been a computer trainer and consultant for more than 30 years, and I’ve 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: 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 like the kind of help your team needs, the full schedule and the recorded courses are both at PCWebinars.com.