How to run a productive meeting: agenda, roles and follow-up
A practical guide to running a productive meeting: a clear agenda, three simple roles, time limits, and a close that names owners and dates.
Read the articleBlog · How-to
In short: A meeting agenda is the list of items a meeting will cover, in the order they will be taken up, with a time, an owner and a result for each one. Put the date, place and attendees at the top, state the purpose in one or two sentences, then list each item with its lead and its time. Send it before the meeting and leave space for decisions and next steps.
A meeting agenda is the list of items a meeting will cover, in the order they will be taken up. A good agenda also says why the meeting is happening, when it starts and ends, and who leads each item. The agenda is written before the meeting and describes what is planned, from the opening to the close.
The minutes are different. They are written during or after the meeting and record what was decided. The guide to meeting minutes covers that part. Many teams keep both in one document, which we explain near the end of this post.
Most agendas, from a ten-minute check-in to a board meeting, have the same six parts. Write them in this order:
A practical guide from Zapier's meeting agenda article makes the same point. It asks for a clear goal, a lead for each topic, an estimate of how long each item will take, and room for notes and next steps.
Copy this structure into a document and fill it in for every meeting. Keep the whole agenda to one page. If it runs longer, the meeting probably has more topics than it can handle.
| Part | What to write |
|---|---|
| Meeting | Title, date, start and end time, place or call link |
| Attendees | Expected people, chair, note-taker |
| Purpose | One or two sentences: why we are meeting |
| Agenda items | Number, topic, lead, minutes allowed, result wanted |
| Pre-reads | Links, with the section to read |
| Next steps | Actions, owners, due dates, next meeting |
Here is a 45-minute team meeting before a product launch. The names are examples only.
| Item | Lead | Time | Result wanted |
|---|---|---|---|
| Actions from last week | Layla | 5 min | Status only |
| Launch date | Omar | 15 min | Decision |
| Support plan for the first week | Huda | 15 min | Discussion, then an owner |
| Risks and open questions | Ahmad | 5 min | A list, with an owner for each risk |
| Next steps and close | Chair | 5 min | Actions read back to the group |
Notice the balance: one decision, one long discussion and one short update. Everything else is brief. That shape keeps the meeting on time and gives the note-taker a clear list to record.
Start from the end time and work backwards. Give each item the time it needs, based on how complex and how important it is. Then order the items by importance, so the most important ones are covered even if the meeting runs late.
Leave a buffer for discussion that runs over. Zapier suggests adding about 10 percent of the total meeting length. For a 60-minute meeting, that is roughly six minutes. It is better to plan that time than to cut the closing short.
Give every item one lead. The lead opens the topic, keeps to the time, and says what result is needed. When an item has two leads, usually nobody is responsible for it.
Send it before the meeting so people can prepare and add what they need. Set a deadline for additions the day before, and ask people to send their items in a message rather than raising them in the meeting. Put the pre-reads in the same message, with the section to read, so nobody has to hunt for them.
Before you send it, check each item and ask whether it needs the whole group. A decision that one person can make in a message does not need a fifteen-minute slot.
It can. Leave a blank space under each item for the decision and the action. During the meeting, fill those spaces in, and the agenda becomes the skeleton of your minutes. Send the finished version the same day. That keeps one record instead of two. If you want a ready layout, use the meeting minutes template.
Formal bodies usually follow a fixed order. The Wikipedia article on agendas describes the standard order of business in Robert's Rules of Order Newly Revised: reading and approving the minutes first, then reports from officers and committees, special orders, unfinished business, and new business. Most discussion and decisions happen under new business, so give it the most time.
For meetings in Arabic and English, write each item in the words people will actually use. A Gulf team that talks in both languages will recognise «مراجعة الـ roadmap» faster than a translated title. Keep product names and technical terms in Latin script, so people can search for them later. For a related guide, read how to run a productive meeting.
Echo records your meeting on iPhone, or on Mac from the menu bar. It writes a full transcript, a summary with the key points and decisions, and a to-do list. Afterwards you can check the discussion against your agenda. Echo's templates include Team Meeting and Client Meeting, and you can export a note to PDF or Word. On Mac, Echo records from the menu bar using the microphone and system audio, so no bot joins the call. Tell everyone you are recording and ask before you start, because the rules differ by country. Echo is free for 30 minutes of recording a month, and Echo Pro gives unlimited minutes.
An agenda is written before the meeting and lists what will be covered. Minutes are written during or after the meeting and record what was decided, who owns each action and when it is due.
One page is the usual limit. If the agenda runs longer, cut items or move status updates into a message sent before the meeting. A long agenda usually means the meeting is trying to do too much.
The person who calls the meeting, or the chair, usually writes it. Attendees can add items before the deadline, but one person should make the final order so the agenda holds together.
Give time to every item that needs discussion or a decision. Status updates can be read before the meeting. Add a small buffer, about 10 percent of the total length, for items that run over.
Reuse the structure, but write new items for each meeting. A recurring meeting can keep the same header and closing section while the items change.
Checked on 4 November 2026.
Try Echo on your next meeting. Free for 30 minutes a month.
Try Echo free