Meeting cadence: how often each meeting should happen, with a template for a team of 5 to 50 — and where each recurring meeting keeps its history (2026)

Meeting cadence is the fixed rhythm of a recurring meeting: how often it happens, on which day and at which hour, and for how long. It is set once, per meeting series, and then left alone — the point of a cadence is that nobody schedules the meeting, nobody asks whether it is on this week, and the work between two occurrences is shaped by the knowledge of when the next one is. A team's "meeting rhythm" or "operating rhythm" is the set of all its cadences together: the daily, the weekly, the one-on-ones, the monthly, the quarterly, and how they fit into one calendar without colliding.

This guide is the craft first — what cadence is and what it isn't, the four rules for choosing one, the cadence of each meeting most teams run — then a template you can copy, sized for a team of 5, 15 and 50 with the hours it costs each person per week, and the signals that a cadence should change. The last part is the one most cadence guides skip: a recurring meeting is a series, and a series is only as useful as its memory. Where the history of each one lives — in the tools your team already uses, and in a channel built to keep it — decides whether the weekly of three weeks ago is a search or a question to the room.

What meeting cadence is — and what it isn't

Three words get used for the same calendar entry, and they are not the same thing:

The cadence is the slow layer. A weekly that moves every week has a schedule but no cadence, and the team pays for it twice: once in the scheduling, and again in the work that cannot be planned around a slot that keeps moving. The agenda is the fast layer, and it has its own guide; this one assumes each occurrence has a list.

Cadence is not "how many meetings we have". A team with a daily stand-up, a weekly and one-on-ones has three cadences and a sane week; a team with the same three meetings booked ad hoc has none and a full calendar. And it is not a company-wide number: the right cadence for a stand-up and for an all-hands differ by a factor of twenty, which is why cadence is set per meeting and then assembled into a rhythm, not chosen once for everything.

Four rules for choosing a cadence

1. The cadence follows the rate of decisions, not the calendar. Ask how long a question can wait before the wait costs more than the meeting. A blocker costs a day for every day it is not raised, so the meeting that surfaces blockers is daily. A scope decision can wait a week without harm, so the meeting that makes it is weekly. A direction change — what the team is for, who is on it — is a quarter's question. If you find yourself calling a meeting between occurrences, the cadence is too slow; if occurrences are cancelled for lack of items, it is too fast.

2. The cost is headcount times length times frequency. A 30-minute weekly for 12 people is six hours a week, 300 hours a year. Written down next to what the meeting produces, that number decides most cadence arguments on its own. Set a budget per person — two to four hours a week of recurring meetings is a common range for a team member, more for a lead — and let the cadences compete for it, so adding one means slowing another.

3. A fixed slot, the same link, rescheduled and never cancelled. Same day, same hour, same meeting link for every occurrence. A series that keeps its slot can be planned around; a series that keeps its link has one address for its history. When the slot cannot be held — a holiday, a trip — the occurrence moves, it does not disappear: a cancelled meeting tells the team the cadence is optional, and from then on it is. How the series itself is set up in Google Calendar and Outlook — the pattern, the end rule, one occurrence moved without the rest — is in recurring meeting.

4. Each occurrence reads from the last one. A recurring meeting is a series, and the series has a memory: the open items of last time are the first thing checked this time, and the parking lot of this time is the start of the next agenda. A cadence without that thread is a set of unrelated meetings that happen to share a slot; the thread is what makes a weekly a weekly. Where the thread lives — in whose notes, in which tool, in which language — is the subject of the second half of this guide.

The cadence of each meeting most teams run

The cadences below are the ones teams converge on in practice; the reasoning is rule 1 applied to each meeting's purpose. The length is the ceiling.

Two things in the table are not obvious until you have run both. The retrospective sits after the review, not before, so that it works from what actually shipped. And the quarterly review is where the cadence itself is on the agenda: once a quarter, every recurring meeting is asked whether it still produces what it was set up for, at the cost it has.

The agendas for each of these — the items, owners and minutes — are in meeting agenda examples; the stand-up, the one-on-one, the all-hands and the project kickoff have their own guides.

A meeting cadence template for a team of 5 to 50

The same cadences assembled into a week, at three sizes. The hours are per person, recurring meetings only, before client calls; they are the budget of rule 2, written out.

The template to copy — one block per team, kept where the team talks, so that a new member reads the rhythm on day one:

[Team] — our meeting cadence · reviewed [date], next review [date, one quarter on]
Budget: [hours] per person per week of recurring meetings.

Stand-up — every working day [time] — 15 min — [link] — owner: [rotating facilitator]
Leaves behind: today's blockers with a name each, posted in [channel] by [time + 20 min].

