Executive Briefing Framework: Structure, Template and Tests

An executive briefing is a document or oral presentation built to let one decision-maker act correctly in a short time. The most defensible framework contains eight elements in a fixed order: the decision requested, the situation, the principal findings, the options with their trade-offs, the recommendation, the next steps, the risks and assumptions, and the sources. This article sets out the evidence for that structure, supplies a reusable template, and describes how to test a draft before it reaches the reader.

TL;DR

• Open with the decision requested and its deadline, then the bottom line; background follows only as far as the decision requires.
• Distinguish a decision brief (optimized for approval or escalation) from an executive summary (optimized for independent understanding of a longer report).
• Compare realistic options, including deferral, against the criteria the decision-maker actually uses: cost, feasibility, security, implementation burden.
• Keep an executive summary to roughly 5% to 10% of the full document, and place methodology, logs and diagrams in an appendix.
• Test the evidence for accuracy, applicability, actionability and adequacy before finalizing.

Table of Contents

• What an executive briefing must accomplish
• Decision brief or executive summary
• The eight-part framework
• A reusable template
• The five-part variant
• Length and proportion
• Testing the evidence: the quality test most drafts skip
• Adapting the framework to technical and security decisions
• Our perspective on briefings under pressure
• Where PROJECT-JTH can help
• Common errors and how to correct them
• Frequently asked questions
• Sources

What an executive briefing must accomplish

The purpose of a briefing is frequently misunderstood as compression. A briefing is better described as an evidence-filtering device. The Agency for Healthcare Research and Quality (AHRQ) documents that managers face time pressure, difficulty accessing relevant evidence, reliance on others to judge its quality, and limited resources. Each of those constraints is a reason a long report goes unread, and each is addressed, at least in part, by a well-built briefing: the author performs the filtering so that the executive does not have to.

Two consequences follow. First, the briefing must be written for a named reader with a named decision, since the same facts require different emphasis for a board, a lender, a partner or an internal operator. The U.S. Small Business Administration makes this point directly in its guidance: the summary cannot be separated from its purpose, and an organization may therefore need several variants of a briefing rather than one permanent template. Second, the briefing must be understandable without the underlying record. A reader who must consult the technical file to grasp the recommendation has not been briefed.

Decision brief or executive summary

The two forms are often conflated, and the conflation produces documents that serve neither purpose. A decision brief is optimized for an immediate approval, action or escalation. An executive summary is optimized to let a reader understand a longer report on its own terms. The practical difference lies in the opening: a decision brief begins with the decision and its business consequence, whereas a summary may legitimately begin with the purpose and background of the report it condenses.

The length figure for summaries is a convention rather than a law. The National Labor Relations Board’s communication standards, updated in February 2026, recommend that a summary stand alone, use plain language and define technical terms for nontechnical readers, and Colorado State University’s writing guide likewise treats the summary as a condensed version of the whole. Such proportions should be treated as starting points and adjusted to the reader’s available time.

The eight-part framework

The framework below is a synthesis, not a universal standard. It combines the modular logic of the Government Accountability Office’s guide for writing executive summaries, which identifies six standard modules (purpose, background, results in brief, principal findings, recommendations and agency comments), with the evidence-assessment steps in AHRQ’s toolbox and the option-and-decision logic in Stanford’s policy memo guidelines, which describe a memo that serves as the guiding document for an oral briefing of a decision-maker.

1. Decision requested and deadline

The first line states what the reader is being asked to do and by when. Without a deadline, the briefing invites indefinite deferral, which is itself a decision with consequences that no one has examined. Duke’s policy memo handout similarly places the most important information first throughout the memo, a principle commonly described as the inverted pyramid.

2. Situation and background

This element explains what changed and why it matters now. It should be limited to the context the decision requires. Historical narrative that does not alter the choice belongs in the appendix.

3. Principal findings

Present the few findings that support the conclusion, not every finding that was made. GAO requires logical sequencing and a direct association between findings and conclusions, so each finding included should be traceable to the recommendation it supports.

4. Options and trade-offs

Options should be realistic and should include deferral or doing nothing. Stanford’s guidance requires that options be justified against decision-relevant criteria, such as cost, feasibility, security, equity or implementation burden. A table is usually the clearest form, with options in rows and criteria in columns.

5. Recommendation

