The Briefing Document Architecture

The briefing document is one page. Not two pages condensed into one with small type — one page with breathing room, clear hierarchy, and enough white space that the executive can annotate it during the conversation. The briefing document has five sections: Background, Finding or Recommendation, Evidence, Risk, and Ask. Each section has a defined word limit. Exceeding the limit means you have not decided what is essential.

# EXECUTIVE BRIEFING: [TOPIC]
Date: [YYYY-MM-DD] | Prepared by: [Name / Agent] | Decision needed by: [Date]

---

## BACKGROUND (2-3 sentences max)
The situation this briefing addresses, stated as briefly as possible.
What changed, what problem exists, or what opportunity is available.
One sentence on why this requires executive attention now.

---

## RECOMMENDATION (1-2 sentences)
What we recommend the executive approve or decide.
Specific, actionable, time-bound. No hedging.

Example: "Approve $250K for a 90-day AI pilot targeting the
claims processing workflow, launching Q2 2026."

---

## EVIDENCE (3 bullet points max)
• [Primary evidence — the strongest single data point or result]
• [Peer comparison — what a comparable organization achieved]
• [Cost of inaction — what happens per quarter of delay]

Each bullet: one sentence, one number, sourced if possible.

---

## PRIMARY RISK (1 sentence risk + 1 sentence mitigation)
Risk: [The most likely reason the recommendation fails.]
Mitigation: [The specific action already taken to address it.]

Do not list three risks. Name the one that matters most.
The executive who asks about a different risk will ask.

---

## ASK (1 sentence + deadline)
"Approve [specific action] by [specific date] to maintain [timeline]."

If no decision by [date]: [specific consequence stated neutrally].

---

CONTACTS: [Name, title, contact] for questions before the meeting.
APPENDIX: Full data and methodology available at [reference or location].