team
Most meeting agenda templates are a list of topics with times beside them. Q4 budget, 20 minutes. Hiring update, 15 minutes. They are easy to fill in, which is why they are everywhere, and they fail in a predictable way: a topic has no finish line. Twenty minutes on the Q4 budget ends when the twenty minutes end, not when anything has been settled, and the same line appears on next week's agenda unchanged.
An agenda that works looks slightly different on the page and completely different in the room. Each line names the decision to be made rather than the subject to be discussed, and that one change does most of the work.
The difference is visible in a single line.
A topic line reads: Pricing review. A decision line reads: Approve the new tier pricing for launch on 14 October, or defer it and name what is missing.
The second version does four things the first cannot. It tells invitees what will be asked of them, so they arrive prepared rather than warming up. It gives the chair a way to end the item, because the question is either answered or explicitly deferred. It makes the absence of the right person obvious before the meeting rather than fifteen minutes into it. And it produces the minutes automatically, since the decision has already been written in the form the record needs.
If an item cannot be written as a question the meeting will answer, it probably does not need a meeting. That test alone removes a surprising share of a recurring calendar. An update that nobody will act on is a document. A discussion with no decision attached is a conversation that can happen between two people rather than nine.
Copy this. Everything in square brackets is a field.
Header
For each item
Close, five minutes
The close is not padding. Five minutes spent stating outcomes aloud, in the words that will be written down, is the cheapest available fix for the gap between what people believe was agreed and what was actually agreed.
Every agenda line is one of three things, and problems come from items that pretend to be one type while behaving as another.
Decide. A choice with options and a person who can approve it. These need the pre-read, the time box, and the owner. They belong at the top of the agenda while attention is highest.
Inform. A status, a number, a heads-up. These need no discussion, only a place to be read. Most of them can leave the meeting entirely and become a written update, and the honest test is whether anyone would ask a question if the item were simply posted instead.
Explore. Open problems with no decision available yet. They are legitimate and they are also the items that eat the clock, because there is no natural stopping point. Explore items go last, with a hard time box, and their output is a list of options for a future decide item rather than a conclusion.
An agenda where every line is labelled with one of those three words is noticeably calmer to run. The chair knows when to cut something off, and participants stop treating an inform item as an invitation to reopen a settled question.
| Type | Output | Where it goes | What it needs |
|---|---|---|---|
| Decide | A decision with an owner and a date | Top of the agenda | Pre-read and the person who can approve |
| Inform | Awareness, or nothing | Usually out of the meeting | A written update people can read |
| Explore | A list of options | End, hard time box | A named next step, not a conclusion |
The core structure does not change. What changes is the standing items.
Weekly team meeting. Decisions first, then blockers, then anything parked from last week that is now ready. No round-the-table status, because status is what the board is for and reading it aloud is the most expensive way to distribute it.
Project status meeting. One line per workstream with a red, amber or green marker written down before the meeting, and time spent only on the ones that changed colour. A workstream that has been green for three weeks needs no airtime.
One-to-one. Two agendas merged, with the other person's items first. The manager's items go second, which is the only reliable way to stop the meeting becoming a status report.
Retrospective. A fixed structure people can prepare for, and one ending rule: the meeting produces a small number of changes with owners, not a long list of observations.
Kickoff. The decisions that unblock everything else, in order: scope boundary, named owner, first milestone date, and how the team will communicate. Anything that can be decided later is decided later.
Board or formal committee. Follows the notice and order of business the bylaws require, and the agenda carries the documents the board is expected to rely on.
In informal teams the chair usually writes the agenda and nobody questions it. In a formal body that assumption is wrong, and the correction is useful even for teams that will never take a vote.
Robert's Rules is direct about it: for a proposed agenda to become the official agenda, it must be adopted by the assembly at the outset of the meeting. When the agenda is presented for adoption, any member may move to amend it by adding an item they want added or proposing another change. It is wrong to assume, as many do, that the president sets the agenda. Preparing a proposed agenda is common, but it becomes binding only when the assembly adopts it.
The working version of that principle for an ordinary team is a standing open list where anyone can add an item at any time during the week, with the chair triaging it a day before the meeting. The triage is where items are merged, dropped, converted into a written update, or handed to two people to settle outside the meeting.
Then one rule in the room: an item added at the start of the meeting has to displace something. Meetings do not run over because people are undisciplined. They run over because new work was added to a fixed container and nothing came out.
Writing items as decisions exposes an invite list problem that topic agendas hide. Once a line reads approve the tier pricing, the question of who can approve it answers itself, and so does the question of who does not need to be there.
That is why the template asks for a reason beside each name rather than just the name. Someone who decides has to be present or the item moves. Someone who informs is needed for their item and not for the rest of the hour. Someone who is affected needs the outcome, which is not the same as needing the meeting.
Applied honestly, this shrinks most recurring meetings. A weekly call with nine attendees usually has three people deciding, two presenting, and four attending because they were on the invitation the first time and nobody has revisited it since. Sending those four the decisions instead of the meeting gives them back an hour a week and costs nothing, provided the decisions actually reach them, which is the part that fails when the record stays inside a document.
It is worth running that review on every recurring meeting about twice a year. Invite lists accumulate, and the cost is invisible because it is spread across other people's calendars rather than the organiser's.
An agenda sent ten minutes before the meeting is a table of contents. Its only function is to tell people what is about to happen to them.
Twenty four hours is the point at which an agenda starts changing behaviour, because it is long enough for somebody to read the pre-read, notice that a figure is missing, or say that the wrong three people are in the room. Every one of those saves more time than the meeting itself.
The pre-read deserves a deadline, not a hope. Writing that the pricing memo must be read before 10:00 makes it a commitment, and a meeting that opens with five minutes of silent reading, for the two people who did not manage it, is still faster than one where the first fifteen minutes are spent explaining what everyone was supposed to have read.
The template above is already the shape of the minutes. Each item has a decision line waiting to be filled in, an owner, and a place to note what it is waiting on. Writing the outcome underneath the question during the meeting turns the agenda into the record without a second document, and it means the person taking notes is filling in fields rather than composing prose while trying to follow the discussion.
What has to leave the document is the commitments. A decision with an owner and a date is not finished when it is written down, and an agenda file, however well structured, is not going to remind anyone on Thursday. Moving each one onto a board where the task carries its own owner and due date is the step that separates teams whose meetings produce work from teams whose meetings produce documents.
Where the decisions already exist as text, that transfer does not have to be manual either. A task tool that can be driven from ChatGPT or Claude will read a set of agreed decisions and create the cards, which removes the last friction from the only part of the meeting that outlives it.
Take the next recurring meeting and rewrite every agenda line as a question, then label each one decide, inform or explore. The inform items usually leave the meeting the same week. Then give the decisions somewhere to live after the call, such as a board that is free for a team of five, and keep the last five minutes for reading the outcomes back to the room.
A one sentence purpose, the attendees with the reason each is needed, a pre-read with a deadline, and one line per item written as the decision to be made, with a type, an owner, a time box, and what must be true if it cannot be decided. Close with five minutes to read decisions back.
About 24 hours. That is long enough for somebody to read the pre-read, spot a missing figure, or point out that the person who can approve the decision is not invited. An agenda sent minutes beforehand changes nothing about how the meeting runs.
In a formal body, the assembly does. Robert's Rules states that a proposed agenda becomes official only when adopted at the outset of the meeting, and that any member may move to amend it. For ordinary teams the practical equivalent is an open list anyone can add to, triaged by the chair a day before.
Long enough to answer its question and no longer, which usually means decision items get the most time and go first. Explore items need a hard time box because they have no natural end, and inform items are often better distributed as a written update than given minutes at all.
No. The structure stays the same and only the standing items change. A weekly team meeting, a project status meeting and a one-to-one all work from the same fields: the decision, the type, the owner, the time, and what is needed beforehand.