Team Practices

Meeting Agenda Templates: 6 Copyable Formats With Timeboxes

By Vact Published

A good meeting agenda is a short list of questions or decisions, each with an owner and a time limit, sent before the meeting and ending with a record of who does what by when. The templates below cover six common meeting types: weekly status, kickoff, the four Scrum events, one-on-one, decision meeting and formal board or committee meeting. Each has timeboxes that add up to a stated total or fit inside a stated maximum, so the agenda can be pasted into a calendar invite and adjusted.

Which meeting needs which agenda

The right agenda follows from the purpose of the meeting. The table is an original synthesis of common practice for project teams; the Scrum rows use the limits in the Scrum Guide, and the board row follows the sequence described later on this page.

MeetingPurposeWho attendsTypical lengthOutputs
Weekly team statusSurface blockers and confirm next week’s commitmentsTeam and project lead30 minutesBlocker list, action items
Project kickoffAlign on goals, scope, roles and ways of workingSponsor, team, key stakeholders60 to 90 minutesAgreed goal, roles, first milestones, open-questions list
Daily ScrumInspect progress toward the Sprint Goal and adapt the planDevelopers15 minutesActionable plan for the next day of work
Sprint PlanningDecide what the Sprint will deliver and howWhole Scrum TeamUp to 8 hours for a one-month SprintSprint Goal, Sprint Backlog
Sprint ReviewInspect the outcome of the SprintScrum Team and stakeholdersUp to 4 hours for a one-month SprintAgreed adaptations, backlog changes
Sprint RetrospectivePlan ways to improve quality and effectivenessScrum TeamUp to 3 hours for a one-month SprintImprovements for the next Sprint
One-on-oneRemove obstacles, give feedback, discuss growthManager and one report30 minutesAction items for both people
Decision meetingChoose between defined optionsDecision owner and the few people who hold input30 to 45 minutesA recorded decision, owner, date
Board or committeeConduct the organisation’s formal businessMembersSet by the bodyApproved minutes, recorded motions

What research says about agendas

Agendas are among the most commonly recommended meeting fixes, and the research on them is more nuanced than the advice.

A 2009 study in the Journal of Business and Psychology by Leach, Rogelberg, Warr and Burnfield, “Perceived Meeting Effectiveness: The Role of Design Characteristics”, tested meeting design characteristics against attendees’ perceptions of meeting effectiveness in two studies: meetings attended in a typical week (N = 958) and the last meeting attended on a particular day (N = 292). Agenda use and the quality of facilities stood out as important predictors of perceived effectiveness, attendee involvement was a key mediator, and larger meetings went with lower involvement. A 2011 follow-up by Cohen, Rogelberg, Allen and Luong in Group Dynamics, “Meeting design characteristics and attendee perceptions of staff/team meeting quality”, surveyed 367 working adults within 48 hours of their most recent staff or team meeting. Nine of the 18 design characteristics it tested significantly predicted perceived meeting quality, and it confirmed earlier findings that agenda use, punctuality, facility quality and facilitator status relate to meeting quality. Both studies measured attendee perceptions, not project results, so they show that people rate agenda-led meetings as better, not that deliverables improve.

Steven Rogelberg, who co-authored both, is more cautious in a February 2019 interview with Knowledge at Wharton. He notes that every book about meetings says to have an agenda, yet his research shows that “having an agenda in and of itself does nothing for meeting effectiveness”, and he criticises “agenda rehash”, where the same items reappear every week under a new date. The practical reading: the agenda helps when it is built fresh for the discussion that is needed, and does little as a recurring header.

The same interview offers three other agenda-related points. He calls defaulting to the meeting length set in Outlook or Google Calendar “a terrible mistake” and suggests sizing the meeting to the agenda and then cutting 5 to 10 minutes. He argues that meeting dysfunction grows with meeting size. He also reports that standing meetings produce the same quality of outcomes as sitting ones “in half as much time”.

Two studies reported in MIT Sloan Management Review bear on agenda wording and frequency. In “Five Ways Leaders Can Get People to Speak Up” (November 2024), Celia Moore and Kate Coombs describe a field experiment at a financial institution in which 43 live team meetings were recorded while the leader deliberately argued for a flawed idea. Broad prompts such as “Does anyone have any input?” had a 51% chance of drawing any dissent, while directly asking for it, for example “What could go wrong with this approach?”, raised the likelihood of a challenge to over 60%. In “The Surprising Impact of Meeting-Free Days” (January 2022), Benjamin Laker, Vijay Pereira, Pawan Budhwar and Ashish Malik surveyed 76 companies, each with more than 1,000 employees, that had introduced one to five meeting-free days a week. Drawing on pulse surveys and before-and-after stress data, they report that removing 60% of meetings, the equivalent of three days a week, increased cooperation by 55% and cut the risk of stress by 57%.

What a good agenda contains

