My company produces quarterly vendor reviews. Each one is thirty to sixty pages of methodology, appendices, scoring rubrics, and — buried somewhere in the middle — the one or two sentences that actually change a decision. Each one lands in my inbox with the unspoken assumption that I will have read it cover to cover before the steering committee meeting. For an embarrassingly long stretch of my career, my strategy was: read the executive summary, skim the section headers, and quietly pray that nobody asks me about page 31.
That strategy works beautifully right up until the meeting where someone asks you about page 31. I had one of those. I confidently agreed with a recommendation that the report had actually argued against two pages later, in a paragraph I'd skimmed past. The room went a little quiet. That was the precise afternoon I decided to fix my process instead of continuing to rely on luck and a confident voice.
The number five is the whole design
I tried plain summarization first and learned a genuinely frustrating thing: if you ask for a summary, you get a summary. It's shorter than the report, sure, but it's still three dense paragraphs you have to actually read, and it still tends to hide the real decision inside a hedge. What I needed was not a shorter document. It was a distillation — the five things I'd need if someone cornered me about this report at a cocktail party and I had to sound like I'd read it. Five is not an arbitrary number. It's roughly the most a person can hold in working memory at one time, which means that after reading the five bullets I have actually retained the report, not just re-skimmed it more efficiently.
So I built the Distill a Long Document to Exactly 5 Key Bullets prompt and run it on Gemini 2.5 Pro. The model choice here is deliberate and completely load-bearing. These documents are long, and Gemini 2.5 Pro's long-context handling means I can paste the entire forty pages — tables, appendices, footnotes, all of it — into a single call and trust that it's genuinely reading down to the bottom rather than summarizing the first chunk and confidently guessing the rest. For a vendor report whose actual recommendation lives on page 38, that capability is the difference between right and wrong, not just fast and slow.
- Set the reader context every single time — the same report gives different bullets to a budget owner and an engineer
- If a bullet has no number, date, or decision in it, it's probably not one of the five most important things
- Read the five bullets before the meeting, not the full PDF at midnight the night before
- The 'exactly five' rule forces real prioritization — it can't cop out by listing everything it found
- When two bullets feel similar, the prompt's no-overlap rule is doing exactly its job
Reader context is the secret ingredient
The thing I underestimated most is how dramatically the reader context changes the output. When I tell it I'm 'an executive deciding whether to renew this vendor's contract,' it surfaces the renewal-relevant facts: the cost trend, the SLA breaches, the one contract clause that quietly changed since last quarter. If I told it I was the engineer integrating the vendor's API, the exact same forty pages would produce five completely different bullets about rate limits and uptime. Most summarizers blithely ignore who's asking and hand everyone the same generic gist. This one makes 'who are you' the first question, and that single input is most of why the bullets feel like they were written for me specifically.
Two months in
Two months into this habit, I haven't been caught flat in a single meeting. If anything, I'm asking noticeably sharper questions, because I walk in already holding the five facts that move the decision instead of a vague, anxious fog of forty pages I half-read at midnight. When a report is dense enough that even the five bullets come back a little wordy, I'll run them through my Tighten a Wordy Paragraph to Half Its Length prompt to get each one down to something I can actually memorize on the walk from my desk to the conference room. Grab the Distill a Long Document to Exactly 5 Key Bullets prompt on Prompt Dock and run it on the longest unread thing sitting in your inbox right now. Set the reader context to your actual role, not a generic one. Five bullets later you'll know more about that document than you would have after grimly reading the entire executive summary.