Issue #16 June 30, 2026 5 min read

Turn a 60-Page Report Into a One-Page Brief

Someone sends you a 60-page report and says "let me know your thoughts by end of day." You have 30 minutes. The report has 47 pages of context and 13 pages that matter. These prompts find the 13 pages, extract what your decision-maker needs to know, and format it so the brief actually gets read.

The Problem

Long reports are not written for the person who needs to act on them. They are written for the person who needs to prove they did the work. The analyst who produced the report includes methodology, caveats, appendices, and 15 charts that all say the same thing in different ways. The executive who receives it needs three numbers, one recommendation, and the strongest argument against that recommendation.

Most people handle this by skimming. They read the executive summary (which the author wrote last, in a rush), glance at the charts, and form an opinion based on whatever caught their eye. The result is decisions based on whichever data point was most visually prominent, not which was most important.

The alternative is not "read the whole thing." Nobody has time for that. The alternative is structured extraction: pull out what matters, identify what is missing, and present it in the format your decision-maker actually uses.

The Fix

  1. Get the report into text. Upload the PDF to ChatGPT, Claude, or Gemini. If it is a spreadsheet or slide deck, paste or upload it directly. The AI needs the full document, not just the executive summary. The value comes from finding things buried on page 43 that contradict the conclusion on page 2.
  2. Run the main extraction prompt. This pulls out the core findings, the actual recommendation (not the hedged version), and the data that supports or undermines it. It also flags what the report does not address, which is often more important than what it does.
  3. Use the follow-up prompts if needed. The contradiction finder surfaces places where the data says one thing but the recommendation says another. The "so what" translator reframes technical findings into business impact for a specific audience.
Copy-paste prompt
"I need to brief [role, e.g. my CEO / the board / a client] on this report by [deadline]. They will spend at most 2 minutes reading my summary. Here is the full report: [paste or upload]. Create a one-page executive brief that covers: (1) The single most important finding, stated in one sentence a non-expert would understand. (2) Three supporting data points, each with the specific number and what it means for us. (3) The report's recommendation, stripped of hedging language. State what they are actually suggesting we do. (4) The strongest reason not to follow that recommendation (pulled from the report's own data or caveats). (5) What this report does NOT address that the reader will probably ask about. (6) One sentence on what decision this brief is driving toward. Keep the brief under 300 words. Use bullet points. No jargon."
Optional: contradiction finder
"Review this report for internal contradictions. Specifically: (1) Places where the data in the body contradicts the claims in the executive summary. (2) Charts or tables that tell a different story than the text describing them. (3) Caveats buried in footnotes or appendices that weaken the main conclusion. (4) Assumptions stated early that are violated by findings presented later. For each contradiction, quote the two conflicting passages and explain why they matter. Rank by impact on the report's main recommendation."
Optional: "so what" translator
"The person reading this brief is [role and what they care about, e.g. 'a CFO who cares about margin impact' or 'a board member focused on risk']. Rewrite the key findings from this report in their language. For each finding: (1) State it in terms they use daily (revenue, headcount, risk exposure, timeline, competitive position). (2) Quantify the business impact where possible. (3) Connect it to a decision they are currently facing. (4) Suggest one question they should ask the report's authors. Keep each finding to 2-3 sentences maximum."
What you get

A 300-word brief that gives your decision-maker the finding, the evidence, the recommendation, and the risk, without making them read 60 pages to get there. A contradiction check that catches the things most readers miss because they stop at the executive summary. And a translation layer that turns technical findings into the language your specific audience uses. The person you send this to will think you spent an hour reading the report. You spent 10 minutes.

Cost
$0 - $20/mo
Time to learn
0 min
Time saved per report
~45 min

Why executive summaries fail

Executive summaries are written by the same person who wrote the report. They carry the same biases, the same framing, and the same blind spots. The author spent three weeks on the analysis and cannot see it from the outside anymore. Their summary emphasizes what was hardest to research, not what is most important to decide.

An AI reading the same report has no attachment to any section. It does not care that the methodology section took two weeks to write. It evaluates every page with equal weight, which means findings buried on page 43 get the same attention as the headline chart on page 5. That neutrality is the advantage.

The missing-information advantage

The most valuable part of any brief is not what the report says. It is what the report does not say. Every 60-page report has gaps the authors know about but chose not to highlight. Competitor data they could not get. Time periods they excluded. Assumptions they made but did not test.

When your brief includes "this report does not address X," you change the conversation. Instead of debating the report's conclusions, the room focuses on whether those conclusions hold given what is missing. That is a higher-quality discussion. The person who surfaces the gap looks like the most careful reader in the room, even if they spent the least time reading.

Format matters more than you think

A 300-word brief with bullet points gets read. A 600-word summary in paragraph form gets skimmed. A forwarded report with "see attached, thoughts?" gets ignored until someone asks about it in a meeting.

The brief is not a summary of the report. It is a decision tool. Every sentence should either inform the decision or clarify the risk of getting it wrong. If a sentence does neither, it does not belong in the brief. AI is good at enforcing this discipline because it does not feel compelled to preserve the author's original structure.

Works for

  • Analyst reports and market research (where the insight is buried under methodology)
  • Audit and compliance reports (where the findings section is page 38 of 52)
  • Consultant deliverables (where 80% of the document justifies the engagement, not the recommendation)
  • Board packs and pre-reads (where each committee member needs a different angle on the same data)
  • Regulatory filings and prospectuses (where legal language obscures the business reality)
  • Due diligence reports (where one buried risk factor can change the entire deal thesis)
  • Internal strategy documents (where the org chart determines the narrative more than the data does)

3 reports per week × 45 minutes saved = ~2+ hours back every week
Plus the quality effect: when your briefs consistently surface the right finding and the right risk, people start sending you the reports first. That is how information flow becomes influence.

The Bigger Picture
Where This Is Going
Each issue builds your AI toolkit. Here is what subscribers get access to as we grow.
Now
Weekly AI Trick
One tested technique per week. Copy-paste prompts. Time and cost estimates. Works Monday morning.
Coming Q2 2026
Searchable Archive
Every trick indexed by role, department, and use case. "Show me all finance tricks" or "What works for product?"
Coming Q2 2026
Custom Topics
Tell us your industry and role. We prioritize tricks that match your daily workflows.
Coming Q3 2026
Competitive Radar
Monthly briefing on how your competitors are using AI. Based on public filings, job postings, and press.

Get Issue #17 next Monday

One trick per week. Five minutes to read. Zero cost to implement.