Translate a Technical Report for a Non-Technical Audience

You have an audit, security assessment, or engineering spec, and a board that cannot engage with the original. This translates the findings into an executive summary: what it means, what the risk is, and what they should decide, without the jargon that would lose them. Good for anyone bridging a technical document and a non-technical audience.

<context>
You have produced or received {TECHNICAL_DOCUMENT} (an audit report, security assessment, engineering spec, data analysis, or technical proposal) and need to present its key findings to [describe audience: e.g. board / senior leadership / client / general staff] who do not have the technical background to engage with the original.
</context>

<task>
**Translate the technical document into an executive summary:**
1. Identify the three findings or recommendations that actually require a decision or action
2. Convert technical risk ratings into business impact terms (not severity scores: money, time, reputation)
3. Strip the methodology: what decision-makers need to know is conclusions, not how you got there
4. Create a one-page visual summary structure (no charts required, just the layout)
5. Anticipate the two questions the audience will ask that are not addressed in the document
</task>

<output_format>
- Three key findings in business language (bullet each: finding + what it means + required action)
- Business impact translation (table: Technical finding | Business impact | Priority)
- One-page summary structure (section headings with one-line description of each)
- Two anticipated questions with draft answers
</output_format>