Meeting cadence: how often should your team meet?

Meeting cadence is how often a meeting happens, and it is the setting most teams never deliberately choose. A weekly sync gets created in someone's calendar during a busy quarter, the recurrence box gets ticked, and three years later it is still going because nobody has the standing to cancel it.

Cadence is usually the decision underneath complaints about meetings. Teams argue about agendas and length when the real problem is that a meeting recurring every week only has enough substance for once a month.

This covers what cadence means, how to pick one, the cadences most teams actually need, and how to tell when one has gone stale.

What meeting cadence means

Cadence is the rhythm of a recurring meeting: daily, weekly, fortnightly (every two weeks), monthly, quarterly. It is one of four settings that define a meeting, and two of the others, duration and attendance, usually get more attention than they deserve:

• Cadence. How often it happens.

• Duration. How long it runs.

• Attendance. Who is required rather than invited.

• Purpose. What the meeting decides or unblocks.

Purpose determines the other three. A meeting that exists to surface blockers needs to happen before blockers cost a day, which usually means daily. A meeting that exists to review results needs to happen after there are results, which usually means monthly or quarterly. A badly-attended meeting is often running at a cadence its purpose does not justify, though an over-broad invite list will do the same thing.

How to choose a cadence

One question does most of the work: what is the cost of waiting?

If a decision waits until the next meeting, what does that cost? If the answer is "a few hours of someone being blocked", the meeting needs to be frequent. If the answer is "nothing much, we would have found out anyway", it does not.

Three follow-ups that sharpen it:

How fast does the underlying thing change? A support queue changes hourly. A hiring plan changes monthly. Match the meeting to the rate of change of the subject, not to the calendar's convenience.

Is this meeting for information or for decisions? Information can go asynchronous, and usually should. Decisions benefit from people in the same place at the same time, because the alternative is a thread that runs for four days and ends in a call anyway.

Who is actually blocked without it? If the honest answer is nobody, the meeting is a status ritual and its cadence can drop a level immediately.

The cadences most teams need

Not prescriptive, but this is the shape that works for most small teams.

Daily, 15 minutes: the standup. Purpose is unblocking, not reporting. If people are describing what they did yesterday rather than what is in their way, it has drifted into a status meeting and should be a written update instead.

Weekly, 30 to 60 minutes: the team meeting. Purpose is coordination and decisions that need discussion. This is the meeting most likely to be running at the wrong cadence, because weekly feels like the default rather than a choice.

Weekly or fortnightly, 45 minutes: the one to one. Purpose is the individual, not the project. The mainstream advice is weekly, and it is right more often than not: the gap between one to ones is the gap before a problem gets raised. Fortnightly is defensible for a settled report you speak to constantly anyway. Going monthly is where they stop working, because a month is long enough for someone to decide to leave before the conversation happens.

Monthly, 60 to 90 minutes: the review. Purpose is looking at results and changing course. Needs enough elapsed time that the numbers have moved.

Quarterly, two to three hours: planning. Purpose is deciding what not to do next quarter. Half a day if the quarter ahead is genuinely contested.

The principle underneath that shape is that a longer gap needs a longer meeting, because more has accumulated to decide. A team running everything weekly has flattened the curve and will feel busy without deciding much.

How to tell a cadence has gone stale

Meetings decay quietly. The signals are consistent:

• The agenda gets written in the meeting. If nobody prepared, ask whether anyone needed it.

• The same people stop talking. Attendance without participation usually means the invite list outgrew the purpose, though a dominant chair will produce the same silence.

• It ends early, repeatedly. Finishing in 20 minutes of a 60-minute slot every week is the calendar telling you the slot is wrong, and possibly the cadence with it.

• Decisions get deferred to a smaller conversation afterwards. The real meeting is happening somewhere else.

• Nobody can say what it decided last time. The most telling of the five, and the one with two possible causes.

That last signal deserves a moment, because the instinct when a team cannot remember what a meeting decided is to meet more often, and that is rarely the fix. Separate the two causes first. If the meeting genuinely decided something and nobody wrote it down, that is a record problem, and a written summary of decisions and owners solves it. If the meeting decided nothing, that is a cadence problem, and the other four signals on this list will be showing too.

Changing a cadence without a fight

Recurring meetings are socially expensive to cancel, which is why so many survive their usefulness. Two things make it easier.

Change the cadence, not the meeting. "Let us move this to fortnightly for a month and see" is a much smaller ask than "should we cancel this", and it usually answers the bigger question anyway. If nobody notices the gap, you have your answer.

Put an end date on new recurring meetings. A meeting created with a review date in eight weeks gets reviewed. A meeting created with no end date gets inherited.

If the meeting is genuinely needed but the attendance is not, the fix is often to keep the cadence and cut the invite list, then send the notes to everyone who used to attend. Most people in a recurring meeting are there for the information, and information does not require attendance.

Cadence and the record

The lower the cadence, the more the record matters. In a daily standup, nobody needs a written record because the next one is tomorrow. In a monthly review, four weeks pass before anyone revisits the decision, and by then memory has done its work.

Practically, that means a meeting running monthly or slower needs a written outcome every time, and a meeting running daily probably does not.

If you already run a notetaker for this, the question worth asking is where the recording goes. Most of them upload the audio and the transcript to the vendor's servers, which is unremarkable for a status meeting and a real problem for a board discussion or a client session. Weeve records the Mac's own audio and writes the transcript and summary on the device, so the record exists and nothing is uploaded. Being straight about the limits: it is Mac only, needs Apple Silicon, and the free Starter plan covers 10 recordings a month. It also produces a summary rather than formal minutes, and if the meeting is a board or a formal committee, minutes are a different document with their own conventions.

FAQ

What is meeting cadence? The frequency at which a recurring meeting happens: daily, weekly, fortnightly, monthly or quarterly. It is set by the meeting's purpose, and specifically by how quickly the subject changes and what it costs to wait for the next one.

How do I choose the right meeting cadence? Ask what the cost of waiting is. If a decision sitting until the next meeting blocks someone for a day, meet more often. If waiting costs nothing, meet less often. Then check whether the meeting is for information, which can be asynchronous, or for decisions, which usually cannot.

What is a good meeting cadence for a small team? A common shape is a daily 15-minute standup for unblocking, a weekly 30 to 60 minute team meeting for decisions, weekly or fortnightly one to ones, a monthly review, and quarterly planning. Treat that as a starting point, not a rule, and drop anything nobody is blocked without.

Is weekly too often for a team meeting? Only if the staleness signals are showing. Weekly is right when decisions genuinely accumulate that fast, and it is the sensible default for most small teams. It is worth questioning when the meeting regularly ends early or has its agenda written in the room, because that is the calendar telling you the subject is not moving weekly. Try fortnightly for a month and see whether anything breaks.

How do I know when a recurring meeting should be cancelled? Watch for the agenda being written during the meeting, the same people never speaking, sessions ending well early, and nobody being able to recall what was decided last time. The last one is often a missing written record rather than a redundant meeting, so check that before cancelling.

What is the difference between meeting cadence and meeting rhythm? They are used interchangeably. Cadence is the more common term in an operations context, and both describe how frequently a recurring meeting occurs.

The right cadence is the slowest one that still beats the cost of waiting.

If the meetings are worth keeping and the record should not leave your machine, Weeve's free Starter plan keeps both on your Mac. If you are not on a Mac, the browser transcriber turns a recording you already have into notes inside the tab.