A weekly status report is one of the highest-leverage documents a project manager writes, and one of the most commonly botched. Reports that bury the headline, list activity instead of outcomes, or soften a real problem into a vague amber waste everyone’s time. This builder turns your raw notes into a prompt that produces a crisp, honest, standardised report every week.
How it works
You drop in the project name, the overall RAG status, your key progress, your risks, and the plan for next week — quick notes are fine. The builder wraps them in a prompt that tells the model to act as a senior project manager and structure the report so a busy executive can grasp the status in seconds. You choose the format — executive summary, bullets, a single table, or a ready-to-send email — and the audience, so the length and tone fit. Copy the prompt, run it, and review.
What makes the output strong
- Headline first. Every report opens with the RAG status and a one-line headline, the way a good executive summary should.
- Outcomes over activity. The prompt explicitly cuts activity that has no business consequence and reports impact instead.
- Honest about risk. It refuses to soften a red into an amber, and when status is not green it adds a decisions-needed section so the reader knows how to help.
Tips for better output
- Write notes, not prose. The model does the polishing; you supply the facts. Half-sentences and fragments are fine.
- Quantify progress. “Closed 14 of 18 UAT defects” reports better than “made good progress on testing.” Give the model numbers and it will use them.
- Be specific about the ask. When you are amber or red, say what decision or resource would move you back toward green, and the prompt will surface it clearly for the reader.