Meeting Agenda Generator

{{ agendaRows.length }} agenda items {{ timingBadgeLabel }} {{ attendeeBadgeLabel }} {{ ownerBadgeLabel }}

Meeting title:

Name the meeting exactly as invitees should see it.

Meeting date:

Use the local meeting date.

Start time:

Use the meeting's planned local start time.

Time zone:

Choose the operating time zone for the meeting invite.

Meeting length:

Use 15-480 minutes; overbooked agendas are flagged instead of silently stretched.

min

Meeting format:

Pick the closest purpose so prompts match the agenda's job.

Time display:

Choose the handoff style your attendees expect.

Desired outcome:

One sentence stating what attendees should decide, produce, or align on.

Facilitator:

Name the person accountable for keeping scope, time, and decisions clear.

Decision rule:

Keep the rule short enough to read in the meeting invite.

Attendees:

List required attendees first; optional attendees can receive the agenda afterward.

Default item length:

Rows with explicit minutes keep their own timebox.

min

Agenda rows:

One row per topic: topic, minutes, owner, desired outcome, prep note.

Paste CSV, TSV, or pipe-delimited topic rows.

Check agenda inputs

{{ error }}

{{ agendaText }}

Time	Agenda item	Minutes	Owner	Desired outcome	Prep	Copy
{{ row.time_label }}	{{ row.label }}	{{ row.minutes }}	{{ row.owner }}	{{ row.outcome }}	{{ row.prep }}
No agenda rows are available.

Check	Status	Evidence	Next action	Copy
{{ row.check }}	{{ row.status }}	{{ row.evidence }}	{{ row.action }}

No agenda rows are available to chart.

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

A meeting agenda is a time plan for group attention. A useful agenda names the outcome, gives each topic a timebox, assigns ownership, and tells attendees what they need to prepare before the meeting starts. Without those details, a 60-minute discussion can spend half its time deciding what the meeting is for.

Outcome-led agendas matter most when a group needs a decision, handoff, planning commitment, status escalation, or working-session artifact. A launch review, for example, should not only list "risks" and "customer messaging." It should say who will recommend the launch scope, how long each topic gets, what evidence attendees should bring, and what decision or next step should be captured before people leave.

Timeboxes make the tradeoff visible. Four 15-minute topics may look harmless until opening context, closeout, decision capture, and drift are included. If the plan asks for more minutes than the calendar slot allows, the agenda is already telling the facilitator where the meeting will break down.

A written agenda does not create decision authority by itself. It can make the expected outcome, owner, preparation, and closeout clearer, but the group still needs the right people in the room and a decision rule everyone understands before the discussion starts.

Technical Details:

Agenda planning combines a calendar slot, a start time, topic durations, owner assignments, and closeout rules. The basic mechanic is simple: the meeting slot is fixed, so every topic minute must fit between the opening check and the closing capture. When topic time expands, the agenda has fewer minutes left for parking-lot questions, late objections, and decision cleanup.

Meeting format changes the facilitation prompts more than the timing math. A decision meeting needs approval language and objection handling. A working session needs artifact progress. A status sync should push pure updates out of live discussion and spend time on blockers. Planning sessions and retrospectives need different closeout wording, but each still depends on a visible outcome, named owners, and enough minutes to finish the agenda.

Outcome Topic rows Timebox fit Readiness checks Closeout

The agenda stays useful when the outcome, row ownership, timing fit, and closing decision capture agree with each other.

Rule Core:

The time plan is built from fixed opening and closing rows plus the topic rows supplied by the reader. Topic rows can be typed as comma-separated, tab-separated, or pipe-separated values. The expected row order is topic, minutes, owner, desired outcome, and prep note.

\begin{array}{lcl} p & = & o + \sum t + b + c \\ r & = & s - o - \sum t - c \end{array}

Meeting agenda timing symbols and source fields.
Symbol	Meaning	Unit	Where it comes from
`s`	Target meeting length	Minutes	`Meeting length`, accepted from 15 to 480 minutes.
`o`	Opening and outcome check	Minutes	3 minutes for meetings up to 20 minutes, 8 minutes for meetings at least 90 minutes, otherwise 5 minutes.
`t`	Topic-row duration	Minutes	Parsed from each agenda row, with the default item length used when a row omits a valid duration.
`c`	Closeout, decisions, and action owners	Minutes	Same base rule as the opening row, with small spare reserves folded into closeout.
`b`	Parking lot and decision buffer	Minutes	Created only when at least 5 spare minutes remain after opening, topics, and closeout.
`p`	Planned agenda minutes	Minutes	Shown in the summary and reflected in the timebox rows.

