Claude for Project Management: Notes to Status Report

Every project manager I teach has the same Thursday afternoon. The work is done, the week actually went fine, and now you are sitting with four sets of scribbled call notes trying to turn them into a status update that somebody above you will skim in about nine seconds. The writing takes an hour. The skim takes nine seconds. That math has bothered me for years, and fixing it is the first thing I show people when we sit down with Claude for project management.

No AI tool manages your project. It will not chase the vendor, and it will not make a call you are paid to make. What it will do is take two chores off your desk — writing the weekly update, and re-explaining your project to a blank screen every time.

Here is exactly how I do both. Ten minutes each, no class required.

Claude for Project Management: Paste Your Notes, Get a Status Report

Start a new chat at claude.ai and paste in your raw notes exactly as you took them — half sentences, misspellings, “ck w/ Dana re: PO” and all. Do not clean them up first; that is the work you are trying to avoid. Then give it a prompt built like this one:

Below are my raw notes from this week on the Riverside migration. Write a weekly status update for the steering committee. Give me: (1) three to five bullets of progress, each naming the deliverable; (2) a table of open risks with owner and due date; (3) a short list of decisions you need from me. Use only what is in the notes. If an item has no owner or no date in the notes, put it in a final section called "Needs confirmation" instead of guessing.

That last sentence is the whole trick, and it is the part almost everyone leaves out. Left to itself, Claude writes beautifully and quietly fills gaps with plausible invention — a due date that sounds about right, an owner who makes sense. The “Needs confirmation” instruction turns that habit into a feature: instead of a confident wrong date, you get a short checklist of the things you actually have to go look up. I have watched people take a sixty-minute report down to about twelve minutes.

Two practical additions. First, add Put the update in an artifact so I can edit it. and the draft opens in a side panel as a clean document you can copy straight into email or your PM tool, rather than being tangled up in the chat. Second, tell it today’s date whenever dates matter. It is not reliably aware of what day it is, so “next Friday” in your notes means nothing to it — write “Friday, September 25” into the prompt and the output comes back right.

The gotcha: check any number you did not personally write. Percent complete, hours burned, budget remaining. If it was not in your notes, it does not belong in your report.

Build a Project So You Stop Re-Explaining Everything

The second chore is invisible until somebody points at it. Every new chat starts from zero, so you spend five messages saying who the vendor is and which version of the plan is current. Claude’s Projects feature ends that.

In the left sidebar click Projects, then Create project, and name it after the real project. Inside you get two things worth your time:

• Project knowledge — upload the current schedule, the charter, the RACI, last month’s approved status report. Every chat inside that project can see all of it without you attaching a thing.
• Custom instructions — a standing note that applies to every conversation there. Mine usually reads something like: I am the PM on this project. Always use the dates in the uploaded schedule and never invent one. Use our team members' names, not job titles. Keep status updates under 250 words. If the schedule and my notes disagree, say so rather than picking one.

Now the status-report prompt above shrinks to two lines, because the context is already sitting there. And you can start asking harder questions of the plan itself. My favorite, run once a month: Using the uploaded schedule, list every task that starts before its predecessor finishes, every task with no named owner, and any week where one person owns more than three overlapping tasks. That is a dependency and workload audit you would otherwise do by squinting at a Gantt chart for an hour. It takes about twenty seconds.

The gotcha here is stale knowledge. Project knowledge is a folder, not a live link to your plan. When the schedule changes, delete the old file and upload the new one. Leave both in there and Claude will blend them, and you will get a confident answer built on dates that expired three weeks ago.

Plenty more on the calendar

If you would rather watch this done live than read about it, I am running Claude For Project Management on Tuesday, September 15. We build the status-report prompt together, set up a real project with knowledge files and custom instructions, and run the risk-register and dependency-audit work against an actual schedule, with time for your own questions at the end.

The full current schedule lives on the front page of PCWebinars.com, and new dates go up as they get confirmed. Register for this one, or browse the others — there is usually something on Excel, Power BI, Copilot, or Claude within the next week or two.

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: 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 to you, the full schedule and the rest of my training library are waiting at PCWebinars.com.