1:1 Cadence Calculator

← Back to Meeting Tools

Overview

One-on-one meetings are the backbone of effective management. They are where trust is built, feedback is exchanged, career development is discussed, and problems are surfaced before they escalate. But the right frequency varies enormously depending on the situation.

A new junior hire navigating their first professional role needs far more frequent check-ins than a seasoned staff engineer who has been on the team for two years. A manager with three direct reports can afford generous weekly sessions; a manager with thirteen reports needs to be more strategic about how they allocate their time.

This calculator weighs five factors to recommend a cadence and duration that balances the report's needs with the manager's available capacity. The goal is to ensure every report gets the support they need, while keeping the manager's total 1:1 commitment sustainable.

Calculator

More junior team members typically benefit from more frequent check-ins
How many ambiguous decisions, stakeholders, or competing priorities does the role involve?
How much coaching or guidance does this person currently need?
Larger spans constrain how much time you can allocate per report
New relationships benefit from more frequent early investment
Recommended cadence
Weekly
Recommended duration
30 min
Monthly time for this report
2.2 hrs
Total monthly 1:1 time
8.7 hrs
Across all reports at this cadence

How It Works

The calculator scores the report's needs based on four factors (seniority, complexity, support level, and relationship newness), then applies a penalty based on the manager's span of control. Larger spans reduce the score, reflecting the practical reality that managers with many reports cannot meet everyone as frequently.

Base score = seniority + complexity + support level + relationship newness

Span penalty:
1-3 reports: 0 | 4-6 reports: 0 | 7-9 reports: 1 | 10-12 reports: 2 | 13+ reports: 3

Final score = base score - span penalty

14+: Weekly, 45-60 min
10 to 13: Weekly, 30 min
7 to 9: Fortnightly, 45 min
4 to 6: Fortnightly, 30 min
1 to 3: Monthly, 30-45 min

The span penalty is intentionally modest. Even with a large team, a report with performance concerns or a brand new relationship should not be pushed to monthly 1:1s. The penalty nudges the recommendation slightly, but the report's individual needs remain the dominant factor.

The total monthly 1:1 time assumes all reports are on the same cadence and duration. In practice, you will likely have a mix. Use this figure as a rough indicator of your total time commitment.

Example Scenarios

New junior engineer with a supportive manager (3 reports)

Seniority: Junior (5). Complexity: Moderate (2). Support: Developing (3). Span: 1-3 (penalty 0). Relationship: Brand new (4). Score: 14.

Recommendation: Weekly, 45-60 minutes. Monthly time: 3.6 hours for this report. Total across 3 reports: 10.8 hours. A new junior team member needs regular guidance and the small span allows generous time investment.

Experienced senior designer (8 reports)

Seniority: Senior (2). Complexity: Complex (3). Support: Performing well (2). Span: 7-9 (penalty 1). Relationship: Established (1). Score: 7.

Recommendation: Fortnightly, 45 minutes. Monthly time: 1.6 hours for this report. Total across 8 reports: 13.0 hours. An established senior contributor needs less frequent but substantive conversations focused on strategic challenges.

Mid-level PM with performance concerns (6 reports)

Seniority: Mid-level (3). Complexity: Complex (3). Support: Performance concerns (5). Span: 4-6 (penalty 0). Relationship: Getting settled (2). Score: 13.

Recommendation: Weekly, 30 minutes. Monthly time: 2.2 hours for this report. Total across 6 reports: 13.0 hours. Performance concerns warrant weekly check-ins to provide consistent feedback and track progress closely.

Staff engineer, settled relationship (10 reports)

Seniority: Staff+ (1). Complexity: Very complex (4). Support: Thriving (1). Span: 10-12 (penalty 2). Relationship: Established (1). Score: 5.

Recommendation: Fortnightly, 30 minutes. Monthly time: 1.1 hours for this report. Total across 10 reports: 10.8 hours. A thriving staff engineer needs less frequent but focused conversations, and the large span makes this cadence practical.

How to Interpret the Result

The recommendation reflects the minimum cadence to meet this report's likely needs. You can always meet more often if your capacity allows. The key is to avoid meeting less frequently than the recommendation without a deliberate reason.

Consider these adjustments:

The total monthly time figure is worth watching carefully. If your 1:1 time exceeds 15 hours per month, your span of control may be unsustainable. Consider whether the organisation needs to redistribute reports or add a management layer.

Best Practices

Common Mistakes

Related Templates