# Executive Summary vs Technical Findings

> Master the two audiences of every pentest report. Learn to translate technical exploits into business risk for executives and reproducible steps for engineers.

Canonical: https://codelivly.com/rooms/executive-summary-vs-technical-findings
Last updated: 2026-08-31

| | |
|---|---|
| Level | Intermediate |
| Category | Cybersecurity |
| Lessons | 4 |
| Estimated time | 30 min |
| XP | 200 |

The pentest report serves two readers with opposite needs. The executive needs to understand business risk, exposure, and budget justification without drowning in jargon. The engineer needs exact reproduction steps, root causes, and stack specific fixes. This module teaches you to write both layers of the report without one compromising the other. You will learn the four question executive summary structure, the translation matrix from technical to business impact, the full technical finding skeleton, and how to keep IDs, severities, and evidence consistent across both audiences. Master this module and your reports will drive funded fixes instead of gathering dust.

## Lessons

1. Why Two Audiences Need Two Different Sections (30 min)
2. Writing an Executive Summary Non Technical Stakeholders Understand (30 min)
3. Structuring Technical Findings for Engineering Teams (30 min)
4. Risk Ratings & Business Impact Framing (30 min)

## Related

- [Learning path: Pentest Methodology & Reporting](https://codelivly.com/learning-paths/pentest-methodology-reporting)
- [All rooms](https://codelivly.com/rooms)