How to write a meeting agenda

To write a meeting agenda, start with one line on why the meeting exists, then list each item with a start time, the minutes it gets, the person leading it and the outcome it needs: a decision, input or information. Phrase items as questions where you can, put the pre-reading with the agenda, and send both early enough to be read. The table under this article shows a complete board agenda built that way.

Start with the purpose and the decisions

Harvard Business Review’s article on agenda design, by organisational psychologist Roger Schwarz, frames an effective agenda as one that sets clear expectations for what happens before and during a meeting: it helps people prepare, allocates time and shows when a discussion is complete. The fastest way to get there is to decide what the meeting must produce before listing what it will cover.

Write the purpose as one sentence at the top. The August board meeting sends the FY26 statements to audit, decides whether Wattle Grove proceeds to tender finalisation and endorses the updated risk register. Anyone reading that sentence knows which three items matter, and the chair knows which ones cannot be cut if the meeting runs long.

If you cannot write the purpose line, the meeting may not need to happen. An update with no decision attached is often better as an email.

Write items as questions, with an outcome

Schwarz’s most practical suggestion is to list topics as questions to be answered. Office space reallocation becomes under what conditions should office space be reallocated. The question tells people what to think about in advance and tells the chair when the item is finished: when the question has an answer.

The same article recommends saying whether each item is there to share information, seek input or make a decision. That one word changes behaviour. People stop debating an item that was only ever for information, and they come prepared to commit on an item marked decision.

The board meeting minutes example on this site shows why this matters after the meeting too. Six of its seven discussion items end in a resolution line, such as that the board accepts the unaudited FY26 statements and recommends them for audit. The table below rewrites those items as the agenda questions that would have produced them. Question 4, should the FY26 statements go to audit, maps exactly onto resolution 4. The minute taker’s job becomes recording the answer.

Time every item

A time beside each item does three jobs. It makes the agenda honest, because adding the minutes shows whether nine items really fit in a morning. It gives the chair permission to move on. And it tells people who only need one item when to join.

The worked agenda runs from 9:30am to 11:45am, the start and close recorded in the minutes: 135 minutes for nine items and a break. The pattern inside it is common to most good agendas:

• Short items that confirm or record get five or ten minutes. Confirming the previous minutes should not take longer than it takes to ask whether anyone has corrections.
• Decisions get twenty. That is enough to hear the recommendation, ask questions and resolve, and not enough to redo the analysis in the room.
• Reports get fifteen, and only for questions, because the report was in the pre-reading.
• A break sits before the second half, because attention after ninety minutes is not what it was at the start.

Sequoia’s structure for early stage board meetings uses the same idea at a larger scale: a calibration section of 45 to 60 minutes on the company’s status, then working sessions of 30 minutes per topic.

Owners and pre-reading

Every item needs one name beside it. Not the finance team, but the treasurer. The owner prepares the paper, opens the item and proposes the outcome. In the worked agenda the CEO owns three items, the chair four and the company secretary two, which is typical of a board where management reports and the chair runs the governance.

Pre-reading is what makes the times achievable. Sequoia advises distributing board materials one to two days in advance and asking members to study them, so the meeting is spent discussing rather than presenting. The board meeting deck example on this site is sent as a pre-read five days before a two hour meeting, and its own agenda slide takes consent items in the first ten minutes and holds the last twenty for three decisions.

For a project team rather than a board, the same principle can be applied in the room. Atlassian’s project kickoff play starts with a five minute silent pre-read of the project’s key document and an overview of the agenda before any discussion. The project kickoff deck example ends with five decisions the room must make before anyone leaves, which is an agenda written onto the last slide.

Order the items deliberately

There is no single correct order, but there are two sensible ones.

Routine first, then decisions. Confirm the minutes, review actions, take reports as read, then spend the long middle of the meeting on decisions. This is the order in the worked agenda and in most formal board meetings, because confirming the minutes and matters arising sets the record straight before new decisions are made.

Decisions first, then updates. For internal meetings where attention fades fast, put the one decision that matters at the top while everyone is fresh, and let updates absorb whatever time remains.

Whichever order you choose, keep confidential items together near the end, so anyone who must leave can do so once. And put the recurring structure in the same place every time. The all hands meeting deck example has used the same eleven slide order for two years precisely so nobody reads ahead to find their part.

Common mistakes

• Topics instead of questions. Budget is a topic. Should the marketing budget move $40,000 into Q3 is an agenda item.
• No times. An untimed agenda is a list, and the last item always gets squeezed.
• Any other business as a long item. It invites new topics nobody prepared for. Keep it to five minutes, or ask for items in advance.
• Reports presented aloud. If it was in the pre-reading, take questions only.
• Pre-reading sent the night before. It will not be read, and the meeting becomes the reading.
• No outcome named. People cannot prepare to decide if they do not know a decision is expected.

After the meeting, the minutes close the loop. The post on how to write meeting minutes covers what to record against each item, and the question page on minutes versus notes explains when a formal record is needed.

Build it

An agenda is a table, and the document maker for tables is built for exactly that: time, item, owner, minutes and outcome in columns, with the purpose line above. Describe the meeting, its purpose, each item with its owner and the outcome needed, and the generator writes and lays out the document, then you can edit any cell. The generator decides a document’s scale before writing it, and a cover is never added to anything under three pages, so a one page agenda will not get one.

The guide to creating a document with AI walks the steps, and the finished agenda downloads as a PDF to attach to the calendar invitation with the pre-reading. If the meeting is formal, the same numbered item list becomes the skeleton of the minutes: each question gets its answer as a resolution, each owner gets their actions and dates, and the structure is in place before the minute taker writes a word.