The recommendation names one option and gives the reason it is preferred under the stated criteria. It should not be hedged into a list of equally weighted possibilities, since the reader has asked for judgment.

6. Next steps

Specify the owner, the resources, the timing and the follow-up. A recommendation without an accountable owner is, in practice, a suggestion.

7. Risks and assumptions

State what could make the recommendation wrong, and which assumptions carry the most weight. This is also the place to record the risk of delay, which executives frequently underestimate when the status quo feels costless.

8. Sources and appendix

Linked material, methodology, logs, diagrams and data tables belong here. Their function is to support the decision, not to replace the argument for it.

A reusable template

The following skeleton can be adapted to a one-page memo, an email or a verbal briefing. Each prompt is deliberately a single sentence, because the discipline of the form is to force a single sentence where drafts tend to produce a paragraph.

1. Decision requested: We ask [named executive] to [approve, fund, defer, escalate] [specific item] by [date].
2. Bottom line: [One sentence stating the conclusion and its business consequence.]
3. What changed: [One to three sentences on the triggering event and why it matters now.]
4. Findings: [Three to five findings, each tied to the conclusion.]
5. Options: [Table: option, cost or resource requirement, benefit, principal risk, feasibility.]
6. Recommendation: [Selected option and the criteria that decided it.]
7. Next steps: [Owner, resources, milestones, date of follow-up.]
8. Risks and assumptions: [Top risks, risk of delay, assumptions that would change the recommendation.]
9. Appendix: [Methodology, supporting data, references.]

The five-part variant

Readers who search for “the five parts of an executive summary” will find that no single standard exists. GAO uses six or seven modules, and the Association of Proposal Management Professionals (APMP) presents a five-box, customer-first structure covering customer drivers, solution and benefits, investment, next steps and a close. A practical five-part version for internal use is: the business problem or objective; the recommended solution; the supporting evidence; the costs, risks and trade-offs; and the action required. It is a compression of the eight-part framework, appropriate when the reader has under five minutes and already knows the background.

Length and proportion

The research on length is consistent in direction and inconsistent in number. The NLRB and Colorado State recommend a summary of approximately 5% to 10% of the full paper. The International Energy Agency’s guide for operating agents recommends roughly two A4 pages, or about 700 words, with about 200 words for key findings and 200 to 300 words for background and context. Those proportions are specific to that guide’s format and should not be applied as general rules.

A more useful constraint is time: a briefing that cannot be read in the interval the executive has available is too long regardless of its percentage. For an oral briefing, the same principle applies; the written memo serves as the guide, and the speaker should be able to state the decision and recommendation within the first minute.

Testing the evidence: the quality test most drafts skip

The usual test of a briefing is whether it is complete. The better test is whether the evidence in it is fit for the decision. AHRQ’s framework supplies four dimensions, which can be applied to each finding before the draft is finalized.

• Accuracy: Is the finding correct, and is its source reliable?
• Applicability: Does it apply to this organization, its size, its sector and its constraints?
• Actionability: Can the organization act on it with the resources and authority it has?
• Adequacy: Is there enough evidence to decide, or does the decision require more before it can responsibly be made?

These tests prevent the failure mode in which a recommendation is technically correct but operationally unusable. A second common failure is modular repetition, in which the same finding is restated in the headline, the evidence and the recommendation without adding decision value. GAO advises that each major message appear once. A useful editing pass is to delete every sentence that repeats a point already made in an earlier section and to check whether the briefing is weakened; typically it is not.

The tone requirement is related. GAO and the Office of Management and Budget converge on the principle that executive communication should be clear without being sensational: it explains why the matter requires attention, separates major findings, describes consequences and choices, and preserves enough context that a non-specialist can follow the decision.

Adapting the framework to technical and security decisions

Briefings on cybersecurity, infrastructure, risk and fractional technology leadership present a particular difficulty: the underlying material is voluminous and specialized, and the reader is typically not a specialist. For these topics, the decision section should explicitly identify the control or capability gap, the business exposure, the options, the recommendation, the cost or resource requirement, the deadline, the risk owner and the validation measure. Architecture diagrams, vulnerability inventories, logs and methodology support the decision and should be referenced from the appendix, not placed in the body.

