The Signal #1: Your Status Report Is 80% Assembly. AI Handles That

Subject: Your status report is 80% assembly work. Here’s the 20% that actually matters.

Hey [Name],

The data for your status report already exists. It’s in Jira, in Slack threads, in the meeting notes from Wednesday. The job every Friday isn’t creating a report - it’s locating, formatting, and translating that data into something an executive can read in 30 seconds.

That’s not insight work. That’s assembly. And assembly is exactly what AI is built for.

Feed your raw project data into an LLM - Jira exports, Slack threads, even screenshots of dashboards. The output won’t be perfect. But the structure will be right. Key points captured. Risks surfaced. What it needs from you: the 20% a machine can’t see. The political context. The relationship nuance. The call on whether Amber should be Red because you know something the data doesn’t show yet.

Typical result: 12 minutes of focused work, not 90 minutes of assembly.

The Signal (Insight)

Status reports are assembly, not creation.

The PM’s job isn’t generating insight from raw data - it’s synthesising information that already exists into a format stakeholders can act on. AI handles the synthesis. You bring the interpretation.

And here’s the counterintuitive part: the more complex the project, the more data there is to process. The more data, the more time AI saves. Complexity is the argument for this approach, not against it.

The Noise (Myth)

“AI won’t understand our project context.”

It doesn’t need to. Feed it your raw data and a clear format. It assembles. You add the context that requires professional judgement - the sponsor dynamic, the risk that isn’t in the tracker yet, the sentence that needs softening because of who’s reading it.

The tool handles the structure. You bring the intelligence.

The Tool (Resource)

A starting prompt for this Friday’s status report:

"You are a Senior PM writing a weekly status report that executives actually read. I'm going to give you raw, unstructured project data. Synthesise it into a concise status report with these sections: Executive Summary (3 sentences: health, key risk, action needed), RAG Status with one-sentence justification, Achievements, Risks & Issues, Next Week's Focus. CONSTRAINTS: ONLY reference data I provide. If data is missing, flag it as [DATA GAP]. Don't soften bad news."

Paste in your Jira board, Slack threads, meeting notes. Don’t curate. Give it the raw material and see what comes back.

That’s Prompt 1 of 5.

The Full Toolkit

Five prompts that cover the entire status reporting process:

The Raw Data Dump - structure a report from unorganised project data The RAG Challenger - pressure-test your status rating before it goes out The Multi-Audience Translator - one source, three versions (exec, tech, client) The Talking Points Generator - standing meeting prep in 5 minutes The Trend Tracker - surface patterns across multiple weeks They won’t replace your judgement. They’ll free it up.

[Get the 5 prompts free → projectorpm.xyz/status-reporter]

The Signal: Cut the noise.

P.S. Want to go further? There’s an automation version that runs this without the paste-and-prompt step each week. More on that inside the toolkit.

Yes, AI helped me to write this :)