Meeting Agenda Templates

A meeting agenda is a commitment, not a wish list. Every block on the agenda is a promise that you will spend that many minutes on that topic, in that order, with the named outcome. Treat it that way and the meeting ends on time, with decisions. Treat it as a suggestion and the meeting ends late, with the same conversation the team has had three times.

The templates below are hand-tuned for common meeting types, editable inline, and designed to paste into whatever tool you already use. The calendar copy format is the least-known option and usually the most useful: it drops HH:MM labels into the clipboard so you can paste them straight into a calendar invite description.

When do you actually need a meeting agenda?

Any meeting with more than three people, any decision meeting, any meeting that repeats weekly or more often, and any meeting that has ever run over time. Small ad-hoc working sessions between two or three people usually don't need one. Everything else does, and the meetings that run long are almost always the ones without a written agenda.

What makes a good meeting agenda?

Specific blocks with named outcomes, durations set ahead of the meeting, and a facilitator who holds the clock. 'Discussion' is not a block. 'Decide whether to proceed with option A or B' is a block. The more specific the block label, the more likely the meeting will produce a result rather than a feeling.

How long should your blocks be?

Shorter than you think. A five-minute block forces the group to stay on point; a fifteen-minute block lets the conversation drift into peripheral territory. Most of the templates below default to three to ten-minute blocks for exactly this reason. If a topic genuinely needs twenty minutes, it probably deserves its own meeting.

Should you share the agenda before the meeting?

Always. Twenty-four hours ahead is the right cadence for most meetings. It gives people time to think, to raise concerns before the meeting starts, and to come in warm rather than trying to catch up in the first five minutes. Meetings where the agenda is presented at the start train the team to arrive passive.

Which template for which meeting?

Weekly Team Meeting. A weekly meeting for a standing team of 4 to 10 people. If the team is smaller, go async. If it's larger, split the meeting in two.
Sprint Retrospective. At the end of every sprint. Two-week sprints get a 45-minute retro, one-week sprints get a 25-minute one. Quarterly retros are useful for larger trends but do not replace the sprint-level one.
Project Kickoff Meeting. Every time a new project starts. Even on small projects, a 30-minute kickoff pays for itself in the first week. Skip only when the team has run the exact same play many times before.
Brainstorming Session. When you need volume of ideas and the team hasn't converged yet. Skip brainstorming when the decision is between three known options; that's a decision meeting, not a brainstorm.
All-Hands Meeting. Monthly or quarterly, depending on company size and pace of change. Weekly all-hands is usually too frequent for the signal it carries. Teams below ~30 people usually don't need a separate all-hands from their weekly meeting.
Decision-Making Meeting. When a decision needs multiple people's input and cannot be resolved async. If the decision owner already knows the answer, skip the meeting and announce the decision with a written rationale.
One-on-One Meeting. Weekly, thirty minutes. Biweekly is long enough that small issues harden into big ones. If the thirty minutes regularly runs long, the issue is usually that status updates haven't moved async yet.
Interview Debrief. After every interview loop. The debrief should happen within 24 hours while memories are fresh. Delaying the debrief makes feedback vaguer and biases the conversation toward whoever remembers the candidate best.