Status Reports People Actually Read

The report nobody opens

Every project manager has written the status report that goes out on Friday afternoon and is never mentioned again. It lists every task, repeats last week's text with three words changed, and ends with a cheerful green. Nobody reads it because nothing in it requires them to.

A status report has one job: to make sure the right people know what they need to know, early enough to act. Everything else is decoration. AI makes the decoration very cheap, which is precisely why you need to be clear about what the report is for before you let it anywhere near one.

Three questions, in this order

A useful report answers three questions, and the reader should be able to find each answer in seconds.

What changed? Not what happened. What is different from last time: a milestone reached, a date moved, a decision made, a supplier who went quiet. If nothing changed, say so in one line. That is useful information too.

What is at risk? The things that might go wrong before the next report, with a sentence on what you are doing about each. Not the full risk register. The two or three items a sponsor would be annoyed to hear about later.

What do I need, and from whom? The most neglected section and the most useful. A named person, a specific ask and a date. "Need a decision from Finance on the contingency by Wednesday" is worth more than the rest of the report put together.

Honest RAG status

The colour is the one part of the report you must not hand over, and it is worth understanding why.

A RAG rating is a judgement. It compresses everything you know about the project, including things that are not written anywhere, into a single word. An AI given your notes will pick a colour based on the tone of those notes. Write cheerfully about a slipping project and it will cheerfully call it green.

There is a second, subtler pull. Models tend towards reassuring language, and so do project managers at five o'clock on a Friday. Amber is uncomfortable to write. The draft will happily soften it for you: "minor delays", "some pressure on timelines", "being actively managed". Each phrase is technically defensible and together they describe a project in trouble while sounding like one that is fine.

So decide the colour yourself, before you prompt, and tell the model what it is. Then instruct it not to soften anything.

The template

I am a project manager writing a weekly status report for [audience,
for example the project sponsor and steering group].
The overall status is [RED / AMBER / GREEN]. Do not change this rating
and do not soften the language around it.
Using only my notes below, write the report with these sections:
NEEDS
What I need, from whom, by when. One line each, named person or role,
specific ask, date. Put this section first.
STATUS: [colour]
One sentence explaining why, in plain words.
WHAT CHANGED SINCE LAST REPORT
Milestones reached or missed, dates moved, decisions made. If a date
moved, give the old date and the new one.
AT RISK
The top three risks before the next report, each with one sentence on
what is being done about it.
NEXT
What happens before the next report.
Rules:

Under 250 words.
Do not describe routine activity that has not changed anything.
Do not use phrases like "on track", "minor", or "being managed"
unless my notes say so.
If my notes do not say who owns something, write OWNER NEEDED.
Do not add anything that is not in my notes.
MY NOTES:
[paste your notes]

The banned phrases are there on purpose. They are the ones that let a report sound fine when it is not. You will find your own to add.

Your notes are the input, not the transcript

The best notes for this prompt are short and blunt, written for yourself during the week. "Supplier missed Tuesday deadline again, third time. Asked Priya to escalate." That is perfect input. A model can turn it into a professional sentence in a second. It cannot turn a vague impression into a fact.

If most of your week happened in meetings, the AI for Meetings course covers turning a transcript into decisions and actions. Do that first, then feed the decisions into this template, rather than pasting whole transcripts into a status report.

One report, several readers

Different audiences need different things. The sponsor wants the colour and the asks. The delivery team wants the dates and what is next. A client wants what was agreed and what happens now, without the internal wrangling.

Rewrite the report above for [the delivery team / a client / a senior
executive with two minutes]. Keep every fact, date and the RAG rating
identical. Lead with what matters to this reader. Cut anything that is
not their concern. Do not make the news sound better than it is.
Under 150 words.