The anatomy of a good Brief

A handoff document fails when it answers the questions the author found interesting instead of the ones the recipient will actually ask. Before adding a single source, write down the five questions the next owner will ask in their first hour: who decides, what is committed, what is at risk, what happens next, and where the numbers came from.

A Brief is judged by how quickly it answers those five. Everything else is supporting material. The best authors spend more time choosing the right sources than polishing prose, because a recipient can forgive messy formatting but cannot forgive missing context.

Try this test: hand your draft to a colleague who has not been involved and ask them to read it once. Then ask them the five questions above. If they hesitate, the Brief is not done yet. The hesitation tells you exactly which source is missing or which assumption is unstated.

Most documents are written to prove the author did the work. A Brief is written to save the recipient time. That inversion changes every decision about what belongs on the page. When you are unsure whether to include something, ask whether it helps the recipient make a faster or better decision. If it does not, leave it out.

A strong Brief is built in four layers. Each layer serves a different reader at a different moment, and together they replace the need for a follow-up meeting. Think of them as a funnel: most readers stop at the top, and only the most committed or skeptical go all the way down.

• Summary — six to ten sentences a reader can absorb standing up. State the situation, the current position, and the immediate decision. This is what an executive reads on a phone between meetings.
• Entities — the people, organizations, dates, and amounts that recur. These are what recipients search for by name when they need to verify ownership, budget, or authority.
• Sources — the raw material: notes, threads, contracts, exports. Messy is fine; unfiltered is better than curated. The goal is evidence, not elegance.
• Quick asks — four curated questions that get a recipient to value in one click. They turn a static document into a conversation.

The layers are sequential. A reader who wants the headline stops at the summary. A reader who doubts the headline drops into the sources. A reader who needs action uses the quick asks. No single reader has to wade through everything, but every reader can go as deep as their role requires.

This structure also makes the Brief easier to maintain. When the deal changes, you update the sources and regenerate the summary. When the team changes, you update the entities. When you learn what recipients actually ask, you update the quick asks. The Brief becomes a living system rather than a one-time document.

Brevity is not about word count; it is about decision relevance. Leave out narrative history that does not change a decision, internal commentary about people, and anything you would not want forwarded. A Brief is a shareable artifact; assume it travels further than you intend.

Also leave out predictions presented as facts. 'The deal will close by Friday' is a prediction. 'The buyer said they intend to sign by Friday in a Slack message at 3:42pm' is sourced. The second version lets the recipient judge confidence for themselves and gives them the evidence to do so.

Leave out jargon that does not serve the recipient. Every acronym should earn its place. If a term is necessary, define it once in the entities layer and use it consistently. If it is not necessary, replace it with plain language. The goal is clarity, not vocabulary.

Recipients trust answers they can verify. When every answer points back to the line in the source that produced it, the reader stops auditing the summary and starts acting on it. That is the difference between a document that gets skimmed and a Brief that gets used.

The evidence trail also protects the author. A month later, when someone asks why a decision was made, the Brief still contains the original source. Memory fades; the trail does not. This is especially valuable in high-stakes handoffs where the outgoing owner may not be available for follow-up questions.

In practice, the evidence trail means attaching the actual email thread rather than summarizing it, uploading the actual budget export rather than retyping the numbers, and including the actual meeting notes rather than relying on what was remembered. The extra context makes the Brief slower to create but dramatically faster to consume.

You do not need to write a Brief from scratch. In fact, you should not. The best Briefs are assembled from existing material and then edited. Here is a sequence that works for most situations.

• Dump every relevant source into the Brief first — emails, notes, spreadsheets, screenshots. Do not organize yet.
• Generate a summary and correct only what is wrong, not what is awkward. The summary should sound like a smart colleague explaining the situation.
• Add the four quick asks you would want if you were receiving this tomorrow. Imagine yourself in the recipient's role.
• Read the Brief as the recipient, not the author, and delete one thing you are attached to but they do not need.
• Publish and send the link; do not attach a PDF. A live Brief can be updated when the situation changes.

The final step is the hardest because it requires letting go of material you worked hard to gather. But the test is simple: if the recipient does not need it to make a decision, it is clutter, not content. A shorter Brief is not a weaker Brief.

Even experienced authors fall into a few traps. Recognizing them early saves time and produces better results.

• Writing the summary first, before the sources are collected. The summary should reflect the evidence, not shape it.
• Curating sources too heavily. If you only include the messages that support your narrative, the Brief becomes propaganda.
• Using too many quick asks. Four is the limit. More becomes a menu; menus get skipped.
• Forgetting the recipient's context. A board member and a new hire need different summaries from the same sources.

Open an example Brief and ask it the questions from this guide, or create your own Brief in a few minutes.