Most project managers meet AI the same way: a blank chat box, a vague ask, and an answer that's confidently wrong on the one detail that matters — an invented date, a softened risk, an owner who never agreed to anything. The problem isn't the model. It's that ad-hoc prompting has no discipline, and a progress rollup or risk register is exactly where invented detail does real damage.
A project manager should use AI the way you'd use a sharp junior PM: hand it the facts you actually have, make it flag every gap instead of filling it, and keep the judgment call yours. The prompts below are built that way. Each one works only from what you paste or attach, marks anything missing as "Not stated" rather than guessing, and leaves bracket placeholders like [Client] literal so nothing client-identifying leaks before you've anonymized it. The output is a fast first draft with its own gap list attached — and that gap list is usually the real value.
That's the whole method: proven, repeatable workflows with guardrails beat clever one-off prompting every time, because the structure is what makes today's progress rollup comparable to last week's and what stops a fuzzy scope from becoming a month-three fight. Paste a prompt, fill the fields, review the flags, send.
Work Task 13 — Progress & Coordination Synthesis
Roll Up the Daily/Weekly Progress Round
Collapses a round of messy team updates — a Slack/Teams paste, a transcript, or your own notes — into a digest under 200 words: moved / blocked / at risk / needs a decision, with a named owner on every unblock. It never invents progress — a vague 'still working on it' gets filed under At risk, not Moved forward.
You are my PM assistant. Below are the raw progress updates from my team for this round — pasted from Slack/Teams, a transcript, or my own notes. They are messy and out of order.
Raw updates:
[PASTE TODAY'S RAW PROGRESS UPDATES HERE — for each person: Name — their raw text]
Produce a progress digest in exactly this structure:
**Moved forward** — what actually progressed since the last round (one line each, name in brackets)
**Blocked** — every blocker, with: who is blocked, what on, and the single person who owns the unblock (infer it if not stated, and mark "[owner unconfirmed]")
**At risk** — anything that did not move and has a deadline this week
**Needs a decision** — open questions where the team is waiting on someone
Rules: do not invent progress. If an update is vague ("still working on it"), list it under At risk, not Moved forward. Keep the whole thing under 200 words — it goes in a channel, not a report.
Work Task 5 — Risk, Issue & Scope-Change Triage
Surface the Project Risks You Missed (Risk Register / RAID)
Reviews your brief, scope, or WBS and returns 10–15 specific, categorized risks you probably haven't planned for — each with likelihood, impact, and one mitigation. Run it at kickoff and every phase transition to feed your risk register or RAID log.
You are a senior project management consultant with 20 years of experience. Review my project information and identify the top risks I have not explicitly planned for.
Project information — work from the project brief, scope, or WBS I've attached to this conversation. (No attachment? Use what's pasted here instead: [PASTE YOUR PROJECT BRIEF, SCOPE, OR WBS HERE])
Identify risks across these categories:
1. Technical (dependencies, integrations, technology assumptions, platform)
2. Resource (team availability, key-person, vendor, skills gap)
3. Scope (ambiguous requirements, undocumented assumptions, creep triggers)
4. External (regulatory, client behavior, market, third-party)
5. Timeline (critical path exposure, float depletion, milestone chains)
For each risk:
- Name it specifically (not "generic technical risk" but, e.g., "the database migration depends on Vendor X delivering the API schema by Week 3, which has not been contractually confirmed")
- Likelihood: Low / Medium / High
- Impact: Low / Medium / High
- One mitigation action
Give me 10–15 specific risks. Be contrarian. Tell me what I probably have not worried about yet.
Work Task 11 — Meeting Minutes & Follow-Up Email
Turn a Meeting Transcript into Clean Minutes
Converts a messy Teams/Co-pilot transcript, Otter export, or rough notes into one-page minutes — decisions, action items with owners and due dates, and open questions — in under five minutes. The first workflow most PMs ship.
You are an experienced project manager writing the official minutes for a meeting you attended. The raw record of the meeting — a transcript, a Co-pilot/Otter export, or my own rough notes — is attached to this conversation. It is messy, out of order, and full of side-chatter.
Meeting type: [status call / kickoff / steering committee / client review]
Raw meeting record — work from the file I've attached. (No attachment? Use what's pasted here instead: [PASTE THE TRANSCRIPT, EXPORT, OR NOTES HERE])
Produce one-page minutes in exactly this structure:
**Meeting:** title, date, and attendees — pull these from the record; if any is not stated, write "Not stated," do not guess.
**Decisions made** — only things the group actually settled. One line each. If something was discussed but left open, it is NOT a decision — it goes under Open questions.
**Action items** — a table: | Action | Owner | Due date |. One row per commitment. The owner is the single named person who agreed to do it; the due date is the date or timeframe stated. If the record does not name an owner OR does not give a due date, still list the item and write "[MISSING OWNER]" or "[MISSING DUE DATE]" in that cell — never invent one, and never silently drop the item.
**Open questions** — anything unresolved, raised-but-not-answered, or parked.
Rules: use ONLY what is in the record. Do not add decisions, owners, dates, or attendees that were not said. If you had to infer an attribution (e.g. who said what), mark it "(inferred)" so I can verify it before this goes out. End with one line: "Items needing follow-up before this is final: …" listing every [MISSING OWNER] / [MISSING DUE DATE] / (inferred) item.
See it work — before → after
Work Task 13 — Progress & Coordination Synthesis
Before
Fifteen minutes after every progress round turning six rambling updates into a status note nobody fully trusts — because 'still working on it' got logged as progress.
After
Progress digest in 90 seconds: 4 items moved, 2 blockers with named unblock owners, one decision flagged for the sponsor. Pasted into the channel with two small edits.