Last Thursday my project lead forwarded me a twelve-page report and typed back one line: “just tell me what matters.” I spent the next twenty minutes skimming charts, hunting for the one number that actually answered his question. A Redditor named u/Wrong-Jury7755 posted a fix for exactly this problem over on r/PromptEngineering, and I wish I’d found it before that meeting. The prompt turns any long report into a one-page brief that people actually read, not a watered-down copy of the original.
A lot of summary prompts just ask the model to “make it shorter,” and you get confident-sounding mush with nothing solid underneath. This one forces structure first: bottom line, findings, reasoning, actions, then open questions. That structure is what makes a report skimmable instead of just short. It works for board updates, sprint retros, research write-ups, basically anything long enough that people quietly stop reading halfway through.
Why It Matters 📋
Long reports get skimmed once, then forgotten in a shared drive somewhere. When nobody reads past page two, decisions get made in hallway conversations instead of from the actual data. This Redditor built the prompt because the “open questions” section, the part everyone skips, turned out to be the most honest part of any report. Tying a number to every bullet stops the model from writing confident sentences that fall apart under one follow-up question. The 400-word cap does something a longer summary never does: it forces real prioritization instead of a smaller copy of the same document.
How To Use It ✍️
Copy this exactly and drop your report where it says [PASTE]:
Summarize the report below into a one-page brief.
Report:
[PASTE]Structure the brief exactly like this:
- Bottom line (2 sentences max): what someone needs to know if they read nothing else.
- What changed / what we found (3 to 5 bullets, each with the specific number or fact behind it).
- Why it matters (2 to 3 bullets tied to a decision, not a vibe).
- What we’re recommending (clear actions, each starting with a verb).
- Open questions (things the report does not answer).
Rules: no adjectives that don’t carry information. If a claim has no evidence in the report, leave it out. Keep it under 400 words.
Three things do the heavy lifting here. The five-part structure stops the model from wandering, one section at a time instead of one big paragraph. The rule tying every finding to a number stops vague language from sneaking past the model’s tendency to sound sure of itself. The strict word count means it has to cut, not just compress, down to what someone with two minutes actually needs.
Each section earns its place. The bottom line forces a single takeaway before anything else gets written. The findings section locks facts to numbers so nothing floats free of evidence. Why it matters ties those facts to a decision instead of a feeling. The recommendations use verbs, not vague suggestions like “consider” or “explore.” And open questions is the honesty check: what the report never actually answered.
Two easy variations if you want to push this further. Add a line asking for a two-sentence executive summary version too, formatted for a slide or a Slack message. Or ask the model to tag each finding with a confidence level, high evidence, thin evidence, or inference, so readers know how much weight to put on each bullet.
Tips & Tricks 🧠
- If a finding has no hard number behind it in the source report, tell the model upfront: “if there’s no number, say so instead of guessing.” This Redditor ran into that exact gap, and it’s the one weak spot in the prompt as written.
- Feed the report in chunks if it runs long. Ask the model to hold off on the “bottom line” until it has seen the whole thing.
- Reuse this for meeting notes, not just reports. Swap “Report” for “Meeting notes” and the structure holds up fine.
- Save it as a snippet in whatever prompt manager you use. This is a weekly-use prompt, not a one-off.
- Run it twice on the same report and compare the “open questions” sections. If they differ, that’s a sign the source document itself is thin on evidence.
Give It A Try 🚀
Copy the prompt above, paste in your next long report, and watch how much of it actually survives the cut. If you land on a fix for the missing-number problem, share it, I’d genuinely like to see it!
Copy-paste this prompt to compress a long report into a one-page summary people actually read
by u/Wrong-Jury7755 in PromptEngineering