tl;dr on Meeting Agenda Templates

A meeting agenda contains five things: the outcome the meeting is for, the items being covered, who is attending and what each of them owns, how long each item gets, and what people need to read beforehand.

To create one for yourself, name the outcome you want from each item rather than the topic, trim the list until it fits the time booked, give every item one named person, put the hardest item second while the room is fresh, send it out a day ahead with the pre-reading marked, and ringfence the last five minutes to read back the actions.

Thirty minutes holds about three real items.

Ten templates follow, covering team meetings, staff meetings, board meetings, one-on-ones, standups, retrospectives, all-hands, sales meetings, sprint planning, and project kickoffs, all copy-and-paste.

Here you will find ten meeting agenda templates that cover team meetings, staff meetings, board meetings, one-on-ones, standups, retrospectives, all-hands, sales meetings, sprint planning, and project kickoffs, ready to copy and paste into Google Docs, Notion, or wherever you need them to be.

They all adhere to the same set of rules, designed to make sure that each meeting has a clear, actionable goal and the steps to get there. If you want to find out the reasoning behind these rules, we have broken it down into six steps for writing an agenda from scratch.

What Goes In a Meeting Agenda

A solid meeting agenda should contain five things as standard. 

  1. Outcome
  2. Items
  3. Attendees and Ownership
  4. Timeframe
  5. Preparation

Anything on top of this tends to be overkill, and if a meeting agenda lacks one of these, then this is where meetings tend to overrun, or end with no decisions being made. 

1. Outcome

In a meeting agenda, this should be a single line at the top stating what the meeting is for. Rather than angling it as “Marketing Budget”, it should be results-based: “Agree marketing budget plans for Q3”. This is the meeting’s north star, and everything that comes under this should be related, or relevant, to the outcome. 

2. Items

This is the “agenda” part: what specific breakdowns, by item, are needed to achieve this goal? Order is particularly important here; for example, there is no point deciding on Google Ad spend budget if you haven’t already laid out what your KPIs are for that particular channel. It also needs to be specific enough that someone who is coming in can understand exactly what’s happening, without requiring too much context.  

3. Attendees and Ownership

This is who needs to be there and which item each person will be talking about and taking ownership of during the session. This makes sure that the right person knows when they need to speak and run with their item, and also who else in the room is there, so if there needs to be work between individuals or departments, the right people are in attendance. By sending this out early, it makes it clear if there are other people that need to attend, or need to be briefed after the fact.  

4. Timeframe

This is a calculation of minutes dedicated to each item, and they need to correlate with the meeting length. So when you start building your agenda, you find there are 45 minutes’ worth of items and discussion on a 30-minute call; either something needs to be cut, or the meeting needs to be extended. This also helps to make sure that certain topics get the right amount of emphasis, and makes sure that tasks don’t get pushed off when things run long.

5. Preparation

There is nothing worse than turning up at a meeting and being asked for a particular figure, or deck, that isn’t to hand. Sending over the agenda, linked to any materials to be read beforehand or details to be brought to the table, saves time and embarrassment and allows for a smooth-running meeting. 

How to Write a Meeting Agenda in Six Steps

Writing a meeting agenda comes down to six things: naming the outcome you want from each item, trimming the list until it fits the time booked, giving every item a named person, putting the hardest item second, sending it out a day ahead with the pre-reading marked, and ringfencing the last five minutes for actions. The steps below take about ten minutes for a recurring meeting, and less once you have a template to work from.

1. Start with the action, not the thing

Look at any meeting agenda, and you’ll find it filled with vague words. Budget, Pipeline, Forecast. This tells you what needs to be discussed, but doesn’t give the layout of what you want to achieve after the conversation. As a result, vague instructions can lead to long, meandering conversations that come to no solid outcomes. Instead of writing “Budget”, list out “Find out what is blocking budget sign off” or “Get unanimous agreement on X on Q3 budget”. Write it as a neutral but desired outcome and not as a vague noun. 

2. Keep trimming the list until it fits the time that is booked

It can be hard to get lots of people together at once in a business, and the temptation might be there to cover as much ground as possible in a 30-minute meeting. Thirty minutes can contain maybe three real items. Any meeting agenda with more than that in a half-hour meeting runs the risk of two things: overrunning considerably or brushing over things that need time to finish. Wherever possible, try to make sure that the meeting agenda fits the time, and if it doesn’t, either move it to another session or try to do it async. Even if this feels counterintuitive, test it for one meeting, see what you achieve, and then you’ll likely find it is way tighter and more focused as a result. 

