Meeting Agenda Template
The agenda you sent out and the meeting that actually happens are two different things. The first is a list of topics with rough time guesses next to them. The second is three people deciding things while everyone else watches the clock. This template is built for the second one, because that's the one that costs you money.
Most agendas fail for a simple reason: they describe what you'll talk about, not what you'll decide. "Q3 budget review" is a topic. "Do we cut the influencer spend or hold it flat through December?" is a decision. A room can talk about a topic for an hour and leave with nothing. The same room resolves a decision in twenty minutes, because the end state is obvious and someone has to own it.
The rule that makes this template work: every item is a decision with an owner and a time budget. If an item has no decision inside it, it's a message, and a message belongs in email, not on the calendar.
The template
Copy this into Google Docs, Word, or Notion before you send the invite.
Meeting: Q3 pricing and hiring plan Date / time: Thu, Oct 15 · 09:00–09:25 Called by: Sarah (owner) Note taker: Priya Pre-read (sent with the invite, read beforehand): last quarter's margins, the open pipeline list, the current onboarding doc
| Decision to make | Owner | Minutes | Pre-read | Outcome wanted |
|---|---|---|---|---|
| Do we raise the service price 6% from March 1, or hold? | Sarah | 7 | Job margins by service | Decision |
| Which two accounts do we close out this quarter? | Marcus | 10 | Open pipeline list | Decision |
| Who owns the Q4 onboarding revamp? | Priya | 5 | Current onboarding steps | One owner named |
Ground rules printed at the bottom:
- The agenda goes out with the invite, and the pre-read goes with it. Nobody presents a document in the room that could have been read beforehand.
- Each item starts with the owner stating the decision in one sentence, then the options. Discussion follows the options, not the other way around.
- When an item's minutes run out, the owner decides, or names who will decide and by when. Nothing rolls over unnamed.
- The last five minutes belong to the note taker. Every action is read back with a name and a date.
How to fill each field
Decision, not topic. "Pricing" is a topic. "Do we raise prices 6% from March 1?" is a decision. Write every row so it can be answered in the room with a yes, a no, or a choice. If you can't write it that way, the item isn't ready for a meeting.
Owner. One person per row. If you can't name an owner, the row isn't ready either — a meeting is not where you find out who owns a decision.
Minutes. This is the longest you'll allow, not your estimate. Five rows of five minutes plus the read-back is a 25-minute meeting. If that's over your budget, cut a row instead of stretching the time.
Pre-read. A row whose pre-read doesn't exist yet moves to the next meeting. Meetings are for taking decisions, not gathering evidence.
Outcome wanted. Write the end state: a decision, one owner named, a date committed. If nobody can say what "done" looks like for the item, it goes back to email.
The part everyone skips
The read-back is the only five minutes of a meeting that reliably turn talk into work. Whoever took notes reads every action back out loud: what, who, by when. If an action has no name or no date, it isn't an action — it's a suggestion, and suggestions die in the notes.
This is where a notetaker earns its keep. Meetbook records the call from the browser tab with no bot in the meeting, then turns it into action items with owners, each one backed by the exact quote, speaker, and timestamp it came from. When the note taker is also the person driving the discussion, the read-back is already half-written. For recurring meetings, the pre-meeting brief pulls up what was decided last time, so the next agenda writes itself.
You don't need the tool to run this template. A person and a notepad do the job fine. The tool just means the note taker gets to stay in the conversation instead of transcribing it.
Same skeleton, three meetings
One-on-one. Three rows max — one from the manager, one from the report, one decision about a blocker or a promotion path. The manager talks last, not first.
Client kickoff. Every row is a decision the client has to make: scope, sign-off owner, timeline. The outcome of the whole meeting is one committed next step with a date, so the deal doesn't sit in "let's circle back."
Standup. No decisions here; it's a coordination message. That means a standup fails the one-line rule and should stay a written update — or shrink to fifteen minutes with the read-back kept at the end.
Three ways this falls apart
- Every item is a topic. The fix is the one-line rule above. If you can't put a decision in the row, the row leaves.
- No owner on the row. Someone has to walk in knowing they're on the hook. Name them on the agenda before the meeting, so they can prepare instead of being surprised.
- The read-back gets cut for time. It's the cheapest five minutes on the calendar and the only part that produces work. If you run long, cut a discussion item before you cut the read-back.
When not to have the meeting
If the whole agenda is updates people could read, cancel it and send the document. If there are no decisions to make, there's no meeting to hold — and everyone on the invite will quietly thank you for it.