Writing Executive Briefing Memos

An executive walks into roughly 20 to 40 meetings a week. Almost none of them have time for a thorough pre-read; most are read in the two minutes between the previous meeting and this one. The brief that fails to deliver in those two minutes does not get a longer read later — it just produces an executive who walks in cold.

This page is about the craft of the brief: what fits, what does not, the structure that makes it scannable, and the small editorial choices that separate the brief that actually helps from the brief that looks like it does. The broader context — when a brief is needed at all and where it fits in the executive's working rhythm — sits in the executive daily rhythm guide; the operational discipline around handling sensitive briefs in inboxes and shared drives pairs with the confidentiality guide.

The Single Hardest Choice

Almost every brief gets longer than it should because the writer is hedging. They are not sure what the executive needs to know, so they include everything. The result is a two-page document the executive will not read past the first paragraph.

The discipline is to make the choice. What does this executive need to know to walk into this meeting prepared? Not "what's relevant," not "what's accurate" — what does the next two minutes of reading need to deliver? Everything else gets cut.

The brief that succeeds is closer in spirit to a flight briefing than to a research report. The pilot does not get the full meteorology — they get what's needed to make the right decisions in the next ninety minutes.

The Standard Structure

Most useful briefs run in roughly the same shape. Variations are fine; abandoning the structure entirely usually produces a worse document.

1. The summary line

One sentence at the very top. Not the title — a real sentence. "30-minute call with the head of [company] to discuss whether to extend the partnership; she is expected to push for early renewal at flat pricing." The executive reads this line and already knows roughly what to expect. Everything else in the document elaborates.

2. Who and what

Two or three lines covering: who is in the meeting, what their role is, and what is on the agenda. Names matter — a brief that calls participants "the head of marketing" instead of using the actual name is a brief that signals less preparation than the executive is about to walk into.

3. Context

What has happened before this meeting. The previous conversation, the relevant history, the deal that was started six months ago. Two to four sentences, max. The temptation is to pad this section because it is the easiest to fill; resist it.

4. What's actually being decided or discussed

The substantive heart of the brief. What is the meeting for, what is the live question, where is the disagreement, what does each side want? This is the section the executive will reread; make sure it is clean.

5. What you recommend or what is needed from them

Briefs that omit this are weaker. Even if the executive already knows what they want to do, naming it explicitly forces clarity. "Recommendation: agree to a one-year extension at current pricing if they agree to expanded usage rights." Or, when no recommendation is appropriate: "Decision needed: whether to introduce them to [other person]."

6. Risks or things to handle carefully

One short paragraph if applicable, none if not. The interpersonal nuances ("she is going to bring up the pricing dispute from last quarter — it was resolved, but expect it"), the political constraints, the things the executive should not say or commit to.

7. Logistics, if relevant

Time, place, dial-in, who is hosting, what they should bring. Often this lives in the calendar invite already; only repeat it in the brief if there is a non-obvious detail.

What Goes In That Most Briefs Miss

Three categories of information are often the most useful and the most omitted.

The other side's likely position

"They are going to ask for X. The reason is Y. They will probably accept Z if X is not available." This is the section that turns a brief from a summary of the past into a tool for the meeting itself. It requires you to have thought about the meeting from the other side, which is exactly the work that makes the executive look prepared in the room.

The thing the executive will be tempted to say but should not

An executive who has been in this conversation many times has reflexes — a position they default to, a comparison they always reach for, a deal point they tend to volunteer. Sometimes the right move in this specific meeting is to not do that. Naming the trap explicitly — "Note: this is not the right meeting to bring up the [X] issue; that conversation belongs in next week's call with [Y]" — saves a real misstep about half the time you flag one.

What success looks like

One sentence describing the outcome you (or the executive) would want from the meeting. Not a long discussion of objectives — one specific outcome. "If they agree to a six-month pilot, this is a good meeting." This sentence at the bottom of the brief reframes the whole document; the executive walks in knowing what they are trying to produce, not just what they are trying to discuss.

What Stays Out