3. Give each item a specific named person

A single person, attending the meeting, named on the agenda. That is the ideal way to allocate an item on an agenda. Instead of just putting ‘Marketing’, by choosing a specific person it prevents those awkward moments where someone is waiting for someone else to start; equally, it means that the person knows what they need to prepare and that they need to step up.

4. Make the hardest item second

Most people will want to get the trickiest item out of the way; the beginning of a meeting never runs smoothly. There are latecomers, small talk, and the final item of the meeting often gets rushed, with people checking the clock for where they need to be. By putting it second, the people in the room will be active, involved, and not too distracted by what comes next. It also allows ample time if there is to be any kind of friction or disagreement to be smoothed out. 

5. Mark the pre-reading and send it a day ahead

If you send the agenda just before the meeting, or even during the meeting itself, that doesn’t allow ample time for preparation. By sending it out in advance, ideally the day before, you allow for people to come prepared with what they need. If there is required reading beforehand, link that as a separate document in the agenda itself with a note to read, rather than putting it directly into the agenda itself. 

6. Ringfence the last five minutes for allocation and confirmation

Use a five-minute block at the end of the meeting, clearly stated as its own item, so that actions can be summarized. Have the meeting organizer read back over what’s been covered, who owns it, and any dates that they need to keep in mind for the action. This means that everybody has a clear outcome of what has happened, with concrete next steps and ownership so that nothing drifts after the meeting has concluded.

Added bonus: while a notetaker like tl;dv can absolutely take the raw transcript and turn it into actionable points, this can also allow the notetaker to summarize even more clearly for the notes afterward. 

10 Meeting Agenda Templates

Below are ten meeting agenda templates covering the formats most teams run weekly. Each one follows the same rules: an outcome line at the top, one named owner per item, timings that add up to the length booked, and the last block reserved for actions. Copy the one you need, swap the bracketed names for real ones, and cut anything your team does not use. A template you have trimmed beats one you have followed.

Team Meeting Agenda Template

The weekly squad sync. This is the template most likely to bloat, because everything that has no other home gets pushed into it. Thirty minutes, three items, and a hard stop on the actions block. If your team meeting regularly runs to an hour, the fix is usually not a longer meeting but a shorter list.

Outcome: Agree what the team is prioritizing this week and clear anything blocking it.
Length: 30 minutes
Pre-reading: Last week’s actions list. Required.

  1. Wins and blockers (5 min). Owner: [Name]. One line each from every attendee. Wins get named, blockers get flagged for item two, not solved here.
  2. Blocker of the week (10 min). Owner: [Name]. The one thing genuinely stopping work. Pick it before the meeting, not during.
  3. This week’s priority (10 min). Owner: [Name]. What the team is actually working on and what gets dropped to make room.
  4. Actions and owners (5 min). Owner: [Meeting lead]. Read back every action, who owns it, and the date.

Staff Meeting Agenda Template

Wider than a team meeting and less about doing the work. A staff meeting is a department or company briefing where most people are listening rather than contributing, so the discussion window needs protecting or it disappears entirely. Forty-five minutes, with a third of it reserved for questions and one real decision in the middle.

Outcome: Bring the department up to date and settle the one decision that needs the room.
Length: 45 minutes
Pre-reading: Department numbers, circulated the day before. Required.

  1. Company and department update (5 min). Owner: [Name]. Headlines only. The numbers were in the pre-read.
  2. Decision item (15 min). Owner: [Name]. The one thing that needs agreeing in the room. Name the decision in the agenda, not just the topic.
  3. Team updates (10 min). Owner: [Each team lead]. Two minutes each, capped. Anything longer becomes its own session.
  4. Questions (10 min). Owner: [Meeting lead]. Real time, not the leftover minutes.
  5. Actions and owners (5 min). Owner: [Meeting lead].

Board Meeting Agenda Template

Formal, minuted, and the one agenda where the order is partly set by governance rather than preference. Approvals come first because they are procedural and quick. The substantive decision goes second, while the room is fresh, which is a departure from how most board packs are built. Ninety minutes, and the actions block gets ten rather than five because board actions carry dates and accountability.

