Stephen Turner
Akash Kumar
Jordan Lee
Taylor Scott
What is a meeting agenda?
A meeting agenda is the shared, written plan for a meeting. It says why the group is meeting and lists the topics in order. Each topic ideally has an owner, a time limit and an expected result: decide, discuss or inform. People use it to prepare, and the chair uses it to keep the meeting on track.
What goes on a meeting agenda
A good agenda answers what people want to know before they walk in. GitLab's public handbook requires an agenda for every work meeting. It asks for a title, the attendees, the date and background on why the group is meeting. It also asks for a place where people can add questions.
An organizational psychologist writing in Harvard Business Review puts the agenda's job simply. It sets clear expectations for what needs to happen before and during the meeting.
- Purpose: the outcome the meeting exists to reach, in one sentence.
- Topics in order, each with an owner and a time allowance.
- The expected result of each topic: decide, discuss, or inform.
- Pre-reading or context, linked rather than pasted.
- Space for questions and for notes taken during the meeting.
A short example
Here is a made-up agenda for a 30-minute planning meeting. The expected result next to each item tells people how to prepare. For an “Inform” item they just listen; for “Decide” they bring a view.
| Topic | Owner | Time | Expected result |
|---|---|---|---|
| Purpose: agree the launch date for the onboarding guide | Chair | 2 min | Inform |
| Status of the draft and open review comments | Writer | 8 min | Inform |
| Choose between the two launch dates | Product lead | 15 min | Decide |
| Confirm next steps and who sends the notes | Chair | 5 min | Decide owners and next steps |
When to share it
Share the agenda early enough for people to read it. GitLab asks for it at least 72 hours ahead. That gives people time to decide whether to attend, do the reading and comment in writing if they can't join.
Many teams give less notice, and that's fine. What matters is that an agenda first seen in the meeting can't help anyone prepare.
Keep one agenda per meeting. GitLab's handbook treats two competing agenda documents as a problem to fix right away, because notes need one source of truth.
How an agenda differs from minutes and a brief
Three documents often get mixed up. Each one belongs to a different moment.
- The agenda is the plan, written before the meeting.
- Minutes are the record of what was decided and who owns each action, written afterwards.
- A meeting brief is one attendee's preparation: research on the people and history behind the meeting.