Seven elements cover nearly every meeting. Each earns its place for a stated reason.

  1. Purpose in one sentence. It lets invitees decide whether they are needed. In the Wharton interview, Rogelberg says leaders who see themselves as stewards of other people’s time “think more carefully about who needs to be there”.
  2. Date, start time, end time and location or link. An end time is what makes timeboxes enforceable.
  3. Items written as questions or decisions. See the next section.
  4. An owner and a timebox for each item. The owner prepares and leads; the timebox protects later items.
  5. Pre-reads, linked. Anything over a page is circulated in advance so the meeting is spent discussing, not reading.
  6. Decision or information label. Marking each item as “decide”, “discuss” or “inform” shows which items could be handled outside the meeting.
  7. A closing slot for actions. Five minutes at the end to read back who owns what, by when.

Writing items as questions or decisions

A topic label (“Budget”) names a subject but not a result. A question or decision names the result, and so tells the room when the item is finished. In a May 2020 MIT Sloan Management Review article on remote meetings, Rogelberg suggests organising the agenda “as a set of questions to be answered rather than a set of topics to be discussed”: the questions show who really has to be invited, and once they have been answered, you know when to end the meeting.

Topic labelRewritten as a question or decision
BudgetDecide: do we move 2,000 from the contingency line to testing?
VendorDecide: which of the two quotes do we sign by Friday?
Website delaysDiscuss: what is blocking the content freeze, and who can unblock it?
RisksDiscuss: which two risks need a mitigation owner this week?
HiringInform: three open roles and their start dates (read in advance)

Weekly team status meeting template

Total: 30 minutes. Send the agenda 24 hours ahead and ask each person to update the shared tracker before the meeting, so the time goes to exceptions. The status report guide covers the written update that feeds this meeting.

TimeItemOwner
0:00 to 0:03Goal for the week and any change since last meetingProject lead
0:03 to 0:08Milestone check: which dates are green, amber or red?Project lead
0:08 to 0:20Blockers: what is stopping work, and who can remove it? (one minute per person, then discussion of the top two)Each team member
0:20 to 0:25Risks and changes: what new risk or scope request arrived?Risk owner
0:25 to 0:30Read back actions and ownersNote-taker

Project kickoff meeting template

Total: 90 minutes. The kickoff is the one meeting where the whole project is on the table, so circulate the charter or brief in advance. The project kickoff checklist lists what should be prepared before it.

TimeItemOwner
0:00 to 0:05Welcome and meeting purposeSponsor
0:05 to 0:15Why this project exists: the problem, the goal and how success will be measuredSponsor
0:15 to 0:30Scope: what is in, what is out, and what is still undecidedProject manager
0:30 to 0:45Roles: who decides, who does, who must be consulted?Project manager
0:45 to 1:00Plan: first milestones, known dependencies and the first two weeksProject manager
1:00 to 1:10Ways of working: meeting rhythm, tools, how to escalate (see the team communication guide)Project manager
1:10 to 1:20Risks and open questions: what could stop us, and what do we still need answered?All
1:20 to 1:30Next steps, owners and datesNote-taker

Scrum event templates (2020 Scrum Guide)

The Scrum Guide, written by Ken Schwaber and Jeff Sutherland (copyright 2020), gives maximum lengths for Sprint Planning, the Sprint Review and the Sprint Retrospective in a one-month Sprint and says that “for shorter Sprints, the event is usually shorter”; the Daily Scrum is 15 minutes. The Sprint itself is a fixed-length event of one month or less. These are ceilings, not targets. The item breakdowns inside each timebox below are original suggestions; the Guide prescribes the timebox, the purpose and, for Sprint Planning, the topics, not a minute-by-minute run.

Sprint Planning (maximum 8 hours for a one-month Sprint)

The Guide gives three topics: “Why is this Sprint valuable?”, “What can be Done this Sprint?” and “How will the chosen work get done?” It adds that the Sprint Goal must be finalised before the end of Sprint Planning. The split of time below is this page’s suggestion for a one-month Sprint; scale it down for shorter Sprints.

Suggested time (share of 8 hours)Item
2 hours (25%)Why is this Sprint valuable? The Product Owner proposes how the product could gain value this Sprint; the whole Scrum Team defines the Sprint Goal
3 hours (37.5%)What can be Done this Sprint? The Developers select backlog items against capacity
3 hours (37.5%)How will the chosen work get done? Break items into work of a day or less

Daily Scrum (15 minutes)

The Guide describes the Daily Scrum as a 15-minute event for the Developers; if the Product Owner or Scrum Master are actively working on Sprint Backlog items they take part as Developers. Its stated purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, and the Developers may use any structure as long as the event focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. A workable agenda is a single question: are we on track for the Sprint Goal, and what changes to the plan does that need? Take anything that needs a longer talk to a separate conversation; the Guide notes that Developers often meet throughout the day for more detailed discussions.