Reserve handling is exact enough to catch common planning errors. If spare time is 5 minutes or more, the plan adds a parking-lot and decision-buffer row. If spare time is between 1 and 4 minutes, those minutes are added to closeout instead of creating a tiny row. If topic minutes push the plan past the target slot, the overrun appears as minutes overbooked.

Meeting agenda parsing and readiness rules.
Area	Rule or boundary	Resulting cue
Agenda row format	CSV, tab-delimited, or pipe-delimited rows are accepted. A header row such as topic plus minutes is skipped.	Rows become agenda items with topic, minutes, owner, desired outcome, and prep.
Duration parsing	Numeric minutes, minute text, hour text, and clock-like hour:minute values are accepted.	Invalid or blank durations use `Default item length`.
Topic duration bounds	Each agenda row is clamped from 1 to 240 minutes after parsing.	Extreme row values cannot silently create negative or zero-length agenda items.
Owner check	Missing owner cells become `TBD`.	`Agenda ownership` moves to review until topic owners are named.
Participant focus	More than 10 listed attendees triggers a review status.	The brief suggests marking optional attendees or sharing notes afterward.
Decision capture	Decision meetings count every topic as decision-oriented; other formats look for decision words such as approve, confirm, choose, vote, or sign off.	`Decision capture` is marked ready when at least one decision-oriented item is present.

The time labels start from the supplied local start time and follow the selected 12-hour or 24-hour display. Time zone text is printed with the agenda so distributed teams can tell which local schedule the agenda represents.

Everyday Use & Decision Guide:

A good first pass is to set the meeting title, date, start time, time zone, and meeting format, then write the desired outcome in one sentence. The outcome should say what the group should decide, produce, or align on. After that, add the facilitator, decision rule, attendee list, and topic rows.

Use agenda rows for the work that truly needs live time. A strong row names the topic, minutes, owner, desired outcome, and prep note. When the row is rough, the generator still builds a draft by using the default item length, filling missing owners as TBD, and replacing blank prep with None. That makes incomplete rows visible instead of hiding them.

For a decision meeting, keep the decision rule short enough to read in the invite and make sure each decision topic has an owner.
For a working session, use desired outcomes that name the artifact state, not just the discussion theme.
For a status sync, shorten pure update topics and give blocker topics the stronger timeboxes.
For a planning session or retrospective, check whether the closeout wording matches the commitment the group needs to make.

The strongest stop-and-verify cue is the timing badge. If the summary says the agenda is overbooked, remove topics, shorten rows, or split the meeting before copying the draft. If the brief shows TBD owners, assign names before sending the agenda. If attendee count is over 10, decide who must attend and who can receive notes afterward.

Do not treat a polished agenda draft as proof that the meeting is ready. Check Facilitation Brief after Agenda Draft, because the brief exposes missing outcomes, overbooked time, unnamed owners, weak prep, participant sprawl, and decision-capture gaps.

Step-by-Step Guide:

Build the agenda from the meeting outcome outward, then use the readiness checks before sharing it.

Enter Meeting title, Meeting date, Start time, Time zone, and Meeting length. The summary should show a planned minute count or an attention state once rows are available.
Choose Meeting format and Time display. The format shapes facilitation prompts, while the time display changes visible start-end labels in Agenda Draft and Timebox Ledger.
Write Desired outcome, Facilitator, and Decision rule. If the outcome is blank, the page shows a validation message asking for a desired outcome before the agenda is trusted.
Add Attendees, one per line or as a comma-separated list. Watch the participant cue in Facilitation Brief if the list grows past 10 people.
Set Default item length, then paste or type Agenda rows as topic, minutes, owner, desired outcome, and prep note. Use Normalize rows after pasting mixed CSV, TSV, or pipe-delimited rows if you want the rows rewritten consistently.
Review Agenda Draft for the invite-ready agenda, Timebox Ledger for row-by-row timing, and Facilitation Brief for readiness checks. If the page reports an invalid start time, correct Start time before using the time labels.
Open Agenda Timeboxes to scan the minute distribution across agenda items. Use JSON only after the visible agenda and brief match what you plan to send.

