Meeting Cadence: How Often Each Meeting Should Happen

Geometric markers connected in a recurring rhythm

A meeting cadence is the recurring rhythm of your meetings: how often each one happens, how long it runs, who attends and what it is for. The right cadence is set meeting by meeting, not once for the whole team. A short daily check for blockers, a weekly meeting for decisions, a monthly review of resources and a quarterly session on direction will cover most small and mid-sized businesses.

This guide shows you how to build that rhythm, what to put on the agenda of each meeting, and how to stop it turning into a calendar full of recurring invitations nobody questions.

Strategic-concierge

Build a More Capable Business

Strategic Concierge helps businesses build, improve and embed the capability to support practical growth and long-term progress.

Explore Strategic Concierge

TL;DR

Match each meeting to one job: triage (daily), diagnosis and action (weekly), resource decisions (monthly) and direction (quarterly).
Keep operational meetings separate from strategic ones, so urgent issues do not crowd out the long-term questions.
Give every meeting a purpose, an expected outcome and a time-boxed plan, and check regularly whether attendees feel their time was well spent.
Review the cadence itself every quarter. Cut, merge or move any meeting that no longer earns its slot.
Write the rhythm down, so the business does not depend on the founder remembering what happens when.

What a meeting cadence actually is
The four horizons: daily, weekly, monthly, quarterly
Keep operational and strategic meetings apart
One-to-ones and team meetings
How to build your cadence in five steps
Make each meeting worth attending
Why a rhythm matters more in small businesses
Our perspective: cadence is a capability, not a calendar
Common mistakes to avoid
Where we can help
FAQ
Sources

What a meeting cadence actually is

People often use “meeting cadence”, “operating cadence” and “management cadence” as if they were different things. In practice they describe the same idea at slightly different scales. Atlassian defines meeting cadence as the predictable, recurring rhythm of meetings, covering frequency, schedule, duration, participants and purpose, designed to keep people aligned, surface problems early and maintain momentum.

An operating cadence is that rhythm applied to running the business: the set of reviews and decisions that connects daily work to quarterly goals. A management cadence is the part of it owned by the leadership team. If you run a company of five or fifty people, you need one coherent system, not three.

The word that matters most is predictable. A cadence works because people know when a topic will be discussed, so they stop raising it by email at 9pm or in a corridor. A meeting that is held at random intervals is just a meeting.

The four horizons: daily, weekly, monthly, quarterly

The most common structure runs at four horizons. The durations below come from Atlassian’s guidance on meeting cadence, and they are a sensible starting point rather than a rule.

Horizon	Typical length	Job of the meeting	Typical output
Daily	About 15 minutes	Triage: what is stuck, what changed since yesterday	Blockers named with an owner
Weekly	60 to 90 minutes	Diagnosis and action: what the numbers say and what we do about it	Decisions and assigned actions
Monthly	Up to 3 hours	Reallocate resources: where time, budget and people should move	Revised priorities and budget shifts
Quarterly	Half to full day	Reset strategy: are we still pointed the right way	Next quarter’s goals and the plan to reach them

Notice that each row has a different job. The common failure is holding four meetings that all try to do the same thing: a status update. If you can swap the agendas of two meetings and nobody notices, one of them should go.

Daily: a short check for blockers

A daily meeting is for surfacing what is stuck, not for reporting on everything that happened. Keep it to about 15 minutes and keep it standing, literally or figuratively. Each person answers three things: what moves today, what is blocked, and who needs to help.

You may not need this daily at all. For a founder-led firm of six where everyone sits within earshot or on the same chat channel, a daily check can be a short message thread. Use a live meeting only for the teams who rely on each other’s output every day, such as delivery, client service or sales operations.

Weekly: where decisions get made

Weekly: where decisions get made — overview diagram

The weekly leadership meeting is the engine of the cadence. If you only fix one meeting, fix this one. It should review a small, fixed set of numbers, deal with the issues those numbers reveal, and finish with actions that have a name and a date against them.

A workable agenda for a 60 to 90 minute weekly leadership meeting:

Check-in (5 minutes). Anything people will be unavailable for, plus one line each on how the week looks.
Scorecard (10 minutes). Five to eight numbers, reviewed as on or off track. No explanations yet.
Actions from last week (10 minutes). Done or not done. Do not re-discuss completed items.
Issues (30 to 45 minutes). Pick the two or three that matter most, and discuss each until a decision or an owner exists.
Wrap-up (5 minutes). Read back the actions and decide what, if anything, needs to be communicated to the wider team.

