{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Topics{{ computation.ok ? values.topic_count : '—' }} Owners{{ computation.ok ? ownerBadge : '—' }} Buffer{{ computation.ok ? formatMinutes(values.buffer_minutes) : '—' }}
Name the meeting as invitees should see it.
Choose the local date and start time for the invite.
This labels the local schedule; attendee conversion belongs in the calendar invite.
Use 15–480 minutes. The agenda reports overrun instead of silently stretching the slot.
min
Choose the purpose closest to the work the group must complete.
Write one concrete sentence that defines success.
Use a named person when possible.
Keep attendance tied to contribution, context, or decision authority.
One topic per line: topic, minutes, owner, desired outcome, preparation note.
Paste CSV, TSV, or pipe-delimited rows. Content stays in this browser.
Explicit topic durations are unchanged; the sample rows do not use this fallback.
min
24-hour time is the neutral display default.
Blank is neutral; add a short rule only when the meeting needs one.
{{ agendaText }}
TimeAgenda itemMinutesOwnerDesired outcomePrepCopy
{{ row.time_label }}{{ row.label }}{{ row.minutes }}{{ row.owner }}{{ row.outcome }}{{ row.prep }}
CheckStatusEvidenceNext actionCopy
{{ row.label }}{{ row.status }}{{ row.evidence }}{{ row.action }}

The chart renderer is unavailable. The exact minutes remain available in the timebox ledger.

Meeting Minutes Generator Turn rough meeting notes into structured Markdown minutes with decisions, accountable action items, and circulation-readiness checks.
Meeting Cost Calculator Estimate the labor cost of one meeting and its yearly recurrence, then compare a shorter or smaller scenario using loaded hourly rates.
Event Schedule Generator Build an event run sheet from pasted session rows, keep fixed cues or continuous flow, and catch overlaps and tight handoffs before publishing.
On-call Handover Report Prepare an on-call handover with normalized incident rows, ownership checks, readiness rules, and warnings for risky or incomplete transfers.

A calendar invitation reserves time, but it does not tell a group what must be different when that time ends. A useful meeting agenda names the outcome, gives each topic an owner, and fits the work into a finite slot. Those choices make it easier to move status updates out of the room and keep live discussion for decisions, problem-solving, and coordination.

Start with the outcome rather than the topic. “Discuss launch readiness” leaves the finish line open. “Approve the launch scope and assign owners for unresolved blockers” tells participants what evidence to bring and what decision the facilitator must close. The same distinction applies to a working session, planning session, status sync, or retrospective.

  • Decision meetings need the decision question, authority, and a rule for objections or escalation.
  • Working sessions need a defined artifact or problem that can visibly advance during the slot.
  • Status syncs earn live time when they surface blockers and dependencies, not when they repeat written updates.
  • Planning and retrospective sessions need a horizon or review period plus owned follow-up actions.

Timeboxing makes tradeoffs visible before the meeting. Opening and closeout need protected minutes, while every topic consumes part of the remaining space. If the total does not fit, an honest agenda reports the overrun instead of silently shortening discussion or extending the meeting. Spare time can become a buffer for drift, objections, or a parking lot.

Ownership and preparation are different from attendance. A topic owner is accountable for moving that item toward its outcome; an attendee may contribute context, expertise, or decision authority. Listing everyone without assigning owners often creates the appearance of preparation while leaving the facilitator to rescue each stalled topic.

An agenda is still a plan, not a guarantee. New information can change priorities once the meeting begins. The practical test is whether the group can see what to shorten, defer, or reassign without losing the desired outcome.

How to Use This Tool:

Define the meeting’s finish condition before allocating topic minutes.

  1. Enter the meeting title, date, start time, time zone, and length. The time zone labels the schedule; it does not convert times for attendees.
  2. Choose the Meeting format, write one concrete Desired outcome, and name the Facilitator. Add a decision rule only when approval or escalation needs an explicit rule.
  3. Add one Agenda row per topic in topic, minutes, owner, desired outcome, preparation order. Commas, tabs, or pipes are accepted. A missing or unreadable duration uses the Default topic length.
  4. Read the fit and ownership checks. Reduce or move at least the reported overrun minutes before publishing, and replace any TBD owner that would leave a topic unled.

Interpreting Results:

Ready means the scheduled rows fit inside the selected length. It does not mean the agenda is strategically complete. Check that the desired outcome is specific, each important topic has an owner, and preparation notes are realistic for the people invited.

Overbooked is an exact minute deficit under the current scheduling rules. Remove time, move a topic to another channel, or lengthen the meeting. Do not treat the displayed end time as a promise when the agenda is still overbooked. If the schedule crosses midnight, time labels add a day offset; the selected time zone remains a label rather than an attendee conversion.

Technical Details:

The schedule follows a documented planning model rather than an external meeting standard. It turns each topic row into an integer-minute block, adds protected opening and closeout blocks, and assigns any meaningful remainder to a buffer. Calendar labels do not model travel time, attendee availability, daylight-saving transitions, or cross-zone conversion.

Formula Core

Let D be the selected meeting length, O the opening minutes, C the closeout minutes, and ti each topic duration. The unallocated remainder is:

R = D − (O+∑i=1nti+C)

Opening and closeout are each 3 minutes when D is at most 20 minutes, 8 minutes when D is at least 90 minutes, and 5 minutes otherwise. For a 60-minute meeting with 42 topic minutes, the base plan is 5 + 42 + 5 = 52 minutes, leaving an 8-minute buffer.

Rule Core

Remainder Rule Fit result
R < 0The absolute deficit becomes overrun minutes.Overbooked
R = 0No buffer is added.Ready
0 < R < 5The remainder extends closeout.Ready
R ≥ 5The remainder becomes a parking-lot and decision buffer.Ready

Topic durations accept whole minutes, clock-style values such as 0:15, and hour or minute suffixes. Positive parsed values are rounded to the nearest whole minute; a blank, unreadable, or non-positive value uses the default topic length. Each final topic must be from 1 to 240 minutes, the meeting length from 15 to 480 minutes, and the source may contain no more than 200 agenda rows.

Rows are scheduled sequentially from the entered start time. The model counts decisions by meeting type and topic wording, records missing owners as TBD, and reports preparation coverage. Those checks are facilitation prompts, not an assessment of whether the meeting itself is necessary.

Privacy Notes:

Agenda text is assembled in the browser and is not sent to a meeting service. That makes the page suitable for internal drafting, but copied or downloaded agendas can still contain names, decisions, risks, and preparation notes. Apply the same access controls to the exported agenda that you would use for the meeting invitation or project record.