A worked illustration, constructed for explanatory purposes and not drawn from any client engagement, shows the translation. A technical finding might read: unsupported servers remain in a production network segment. The executive version reads: two systems that process customer records can no longer receive vendor security updates; replacing them is estimated to require a defined budget and a six-week window; deferral leaves the exposure open until the next planning cycle; the operations lead is proposed as owner, and completion will be validated by a follow-up scan. The first sentence describes a condition. The second describes a decision.

For small businesses in the United States, the same translation applies across operations, cybersecurity and technology findings: business impact, decision alternatives, required investment, the risk of delay and an accountable next step. Teams building a board-level cybersecurity narrative may find the sequencing in our guide to NIST CSF implementation with board-ready profiles a useful companion, and IT leaders preparing infrastructure decisions can compare the deliverables described in our cloud migration assessment article.

Our perspective on briefings under pressure

We approach the briefing as a problem of clarity under pressure before we approach it as a problem of formatting. In our work across technical advisory, leadership training and software, the same pattern recurs: the people who must decide are rarely short of information, and are short of a sequence that lets them use it. A template does not supply that sequence unless the author has first settled what the decision is.

For that reason we recommend writing the decision sentence before anything else, and refusing to continue until it can be stated in a single line. If it cannot, the problem lies upstream of the document, usually in an unresolved disagreement about the objective. We also recommend that technical specialists draft the appendix first and the briefing second, so that the detail is preserved without being allowed to crowd the argument.

The discipline extends to delivery. Under stress, a reader’s attention narrows, and a briefing that opens with background spends the scarcest resource on the least valuable material. Our own material on restoring clarity under pressure treats this as a communication habit that can be trained, not a trait.

— Jesse Hart

Where PROJECT-JTH can help

Organizations that need the findings behind a briefing, and not only its format, can engage us for technical consulting and systems risk review, which covers risk assessment, security remediation and infrastructure review. Independent consultants and advisory practices that produce assessment reports for clients may prefer Project Praxis, priced at $99 per month, which is built around consulting assessment and report workflows. Pricing for consulting engagements is not published; the contact route is on the site.

Common errors and how to correct them

Several recurring errors reduce the value of otherwise sound briefings. Burying the request is the most frequent: the decision appears in the final paragraph, after the executive has already formed an impression of the issue as informational. The correction is to move the request to the first line. A second error is presenting a single option, which gives the reader no basis for judging whether alternatives were considered; including deferral as an explicit option addresses this. A third is jargon left undefined, which conflicts with the NLRB’s direction to define technical terms for nontechnical readers. A fourth is the absence of an owner and date, which converts a recommendation into an observation.

A final error concerns variants. Because the SBA guidance ties the summary to its purpose, a single briefing circulated unchanged to a board, a lender and an operations team will serve at most one of them. Maintaining a short master record of findings, from which each variant is assembled, is usually more efficient than editing one document three times.

Frequently asked questions

What makes a good executive summary?

A good summary is independently understandable, concise, accurate, written in plain language, aimed at a specific audience and oriented toward a recommendation. It should present each major message once. Length conventions of about 5% to 10% of the full document are common, though they are conventions and not rules.

How do you write a briefing document?

Identify the decision-maker and the deadline, then state the bottom line first. Explain what changed, present the few findings that support the conclusion, compare realistic options including deferral, state the recommendation, and specify owner, resources, timing and follow-up. Place supporting detail in an appendix.

How do you create an executive briefing?

Begin with the business objective and the audience, not with generic background. Frame the question behind the decision, gather only evidence that bears on it, and test that evidence for accuracy, applicability, actionability and adequacy. Then assemble the briefing using the eight-part framework above.

Is there a standard number of parts?

No. GAO uses six or seven modules, APMP uses five boxes for proposals, and university guides use their own sequences. The eight-part framework here is a synthesis, and a five-part version is a reasonable compression when the reader has little time.

Sources

• AHRQ, Informed Decisions Toolbox
• GAO, Guide for Writing Executive Summaries
• Stanford Law School, Policy Memos
• NLRB Communication Standards, Executive Summary
• IEA EBC, Executive Summary Writing Guide for Operating Agents
• Colorado State University, Executive Summaries
• Duke Writing Studio, Policy Memo
• U.S. Small Business Administration, How to Develop and Use a Good Executive Summary
• OMB, Clarifying Regulatory Requirements: Executive Summaries

Recommended

• Leaders: 3 Moves From Neuro + AAR to Restore Clarity Under Pressure
• 60 Second Rehearsal to Fix Communication Under Pressure for Leaders