Weekly — [day] [time] — [minutes] — [link] — owner: [name]
Leaves behind: decisions, open items, the parking lot for next week.

One-on-ones — weekly, [day], 30 min each — the same link per pair — owner: the report
Leaves behind: next steps with names and dates, visible to both.

Planning and review — every two weeks, [day] [time] — 60 min — [link] — owner: [name]
Leaves behind: the cycle's scope with owners; what shipped and what did not.

Retrospective — every two weeks, after the review — 45 min — [link] — owner: [rotating]
Leaves behind: two or three changes to how we work, each with an owner.

All-hands — [monthly / every two weeks], [day] [time] — [minutes] — [link] — owner: [name]
Leaves behind: the numbers, the decision explained, every question answered or dated.

Rules: fixed slots, same link every time; an occurrence is rescheduled, never cancelled; each meeting opens with last time's open items; the cadence itself is reviewed at the quarterly.

The block is plain text; it pastes into a chat message, a document or a canvas without reformatting.

The weekly budget: checking a cadence with arithmetic

Rule 2 as a worked example, for the 15-person column. A team member attends a daily stand-up (5 × 15 min), a weekly (45 min), a one-on-one (30 min), planning and review every two weeks (30 min a week averaged), a retrospective every two weeks (about 22 min a week averaged) and an all-hands every two weeks (15 min a week averaged): about three hours and ten minutes a week. A lead adds the leadership meeting and two or three one-on-ones on the other side of the table: about four and a half. Across fifteen people that is roughly 50 hours a week, 2,500 a year.

The number is not an argument against meetings. It is the price, and the question is whether what the cadence produces — the blockers caught in a day rather than a week, the decisions made on Tuesday rather than in a thread that runs to Friday — is worth it. Usually it is, for the meetings in the table. The arithmetic finds the ones where it is not: the 60-minute weekly that could be 30, the status meeting that duplicates the stand-up, the leadership meeting with nine people and two deciders.

When to change a cadence: five signals

A cadence is reviewed quarterly and changed rarely, because changing it costs the planning that depended on it. Between reviews, five signals say a cadence is wrong now:

1. Meetings are being called between occurrences. The questions cannot wait for the slot; the cadence is too slow, or the meeting is the wrong size for the questions it gets.
2. Occurrences are cancelled for lack of items, two or three times in a row. Too fast — or the agenda is being collected too late to show that there are items.
3. Decisions are made elsewhere and reported to the meeting. The meeting has become a status meeting; either move the decision back into it or shorten it to what it still does.
4. Open items are older than twice the cadence. An action item two weeks old on a weekly, a month old on a fortnightly, is a sign the series has no memory — nobody checks last time's list — or that the item is a project, not a task.
5. Attendance drifts. When the people who need the decision stop coming and the people who do not keep coming, the slot or the invite list is wrong before the frequency is.

The fix is almost never "more meetings". It is one cadence slowed, one sped up, one meeting merged into another, and the parking lot of one series moved to where it belongs.

Where each recurring meeting keeps its history in the tools you already use

A recurring meeting lives in a calendar, and what each occurrence leaves behind lives wherever the tool puts it. Documented behaviour only, from the vendors' own pages; each cell names the month its fact was checked.

Across the four, each occurrence leaves one document or one summary, in the language it was written or held in, and the thread between occurrences — last time's open items at the start of this time — is a person's job: someone opens the previous document and reads it into the meeting. Where that is fine, any of the four will do and the table is the whole answer. The next section is one way the job gets done where the series needs a memory of its own, read by members who do not all read the same language.

How a series keeps its history in a channel

InterMIND is a communication space where a recurring meeting lives in a channel. The meeting link is permanent, so the room is the same every occurrence; the cadence is set once, in Google Calendar or Outlook, on an event the product pre-fills with the join link and the recap link — and a one-off room that already met can be made recurring from its row without losing its chat and recaps. Whatever the cadence, the channel keeps the whole series in one place and in each member's language: the chat is translated per reader — each member types in their own language and reads the others in theirs, with the original one toggle away — and the channel keeps the recap of every past session, not only the latest, so the weekly of three weeks ago is a switch between sessions on the recap page rather than a question to the room. An ad-hoc meeting by link keeps only its latest recap, and its chat is wiped when the call ends; a series belongs in a channel.