Outcome: Approve the standing items and reach a decision on [specific item].
Length: 90 minutes
Pre-reading: Board pack including financials and previous minutes, sent one week ahead. Required.

  1. Apologies and approval of previous minutes (5 min). Owner: [Chair]. Procedural. Corrections noted, not debated.
  2. Principal decision (25 min). Owner: [Name]. The item the meeting exists for. Stated as a decision in the agenda so the board arrives ready to make it.
  3. CEO report (15 min). Owner: [CEO]. Against the written report, not a re-reading of it.
  4. Financial review (20 min). Owner: [CFO or finance lead]. Variance against plan, cash position, and anything requiring board attention.
  5. Risk and any other business (15 min). Owner: [Chair]. Items raised before the meeting, not from the floor.
  6. Actions, owners, and dates (10 min). Owner: [Chair]. Read back for the minutes.

One-on-One Meeting Agenda Template

The one meeting where the agenda should mostly belong to the other person. If a manager fills all thirty minutes with their own items, it becomes a status update with a friendlier name. Their topics go first, the difficult conversation goes second while there is still time to handle it properly, and development gets its own slot so it does not get squeezed out every single week.

Outcome: Cover what [Name] needs, address [specific issue], and agree one development action.
Length: 30 minutes
Pre-reading: Their notes, added to the shared doc beforehand. Optional but encouraged.

  1. Their agenda (10 min). Owner: [Direct report]. Whatever they brought. This slot does not get borrowed.
  2. The thing that needs saying (10 min). Owner: [Manager]. Feedback, a concern, or a decision affecting them. Second, so it is not rushed and not left to the door.
  3. Development (5 min). Owner: [Both]. One concrete step, not a career conversation in miniature.
  4. Actions and owners (5 min). Owner: [Manager].

Daily Standup Agenda Template

Fifteen minutes, and it only works if the blockers get separated from the updates. Standups run long when a blocker gets raised and the group starts solving it in real time with eight people watching. Flag it, name who is picking it up, move on. The solving happens after, with the two people who need to be there.

Outcome: Surface today’s work and name anyone who is stuck.
Length: 15 minutes
Pre-reading: None. If a standup needs pre-reading it is not a standup.

  1. Round the room (7 min). Owner: [Each attendee]. Finished yesterday, doing today. Under a minute each.
  2. Blockers (5 min). Owner: [Standup lead]. Named and assigned, not solved. Anything needing discussion gets a follow-up slot.
  3. Follow-ups and owners (3 min). Owner: [Standup lead]. Who is meeting who, straight after.

Retrospective Meeting Agenda Template

The hard item goes second here for a specific reason. Teams that open with what went well spend twenty minutes being pleasant and then rush the part that changes anything. Put the difficult conversation while the energy is there, then close on what worked. And the improvements slot needs real time, because a retro that ends without two named, dated actions is a therapy session.

Outcome: Agree two changes the team will make next sprint, with owners.
Length: 60 minutes
Pre-reading: Sprint data and last retro’s actions. Required.

  1. The data (10 min). Owner: [Scrum lead]. What shipped, what slipped, what carried over. Facts before opinions.
  2. What went wrong (20 min). Owner: [Facilitator]. Process and decisions, not people. Longest block on the agenda for a reason.
  3. What went well (10 min). Owner: [Facilitator]. Specifically what to keep doing.
  4. Pick two improvements (15 min). Owner: [Team]. Two, not ten. Ten changes nothing.
  5. Actions and owners (5 min). Owner: [Scrum lead]. These go on the next retro’s pre-read.

All-Hands Meeting Agenda Template

Mostly broadcast, which is why Q&A gets thirteen minutes rather than the two it usually gets when the CEO overruns. The announcement goes second because that is what people came for, and burying it at the end means half the audience has stopped listening. Everything numeric should be on a slide people can screenshot, because nobody retains a spoken figure.

Outcome: Share [announcement] and give the company room to ask about it.
Length: 45 minutes
Pre-reading: None. Send the deck afterward instead.

  1. Where we are (8 min). Owner: [CEO or lead]. Numbers against the goal, on screen.
  2. The announcement (12 min). Owner: [Name]. The reason this meeting is happening. What changes and what it means for people’s work.
  3. Team spotlight (7 min). Owner: [Rotating team lead]. One team, one thing they shipped.
  4. Questions (13 min). Owner: [Facilitator]. Collected in advance and live, in that order, so the silence at the start does not kill it.
  5. Close and next steps (5 min). Owner: [CEO or lead].

