Meeting Cadence: How Often Your Team Should Actually Meet

Priya runs a nine-person operations team, and on a Sunday evening she finally counts it. Every person on her team sits in 6.5 hours of recurring meetings a week before anyone books a single ad hoc call. Nobody chose that number. It grew one reasonable invite at a time.

If your calendar looks like Priya's, the problem isn't any single meeting. It's the meeting cadence: how often each recurring meeting happens, who's in it, how long it runs and what it produces. Get it wrong and meetings eat the week.

This guide gives you three things for Monday: a meeting cadence map from daily to quarterly, a five-question audit that tells you which meetings to keep, shrink, move to writing, merge or cut, and a short note that lets your team meet less often without losing the thread. If you'd like the notes part handled for you, ParrotNotes records and summarizes in-person meetings free, no meeting bot required.

What is a meeting cadence?

A meeting cadence is the set schedule of a team's recurring meetings: which meetings exist, how often each one happens, who attends and how long it lasts. A daily stand-up, a weekly team meeting and a quarterly review together make up one team's cadence.

Most definitions stop at frequency. Add one more field: output. Every recurring meeting should leave something written behind, such as blockers, a decision or a quarterly plan. A meeting that produces nothing written can usually become a two-minute read.

The stakes are real. In Harvard Business Review's "Stop the Meeting Madness", Leslie Perlow, Constance Noonan Hadley and Eunice Eun report that executives spend nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s.

The meeting cadence map: who meets, how often and what it produces

Use this map as a starting point for a team of 5 to 15 people in the same office or on the same project.

Each row already has an agenda post you can copy. For the weekly slot, use the staff meeting agenda template; for one-on-ones, the one-on-one meeting template. Sales teams can swap in the sales meeting agenda for the weekly row and the sales QBR for the quarterly one.

Two rules sit under the table. The faster a meeting repeats, the shorter it should be. And if nobody can name a meeting's output, it's the first candidate for the audit.

How to choose a meeting cadence for your team

There's no universal right answer to how often a team should meet. Four questions get you close.

1. How fast does the work change? A team shipping something daily needs a daily touchpoint. A team on a six-month contract can meet weekly.
2. How many people depend on each other's work? If three people hand work to each other daily, they need a stand-up. If everyone works on separate accounts, a weekly meeting is enough.
3. Where are decisions made? Meetings earn their slot when a group has to decide something together. Pure information sharing rarely needs a room.
4. What's already written down? A team with good notes and recaps can meet less often, because nobody needs the meeting to find out what happened last time.

Watch for the signs of a cadence that's off. Too many meetings shows up as repeated updates and phones out. Too few shows up as surprise decisions, duplicated work and long email threads.

Structure also matters. Microsoft's WorkLab report Breaking down the infinite workday, based on Microsoft 365 signals, found that 57% of meetings are ad hoc calls without a calendar invite. A clear recurring cadence gives those conversations a home, so fewer of them interrupt the day.

Audit your calendar: keep, shrink, go async, merge or cut

Before you add structure, take some away. List every recurring meeting on the team's calendar and put each one through five questions.

1. Does it produce a written output that someone uses? If not, cut it or turn it into a written update.
2. Does it need a live conversation? Status reports and announcements don't. Move them to a written or recorded update: go async.
3. Is everyone in the room needed for most of it? If half the invitees only speak for five minutes, shrink the invite list or the time box.
4. Does it cover the same ground as another meeting? Two syncs on overlapping projects can merge into one.
5. Would anyone notice if it happened half as often? If a weekly meeting often ends with "nothing new," try every two weeks.

A worked example: Priya's team (illustrative)

Here's the audit on Priya's fictional nine-person team, counted in minutes per team member per week.

That's four hours back per person per week. Across nine people, it's 36 person-hours a week, close to one full-time week of work, without cancelling a single conversation that produced a decision.

Priya's numbers are an illustration, not a study. But the direction matches research. In MIT Sloan Management Review, Ben Laker and colleagues studied 76 companies with more than 1,000 employees each. Nearly half (47%) cut meetings by 40% by introducing two no-meeting days a week, and the best results came at companies with three meeting-free days.

How notes carry context so the cadence can be lighter

Here's the catch. Teams meet often because meetings are where context lives. Cut a meeting without replacing that context and people book ad hoc calls to catch up.

The fix is a short written record that travels from one meeting to the next. Call it a carry-forward note: three lines, written in the last two minutes of every recurring meeting.

Decided: [what the group agreed, in one sentence each]
Owners: [name → action → due date]
Open next time: [the one or two items that carry to the next meeting]

The next meeting opens by reading it. That's what makes a lighter cadence safe.

Tomás, a team lead in a fictional 12-person finance office, moved one-on-ones with his three most senior reports from weekly to every two weeks. He worried he'd lose track of what they'd raised.

So he closed each one-on-one with a carry-forward note and read it back at the start of the next. Six weeks in, nothing had slipped. Each of those reports had an extra hour a month back.

Writing the note by hand works. Recording the meeting is faster. With ParrotNotes, you put a phone on the table and tap record. You get a transcript, a summary and action items, which covers most of the carry-forward note.

Pro adds speaker identification and AI semantic search across your notes, so "what did we decide about the Q3 budget?" finds the right meeting. For formal records, the meeting minutes template and the free meeting minutes generator turn a recording into minutes.

Want every meeting to leave its own notes behind? Try ParrotNotes free with 100 minutes of recording a month and an AI summary on every recording.

Set the new meeting cadence and review it every quarter

Announce the new cadence, run it for a quarter, then check it.

1. Share the map. Send the team the new schedule, with each meeting's length and output.
2. Move the invites in one go. Delete the old recurring invites and create new ones.
3. Put the agenda in the invite. The meeting agenda template has formats you can paste in.
4. Start every meeting with the last carry-forward note. Two minutes, every time.
5. Review after one quarter. Re-run the five-question audit and adjust.

Aiko, a fictional director of a 30-person customer service department, replaced her weekly cross-team status meeting with written recaps from each team lead. She kept a monthly 60-minute business review for decisions.

At the end of the quarter she re-ran the audit. One team needed its weekly meeting back for a busy season, so she added it for eight weeks, then dropped it again. A meeting cadence isn't set once. It's reviewed.

Pick the lighter cadence and let the notes do the remembering

The right meeting cadence is the lightest one that still gets decisions made.

• Give every recurring meeting a cadence, an attendee list, a length and a written output.
• Put each meeting through five questions: keep, shrink, go async, merge or cut.
• Close every meeting with a three-line carry-forward note and open the next by reading it.
• Review the whole cadence once a quarter.

Priya's team got four hours a week back each, on paper, in one evening. If you'd rather not write the carry-forward note by hand, download ParrotNotes, record your next team meeting and read the summary before the next one starts.