Turn a Long Report into a One-Page Executive Summary That Leads with the Ask

Returns a one-page executive summary that opens with the decision needed, keeps every source number exact, and lists claims the report does not back up.

You getDecision or ask, context and key findings

Prompt

Prompt
You are a chief of staff who writes executive summaries that senior leaders read in two minutes.

I will paste a long report right after this message. Turn it into a one-page executive summary of 300-400 words.

Rules:
1. Open with the decision or ask in one or two sentences: what the reader must approve, choose or know, and by when. If the report has no clear ask, say so and state the most likely one.
2. Copy every number exactly as the source gives it, including units, dates and rounding. Do not calculate new figures, convert units or round.
3. Include only what the report states. If a conclusion in the report is not backed by data or evidence inside it, list it under Unsupported claims with a short reason.
4. Each key finding is one sentence and names the section or page it came from.
5. Write for a reader who has not seen the report; define any acronym on first use.

Output format:
- Decision or ask (1-2 sentences)
- Context (2-3 sentences)
- Key findings (3-5 bullets, each with source section)
- Recommendation or options (from the report only)
- Risks and open questions (2-4 bullets)
- Unsupported claims (table: Claim | Where it appears | What is missing)

End with one line naming anything you could not verify or any part of the report that was unclear or missing.

Example output

At a glancePicking automation pilot: headline resultsLeeds pilot, June to November, with the expansion ask
Picks per labour hour
92 to 131
Section 3.1
Order error rate
1.8% to 0.6%
Section 3.2
Temporary staff hours saved
2,150 hours
Section 3.4
Capital cost for 3 more sites
£2.4M
Plus £310,000 annual support

Example for: a 28-page operations report on a 6-month warehouse picking automation pilot at a fictional retailer, Northvale Supply.

Executive Summary: Warehouse Picking Automation Pilot

Decision or ask
Approve expanding the robotic picking pilot from the Leeds site to 3 additional warehouses at a capital cost of £2.4M, with a decision needed by 15 March to secure Q2 vendor delivery slots.

Context
Northvale ran a 6-month pilot of autonomous picking robots at its Leeds warehouse from June to November. The operations team compared pilot results against the same period last year. The report recommends a phased rollout starting in Q2.

Key findings

  • Picks per labour hour rose from 92 to 131 during the pilot (Section 3.1).
  • Order error rate fell from 1.8% to 0.6% (Section 3.2).
  • Robot downtime averaged 4.2 hours per week, mostly from software updates (Section 4.3).
  • Temporary staff hours at Leeds dropped by 2,150 hours over the pilot (Section 3.4).
  • Vendor quotes total £2.4M for 3 sites, plus £310,000 annual support (Appendix B).

Recommendation
The report recommends rolling out to Bristol, Derby and Glasgow in that order, one site per quarter, with Leeds staff training each new site (Section 6).

Risks and open questions

  • Pilot ran outside the November-December peak; performance under peak volume is untested.
  • Bristol's floor layout differs from Leeds; no site survey is included.
  • Staff redeployment plan for affected temporary roles is not described.

Unsupported claims

ClaimWhere it appearsWhat is missing
Payback within 18 monthsExecutive overview, p. 2No payback calculation or cost model shown
Staff satisfaction improvedSection 5No survey data; only two manager quotes
Results will scale to all sitesSection 6Only one site tested; no comparison of site conditions

Could not verify: Appendix C (vendor SLA terms) was referenced but not included in the pasted text.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Putting the decision first means busy readers know what is being asked before reading any detail.
  • Banning new calculations and rounding keeps the summary safe to quote and prevents silent number drift.
  • The unsupported-claims table catches weak conclusions before they reach a leadership meeting.

Use before a leadership meeting or board pack when you have a long report but little reading time. Paste the full text into ChatGPT, Claude or Gemini; keep section headings so findings can be traced.

Common edits

  • Change the length to 150 words for an email or Slack update.
  • Add a line asking for a one-slide version with the ask and three findings.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity