A meeting agenda template you can copy in 30 seconds

The meeting agenda template

Copy this whole block into the body of the calendar invite or a shared doc. Replace anything in square brackets. Delete any line that does not apply, but think twice before deleting the purpose line or the owner column. The last three lines — parking lot, not on this agenda, next meeting — sit at the bottom of the same invite, under the item list. They are what stops the same subjects coming back week after week.

Meeting: [Name of the meeting]

Date and time: [Day, date] · [Start]–[End] · [Time zone]

Where: [Room, or the call link]

Purpose: [One sentence, starting with a verb. Why this meeting is happening today.]

We leave with: [The outcome. A decision, a plan, an approved document, a number everyone agrees on.]

Chair: [Name] · Notes: [Name] · Timekeeper: [Name]

Attendees: [Name (role)], [Name (role)], [Name (role)]

Pre-read ([X] minutes, before the meeting): [Doc name and link] · [Doc name and link]

• Parking lot: [Anything raised that matters but is not for today. Write it down with a name and a date, then move on.]
• Not on this agenda: [One line naming the thing people might expect and will not get, and when they will get it. Saves three emails.]
• Next meeting: [Date, and the one thing that must be ready by then.]

What a meeting agenda actually has to do

That template is short because an agenda has one job. Tell people what will be decided, in what order, and who is bringing it. Everything else is decoration.

Test yours like this. If a person reads it and still does not know what to prepare, it failed. If nobody can tell on Friday whether the meeting achieved anything, it failed. Most agendas that fail this test are really just a list of topics with times next to them.

Six parts do the whole job:

• Purpose. One sentence starting with a verb, saying why this meeting exists today.
• Desired outcome. The thing that exists at the end that did not exist at the start. A decision, a number, a signed-off document.
• Timeboxed items with an owner. A clock time, a question, and exactly one person's name.
• Pre-reads. Links, with an honest reading time, sent early enough to be read.
• Decisions separated from updates. These two need different amounts of time and different behaviour in the room.
• Parking lot. Somewhere to put the important thing that is not today's thing.

A filled example: a 30-minute weekly sync

Here is the same template with a real meeting in it. Ledgerloop is a small invoicing tool. The company is invented, the shape of the meeting is not.

Meeting: Ledgerloop growth sync

Date and time: Thursday 15 October 2026 · 09:30–10:00 · CET

Where: Meeting room 2, plus a Google Meet link for Priya

Purpose: Decide the refund window and approve the October pricing page, so the page can ship on Monday the 19th.

We leave with: Two decisions written down. Nothing else.

Chair: Amina · Notes: Tomas · Timekeeper: Karl

Attendees: Amina Haddad (product), Tomas Nowak (engineering), Priya Raman (support, dialling in), Karl Ivarsson (sales)