The scorecard depends on your business. A recruitment firm might track live roles, submissions, interviews and placements. A consultancy might track pipeline, utilisation and invoices outstanding. The point is to choose the numbers once and keep them stable, so trends are visible.

Monthly: moving resources, not repeating the week

The monthly meeting looks at a longer window than the weekly and asks different questions. Which initiatives are paying back? Which clients or channels deserve more of your time? Where is the budget going and does it match the plan? Up to three hours is reasonable for a full review, but a small business can often do it in half that if the numbers are prepared in advance.

Preparation is the difference. Circulate the figures a day before, so the meeting is for decisions and not for reading a spreadsheet aloud.

Quarterly: direction and the next ninety days

The quarterly session is the one most small businesses skip, and the one that most affects the following twelve months. Spend a half day to a full day on three questions: what did we say we would achieve and what happened; what has changed in our market or our clients; and what are the three to five things we will do in the next quarter.

Hold it away from the daily noise if you can, and treat the output as a short written plan that the weekly meeting then tracks. A quarterly operating cadence is simply this session plus the weekly and monthly meetings that follow its priorities.

Keep operational and strategic meetings apart

A useful rule from leadership meeting guidance: hold operational meetings frequently, weekly at a minimum, and strategic meetings periodically, quarterly at a minimum. The reasoning is practical. Urgent operational issues always win when they share a room with long-term questions, so strategy gets pushed to “next time” indefinitely.

If your weekly meeting regularly runs over because strategic topics keep appearing, park them. Keep a running list and take it to the monthly or quarterly session. If a topic cannot wait, schedule a separate decision meeting with the right people and a clear question to answer.

One-to-ones and team meetings

The leadership cadence is only part of the picture. Two other layers matter.

One-to-ones. Research summarised in Steven Rogelberg’s work suggests a weekly or every-other-week rhythm works best, because longer gaps make feedback less timely. The same source notes that one-to-ones are more effective when the direct report builds the agenda, and suggests giving one meeting in every four to longer-term, non-tactical topics such as development and career. Otherwise the rhythm becomes reactive and stale.

Team meetings. A weekly team meeting with direct reports, plus a company-wide update at whatever interval suits your size, is enough for most firms. For a business under about twenty people, a monthly all-hands of 30 to 45 minutes covering results, priorities and one deeper topic is usually sufficient. Larger or distributed teams may need it more often.

One-to-ones and team meetings — overview diagram

Rogelberg also points out that meetings held less often than every two weeks tend to suffer from recency bias: people discuss only what happened lately, not the whole period. That is a reason to keep the weekly and fortnightly layers in place even when the monthly review feels like it covers the same ground.

How to build your cadence in five steps

List every recurring meeting you have now. Include one-to-ones, client meetings and the “quick sync” that has been running for a year. Note the length, attendees and who actually speaks.
Write one sentence of purpose for each. If you cannot state what decision or output the meeting produces, mark it for removal or merging.
Assign each to a horizon. Daily, weekly, monthly or quarterly. Check that each horizon has at least one meeting with a distinct job.
Set the agenda template and the numbers. Use the same agenda every time, with a fixed scorecard for the weekly and monthly meetings.
Run it for a quarter, then review it. Ask attendees which meetings were worth their time, and change the cadence on the evidence.

The review matters because there is a trap in over-engineering. A study on decision-making meetings, published in 2024, looked at whether scheduling matters and found that unscheduled, focused decision meetings can be more efficient in some real-world situations. Pre-set agendas can lead participants to form fixed opinions in advance. The lesson is not to drop the rhythm. It is to keep your core cadence for recurring operational work and leave room for short, ad hoc decision meetings when a specific choice cannot wait.

Make each meeting worth attending

The CIPD’s evidence review on productive meetings is the most useful UK reference on this. It finds that whether attendees feel their time was well spent is a main predictor of how satisfied they are with a meeting. It also points to agendas that set out specific outcomes and time-boxed tasks as a route to better meetings, and reports that senior executives see about a third of their meeting time as unproductive.

The review recommends the POP framework: Purpose, Outcomes and Plan. Before each meeting, write one line for each:

