In a small business, the weekly team meeting is often the only time everyone is in the same room. That makes it valuable, and it is also why it so often goes wrong. With no agenda, it turns into a round of updates that everyone half-listens to, runs over by 20 minutes, and ends without anyone quite sure what was agreed.
A good team meeting agenda is short, runs in the same order every week, and spends most of its time on the things only a meeting can do: deciding, unblocking and agreeing who does what. This post gives you that agenda for a team of 3 to 20, with a template to copy.
What the weekly meeting is for
Before the agenda, the purpose. A weekly team meeting in a small business should do 4 things:
- Check the numbers that matter, so everyone knows whether the week went well
- Surface what is stuck, while it can still be fixed this week
- Make the decisions that need more than one person
- Leave with owners and dates for everything agreed
What it should not be is a status update. If each person spends 3 minutes listing what they did, a team of 8 has spent 24 minutes on information that could have been read beforehand in 2.
The team meeting agenda
30 minutes, the same order every week.
1. Numbers (5 minutes). 3 to 5 figures the business actually runs on, compared with last week. Sales, orders, open quotes, cash in, whatever fits your business. No discussion yet, just the numbers, and a flag on anything that moved the wrong way.
2. Goals check (5 minutes). For each of this quarter's goals, one line: on track, at risk or off track. Only the at-risk and off-track ones get discussed, and only briefly. If a goal needs more than 2 minutes, it goes on the list for section 4.
3. What is stuck (10 minutes). Each person names anything that is blocked or slipping. Not everything they are doing, just what is stuck. The group decides for each one: who can help, what changes, or whether it waits.
4. Decisions (8 minutes). The items that were added to the agenda in advance because they need the team: a change of supplier, a new process, a customer problem. Each one ends with a decision or a named person who will bring the information needed to make one.
5. Read back actions (2 minutes). Whoever is taking notes reads every action item aloud with its owner and date. Anything nobody owns does not leave the room.
The template
## Weekly team meeting: [date]
## 1. Numbers
- [Metric]: [this week] vs [last week]
- [Metric]: [this week] vs [last week]
## 2. Goals
- [Goal]: on track / at risk / off track
- [Goal]: on track / at risk / off track
## 3. Stuck
- [Item] — [who raised it] — [what we agreed]
## 4. Decisions
- [Topic added in advance] — [decision, or who brings what by when]
## 5. Actions
- [ ] [Verb + task] — [owner] — [date]
4 rules that keep it to 30 minutes
Updates happen before the meeting. Everyone looks at the shared task list and the goals before they walk in. If the work is tracked somewhere the whole team can see, there is no need to narrate it.
Agenda items are added in advance. Anyone can add a topic to section 4, but it has to be there before the meeting starts. Topics raised in the room go to next week unless they are genuinely urgent.
Same day, same time, same order. A meeting that always happens at 9 on Monday in the same shape takes no organising and becomes a habit. One that moves around gets skipped.
End on time, even if you have not finished. Unfinished decisions go to the top of next week's section 4. Running over teaches everyone that the end time is a suggestion.
Adjusting it for your team
For 3 or 4 people, cut it to 15 minutes. Merge numbers and goals into one section, and drop the formal read-back in favour of a quick check at the end.
For a team that is mostly remote, keep the same agenda but put sections 1 and 2 in writing before the call. The call is then only for what is stuck and what needs deciding.
For a team on shifts, pick the time with the most overlap and rotate the note-taker so the people who miss it have a clear written version.
For the daily version, a 10-minute stand-up is a different meeting with a different job. Our stand-up meeting guide covers it.
Running it in EvyOS
The meeting is only as quick as the information behind it. In an EvyOS shared workspace, the parts you would otherwise narrate are already visible: goals show progress calculated from the work underneath them, the activity feed shows what changed this week, and the Today view shows what is overdue.
That leaves the meeting for deciding. Keep the agenda as a note in a meetings folder, add section 4 topics to it during the week, and turn each action item into a task assigned to its owner before the day is out. Making the meeting itself a weekly habit in the workspace gives you a record of how often it actually happens.
The set up team rituals template helps you decide what each recurring meeting is for and drop the ones that have no answer, and the run meetings with an agenda template makes the agenda-first habit stick. For the notes themselves, see our meeting notes template.
The short version
Run the weekly team meeting in 30 minutes, in the same order every week: numbers, goals, what is stuck, decisions, actions. Do the updates before the meeting, add topics in advance, and end on time. Everything agreed leaves the room with one owner and a date.
Set up a workspace for your team, or see how EvyOS works for teams.