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.
Why status reports go wrong and how this addresses each failure
Burying the headline
The most common mistake in status reporting is putting the RAG status and the key message on page two, after a project background section the reader already knows. Executives reading a stack of project reports on a Monday morning skim the first paragraph and stop if it does not tell them what they need to know. The prompt produced by this builder instructs the model to open with the RAG status and a single-sentence headline before anything else.
Reporting activity instead of outcomes
“Completed three workshops with the business” is an activity. “Completed requirements sign-off with the business; build can begin on Monday” is an outcome. The difference is whether the reader learns what changed as a result. The prompt explicitly tells the model to look at each bullet of activity you provide and ask “what does this mean for the project?” — if the answer is nothing, it cuts it.
Softening a real problem
Amber is the most commonly misused RAG status. In practice it often means “this is red but I’m hoping it gets better and I don’t want to have the difficult conversation yet.” A report that calls a red amber and then provides five paragraphs of mitigation plans does not help the reader — it actively obscures the information they need to make a good decision. The prompt tells the model to use the RAG status the user provides, not to second-guess it, and to add an explicit “decisions needed” section whenever the status is not green.
Missing the ask
Every amber or red report should make it crystal clear what the project team needs from the reader. Is it a decision? A resource? An escalation? Permission to de-scope? When the ask is buried at the end of a long risk section, executives either miss it or act on incomplete information. The builder’s prompt surfaces the ask as a named section in amber and red reports, directly after the headline.
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.