Sprint Review (maximum 4 hours for a one-month Sprint)

The Guide says the purpose is “to inspect the outcome of the Sprint and determine future adaptations”, and calls the event a working session that the Scrum Team should avoid limiting to a presentation.

ItemSuggested time in a 4-hour slot
What was the Sprint Goal and was it met?15 minutes
Demonstration of the Done work60 minutes
What has changed in the market, the users or the budget?30 minutes
What should the backlog look like next, and what does the timeline look like?45 minutes
Stakeholder feedback and decisionsremaining time

Sprint Retrospective (maximum 3 hours for a one-month Sprint)

The Guide says the purpose is “to plan ways to increase quality and effectiveness”. Suggested order: what went well and what did not (about 45 minutes); choose the one to three problems worth fixing (about 30 minutes); agree concrete changes with owners (about 45 minutes). That is about two hours, inside the three-hour maximum. The Guide adds that the most impactful improvements are addressed as soon as possible and may even be added to the Sprint Backlog for the next Sprint.

One-on-one meeting template

Total: 30 minutes, weekly or every two weeks. The direct report owns the agenda and the manager adds items; both keep a shared running document so that action items carry over.

TimeItem
0:00 to 0:05How are things? Workload, energy and anything personal either side wants to share
0:05 to 0:15The report’s topics: what do they want help with, a decision on, or feedback about?
0:15 to 0:22Manager’s topics: priorities that changed, feedback on recent work
0:22 to 0:27Growth: one skill or opportunity worth working on this quarter
0:27 to 0:30Read back action items for both people

Decision meeting template

Total: 45 minutes. A decision meeting is for choosing, not for informing. Circulate a one-page brief with the options, criteria, cost and risks so that nobody learns the options in the room. Ask for challenge explicitly: in the Moore and Coombs study above, broad invitations drew dissent less often than direct requests for it.

TimeItem
0:00 to 0:03State the decision, the deadline and who decides
0:03 to 0:10Options and criteria: what are the choices, and what will we judge them on?
0:10 to 0:25Discussion: what could go wrong with each option? Each person names one risk before open debate
0:25 to 0:35Decide: the owner states the choice and the main reason
0:35 to 0:40Name dissent: what are the objections and are they acceptable?
0:40 to 0:45Actions and communication: who tells whom, by when?

Where the meeting is also about choosing between competing risks, the risk register guide gives a format for recording them.

Board or committee meeting: standard order of business

Formal bodies use a fixed order so that members know when each type of business will arise. The official Robert’s Rules of Order website states in its FAQ that a proposed agenda becomes official only when the assembly adopts it at the outset of the meeting, and that members may move to amend it first; it also rejects the idea that the president alone sets the agenda. The same FAQ cites Robert’s Rules of Order Newly Revised (RONR), 12th edition, as its authority, and cautions that RONR’s rules are defaults: they govern only where applicable law, the body’s bylaws and any special rules of order it has adopted say nothing different. Check those documents first.

Montana State University Extension’s Guide for Simplified Parliamentary Procedure (April 2024), which names the 12th edition as the current authoritative text, lists the basic order of business as: call to order; reading and approval of the minutes; reports of officers, boards and standing committees; reports of special committees; special orders (matters that demand special priority); unfinished business; new business; and, for public boards, public comment. An order-of-business handout by parliamentarian Jim Slaughter, based on the 12th edition, gives the same sequence from call to order to new business, without the special-orders heading, and adds that the chair should not call the meeting to order until a quorum is present.

OrderItemSuggested time (90-minute meeting)
1Call to order, once a quorum is present2 minutes
2Adoption of the agenda, where the body uses one3 minutes
3Reading and approval of minutes5 minutes
4Reports of officers, boards and standing committees20 minutes
5Reports of special committees10 minutes
6Special orders (matters that demand special priority)10 minutes
7Unfinished business15 minutes
8New business20 minutes
9Announcements3 minutes
10Adjournment2 minutes

The suggested times are an original allocation. Rows 2 and 9 sit outside the standard headings: the FAQ places adoption of an agenda at the outset of the meeting, and the Montana State guide’s suggested procedure puts announcements after new business.

Minutes and action items

Minutes record decisions and commitments. The official Robert’s Rules FAQ states that “minutes are a record of what was done at a meeting, not a record of what was said”, and calls summarising the discussion in them improper. For project meetings the same principle is a good default: record the decision, the reason in a sentence, and the actions.

A minute for each agenda item needs five fields:

FieldExample
ItemVendor quote
OutcomeChose quote B
WhyLower integration risk
ActionSign contract
Owner and datePriya, Friday 20 November

Send the minutes within 24 hours, keep the action list in the same place as the project plan, and open the next meeting by reading the previous actions. Where an item recurs without progress for three meetings, move it to a separate working session so that the weekly agenda does not become the “agenda rehash” Rogelberg warns about.

Sources