• The full attached agenda. The brief points to it; it does not duplicate it.
• Background that is in their head already. If the executive has been working with this customer for two years, do not start by explaining who the customer is.
• Editorial commentary. "This will be a tough meeting" or "we should be careful here" tells the executive nothing they cannot read for themselves. Stay neutral.
• Long quotes. A long block quote is a sign that you have not edited; pull the relevant phrase and paraphrase the rest.
• Hedging language. "It's possible that" and "we might want to consider" are filler. State things; if uncertain, say "uncertain whether."
• Anything you would not be comfortable with the meeting attendees reading. Briefs do, occasionally, end up forwarded by accident. Write to that risk.

Length and Format

One page is the target

A brief that runs longer than one page is almost always too long. The discipline of fitting on one page forces the editorial choices the document needs anyway. Two pages is acceptable for a board-meeting brief or a major external meeting; four pages is rarely useful.

Format follows reading conditions

If the executive reads on a phone, the brief should fit on a phone screen with bullet points the eye can scan. If they read on a tablet on the way to the office, a slightly denser format is fine. If they read on the printed page on their desk, you have more flexibility. Match the medium.

Headers and bullets, not paragraphs

Briefs are scanned, not read. A document with seven headers and short bullet lists supports scanning; a document with three dense paragraphs does not. The brief should be readable at three speeds: thirty seconds (skim the headers and the summary line), two minutes (read all the bullets), five minutes (read the full document). Briefs that only work at five minutes have failed; almost no executive will give them five.

The Voice Question

Briefs are typically written in your voice for the executive's eyes. This is different from communications you draft for the executive to send. The voice should be neutral and direct — closer to news writing than to internal team chat. Two specific moves:

• Use the name, not "the executive." "Recommend agreeing to..." is more readable than "It is recommended that [executive] agree to..."
• Name people by full name on first use, surname after. Standard professional convention; signals care.

Resist the urge to write in your executive's voice. The brief is your work, even when it is in service of theirs.

Iteration: Briefs Get Better Over Time

Two practices compound:

The post-meeting glance-back

After a meeting your brief covered, take thirty seconds to ask yourself: was the brief useful? Did it cover the actual content of the meeting? Did the executive flag anything they wished it had included? You will not always remember to do this; the third time you do it, the pattern starts to surface.

A shared phrasebook of recurring patterns

Most executives have ten to fifteen meeting types they attend repeatedly — quarterly business reviews, customer advisory boards, vendor pitches, team standups, executive committee, board prep. The brief for each type stabilizes after you have written three or four. Save the structure for each; the next one becomes much faster. The bigger collection of these belongs alongside your other reusable templates, near the communication templates in the broader template library.

When You Will Not Have Enough Information

Sometimes you are asked to write a brief for a meeting you do not have full context on. You did not see the original email exchange, you have not been read in on the strategy, the executive has the relevant context in their head and not on paper.

The right response in that situation is to ask one specific question — "I'm putting together the brief for tomorrow's [meeting]. Can you give me the one sentence on what you want to walk out with?" — rather than to guess. The brief written from a guess is often worse than no brief; it pushes a misframing into the executive's mind right before the meeting.

Sometimes the answer is "no brief is needed for this one" and that is fine. Skip cleanly. The executive will notice when you skip selectively — it signals judgement, not gaps.

Common Mistakes

• Writing the brief at the last possible moment. A brief drafted thirty minutes before the meeting reads as such. Aim to draft the night before; finalize the morning of.
• Burying the lead. The most important thing should be in the first sentence, not on the second page.
• Treating the brief as a status report. A brief is forward-looking — it is about the meeting that is about to happen, not about what has already been done.
• Including everything you know. The brief is the result of editing. If you have not cut anything, you have not edited.
• Forgetting that briefs are sometimes forwarded. Write so that an accidental forward to someone else in the meeting would not produce a problem.
• Letting the format drift over time. Each brief should look like the previous one. Consistency makes scanning faster.

The weekly habit of writing briefs is one of the more underrated forms of professional development for an admin. It builds editorial skill, forces you to think about meetings strategically, and produces visible artifacts of judgement that other people see. Over a year, it tends to be one of the things most strongly associated with admins who get pulled into more substantive work — not because the briefs themselves are visible to senior leaders, but because they shape the executive's experience of working with you in ways that compound. The structural place for the brief format itself, and the per-meeting-type variants you build over time, is in your desk manual.