Almost every guide to meeting cadence hands you the same four intervals: daily standup, weekly sync, monthly review, quarterly planning. That list is not wrong, it is just not a cadence. It is a menu. Teams pick from it, put the slots in the calendar, and six months later half those slots have quietly turned into status readouts that a written update would have covered in four minutes.
The cadence that survives contact with a real quarter is built backwards. You start from the decisions your team has to make, work out how fast the information behind each decision changes, and only then pick an interval. Frequency is the output of that reasoning, never the input.
A cadence is a decision schedule, not a meeting schedule. Every recurring slot should exist to make one named type of decision. If nothing gets decided, the slot is a newsletter with worse formatting.
Match the interval to the clock speed of the information. A number that moves daily needs a daily look. A number that moves quarterly does not need a weekly meeting attached to it.
Cadences fail by decay, not by design. Fortnightly slots stretch to six weeks, one-hour slots stay one hour after the agenda shrinks, and new meetings get added without anything being removed.
Budget the hours before you fill them. Decide what share of the week the team can spend in recurring meetings, then fit the cadence inside that number.
Put a review date on the cadence itself. A cadence nobody re-examines is just an old decision that keeps charging rent.
What a meeting cadence is
A meeting cadence is the fixed pattern of recurring meetings a team holds: which meetings exist, who attends each one, how often they repeat, and how long they run. It is the standing structure of the team's week and quarter, separate from the ad-hoc meetings that get booked as work comes up.
The word carries a second, more useful meaning in practice. A cadence is also a promise about waiting time. If the team knows a decision of a certain kind gets made every Tuesday, nobody has to call an emergency meeting to make it on Thursday. The interval sets the maximum time anything has to sit before it gets addressed, which is why an under-designed cadence produces the exact thing it was meant to prevent: a calendar full of urgent one-off calls.
Tip: Write the maximum acceptable waiting time next to each recurring slot before you choose its frequency. "Blockers cannot wait more than a day" gives you daily. "Roadmap trade-offs can wait two weeks" gives you fortnightly. The interval then argues for itself.
Why most cadences drift
Three failure modes account for nearly every broken cadence, and none of them is about picking the wrong starting frequency.
Decay through rescheduling. A fortnightly slot is fragile in a way a weekly one is not. In a r/DevManagers thread on whether managers need one-to-one meetings with every report, the recurring complaint about fortnightly one-to-ones is arithmetic rather than philosophical: one holiday, one conflict, and the gap between two conversations stretches to four or six weeks without anyone deciding it should. Weekly slots absorb a cancellation. Fortnightly ones do not.
Shortening instead of removing. The instinct when meeting load hurts is to cut every meeting from 60 minutes to 30. A r/productivity thread on cutting a team's weekly meeting time from six hours to 90 minutes describes the outcome most teams get from that move: the meetings simply felt rushed, and the relief only arrived once the number of meetings came down rather than their length. Eight rushed meetings cost more attention than four unhurried ones, because each one carries its own context switch.
Everyone in every room. A six-comment thread in r/changemanagement about meeting cadence lands on the split that works: the core team meets weekly, the wider stakeholder group monthly or less. Cadences bloat when a meeting that needs four people keeps a standing invite list of twelve, because the frequency that suits the four is unbearable for the other eight.
Careful: A slot that gets cancelled twice in a month is not a scheduling problem. It is the team voting on the interval. Change the frequency rather than defending the booking.
The cost is not abstract. Harvard Business Review's research on meeting load put executives at nearly 23 hours a week in meetings, against under 10 hours in the 1960s. A thread in r/managers with 80-plus comments on surviving back-to-back meetings is what that looks like from inside a calendar.
How to set a meeting cadence in five steps
Step 1: Audit what you already run
You cannot design a cadence on top of an unknown one. Export the last four weeks of the team calendar, filter to recurring events only, and total the hours per person per week. Most teams are surprised twice: by the total, and by how many of the slots nobody remembers agreeing to.
30-minute cadence audit
Step 2: Sort every slot by the decision it makes
Give each surviving meeting exactly one decision type. Coordination decisions settle who does what next. Progress decisions settle whether to continue, change or stop. Direction decisions settle what the team is aiming at. Relationship conversations are not decisions at all, and they need their own slot rather than a tail end of someone else's.
A meeting that carries two decision types will reliably serve one and starve the other, usually starving the slower one, because the urgent coordination item always speaks first.
Step 3: Match the interval to the information's clock speed
Now the frequency question answers itself. Ask how often the underlying information changes enough to alter the decision, and set the interval to that.
| Decision type | Information changes | Interval | Length | Who attends |
|---|---|---|---|---|
Coordination (who does what next) | Daily | Daily or 3x weekly | 10 to 15 min | Doers only |
Decision typeCoordination (who does what next) Information changesDaily IntervalDaily or 3x weekly Length10 to 15 min Who attendsDoers only | ||||
Progress (continue, change, stop) | Weekly | Weekly | 30 to 45 min | Team plus owner |
Decision typeProgress (continue, change, stop) Information changesWeekly IntervalWeekly Length30 to 45 min Who attendsTeam plus owner | ||||
Direction (what we are aiming at) | Monthly | Monthly | 60 min | Owners plus leadership |
Decision typeDirection (what we are aiming at) Information changesMonthly IntervalMonthly Length60 min Who attendsOwners plus leadership | ||||
Strategy (what we stop doing) | Quarterly | Quarterly | Half day | Leadership plus team leads |
Decision typeStrategy (what we stop doing) Information changesQuarterly IntervalQuarterly LengthHalf day Who attendsLeadership plus team leads | ||||
Relationship (how the person is doing) | Continuous | Weekly, 30 min | 30 min | Manager plus one report |
Decision typeRelationship (how the person is doing) Information changesContinuous IntervalWeekly, 30 min Length30 min Who attendsManager plus one report | ||||
Careful: Weekly one-to-ones look expensive next to fortnightly ones and are not. A 30-minute weekly conversation costs 26 hours a year and survives holidays. The fortnightly version costs 13 hours a year and quietly becomes monthly.
Step 4: Give every slot an agenda it cannot drift out of
A recurring meeting without a fixed skeleton reverts to status reporting within about a month, because status is the easiest thing to talk about. Fix the skeleton once and reuse it. Paste these into the calendar invite description so the agenda arrives with the meeting rather than in a separate document nobody opens. Our collection of meeting agenda templates covers more meeting types than the three here.
Weekly team sync, 30 minutes:
1. Metrics that moved (5 min): numbers only, no narration
2. Blockers needing a decision today (10 min): one line each, owner named
3. Decisions made last week and what happened (5 min)
4. Next week's single priority per person (10 min)
Not on this agenda: status updates (written, posted Monday 09:00),
anything affecting fewer than half the people in the room.
Monthly review, 60 minutes:
1. Targets vs actuals, month and quarter to date (10 min)
2. What we said we would do last month, and did we (10 min)
3. One thing to stop doing (15 min): this slot is mandatory
4. Risks that need a decision above this room (10 min)
5. Priorities for next month, max three (15 min)
Weekly one-to-one, 30 minutes:
Report's agenda first (15 min): they write it, they open
Manager's items (10 min): feedback, context, decisions needed
Career and workload check (5 min): asked every week, even briefly
Never used for: project status, which belongs in the team sync.
Step 5: Put a review date on the cadence
Book a 45-minute cadence review for the end of the quarter, on the calendar, now. Re-run the Step 1 audit, and hold every slot to a single test: name a decision it produced in the last eight weeks. Slots that fail get deleted or downgraded to a written update, or handed to meeting minutes software so the record survives without the room. Without this date the cadence only ever accumulates, because adding a meeting takes one invite and removing one takes a conversation.
Cadence patterns by team shape
The same five steps produce different answers depending on how the team is arranged. These are starting points to adapt, not prescriptions.
| Team shape | Daily | Weekly | Monthly | Quarterly | Recurring hours/person/week |
|---|---|---|---|---|---|
Founding team, 3 to 6 people | None, you already talk | One 45-min sync | One 60-min review | Half-day planning | ~1.5 |
Team shapeFounding team, 3 to 6 people DailyNone, you already talk WeeklyOne 45-min sync MonthlyOne 60-min review QuarterlyHalf-day planning Recurring hours/person/week~1.5 | |||||
Single team, 7 to 12 | 10-min standup | 30-min sync plus 30-min 1:1 | 60-min review | Half-day planning | ~2.5 |
Team shapeSingle team, 7 to 12 Daily10-min standup Weekly30-min sync plus 30-min 1:1 Monthly60-min review QuarterlyHalf-day planning Recurring hours/person/week~2.5 | |||||
Distributed across time zones | Written daily update | 45-min sync in the overlap window | 60-min review, recorded | Full-day offsite | ~2 |
Team shapeDistributed across time zones DailyWritten daily update Weekly45-min sync in the overlap window Monthly60-min review, recorded QuarterlyFull-day offsite Recurring hours/person/week~2 | |||||
Department, 20-plus | Standup per sub-team | Sub-team sync plus leads sync | All-hands, 45 min | Half-day per sub-team | ~3 |
Team shapeDepartment, 20-plus DailyStandup per sub-team WeeklySub-team sync plus leads sync MonthlyAll-hands, 45 min QuarterlyHalf-day per sub-team Recurring hours/person/week~3 | |||||
Tip: The right-hand column is the number to defend. If a proposed new meeting pushes the team past its budget, something existing has to leave the calendar in the same conversation.
One-off meetings sit outside all of this. When a topic genuinely needs people who do not share a standing slot, an appointment poll finds the time in one round instead of adding a permanent entry to the cadence, and a clear meeting request email does the rest.
Distributed teams need one extra rule. Anything a time zone cannot attend live has to exist as a written artefact within a day, or the cadence silently splits into a core group that was in the room and a periphery that reads about it later.
Tools that hold a cadence together
The calendar app you already use handles the recurring slots themselves. What breaks a cadence is everything around the slot: whether the written update actually gets written, whether decisions survive the meeting, and whether people outside the team can reach it without a booking negotiation.
meetergo covers the parts of that with a scheduling and pipeline job attached. Automated workflows send the pre-read and the agenda reminder on a schedule instead of relying on someone remembering, and the unified calendar view shows the team's real recurring load across connected Google, Outlook and Apple calendars, which is the number Step 1 asks for. For recurring sessions that involve people outside the company, such as a standing client check-in, recurring bookings let the other side book the series once rather than one slot at a time, and meetergo connect runs the video call in the browser without a separate Zoom or Teams licence. A shared team page gives the whole group one address for that, rather than one link per person.
The written record is the other half. meetergo Log transcribes meetings locally on the device, so the decision from Tuesday exists in text before the next sync, which is what stops a meeting from repeating itself. Because the transcription runs on the machine rather than on a US cloud service, it also avoids the GDPR problem that most AI meeting note tools carry. meetergo is a German company with EU servers and no US parent, so recordings of an internal strategy meeting stay under EU law.
The honest limitation: meetergo will not police your agenda, count your meeting hours for you or tell you a slot has gone stale. It is a booking and click-to-contract pipeline, not a meeting-management product. The audit in Step 1 and the review in Step 5 are manual work, and no tool removes them. If your problem is purely internal recurring meetings with no external attendees and no record-keeping need, your calendar app plus a shared doc is enough.
Give every recurring meeting a written record.
Give every recurring meeting a written record.
Common mistakes
- Booking the cadence before naming the decisions. The calendar fills, the reasoning never happens, and every slot becomes negotiable within a quarter.
- Treating meeting length as the lever. Halving durations keeps the context switches and removes the slack that made the meeting bearable. Remove meetings, then shorten what remains.
- Letting the invite list grow by default. Attendance should be argued for each time the meeting's purpose changes. A standing invite is not evidence that someone needs to be there.
- Running one-to-ones fortnightly. The interval looks efficient and decays into monthly the first time anyone takes a holiday.
- Scheduling recurring meetings across the middle of the day. Two meetings at 11:00 and 14:00 destroy more focus time than four consecutive slots in one morning block. Cluster them.
- Never scheduling the meeting about the meetings. Without a booked review date, the cadence only grows.
FAQ
What does meeting cadence mean?
Meeting cadence means the fixed pattern of a team's recurring meetings: which ones exist, who is in them, how often they repeat and how long they last. It describes the standing rhythm of the week and quarter, as opposed to meetings booked ad hoc when work demands them.
How often should a team meeting be?
Set the interval by how fast the information behind the decision changes. Coordination that shifts daily needs a short daily or three-times-weekly slot. Progress reviews suit weekly. Direction-setting suits monthly, and strategy suits quarterly. Frequency should follow the decision, not the calendar's convenience.
What is a good meeting cadence for a remote team?
Distributed teams work best with fewer live meetings and a firm written layer underneath. Keep one weekly live sync inside the time-zone overlap, replace the daily standup with a written update, record the monthly review, and require that anything decided live is written up within a day so people outside the room are not second-class.
How many hours a week should a team spend in meetings?
Set a budget rather than a rule. Individual contributors generally hold quality at two to three hours of recurring meetings a week, managers at five to eight. The number matters less than defending it: once a budget exists, a new meeting has to displace an old one instead of being added silently.
How do I cut meetings without losing alignment?
Downgrade before you delete. Move status reporting to a written update, keep only the decision portion live, and shorten the invite list to the people who make that decision. Alignment is lost when information stops flowing, not when a calendar slot disappears, so replace the flow first and remove the slot second.
Should one-to-ones be weekly or fortnightly?
Weekly, at 30 minutes, for most managers with fewer than eight reports. Fortnightly slots survive on paper and not in practice: a single holiday or conflict stretches the real gap to four to six weeks, which is long enough for a workload or morale problem to become a resignation.
