Quick summary: one Reddit user turned a weekly status report from a formatting chore into a two-minute cleanup job, using a single prompt with strict section order and a built-in flag for anything unclear.
If you write the same report every Friday, you know the drill. Notes come out in whatever order they happened, and then you spend twenty minutes reshaping them into something a manager can actually read. This Redditor, posting in r/PromptEngineering, got tired of that dance and built a prompt to do the shaping instead. Now the notes go in messy, and the report comes out clean.
What makes it work
The prompt isn’t fancy. It just locks in five sections every time: Summary, Done this week, In progress, Blockers, Next week. That consistency is the whole trick. Once the structure never changes, you stop thinking about formatting and start thinking about content. You paste, you get a report, you move on.
Two rules do the heavy lifting underneath that structure. The first tells the model to mark anything unclear with “[check]” instead of quietly smoothing it over into something that sounds finished. The second bans invented numbers outright: if a metric wasn’t in the notes, it doesn’t show up in the report. Together those rules turn a report generator into something you can actually trust without rereading every line for made-up details.
That second rule matters more than it looks at first glance. Most people who’ve tried AI for status reports have hit the same problem: the model fills gaps with confident-sounding guesses. A percentage that was never measured. A “completed” status for something still stuck in review. This prompt closes that door before it opens, and it does it with one plain sentence instead of a paragraph of caveats.
The original poster called the “[check]” flag the piece that makes the whole thing trustworthy. Instead of hiding a vague note behind smooth prose, the model marks the spot so you can go verify it before you send the report out. That’s a small design choice with a big payoff.
Where this pays off 📋
- Weekly team updates for a manager who wants five sections and nothing extra
- Freelance client check-ins where “blockers: none” needs to actually mean none
- Sprint recaps pulled from scattered notes taken during standups
- Async updates for remote teams where nobody has time to read a wall of text
- Personal project logs you keep for your own accountability, not just for a boss
The author also asked the community if anyone had extended this to pull raw notes automatically instead of pasting them by hand every week. That’s the natural next step: wire this prompt to a notes app, a task tracker, or a daily journal entry and skip the copy-paste entirely.
Prompt of the Day
Turn my raw notes into a status report with these exact sections:
Summary: 2 sentences, plain language, no jargon.
Done this week: bullets, past tense.
In progress: bullets, with a rough % or stage if I gave one.
Blockers: bullets. If none, write “none.”
Next week: bullets, one owner per line if stated.Rules:
– Use only what’s in my notes. Mark anything unclear with [check].
– Don’t invent numbers. If I didn’t give a metric, leave it out.Notes: [paste]
Why it holds up
The section headers act as a strict template, so the model can’t wander off into a different structure halfway through the report. The “[check]” rule is a safety valve, catching vague notes before they turn into confident-sounding fiction you’d have to walk back later. And the “don’t invent numbers” line is a direct constraint against the most common failure mode in AI-written reports: fabricated specifics that sound just plausible enough to slip past a quick read.
Want to push it further? Try adding a line like “flag any blocker mentioned in more than one week’s notes” if you keep a running log across reports. Or ask for a one-line Slack-ready summary alongside the full report, so you’ve got a short version ready for a quick channel post without extra work.
The bigger idea here isn’t really about status reports. It’s about giving a prompt strict rails and an honest way to say “I’m not sure” instead of papering over gaps with confident filler. That pattern works just as well for meeting notes, project recaps, or any report you end up writing on repeat.
Drop your own messy notes into this template this week and see what comes back. Chances are good you’ll spend less time formatting and more time actually reading what you wrote! If you build a version that pulls notes in automatically, the original poster in r/PromptEngineering would probably love to hear how you did it.
A report-generator prompt that turns raw update notes into a clean weekly status report
by u/Lanky_Revolution8174 in PromptEngineering