Purpose: why are we meeting?
Outcomes: what will be decided or produced by the end?
Plan: who covers what, in what order, for how long?

It also suggests that a good share of the effort belongs outside the room, in preparation and follow-up, rather than in the meeting itself. If your actions are not written down and sent within a day, the meeting has not finished.

Why a rhythm matters more in small businesses

In a small firm, the founder is usually the cadence. Priorities sit in their head, decisions wait for their availability, and when they are away the rhythm stops. A piece on UK SME process overhauls describes how founders who document their systems, including a weekly rhythm for something as ordinary as invoicing, stop being the bottleneck and can spend time on growth instead of day-to-day operations.

There is also a customer-facing benefit. Research on UK SMEs found that a formal meeting cadence creates a forum for cross-functional communication and, for many firms, becomes the main way a culture of customer service and continuous improvement is built. Reviewing client feedback and delivery quality at a fixed point each week or month is how it stops being an intention.

Our perspective: cadence is a capability, not a calendar

We see meeting cadence as one of the clearest signs of whether a business has capability or only effort. Plenty of firms have busy diaries. Fewer can say what each meeting decides, who owns the outputs, and what changes as a result.

Our approach to working with businesses is staged: Build, Iterate, Optimise, Embed, Grow. Cadence fits that sequence naturally. You do not need a full operating rhythm on day one. You need a launch-ready foundation first: a clear direction and a short list of numbers that matter. Then the weekly meeting can be built around them, tested for a few cycles, tightened, and finally embedded so it runs without outside help.

Three things we would tell any owner:

Start with the decision, not the meeting. If a decision recurs weekly, it needs a weekly home. If it recurs quarterly, it needs a quarterly one. Our guide to capability mapping around one decision takes this approach.
Alignment before efficiency. A fast meeting that is aligned on the wrong thing is still wrong. We make the same argument for commercial teams in our RevOps strategy guide.
Design it so the founder can step out. For founder-led firms, the test of a cadence is whether it runs when the founder is not in the room. We cover this for recruitment businesses.

A cadence is not finished when the invitations are sent. It is finished when the team would notice, and object, if a meeting were cancelled.

— Chris

Common mistakes to avoid

Recurring meetings with no end date. Set a review date for every new recurring meeting. If it has not earned its place at that point, stop it.
Status updates in the room. Anything that can be read should be circulated beforehand. Use meeting time for discussion and decisions.
Too many attendees. If someone only listens, send them the notes instead.
Everything at one frequency. A weekly meeting that tries to cover strategy, operations and people will do none of them well.
No owner for the cadence. Someone, often an operations lead or the managing director, should own the calendar and the agendas.
Copying a template unchanged. A template from a large technology company will not suit a ten-person professional services firm. Adapt the length and frequency to your size.

Where we can help

If you want a cadence designed around your own numbers and decisions, our Foundation stage is built to give you a launch-ready base in one month, and you can read how we deliver it in four weeks. For ongoing support, Managed Capability is priced at £999 per month, £2,850 per quarter or £10,000 per year, and you can see the full options on our pricing page. If you would rather talk it through first, you can book a discovery call.

FAQ

What is the definition of meeting cadence?

Meeting cadence is the predictable, recurring rhythm of an organisation’s meetings. It covers how often each meeting happens, when, for how long, who attends and what it is for. The aim is to keep people aligned, bring problems up early and maintain momentum.

How often should a leadership team meet?

Most leadership teams meet weekly for operational matters, monthly for resource and performance review, and quarterly for strategy. A weekly meeting of 60 to 90 minutes is the usual core. Add a short daily check only if your team depends on each other’s work every day.

What should a weekly leadership meeting agenda include?

Include a short check-in, a review of five to eight fixed numbers, last week’s actions, two or three priority issues, and a wrap-up that confirms owners and deadlines. Keep strategic topics for the monthly or quarterly session. Use the same structure each week so people can prepare.

What is the difference between meeting cadence and operating cadence?

Meeting cadence is the rhythm of the meetings themselves. Operating cadence applies that rhythm to running the business, linking meetings, reviews, reports and decisions to goals. For a small business the two are effectively one system.

How do I know if my cadence is working?

Ask attendees whether they feel their time was well spent, because the CIPD identifies this as a key driver of meeting satisfaction. Also check whether decisions are being made, actions completed and fewer issues arriving outside meetings. If not, cut or reshape the meeting.