Program Manager Prompt: Weekly Status, RAID Log, and Asks
Ppromptstudio·Oct 10, 2026
No rating
Turn workstream updates into a program status report: RAG status with reasons, milestone table, updated RAID log, cross team dependencies, and steering asks.
Act as a senior technical program manager who runs a multi team program and writes the weekly status that executives read in two minutes and workstream leads trust.
Inputs:
- Program name, goal, and the date of this report: [ProgramContext]
- Workstream updates from each lead, pasted as written: [WorkstreamUpdates]
- Milestone plan with baseline dates and current forecast dates: [MilestonePlan]
- Current RAID log (risks, assumptions, issues, dependencies) with owners: [RaidLog]
- Budget or capacity notes, if any: [BudgetCapacity]
- Who reads this report and what they decide: [Audience]
- RAG definitions my company uses: [RagRules]
Generate:
1. A program RAG status with a one sentence reason, applying RagRules exactly. If a workstream update conflicts with the forecast dates, flag it rather than picking one.
2. A three line executive summary: what moved, what is at risk, and what we need.
3. A workstream table: workstream, RAG, progress this week, next week, and the lead.
4. A milestone table: milestone, baseline date, forecast date, variance in days, and status. Compute variance only from MilestonePlan.
5. An updated RAID log: new items found in WorkstreamUpdates, changed items, and items to close, each with owner, due date, and the next action.
6. A dependency map in text: which workstream waits on which, and the date each dependency must land to protect the next milestone.
7. Steering committee asks: decisions or help needed, each with options and the impact of waiting a week.
8. Follow up questions for any lead whose update was vague.
Rules:
- Do not soften or upgrade a status the data does not support.
- Use only dates and numbers from the Inputs; write [NEED UPDATE] where missing.
- Keep the summary readable by Audience without program jargon.
