How to write a meeting agenda with timings that hold

A good meeting agenda states the purpose of the meeting, lists the items in order with an owner and a time for each, and goes out in advance with anything people need to read. It answers two questions for every attendee before they arrive: why am I here, and what do I need to prepare? The meeting agenda generator turns a list of items into a timed agenda with start and end times worked out, and this guide covers how to write one that holds.

Start with the purpose

Before listing topics, write one sentence saying what the meeting must produce. "Discuss the launch" is a topic; "Decide whether we launch on 3 June or delay to July" is a purpose. A clear purpose tells you who needs to be there, what to cut, and when the meeting is finished. If you cannot write that sentence, the meeting may not be needed. Updates that need no discussion travel better as an email or a shared document, and the meeting cost calculator is a sobering way to check what an hour of everyone's time costs.

Writing the items

• Phrase items as questions or outcomes. "Budget: approve or cut the extra £2,000?" is easier to close than "Budget".
• Give each item an owner, the person who introduces it and drives it to a conclusion.
• Give each item a time. Timings force realism: if the items add up to 90 minutes in a 45-minute slot, you find out now rather than halfway through.
• Put the most important item early, while people are fresh and before anyone has to leave.
• End with a few minutes to recap decisions and actions, so the minutes are easy to write.

In the generator you write each item as Topic | owner | minutes, one per line, add a start time, and it calculates when every item starts and ends and when the meeting finishes. It warns when the total runs over an hour, which is usually a sign to cut or split.

A worked example

An invented product team is meeting for 45 minutes to decide whether a new mobile app is ready to launch. The purpose: decide go or no-go for a 3 June launch, and agree who does what in the final week.

• 10:00 to 10:05 — Purpose and decision criteria (Lena, product lead), 5 minutes.
• 10:05 to 10:15 — Test results and open bugs (Omar, QA), 10 minutes.
• 10:15 to 10:25 — Support readiness: help articles and staff rota (Kim, support), 10 minutes.
• 10:25 to 10:35 — Go or no-go discussion and decision (Lena, all), 10 minutes.
• 10:35 to 10:45 — Final-week actions and owners (Lena, with Raj taking notes), 10 minutes.

The pre-read is the bug list and the test report, shared two days ahead. Notice the decision gets its own slot near the end, after the evidence, rather than an open-ended "any other business".

Sending it in advance

Send the agenda at least a day before, longer for big decisions, together with any documents to read. Say clearly what you expect: "Please read the test report and add questions in the doc by Monday." That turns meeting time into decision time rather than reading time. Include the location or video link, and if attendees are spread across time zones, show the time in each; Working across time zones covers the details, and the calendar link generator creates an invite people can add in one click.

Common mistakes

• No purpose. A list of topics with no outcome invites a meeting that runs until the time is up.
• Too many items. Four or five well-chosen items beat ten rushed ones.
• Status updates read aloud. If it could be read, send it as a pre-read.
• Everyone invited. People who only need the outcome can read the minutes.
• Ignoring the timings. An agenda only works if the chair holds to it; the meeting timer shows a countdown for each item.

After the meeting, the agenda becomes the skeleton of the minutes; How to write meeting minutes people will actually read covers that half.