Pre-read (6 minutes): Refund data, September (one page, four charts) · Pricing page draft v3 (Karl's comments already in the margin)

• Parking lot: should tax handling move to Stripe Tax? Raised by Karl at 09:47. Karl writes a one-page comparison by Wednesday 21 October, and it gets its own 20-minute meeting instead of five rushed minutes here.
• Not on this agenda: the Q4 roadmap. That is 6 November.
• Next meeting: Thursday 22 October. The Stripe Tax one-pager must be circulated by Wednesday evening.

What the example gets right, and what goes in each field

Now look at what is missing. There is no item called "AOB". There is no item called "Marketing". There is no item without a person's name against it, and no item that could be answered by reading a dashboard.

The two decision items are worded as questions with a small set of answers. Fourteen days or thirty days. Approve or send back. A question with two answers gets settled in ten minutes. An item called "refunds" eats the whole meeting and ends with somebody saying "let's take it offline".

The timeboxes also do not add up to thirty minutes on purpose. The six items total 26 minutes, so the recap ends at 09:56 and four minutes of the slot are never booked. Those four minutes are what pays for the meeting starting two minutes late, which it will, and for the one item that runs a minute long. An agenda that fills the slot exactly has already overrun before anyone speaks.

Here is every field on the template, with the one line of work it needs and the one mistake people make.

• Purpose. Start with a verb: decide, approve, choose, unblock. Wrong: describing the topic. If your purpose line would still be true after a meeting that changed nothing, it is a topic.
• We leave with. Name the artefact. "A refund window written in the notes." Wrong: writing "alignment". You cannot check alignment on Friday.
• Date, time, time zone. Always write the time zone when one person is remote. Wrong: assuming people read the calendar rather than the agenda text.
• Roles. Chair runs it, notes person writes it, timekeeper calls time. Wrong: letting the most senior person take notes. They stop the moment it gets interesting.
• Attendees with roles. The role in brackets tells people why each person is there. Wrong: inviting people "for visibility". Send them the notes instead. Each extra person makes the room quieter.
• Items written as questions. "Do we ship on the 19th or the 26th?" Wrong: one-word items. "Budget" is a category, not an item.
• Type. Decision, discussion, update, open, close. It tells people how to behave before the item starts.
• Owner. Exactly one name per row. Wrong: a team, a department, or "we". More on this below.
• Outcome needed. What must be true when the item ends. Wrong: repeating the item title in different words.
• Time. Clock times, not durations. "10 min" tells nobody in the room whether you are behind.
• Pre-read with a reading time. "One page, 6 minutes." Wrong: attaching a 40-slide deck at 11pm and calling it a pre-read.
• Parking lot and not-on-this-agenda. Both exist to protect the timeboxes. Wrong: a parking lot nobody empties, which teaches people that parked means buried.

The agenda item with no owner

This is the most common way an agenda fails, so it gets its own section.

An item with no name against it belongs to nobody. In a room of six, everyone assumes somebody else prepared it. The chair opens it, there is a pause, someone improvises for four minutes, and it rolls to next week with the same missing name. Three weeks of that costs twelve minutes and produces nothing.

Two owners is the same problem wearing a different hat. Both prepare half, each assuming the other covered the rest. The rules are short:

• One name per item. Not a team, not a department, not "we", not "product".
• The owner is the person who brings the item, not the person who will do the work afterwards. Those are often different people.
• If nobody will put their name on an item, cut it. That refusal is your answer about how important it really is.
• If two people both want it, one owns the row and the other is named in the outcome column as the person bringing the numbers.
• An item owned by someone who is not in the room is not an agenda item. It is an email.
• The chair owns the open and the recap. Never leave those two unnamed either.

Split decisions from updates

Sort every item into one of two piles before you send the agenda. Decisions need argument, time and everyone in the room. Updates need one person, two minutes, and no argument at all.

Sorting is quick if you use one test. Ask what changes if the item is cut from the agenda. If something stays unresolved and blocks someone, it is a decision. If people would simply find out later, it is an update. Anything that survives being cut does not need the room.

Mixing them is why meetings overrun. An update expands to fill whatever space it is given, and it usually takes the space the decision needed. Give updates a hard cap, or move them into writing and drop them from the meeting entirely.

Some items really are both, and the fix is to split the row rather than argue about the label. Put the numbers into the pre-read as an update, then leave one decision row that asks the question those numbers raise. A support backlog is an update; "do we hire a second support person in November?" is the decision hiding underneath it, and it deserves its own timebox and its own owner. If you cannot phrase the decision as a question with a small set of answers, it is not ready to be decided this week, so make it an update and book the decision for next time.

Timeboxes and the parking lot

Add your timeboxes up before you send the agenda. If they total exactly the length of the meeting, you have already overrun, because the meeting starts late and the recap needs three minutes. Aim for about 85% of the slot.

When a timebox runs out, you have three moves and only three. Decide with what you have, which is possible more often than people think. Park it, with a name and a date attached at the moment you park it. Extend it, and say out loud which item you are cutting to pay for it. What you must not do is quietly run over, because that spends time belonging to an item somebody prepared for.

A parking lot only works if somebody empties it. Give every parked item an owner and a date the second it goes in, then paste the parking lot at the top of next week's agenda so it is visible. Anything sitting there for three weeks gets deleted on purpose, not by accident.

The recap at the end is the item people cut first and should cut last. Two or three minutes where each person says their own action out loud is the cheapest way to find out that two people heard the same sentence differently. If you would rather that list build itself, there is a separate guide on getting meeting action items automatically.

Four variants of the same template

The six parts stay the same. What changes is which items are fixed and what you cut first.

Weekly team sync, 25 minutes. One decision, one or two updates capped at three minutes each, blockers, recap. Cut the round-the-table update where everyone says what they did. That belongs in writing. Keep a standing "what changed since last week" line at the top so the meeting always starts with a fact rather than a warm-up.

Project status, 30 minutes. Fixed items: milestones hit versus missed, decisions the project needs from this room, risks with an owner and a date, and the next milestone. Put the schedule slip first, not last, because that is the item people avoid. Cut demos. Record them or show them somewhere else.

Board meeting, 90 minutes. Formal and mostly fixed by your own rules: quorum, approval of the previous minutes, chief executive report, financials, resolutions to be voted on, then any other business. Every resolution gets its exact wording written in the agenda before the meeting, not drafted live. The minutes have to match the agenda item by item, so keep the numbering identical and use the board meeting minutes template for the write-up.

One-on-one, 30 minutes. The report owns the agenda, not the manager. Three buckets: what is blocking you, what you want feedback on, and career or growth. The manager adds at most one item. Cut the status update entirely, since that is what the project meeting is for. There is a fuller layout on the one-on-one meeting template page.

Pre-reads, and a checklist before you send

A pre-read turns a 45-minute meeting into a 25-minute one, but only when four things are true.

It is short and states its reading time. "One page, 6 minutes" gets read. "Deck attached" does not.

It arrives at least 24 hours ahead. A document sent at 11pm was not sent, it was filed.

The meeting does not repeat it. If you present the pre-read out loud, you have taught the room not to read the next one.

The link lives in the agenda itself, not in a separate email, and the sharing permissions actually work for everyone invited.

Then run this checklist before you press send.

1. 1Read your purpose line. Does it start with a verb, and would you know on Friday whether it happened?
2. 2Check every row has exactly one name in the owner column.
3. 3Add the timeboxes up. They should total about 85% of the meeting length.
4. 4Count the decision items. More than three in an hour is too many.
5. 5Delete one item. There is almost always one that could have been a message.
6. 6Paste the agenda into the body of the calendar invite, not as an attachment.
7. 7Send it at least 24 hours ahead, with the pre-read links live and shared with the right people.

After the meeting: notes that match the agenda

The agenda is half the loop. The other half is notes that come back in the same shape, so you can see at a glance which items got decided and which quietly did not. When notes are organised by agenda item, an item that produced nothing is impossible to hide, and that is usually the item that needed attention.

Doing it by hand means one person types while everyone else talks. They miss the decision they were writing about, and finish the notes from memory two hours later. If that person is also the chair, the meeting is worse for it.

If you would rather not, Noter AI records the meeting from a phone on the table, one tap, screen locked, and gives you a transcript with speaker labels and timestamps. Tap any line to hear that exact moment, which is how you settle "that is not what I agreed to" without anyone's memory being the deciding evidence. For an online call it sends a bot that joins Zoom, Google Meet, Microsoft Teams or Webex instead.

The part that matters for an agenda is the output style. Minutes of meeting produces the formal record, the same shape as the meeting minutes template. To-do list gives you only the actions with owners. Custom is the one to use here: you describe the structure you want, so you can hand it your agenda headings and get the summary back under those exact headings, in the same order, with decisions and parked items kept apart. The same recording can be run through each style, so one meeting gives you both the minutes and the task list.

If your meetings run in two languages this matters more than it sounds. Transcription covers 60+ languages and detects them automatically, tagging language word by word, so an item discussed half in Arabic and half in English is written down accurately either way. Tools that make you pick one language before recording spell the second one out phonetically, and an agenda item name is exactly the kind of phrase that gets mangled. Fuller comparison on the best app for multilingual meetings page.

It costs $9.99 a month, or $49.99 for the year, at one flat price rather than per seat. Agendas belong to recurring meetings, which is exactly where seat licences get expensive quietly: you buy for the five regulars, then the meeting picks up two standing guests, and the bill moves without anyone deciding it should. Here the price is the same whether one person records the weekly or everybody in the room does, because each person records from their own phone. Test it on the next meeting you were going to run from this template anyway. Free trial, App Store and Google Play.