Sales Meeting Agenda Template

Deals at risk go second, not last. Pipeline review has a habit of eating the whole hour, and the deals that need help get four rushed minutes at the end when everyone is already late for their next call. Put them where they get properly worked, and cap the pipeline walk so it does not expand to fill whatever it is given.

Outcome: Agree the plan for every deal at risk this month and confirm the forecast.
Length: 60 minutes
Pre-reading: CRM pipeline export and current number against target. Required.

  1. Number against target (10 min). Owner: [Sales lead]. Where the team is, no commentary needed on figures already circulated.
  2. Deals at risk (20 min). Owner: [Rep owning each deal]. Named deals, what is blocking them, what the rep needs. This is the working part of the meeting.
  3. Pipeline for next period (15 min). Owner: [Sales lead]. Coverage, gaps, and where new pipeline is coming from.
  4. One coaching item (10 min). Owner: [Sales lead or manager]. A single call moment or objection, worked as a group.
  5. Actions and owners (5 min). Owner: [Sales lead].

Sprint Planning Meeting Agenda Template

Ninety minutes, and the sprint goal comes before the backlog rather than after it. Teams that review the backlog first end up reverse-engineering a goal from whatever tickets they happened to pull, which is how sprints end up with no coherent theme. Agree what the sprint is for, then choose work that serves it.

Outcome: Commit to a sprint goal and the work that delivers it.
Length: 90 minutes
Pre-reading: Groomed backlog and last sprint’s carryover. Required.

  1. Last sprint outcome (10 min). Owner: [Scrum lead]. Shipped, carried over, and why. Short, since the retro covers the detail.
  2. Agree the sprint goal (20 min). Owner: [Product owner]. One sentence the whole team can repeat. Everything after this is filtered through it.
  3. Backlog review (25 min). Owner: [Product owner]. Priority order against the goal.
  4. Capacity and commitment (25 min). Owner: [Team]. Real capacity including leave and support load, then what the team actually commits to.
  5. Actions and owners (10 min). Owner: [Scrum lead].

For the wider ceremony set, including grooming and review formats, the agile scrum meeting templates go further than this one does.

Project Kickoff Meeting Agenda Template

Scope goes second, and specifically what is out of scope. Kickoffs that skip this produce a project where three people hold three different mental models of what is being built, and the difference surfaces at week six. Naming the exclusions out loud, in a room, with everyone present, is the single most useful thing a kickoff does.

Outcome: Agree what this project is, what it is not, and who owns which part.
Length: 60 minutes
Pre-reading: Project brief and proposed timeline. Required.

  1. Why this project exists (10 min). Owner: [Project sponsor]. The problem and what success looks like.
  2. Scope, and what is out of scope (15 min). Owner: [Project lead]. Both halves. The second half is the one that saves the project.
  3. Who owns what (10 min). Owner: [Project lead]. Named people against workstreams.
  4. Timeline and milestones (15 min). Owner: [Project lead]. Dates, dependencies, and the first checkpoint.
  5. Risks (5 min). Owner: [Team]. Named now, logged, reviewed at the checkpoint.
  6. Actions and owners (5 min). Owner: [Project lead].

A longer walkthrough of the kickoff format, including the pre-kickoff checklist, sits in the project kickoff meeting guide.

One-to-one meeting agenda template filled in
One-to-one meeting agenda template filled in

Meeting Agenda Examples: Blank vs Filled In

The above meeting agenda templates are blank structures that can be tweaked and reused time and again. A meeting agenda example is that structure, but filled in, showing exactly what it would look like in real life. 

The structured templates above can still be used inefficiently, and while not inherently wrong, this will likely lead to vagueness or things running over. For example, here is what a lot of teams might end up with.

  1. Wins and blockers (5 min)
  2. Q3 campaign (10 min)
  3. Website (10 min)
  4. AOB (5 min)

On first glance, it fits the timeline, seems pretty specific and has a better indication of what is expected, but it also lacks detail. The items are on there, but they are simple nouns; there’s no ownership, nothing that explains what they want the outcome to be. ‘Website’ might end up being 10 minutes of people just complaining that the website is loading slowly; ‘Q3 campaign’ starts with someone just saying, “So, where are we at with this?”

A better version of this same meeting agenda should look something more like this:

