How to write a one-page brief that catches someone up fast

Someone missed the offsite. A new person joins the project next week. Your manager asks "where are we on this?" on Thursday afternoon. In each case the worst answer is to forward the whole thread, and the best is a single page they can read in two minutes.

A one-page brief isn't a summary of everything that happened. It's the minimum someone needs to understand the situation and act on it.

What a good brief answers

A brief that works answers four questions, in this order:

1. What's the situation? Where things stand right now, in two or three sentences.
2. What matters? The few facts that change what the reader should do or think.
3. What was decided? Things that are settled and shouldn't be reopened.
4. What happens next? Who is doing what, and especially anything the reader owns.

If a sentence doesn't help answer one of those, it probably doesn't belong.

Start with the situation, not the history

The most common mistake is telling the story in order: first we met, then we discussed, then someone raised a concern. The reader doesn't need the story. They need the current state.

Compare:

We met Tuesday to go over Q3. Revenue was discussed and several people noted the enterprise deals were slipping…

with:

Q3 revenue came in 12% under target, mostly because two enterprise deals slipped to Q4. We're responding by pausing the mobile rewrite and fixing web checkout first.

The second version gives the reader the conclusion first. If they want the history, they can ask.

Pick the facts that change decisions

From everything you know, pick the three to five facts that would change what the reader does. Numbers, dates, constraints, changes from what they last heard.

Good facts for a brief:

• "New per-seat pricing goes out Nov 1. Existing customers keep the old price for a year."
• "Two support hires are approved. The designer role is on hold."

Weak facts for a brief:

• "There was a lot of discussion about pricing."
• "The team is excited about the new direction."

The weak ones aren't wrong; they just don't help the reader do anything.

Make decisions unmissable

Write decisions as plain statements, ideally in a short list of their own. "We're pausing the mobile rewrite until January." Not "the group felt it might be best to consider pausing".

Clear decisions save everyone time. They stop the reader from relitigating something that's settled, and they make it obvious when something actually changed.

End with what the reader needs to do

If the reader owns anything, put it where they can't miss it, with a date. "Sam: you own the customer email about pricing. Draft due Friday." This is often the single most important line in the brief, and it's the one most often buried.

Then list the other next steps briefly, so the reader knows what's moving without them.

How to keep it to one page

• Cut the history. One sentence of context at most.
• Cut the attribution. Who said what rarely matters to someone catching up.
• Use lists for facts and decisions, prose only for the situation.
• Link instead of including. If someone needs the full spreadsheet or the recording, link to it rather than summarizing it.
• Leave out anything still being argued, unless the reader needs to weigh in. Then put it under "open questions" with a clear ask.

A template

You can reuse this shape for almost any brief:

Situation: Two or three sentences on where things stand.

What matters:

• Fact that changes decisions
• Fact that changes decisions
• Fact that changes decisions

Decided:

• Decision
• Decision

Next:

• You: what the reader owns, and by when
• Other next steps, briefly

Open questions (only if the reader can help)

Before you send it

Read it as the person receiving it. Could they act on it without asking you a follow-up question? Could they explain the situation to someone else in one sentence? If not, the brief is either missing a fact or hiding the conclusion.

For the action items part of a brief, the same rules apply as for any meeting recap: every item needs an owner and a date, and a missing owner should be marked rather than guessed. There's more on that in how to turn meeting notes into action items.