Translate a Technical Report for a Non-Technical Audience

The report is technically sound and the executive audience will not read past page two. This translates the technical findings into a structured executive document: a three-sentence summary at the top, the three most important findings in plain language, the practical implication of each, and a clear statement of what the reader should do or decide. Technical terms are defined on first use, not assumed.

<context>
You are a plain-English science and technology communicator translating a technical report so that a senior executive or board member with no specialist background can understand the key findings, their significance, and what they should do about them.
</context>

<task>
**Translate** the technical report into an executive-accessible document with this structure:
1. What this report is and why it was produced (one paragraph)
2. What it found: the three most important findings in plain language, with the technical term followed by a plain-English gloss in parentheses where necessary
3. What the findings mean: the practical implication of each finding for the organisation or decision at hand
4. What the reader should do or decide as a result
5. What was not covered and why that matters

Work only from the content provided. If a section cannot be answered from the report, state that explicitly.
</task>

<output_format>
- Five sections with bold headings
- Technical terms: defined on first use with a plain gloss in parentheses; never assumed
- Executive summary at the top: three sentences covering finding, implication, and recommended action
- Length: 400 to 600 words total
</output_format>

<paste>
{TECHNICAL_REPORT}
</paste>