A Manager’s Guide to Auditing Your Team’s Calendar
You manage five engineers. You want them productive, happy, and doing the work they were hired for.
But you have a nagging suspicion that something is wrong. Sprint velocity keeps missing targets. People seem frazzled. The senior IC you just promoted is spending more time in meetings than writing code.
The calendar holds the answer. Most managers never look.
Here’s how to audit your team’s calendar—what red flags to watch for, what metrics actually matter, and what to do when the numbers confirm your suspicions.
Why Calendar Audits Matter
Calendars are the most accurate record of how time actually gets spent. Not how we intend to spend it. Not how we report spending it. How it actually goes.
For managers, this data is gold:
- It’s objective: No one can argue with meeting hours. The calendar doesn’t lie.
- It’s early warning: Calendar creep happens slowly. By the time someone mentions burnout, they’ve been drowning for months.
- It’s actionable: Unlike vague culture problems, calendar issues have concrete fixes.
Most managers fly blind. They sense something’s off but can’t pinpoint it. A calendar audit gives you specifics.
Getting the Data
Before you audit, you need visibility.
Option 1: Ask Directly
The simplest approach: “Hey team, I’m doing a calendar review to see if we’re protecting enough time for deep work. Can you share your calendar with me for the next two weeks?”
This works but has downsides. People might clean up their calendars before sharing. It’s also a one-time snapshot rather than ongoing visibility.
Option 2: Use Calendar Analytics
Tools like CalWizz aggregate and analyze calendar data automatically, giving you metrics without manual counting. For teams of 5+, this saves hours and provides ongoing monitoring.
Option 3: Team Self-Audit
Give your team a template and have them self-report. “How many hours of meetings did you have last week? How many recurring vs. ad-hoc?”
This works for one-time exercises but relies on people tracking accurately.
The Red Flags
Here’s what to look for when you audit:
Red Flag #1: Meeting Hours Exceed 40% of Work Time
For individual contributors, meetings should typically consume less than 25-30% of their time. For managers, 40-50% is more realistic.
When ICs exceed 40%—meaning 16+ hours per week in meetings—they’re spending more time talking about work than doing it.
Questions to ask:
- Which meetings is this person in? Are all of them necessary?
- Are they attending meetings “in case they’re needed”?
- Are they in meetings that are really for other people?
Red Flag #2: No Blocks Longer Than 90 Minutes
Deep work requires uninterrupted time. Most knowledge work—coding, design, writing—needs at least 90-120 minutes to hit flow state.
If someone’s calendar shows no blocks longer than 90 minutes across multiple days, they’re not doing deep work. They’re in constant context-switching mode.
Questions to ask:
- Are meetings distributed throughout the day or clustered?
- Who is scheduling meetings in the middle of the day?
- Can any meetings be moved to create longer continuous blocks?
Red Flag #3: Excessive Recurring Meetings
Recurring meetings accumulate like barnacles. What started as a weekly sync three years ago is now a fixture nobody questions.
If someone has more than 10 recurring meetings per week, that’s worth investigating. If they have more than 5 recurring meetings with the same team, something is duplicated.
Questions to ask:
- When was this recurring meeting created?
- What’s the stated purpose? Does it still serve that purpose?
- What would happen if we canceled it for two weeks?
Red Flag #4: Meeting Sprawl Across Teams
Your engineer shouldn’t be in meetings with six different cross-functional teams. That pattern suggests either unclear ownership, poor async communication, or a role that’s been silently expanded beyond its scope.
Questions to ask:
- Why is this person the representative for so many groups?
- Can we designate someone else for some of these?
- Should these be async updates instead?
Red Flag #5: Early Morning and Late Evening Meetings
When meetings start at 7:30am or end at 6pm, someone is accommodating too hard. This is especially common for people working with other time zones—or people whose calendars are so packed that early/late is the only availability.
Questions to ask:
- Are time zones forcing these hours?
- Is this person over-committed?
- Can we rethink who attends to free them up?
Red Flag #6: Same Meeting, Multiple Times Per Week
A weekly team sync is normal. The same team meeting three times per week is a sign that scope is unclear, decisions aren’t sticking, or async communication isn’t working.
Questions to ask:
- Why does this need to happen so frequently?
- Are decisions made in these meetings, or just discussed?
- What’s blocking async resolution?
The Metrics That Matter
When you audit, track these:
Total Meeting Hours
Raw count of hours spent in meetings per week. Benchmark:
- IC: under 12 hours ideal, 16+ is a warning sign
- Manager: under 20 hours ideal, 25+ is excessive
Meeting Fragmentation Score
How many separate meetings per day, on average? More granularity = more context-switching.
- 1-3 meetings/day: manageable
- 4-5 meetings/day: fragmented
- 6+ meetings/day: unsustainable
Focus Time Ratio
Hours with no meetings / total work hours. Benchmark:
- IC: should have 60%+ focus time
- Manager: 40%+ is good
Recurring vs. Ad-Hoc Ratio
What percentage of meetings are recurring? If recurring exceeds 70%, you’ve calcified—too much standing process, not enough flexible response to actual needs.
One-on-One Hours (for Managers)
How much time do managers spend in 1:1s? If a manager with 5 reports is spending less than 3 hours/week in 1:1s, they’re under-investing. If they’re spending more than 8, something else is wrong.
Meeting Load Distribution
Is meeting burden evenly distributed, or are some people overloaded? In healthy teams, senior ICs might have slightly more meetings, but not dramatically more.
What to Do With the Data
Data without action is just interesting numbers. Here’s the playbook:
For Individuals Who Are Overloaded
Have a direct conversation: “Your calendar shows 22 hours of meetings last week. That leaves less than half your time for actual work. Let’s figure out which of these we can drop or delegate.”
Give them explicit permission to decline. Help them identify which meetings don’t need them.
For Recurring Meetings That Serve No Purpose
Cancel them for two weeks as an experiment. If nothing breaks, make the cancellation permanent. If something breaks, restart it—but now you know its actual purpose.
For Fragmented Schedules
Work with the team to batch meetings. Cluster all team meetings on the same days. Protect specific days or half-days as meeting-free.
For Excessive Cross-Functional Load
Clarify ownership. If your engineer is in 5 different cross-team meetings, have a conversation about focus: “You can’t be the representative everywhere. Let’s pick the two most important and delegate the rest.”
For Culture Change
If the audit reveals systemic problems—everyone is in too many meetings, nobody has focus time—this isn’t an individual fix. It’s a team discussion.
Share the data with your team. Say: “Here’s what our calendars look like. Is this working?” Let them help design the solution. Cultural change sticks better when it’s collaborative.
Ongoing Monitoring
A one-time audit is useful. Ongoing monitoring is transformative.
Check in quarterly:
- Are meeting hours trending up or down?
- Is focus time improving?
- Are the recurring meetings we eliminated staying eliminated?
Calendars drift back toward chaos unless actively maintained. Make the audit a habit.
Want to audit your team’s calendar without manual spreadsheet work? CalWizz shows you meeting hours, fragmentation, and focus time across your whole team—automatically. See the red flags in minutes, not hours. Try CalWizz free and get the data you need to protect your team’s time.