Meeting too often wastes time. Meeting too rarely lets problems fester. The right cadence depends on several factors: how large your team is, how tightly coupled the work is, how fast things are moving, what phase the project is in, and how effectively your team communicates asynchronously.
This calculator weighs all five of those factors to recommend a meeting frequency and duration that fits your team's actual needs. Rather than guessing or defaulting to "weekly because that is what we have always done," you can make a deliberate, informed choice about how often to bring the team together.
The goal is not to minimise meetings. It is to find the cadence where your team gets enough face time to stay aligned, without burning hours on gatherings that could be replaced by a well-written message or shared document.
Calculator
The number of people who regularly attend this meeting
How much does one person's work depend on another's?
How quickly does the situation change?
Where is the project in its lifecycle?
How effectively does the team communicate outside meetings?
Recommended frequency
Weekly
Recommended duration
45 min
Monthly time investment
3.2 hrs
Score
13
Out of 25
How It Works
The calculator assigns a score to each of the five factors. Larger teams, tighter dependencies, faster pace, active project phases, and lower async maturity all push the score higher, indicating a need for more frequent meetings.
Total score = team size + dependency + urgency + project phase + async maturity
5 to 9: Monthly (90 min) 10 to 13: Fortnightly (60 min) 14 to 17: Weekly (45 min) 18 to 21: Twice weekly (25 min) 22 to 25: Daily (15 min)
Monthly time = frequency per month x duration in minutes / 60
The duration recommendation follows a simple principle: more frequent meetings should be shorter. When you meet daily, 15 minutes is enough to surface blockers and align priorities. When you meet monthly, you need a longer session to cover everything that has happened since the last gathering.
The monthly time investment gives you a single figure to evaluate the total cost of this meeting cadence. If it feels too high, consider improving your async communication to reduce the frequency. If it feels too low, your team may be under-communicating.
Example Scenarios
4-person async-first team
Team size: 4-6 (2). Dependency: Low (2). Urgency: Steady (2). Phase: Steady state (2). Async: Async-first (1). Total: 9.
Recommendation: Monthly, 90 minutes. Monthly time investment: 1.5 hours. This team communicates well asynchronously and only needs a monthly sync to align on the bigger picture.
8-person sprint team
Team size: 7-10 (3). Dependency: High (4). Urgency: Fast-moving (4). Phase: Active development (4). Async: Moderate (3). Total: 18.
Recommendation: Twice weekly, 25 minutes. Monthly time investment: 3.6 hours. High dependency and fast pace mean this team benefits from frequent, short check-ins to stay synchronised.
12-person cross-functional group
Team size: 11-15 (4). Dependency: Moderate (3). Urgency: Moderate (3). Phase: Steady state (2). Async: Some async (4). Total: 16.
Recommendation: Weekly, 45 minutes. Monthly time investment: 3.2 hours. A weekly cadence gives this larger group enough structure to coordinate without overloading calendars.
Startup in launch mode
Team size: 4-6 (2). Dependency: Very high (5). Urgency: Crisis / launch (5). Phase: Active development (4). Async: Low (5). Total: 21.
Recommendation: Twice weekly, 25 minutes. Monthly time investment: 3.6 hours. The intense pace and high interdependence call for frequent alignment, but keeping sessions short prevents meeting fatigue.
How to Interpret the Result
The recommendation is a starting point, not an absolute rule. Use it as a baseline and adjust based on what you observe over a few weeks. If the team consistently finishes early, consider reducing the frequency or duration. If important topics keep getting deferred, you may need to meet more often or extend the session.
Pay attention to these signals:
Meetings feel rushed. You may need longer sessions or more frequent meetings.
Meetings end early with nothing left to discuss. Reduce frequency or shorten the duration.
Surprises keep emerging between meetings. The cadence may be too infrequent for your current pace.
People frequently cancel or skip. The meeting may not be providing enough value at its current frequency.
The same updates are repeated. Consider a written status update to replace the verbal round-robin.
The monthly time investment figure is particularly useful for comparing meeting load across teams. If one team is spending 8 hours per month in a recurring sync while another spends 1.5 hours, that difference should be intentional and justified by the nature of the work.
Best Practices
Re-evaluate frequency quarterly. Project phases change, team composition shifts, and async habits evolve. What worked three months ago may no longer be the right cadence.
Match format to frequency. Daily meetings should be stand-ups with a tight structure. Weekly meetings can be more conversational. Monthly meetings benefit from a prepared agenda with pre-reads.
Invest in async to reduce sync. The strongest lever for reducing meeting frequency is improving your asynchronous communication. Better documentation, clearer written updates, and effective use of collaboration tools all reduce the need to meet.
Separate status from discussion. If most of the meeting is spent sharing updates, move the updates to a written format and reserve the meeting for discussion, decisions, and problem-solving.
Use shorter default durations. A 25-minute meeting forces sharper focus than a 60-minute one. Start shorter and extend only if needed.
Protect maker time. When scheduling recurring meetings, be mindful of how they fragment the working day. A single well-timed meeting is far less disruptive than the same duration scattered across multiple slots.
Common Mistakes
Defaulting to weekly without thinking. Weekly meetings are the most common cadence, but that does not mean they are always the right one. A team with low dependency and strong async habits may be perfectly well served by fortnightly or monthly check-ins.
Never adjusting after the initial setup. Teams often set a meeting cadence when a project starts and never revisit it, even as circumstances change dramatically.
Compensating for poor async with more meetings. If the root cause of miscommunication is unclear written updates or lack of documentation, adding more meetings treats the symptom rather than the cause.
Ignoring team size in duration planning. A 15-minute meeting works for 4 people but becomes impossibly compressed with 12. Larger groups need proportionally longer sessions, or a different format entirely.
Treating all meetings as equal. A planning meeting, a retrospective, and a daily stand-up serve different purposes and should have different frequencies. Do not lump them into a single recurring slot.
Scheduling meetings at the same frequency for every team. Different teams have different needs. A customer support team with real-time dependencies needs a very different cadence from a research team doing independent deep work.