How to brief your manager in five sentences
Your manager does not read messages. They triage them — on a phone, between meetings, with thirty seconds before the next thing starts. A brief that respects that reality gets a decision in minutes. A brief that tells a story waits days for a meeting slot. This guide shows the difference, then gives you a five-sentence frame you can reuse for every update.
Why do managers reward brevity?
A manager’s unit of work is the decision. Every message they open is a request to think, and long messages hide the request inside a story. When you send four paragraphs of context, you transfer work: now they must find the question, weigh it, and remember it until they have time to answer.
A structured brief does that work in advance. It declares what kind of message this is, what is at stake, and which single action is theirs. People who consistently write this way become safe to read between meetings — so their messages get opened first and answered fastest. Brevity is not a style preference. It is a service.
What does a weak brief look like?
Hi Daniela,
Quick update on the Meridian project. So as you know we’ve been working with the vendor on the integration piece, and there have been a few back-and-forths about the timeline. Originally they said end of the month, but then their lead engineer went on leave, and now they’re saying it might slip. We’ve also been looking at whether we could do part of it in-house, which Tom thinks is doable but he’d need to check a few things first. There are also some budget implications depending on which way we go, which I can walk you through. Anyway, lots of moving parts — happy to jump on a call whenever you have time and I can give you the full picture.
Thanks, Priya
The structure is chronological: events in the order they happened. The decision is never named. The deadline does not exist. The closing line outsources the real brief to a future meeting. Daniela now has homework — and until she does it, nothing moves.
What does a strong brief look like?
Hi Daniela — Meridian needs a decision.
Situation: the vendor’s integration slips two weeks; their lead engineer is out. Decision needed: wait for the vendor, or move the work in-house to Tom’s team. Risk: in-house protects the deadline but costs roughly 20 hours of Tom’s time during the audit. From you: a yes or no on the in-house option. By when: Wednesday, so Tom can start Thursday.
Detail below if useful. Priya
Twenty seconds to read. The first line declares what kind of message this is. The five lines answer the five questions Daniela would have asked anyway. She can reply with one word.
What is the five-sentence frame?
- Situation. One sentence, present tense, no history. What is true right now.
- Decision needed. The fork in the road, stated as options. Not what happened — what must be decided.
- Risk. The one real risk, with a number if you have one. Listing five risks signals you have not ranked them.
- What you need. From this person specifically: a decision, a resource, an escalation. Name it.
- By when. A date, plus the reason the date exists. Deadlines without reasons read as pressure; deadlines with reasons read as logistics.
Write the five sentences in that order even when it feels blunt. Bluntness in structure leaves room for politeness in wording.
What if it does not fit in five sentences?
Then the five sentences become the front door. Send them first, add a divider, and put the supporting detail underneath for whoever wants the long version. The brief must survive on its own; the appendix is optional reading.
And if no decision is needed, say so in the first line — “FYI, no action needed.” Labeling which messages need your manager is half of what makes the labeled ones work.
Save these rules as a playbook
Briefing a manager is a role: the same frame, filled with new facts each week. In ILURA you save this five-sentence frame once as a role playbook, and every draft starts structured instead of chronological — straight from the Share Sheet or a Shortcut, generated on your iPhone. Correct one draft and the playbook remembers your version of the frame.
Turn this message into an agent rule
Do not treat the answer as a one-off rewrite. Save the repeatable behavior behind it so your ILURA agent can apply the same judgment next time.
- What situation triggered the message?
- What tone, boundary or decision should repeat?
- What should the agent avoid doing again?
Problems this guide helps with
The same rule appears in real user searches.
Do it now
Draft this in ILURA right now.
Open ILURA, paste your message, and get help with "brief your manager quickly" — in your voice, on device, free. It quietly saves the rule (Situation, decision needed, risk, ask, deadline.), so the next time is one tap.
Free to start · No account · Data Not CollectedQuick answers
- What if the situation is too complex for five sentences?
- The five sentences are the front door, not the whole house. Send them first, then put the supporting detail below a divider for whoever wants it.
- Should I brief my manager by email or chat?
- Use whichever channel your manager actually reads, but keep the structure identical. The five-sentence frame works in chat, email, or a hallway conversation.
- What if I do not need a decision, just visibility?
- Say so in the first line — 'FYI, no action needed' — and your updates will be read more, not less. Managers reward people who label which messages need them.