Imagine you have a page of notes from a project you’ve been working on for the last month. There are a few metrics, some things the team finished, a problem with the timeline, two options you’ve been discussing, and a recommendation you’re starting to lean toward.
Now you need to send something to someone else.
What exactly are you writing?
This is one of those questions that sounds more obvious than it is. “Brief,” “update,” and “summary” get used pretty loosely at work, and sometimes we start writing before we’ve decided what we actually want the document to accomplish.
I’ve found it easier to think about three common formats based on the question the reader is bringing with them.
“Where are we?”
That’s a status update.
Your reader already has some context about the project. They don’t need you to introduce the entire thing again. They mostly want to know what changed since the last time they heard about it.
Tell them what moved forward. Call out the details that matter. Be clear about anything that is blocked or at risk, and finish with what happens next.
If the launch date moved from May 10 to May 17, say so. If testing is 90% complete, that’s probably useful. If you’re waiting on security approval before anything else can happen, don’t hide that in the middle of a paragraph.
A good status update lets someone get oriented without sitting through a replay of your entire week.
“What do I need to know?”
That’s where I’d reach for an executive brief.
Maybe someone is joining the conversation late. Maybe they’re responsible for several projects and don’t have time to read all of the background material. Maybe they simply need the important picture before a meeting.
An executive brief takes a larger amount of information and compresses it into what matters most.
You might include a short summary, a few important facts or metrics, the current situation, the biggest risks, and whatever recommendation or next step deserves attention. You’re giving the reader enough context to understand the situation without asking them to become an expert on it.
And despite the name, I don’t think this format has to be reserved for executives. The useful idea is the compression, not the job title.
“What should we do?”
Now you’re probably writing a decision brief.
This one should revolve around the choice itself. If the reader gets halfway through the document and still doesn’t know what they’re being asked to decide, something has gone wrong.
Put the decision near the top. Then explain the context, realistic options, trade-offs, risks, and your recommendation if you have one.
Suppose you’re deciding whether to delay a launch for another round of testing. One option gets you to market sooner but accepts more uncertainty. The other gives you more confidence but costs another two weeks.
That’s the information the reader needs. They probably don’t need a three-page history of every testing meeting that brought you to this point.
One project could need all three
The interesting thing is that these formats aren’t competing with each other. You might actually write all three at different points in the same project.
On Friday, your manager gets a status update explaining what changed that week. Before Monday’s leadership meeting, someone gets an executive brief that summarizes the bigger picture.
Then a decision comes up about adding two weeks to the schedule, so you prepare a short decision brief explaining the options and trade-offs.
The underlying project hasn’t changed. What changed is the reader and what they need from the information.
Ask one question before you start writing
Before I start organizing a pile of notes now, I like to ask: What should this person know, understand, or decide after reading this?
That question does a surprising amount of work.
If they need to know where the project stands, I can focus on changes, risks, and next steps. If they need the bigger picture, I can pull together the most important context. If they need to make a decision, I can stop burying the choice underneath everything else.
It also gives me permission to leave things out.
Not every note belongs in every document. Something can be important to the project without being important to this particular reader at this particular moment.
That’s one reason Briefly has different brief types instead of treating every pile of notes like it needs the same generic summary. A status update, executive brief, and decision brief can all start from the same messy material, but they should not necessarily end up looking the same.
Sometimes choosing the right format is half the writing problem. Once you know the question you’re trying to answer, the rest gets a lot easier.