28 August 2026
A manager who didn't attend the meeting needs three things in the first two lines: what was decided, what's at risk, and what they're being asked to do. Everything else — who was there, what the agenda said, what got discussed — is context they'll read only if the first two lines earn it. Lead with attendance and you've already lost them; lead with the ask and you get a reply before lunch.
A manager scanning their inbox between two other calls opens a message, sees a paragraph that starts with names and a date, and closes it. Not because they don't care — because the first line didn't tell them whether they need to act. They're triaging, not reading, and a summary that opens with attendance reads like it has nothing urgent in it, even when it does.
This is the gap between a note written for the room and a note written for someone who wasn't in it. The team already knows who was there. The manager needs to know, in the time it takes to read a text message, whether this is their problem now.
Three things earn a reply: the decision, the risk, and the ask. Order matters — put the ask last and it gets skipped along with everything after it.
Your team's notes should keep the full trail — who raised the concern, what was tried before, why the vendor's first offer got rejected. That record protects the team later, when someone asks why a decision was made. None of that belongs in the version that goes up.
The mistake is writing one document and sending it to both audiences. The team wants the reasoning; the manager wants the outcome. Compressing the team's notes into two lines isn't losing detail — it's routing detail to the people who'll use it and stripping it from the people who won't.
Start from the full transcript or notes, then ask one question of every line: does this change what the manager does today? Almost everything fails that test. What survives is usually one decision, one number, and one date.
A workable template: 'Decided [X]. Risk is [Y] by [date]. Need [Z] from you by [deadline].' It reads like a text because that's the register a manager reads it in — between meetings, on a phone, deciding in ten seconds whether to reply now or later.
AVAY's AI participant keeps a running record of decisions during the call and can search across every past meeting, so a two-line draft for a specific stakeholder can be pulled together from what was actually said rather than reconstructed from memory afterward. Ask it out loud mid-call — 'what does the risk owner need to know' — and it can surface the relevant lines.
It doesn't know your org chart. It can't tell you that this particular risk is the one that gets escalated to a VP and that one isn't — that judgment is still the human's job. What it removes is the transcription and recall work, not the decision about who needs to hear it.
| Team record | Upward summary | |
|---|---|---|
| Purpose | Preserve reasoning and trail for later | Get a decision or reply from someone who wasn't there |
| Opens with | Attendees, agenda, context | The decision, the risk, or the ask |
| Length | As long as the discussion needs | Two to three lines, no more |
| What's cut | Nothing — it's the archive | Everything except what changes their day |
Two to three lines: the decision, the risk with a date attached, and the specific ask. If it takes longer than fifteen seconds to read, it's still a team note, not an upward one.
Say that directly — 'no decision yet, blocked on X, need Y by Friday' is more useful to a manager than a paragraph explaining the discussion. An open risk with a deadline is still a valid two-line summary.
No — the team's notes carry the reasoning trail your manager doesn't need and won't read. Write the two-line version separately, even if it takes an extra two minutes; it's the version that actually gets a reply.
If it changes a deadline, a budget, or something the manager is accountable for outside this team, it's theirs to know. If it's recoverable inside the team without their input, keep it in the team record and leave it out.
A manager who wasn't in the room reads for the decision, the risk, and the ask — put those in the first two lines and everything else is optional; put attendance first and none of it gets read.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.