Interpreting Results:

Read the summary first. Agenda ready means the required inputs are present and the time plan is not overbooked. Agenda overbooked means planned minutes exceed the target slot. Agenda needs attention means required details such as title, desired outcome, topic rows, or valid start time are missing.

How to interpret meeting agenda output cues.
Output cue	Boundary or trigger	How to respond
`Timebox fit`	Overbooked when planned minutes are greater than the target meeting length.	Remove, shorten, or split at least the shown overrun minutes.
`Agenda ownership`	Review when one or more topic rows use `TBD` as owner.	Name the person accountable for each topic before the invite goes out.
`Preparation cues`	Light when no row-specific prep notes are included.	Add pre-read links, input requests, or evidence notes when preparation would save live discussion time.
`Participant focus`	Review when attendee count is greater than 10.	Keep people who own topics, make decisions, or provide needed context; send notes to others.
`Decision capture`	Ready when at least one decision-oriented item is detected.	Use closeout to record decision, owner, due date, and conditions.

The agenda can show owners named even when those owners have not accepted the work. Treat the output as a draft for coordination, then confirm owner acceptance and decision authority before the meeting starts.

Worked Examples:

A launch readiness review has a 60-minute slot, a 09:00 start, decision format, four topic rows totaling 50 minutes, and a named facilitator. The opening and closeout take 5 minutes each, so planned_minutes reaches exactly 60. The summary reads as a 60 minute plan, Timebox fit is ready, and the agenda can be copied after owners and prep notes are checked.

A working session uses a 45-minute slot but includes topics of 20, 15, and 15 minutes. With 5 minutes for opening and 5 minutes for closeout, the plan needs 60 minutes. The summary reports 15 minutes over, and Timebox fit marks the agenda overbooked. Shortening one topic is not enough unless at least 15 minutes come out of the plan.

A planning session leaves two rows without minutes and sets Default item length to 10 minutes. Those rows become 10-minute items. If one row also omits an owner, Agenda ownership moves to review and the ledger shows TBD. The fix is to add the owner in the row, then run Normalize rows so the pasted agenda is easier to review.

A distributed retrospective starts at 2:30 PM, uses 12-hour display, and lists the time zone. The ledger prints start-end labels such as 2:30 PM-2:38 PM, and the agenda draft includes the time zone next to the meeting time. That helps recipients see the intended local schedule, but it does not convert the meeting time for every attendee.

FAQ:

Can I paste rows from a spreadsheet?

Yes. Paste comma-separated, tab-separated, or pipe-separated rows in the order topic, minutes, owner, desired outcome, and prep note. A first row that looks like topic plus minutes is treated as a header and skipped.

What does overbooked mean?

Overbooked means planned agenda minutes are greater than Meeting length. The summary shows the overrun minutes, and Facilitation Brief tells you to remove, shorten, or split at least that much time.

Why did a parking lot row appear?

A parking lot and decision buffer row appears when at least 5 spare minutes remain after opening, topic rows, and closeout. Smaller spare reserves are folded into closeout.

Why are some owners marked TBD?

A row gets TBD when the owner cell is blank. Add a named owner to each topic row before sending the agenda, especially for decision and handoff meetings.

Does the agenda decide who has authority?

No. The decision rule is printed in the draft so attendees can see how approval will be captured, but authority and accountability still need to be agreed by the team.

Is my meeting text sent to a separate agenda service?

The agenda is assembled in the page from the fields you type. The tool has no separate agenda-processing endpoint for meeting text.

Glossary:

Desired outcome: The decision, artifact, alignment, or next step the meeting should produce.
Timebox: A fixed number of minutes assigned to an agenda item.
Decision rule: The short statement that explains how approval, objections, or owner recommendations will be handled.
Facilitator: The person accountable for scope, timing, decision capture, and closeout during the meeting.
Parking lot: A place for relevant items that should be captured without taking over the current topic.
Prep note: A row-level reminder about what an owner or attendee should read, bring, or decide before the meeting.

References:

Want a Better Decision? Plan a Better Meeting, McKinsey & Company, May 8, 2019.
How to Design an Agenda for an Effective Meeting, ADvancing States, March 26, 2015.
Effective Meeting Agenda, SessionLab.
How to Write an Effective Team Meeting Agenda (with Templates!), Atlassian, September 2, 2022.