Rule 4 is what the recap does. When the call ends, the recap is written from the meeting itself — a summary, the action items with owners — and arrives by email to each signed-in participant, as a message in the channel and as a link in the calendar event, each member reading it in their own language rather than the one the room happened to use. Any member can edit it, every edit keeps author and revision history. For a channel's recurring meeting, the open action items of the previous session are read back when the next recap is written and judged against what was said: an item someone reported finished is marked done, anything else is marked not done with the reason in the words of the meeting, or "not discussed" — and at the start of the next session Mia names the open items and their owners, so last time's list is the first thing spoken about rather than the first thing forgotten. This part runs for selected accounts while it is being refined.

The cadence block itself — the template above — is a note in the channel, where a new member finds it on day one. During the quarterly, the note goes on everyone's screen next to the video tiles with Share to conference: the sharer edits it live while the room watches, and every participant reads it in their own language. The same works for a previous session's recap, for reviewing last cycle together before planning the next.

A series is members-only. A colleague or a client who belongs in the channel is added by email invitation onto a free account and reads the channel in their language. Someone who needs one occurrence only — a partner for one review, a candidate for one call — joins an ad-hoc meeting by link, from a phone, without an account and at no cost, hears the meeting live in their own language and gets nothing afterwards: the account is free, and it is what makes the record reachable. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia; a member on leave for a month keeps access and costs nothing that month, and the series they come back to is in the channel, with every session's recap.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

A cadence survives every tool: somebody still has to decide how often, hold the slot, and open each occurrence with what the last one left open. What does not have to survive is the second job — finding last time's document, reading it into the room, and typing this time's up by hand, in one language, for people who read others.

FAQ

What is meeting cadence?

Meeting cadence is the fixed rhythm of a recurring meeting: how often it happens, on which day and at which hour, and for how long. It is set once per meeting series — a daily stand-up, a weekly team meeting, a monthly all-hands — and left alone, so that nobody schedules the meeting and the work between occurrences can be planned around it. A team's meeting rhythm is all of its cadences together.

What is a good meeting cadence?

One that matches how long each kind of question can wait. Blockers cannot wait a week, so the meeting that surfaces them is daily and short; decisions can wait a week, so the team meeting is weekly; review and planning follow the team's cycle, every one or two weeks; direction is quarterly. A good cadence also fits a budget — two to four hours a week of recurring meetings per team member is a common range — and is reviewed once a quarter rather than changed ad hoc.

How often should a team meet?

For most teams of five to fifty: a daily stand-up of fifteen minutes or less, a weekly team meeting of 30 to 60 minutes, one-on-ones weekly or every two weeks, planning and review every one or two weeks, a retrospective every two weeks or monthly, and an all-hands weekly up to about thirty people and every two weeks or monthly above that. The template in this guide lays the set out for 5, 15 and 50 people with the hours it costs each person.

What does cadence mean in meetings?

Cadence means the regular, repeating interval at which a meeting is held — "a weekly cadence", "a two-week cadence" — and by extension the fixed day, hour and length that come with it. A "cadence meeting" or "cadence call" is a recurring meeting held on that interval, usually between a team and a stakeholder or a client, to review progress and next steps; the term is common in sales and in client delivery.

How often should one-on-ones be?

Weekly, 30 minutes, for a new report in their first 90 days and for anyone remote or in another time zone; every two weeks, 45 minutes, once the relationship is established and the work is going well, with a monthly session for growth replacing one regular one. The rule that matters more than the interval: a one-on-one is rescheduled, never cancelled. The one-on-one meeting template has the structure and the questions.

How do you decide the cadence of a recurring meeting?

Ask what the meeting produces and how long that result can wait: the wait sets the frequency. Multiply headcount by length by frequency to see the cost, and set it against a per-person budget so that adding one cadence means slowing another. Fix the slot and the link, open each occurrence with the last one's open items, and put the cadence itself on the agenda of the quarterly review. Change it when meetings get called between occurrences, when occurrences are cancelled for lack of items, or when open items grow older than twice the interval.

What is the difference between meeting cadence and meeting rhythm?

Cadence is the property of one recurring meeting — its frequency, slot and length. Rhythm, or operating rhythm, is the set of all a team's or a company's cadences and how they fit together: the daily inside the weekly, the weeklies inside the monthly, the quarterly review where the rhythm itself is adjusted. You choose cadences one meeting at a time and then check that the rhythm fits in the budget and the calendar.

Sources: Microsoft — Schedule a meeting in Microsoft Teams; Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Generating meeting agenda with AI Companion; Zoom — Using Meeting Summary with AI Companion; Google Meet — Start or schedule a Google Meet video meeting; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Use huddles in Slack; Slack — Meeting agenda template. Each table cell names the month its fact was checked — the earliest checked August 2026, the latest checked October 2026. Vendors change plans, features and language lists over time; check their pages for the current state.