Outcome: Agree what marketing ships this week and unblock the Q3 landing page.

Length: 30 minutes
Pre-reading: Last week’s actions list. Required.

  1. Wins and blockers (5 min). Owner: Priya. One line each. Blockers get flagged for item two, not solved here.
  2. Q3 landing page is blocked on legal sign-off (10 min). Owner: Tom. Decide whether we ship without the case study or push the date. Tom brings legal’s last response.
  3. Confirm this week’s priority: campaign or website (10 min). Owner: Priya. We cannot do both by Friday. Pick one and name what slips.
  4. Actions and owners (5 min). Owner: Priya.

It’s the same template, the same items, and the same timeframe; the main difference is that there is an owner and a specific goal for each section. People will know what they need to read, what they need to prepare, and what the overall goal of the meeting is. It clearly lays out the blockers and constraints, so that people can be prepared to deal with these, answer any questions, and find a resolution. 

When you are filling in an agenda for a meeting, the key thing to check is whether someone who read it would know what they need to do and what to expect. If not, then the meeting will likely spend a good chunk of time trying to nail that down.

From Agenda to Recap Without Retyping It

Having a solid meeting agenda template can structure and drive a meeting to success; it doesn’t record it. When Priya mentioned whether or not to ship without a case study, a week later, not everybody will have the same recollection of events, and a meeting recap written from memory won’t necessarily convey what was actually decided. 

This used to be covered by someone scratching up meeting minutes with a biro and trying to retain everything that was being said; thankfully, we now live in a world where tl;dv can get the recording, the transcript, the summary and action list, directly to your inbox or library straight after the meeting has finished.

You even have the ability to set meeting templates, with the above, letting you define the way the notes are generated. Customized to exactly what you need, where it needs to go, and who needs to use it. 

Meeting Templates in tl;dv
Meeting Templates in tl;dv

You can then take that and connect it to the rest of your tech stack. For example, Pipeline catch-up? Notes straight into your CRM, highlights clipped and sent to the people who were on demos, and the notes are there ready for anybody who needs to go through them in more detail. 

That being said, it relies on one thing: a well-structured meeting built on a solid agenda. 

Use Your Meeting Library to Write the Next Agenda

The application for your meeting transcripts and notes is even stronger once you have built up a library of your meetings as well. tl;dv has an MCP server, which means that you can directly connect your library to Claude and query all of your data rather than just a single call. 

How can you use it? Simply ask it to review your last ten weekly team meetings and prompt it to find out where it consistently overran. What agenda items get raised time and again with no outcome? What meetings produce the fewest actions? You are then able to identify what your biggest blockers are, not just to the items on your agenda, but across all your recurring meetings.

From that, you can even get it to draft the next agenda, based on what it found, plus the steps above. With a read-only MCP, it can read your meetings, change nothing, and then get the AI to write an agenda taking into consideration what tends to go awry and building in guardrails to prevent it. 

To get started, use the templates above, run your next meeting using one of them with tl;dv running alongside. Compare the recap it generates to your regular notes and then see how much easier it is to go in with a plan and a tool that makes it easier. 

FAQs About Meeting Agendas

Whoever called the meeting owns the agenda, even when somebody else types it up. The people running individual items supply their own item, what it needs, and how long it will take. Board agendas are usually drafted by the company secretary and signed off by the chair. For recurring team meetings, rotating who drafts it tends to raise how much people contribute.

A day ahead covers most recurring team meetings. Anything with real pre-reading needs three to five working days, and board meetings are commonly sent a week out, though the actual requirement sits in your own governing documents rather than in law. The test is whether people have time to read it, gather what they need, and ask for something to be added.

About three real items in thirty minutes, and five or six in an hour. Real means anything needing discussion or a decision. Status updates that nobody responds to are not items; they are a document sent to the wrong place. Agendas with eight items on a one-hour call reliably lose the last two.

Usually, because the items are topics rather than decisions, there is no finish line for discussion. The other common causes are timing that never added up to the booked length in the first place, no named owner for each item, which slows each one down, and the decision-maker not being in the room. Labeling each item as decide, discuss, or inform fixes most of it.

An agenda is written before the meeting and says what will be covered. Minutes are written during or after the meeting and record what was said, decided, and assigned. One is a plan; the other is evidence. Board and committee meetings usually need both, since the minutes are the formal record. There is more on the difference between meeting notes and minutes if you need the longer version.