Raw view: Executive Summary of a Technical Document
No invisible, zero-width, or bidi-control characters detected.
<document>
{{DOCUMENT}}
</document>
Write an executive summary of the document above for {{READER}} (for example, "the VP of Engineering" or "a non-technical steering committee"). Maximum {{MAX_WORDS}} words (default 350). The reader will spend two minutes on this and may make a decision from it alone, so lead with what they need to decide or know, and never let a detail in that the source does not support.
<decision_needed>
{{DECISION_NEEDED}}
</decision_needed>
<decision_needed> states what the reader is being asked to do (approve, fund, choose, be informed). If it is empty, infer the implicit ask from the document and label it `[inferred ask]`.
Procedure:
1. Read the whole document first. Then extract, as verbatim quotes with their location (section or page), the sentences that carry: the problem, the recommendation, each quantified impact (cost, time, risk, revenue, users), each major risk or caveat, and the timeline. Work from these quotes only; this keeps the summary faithful.
2. Translate every technical term the reader would not use in their own meetings into its consequence. "Replaces the synchronous call with a queue" becomes "removes the single point of failure that caused the two outages in Q2". Keep the term in parentheses only if the reader will see it elsewhere.
3. Keep every number exactly as the source states it, with its unit and basis ("40% of API traffic, measured over 30 days"). If the source gives a range or a confidence, keep it. Never round a range into a point estimate.
4. Represent the document's uncertainty honestly. If the author says "we believe" or "preliminary", the summary says so. Overstating confidence is the most damaging error a summary can make.
5. Where the document is silent on something the reader will ask (total cost, who owns it, what happens if we do nothing), say "The document does not address X" rather than filling the gap.
6. Check the finished summary line by line against your quotes from step 1. Remove any claim you cannot trace.
Write in plain, declarative sentences in the reader's vocabulary. No hedging phrases that the source does not justify, no jargon the reader would not use, no bullet fragments where a sentence is clearer.
## Output format
**The ask** - one bold sentence: what the reader is being asked to do, by when. `[inferred ask]` if applicable.
**Summary** - 3-5 short paragraphs in this order: the problem and why it matters now; the recommendation and what it delivers (with numbers); cost, timeline, and owner; the main risks and what mitigates them; what happens if the recommendation is declined.
**Key numbers** - a compact table: metric, value as stated, source location.
**Not covered in the source** - bullet list of the questions from step 5 the document does not answer.
**Traceability** - for the author's review only: each paragraph of the summary followed by the quote locations it rests on.