Skip to content
Writing Style Library

Meeting Agenda

A short pre-meeting document listing what will be discussed, in what order, with time and intended outcomes.

Meeting Agenda

Section titled “Meeting Agenda”

A meeting agenda is a short document circulated before a meeting that lists what will be discussed, in what order, with how much time each item needs and what outcome it is meant to produce. Its job is to make the meeting purposeful and let participants prepare. A meeting without an agenda defaults to whoever talks loudest or remembers to raise a topic; a meeting with one has a reason to exist.

Writing the agenda is itself a forcing function. Naming the intended outcome for each item - discussion, decision, or update - reveals whether the item belongs on this call at all. For participants, receiving the agenda before the meeting lets them prepare questions, review materials, and show up ready rather than reactive.

Unlike meeting notes, which are written during or after a meeting to record what was decided and who owns what, an agenda is forward-looking. It plans the conversation that has not happened yet, where notes capture the conversation that already did. An agenda is not a wishlist of topics - it is a plan for a bounded piece of time with specific things that need to happen.

Canonical template

Section titled “Canonical template”
# [Meeting Title] - [Date]
Time: [start] - [end] | [Duration]
Location / Link: [room or video URL]
Attendees: [Name, Name, Name]


## Agenda


1. [Item name] ([time box, e.g., 5 min]) - [outcome: discuss / decide / update]
   [One sentence of context if needed]


2. [Item name] ([time box]) - [outcome: discuss / decide / update]
   [One sentence of context if needed]


3. [Item name] ([time box]) - [outcome: discuss / decide / update]


## Pre-reading
- [Link or document title]


## Questions or additions
Add items before [date or time] to [contact or shared doc].

When to use

Section titled “When to use”

Send a meeting agenda for any scheduled call where participants need to prepare or align on topics in advance. Recurring meetings benefit from agenda discipline - without it, scope creep accumulates session over session. Stakeholder or cross-functional calls where attendees arrive from different contexts need a shared map of what is happening and why. Any meeting that involves a decision or significant discussion should name those items explicitly so participants know what role they are playing when they arrive.

When not to use

Section titled “When not to use”

Skip an agenda for spontaneous conversations and hallway check-ins with no prior scheduling - the structure implies formality the interaction does not need. Emergency and incident response calls are driven by the situation, not a pre-set order; adding agenda ceremony slows the response. For casual 1:1 check-ins with a trusted peer, a rigid topic list can feel bureaucratic and inhibit the candid conversation both parties need.

Pairs well with

Section titled “Pairs well with”

operator, executive, matter-of-fact, instructional, executive-summary

Often confused with

Section titled “Often confused with”

meeting-notes: Meeting notes are a structured capture of what was decided and who was assigned what, organized by outcome (decisions, actions, open items) rather than chronology. They are written during or after a meeting to record what happened. A meeting agenda is written before the meeting to plan what will happen - the two documents cover the same event from opposite directions in time.

Tells

Section titled “Tells”
  • A header with date, time, location or link, and attendees
  • Each item carries a time box naming how many minutes it will take
  • Each item states an outcome type: discuss, decide, or update
  • Items are listed in the order they will occur in the meeting
  • Time boxes across all items total at or under the meeting duration
  • Circulated before the meeting, not during or after it
  • A one-sentence context note appears under items participants need to prepare for

Anti-patterns

Section titled “Anti-patterns”
  • Listing topics with no stated outcome type for each item - Without knowing whether an item is a discussion, a decision, or an update, participants cannot prepare and the facilitator has no shared basis for calling an item done.
  • Adding a Decisions or Actions section inside the agenda document to capture what happens during the meeting - That converts the agenda into meeting notes, which are organized by outcome from a conversation that already occurred - not a plan for what is still to come. The two documents should stay separate.
  • Issuing the agenda with so many items that the time boxes total more than the meeting window allows - An agenda that cannot fit in the available time is a topic dump, not a plan. Cut to what can be covered, or split across multiple meetings.
  • Distributing the agenda during the meeting or after it ends - An agenda serves two jobs - enabling preparation and establishing shared purpose - and both require advance circulation. A same-moment or post-meeting agenda cannot do either.

Failure modes

Section titled “Failure modes”
  • Over-scripted - each item arrives padded with sub-bullets, talking points, speaker assignments, and transition cues, turning a lightweight plan into a stage-managed script that leaves no room for actual conversation - Keep each item to a label, a time box, and an outcome type. If an item needs preparation material, link to a separate pre-read document rather than embedding it in the agenda.
  • Over-compresses - the agenda reduces every item to a label, time box, and outcome type so aggressively that participants know the order of discussion but not what they need to prepare or decide - Keep the agenda lightweight, but add one sentence of preparation context under any item where participants need background to participate usefully.

Instruction

Section titled “Instruction”
Write as a meeting agenda. List what will be discussed in the order it will occur, with a time box
and an intended outcome type (discuss, decide, or update) for each item. Include a brief header
with date, time, location or link, and attendees. Keep each item label short; if an item requires
preparation context, add one sentence under it - not a paragraph. Total the time boxes to confirm
they fit within the meeting window before finalizing. This document is meant to be circulated
before the meeting - an agenda issued during or after the meeting cannot serve its purpose.

Template

Section titled “Template”

See the Meeting Agenda template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Operator, Executive, Matter of Fact, Instructional, Executive Summary

Avoid with

Section titled “Avoid with”

Confessional, Reverent, Playful

Often confused with

Section titled “Often confused with”

Meeting Notes

Examples

Section titled “Examples”

Async Standup Proposal - Team Review and Decision - June 3, 2026

Section titled “Async Standup Proposal - Team Review and Decision - June 3, 2026”

Time: 8:00 - 8:45am Pacific | 45 min Location / Link: https://meet.example.com/eng-team Attendees: Engineering team (11), Engineering manager, Director of engineering

Agenda

Section titled “Agenda”

  1. Context and data (5 min) - update Q1 attendance and signal-to-noise data from the RFC - no need to re-read the full doc, just the two headline numbers.

  2. RFC walkthrough (10 min) - update Engineering manager presents the proposed format: async posts in #team-standup by 10am local time, on-call triage, and the Thursday working session replacing the daily sync slot.

  3. Questions and concerns (20 min) - discuss Open floor. Focus on what the RFC does not address.

  4. Trial decision (5 min) - decide Decide: run the 30-day trial as proposed, run with amendments, or decline.

  5. If approved: first logistics (5 min) - decide Set the trial start date and assign the first week of on-call triage.

Pre-reading

Section titled “Pre-reading”
  • RFC: docs/rfc-async-standups.md (10 min read)

Questions or additions

Section titled “Questions or additions”

Add items to #team-standup or reply to the calendar invite by Tuesday, June 2 at 5pm Pacific.