Recurring Meetings Hours Per Week
Last updated: October 27, 2026
Span reports the average hours per person per working week spent in recurring meetings, split by size: Recurring 1:1s, Recurring 3-7, and Recurring 8+.
Why it matters
Recurring meetings are the fixed cost on every calendar. Splitting them by size shows where that cost goes: regular 1:1s with managers, standups and team syncs, or large all-hands and town halls. Use the breakdown to spot calendar overload, find series that no longer earn their slot, and decide which large meetings could become async updates. Very low meeting load can also signal isolation, so look for balance rather than zero.
How it works
Hours per week = (Total hours in the meeting category ÷ Active weekdays) × 5Category | Rule | Column on the Focus time page |
|---|---|---|
Recurring 1:1s | Part of a recurring series with exactly 2 invitees | Recurring 1:1s (h/wk) |
Recurring 3-7 | Part of a recurring series with 3 to 7 invitees | Recurring 3-7 ppl (h/wk) |
Recurring 8+ | Part of a recurring series with 8 or more invitees | Recurring 8+ ppl (h/wk) |
Size comes from the invite list. Span counts every invitee with a valid email, including people who declined. A series with 0 or 1 invitee never qualifies as a meeting, so it adds no hours.
Which events qualify. An event counts only if it's confirmed (not tentative or cancelled), lasts 4 hours or less, and has more than one invitee who hasn't declined. A person's time counts when Span reads their own calendar, they didn't mark it as free, and, as a required invitee, they didn't decline, or, as an optional invitee, they accepted.
Steps:
Span classifies each event. Recurring means the event belongs to a series; editing one instance doesn't change that.
For each person, it merges overlapping meetings in the same category, splits them into days in the person's calendar time zone, and drops weekends and out-of-office days.
It divides by active weekdays (Monday to Friday, not out of office) and multiplies by 5. Values show to one decimal place, for example 2.5 h/wk.
Team values pool every member's hours and active weekdays.
Setup
Connect Google Calendar or Microsoft (Outlook) calendar. Calendar integration is required for these metrics. Choose the out-of-office source in Settings → Org Calendar → Out of Office Days Source.
Find the metrics in Insights → Productivity → Focus time, on team and person pages, and in custom dashboards. Filter by attendee range, IC level, job title, team, and time period, and compare with a previous period. Benchmarks show percentile ranks within your organization.
Targets and signals. In Targets, the Meeting Time target (by default 15 hours per person-week for individual contributors) alerts when a person nears the team's target. Separately, the High meeting load signal flags a team whose total meeting hours over the past 2 weeks run at least 10% above its 30-, 60-, or 90-day average, with a breakdown by meeting type.
Things to know
Worked example: someone spends 4 hours in recurring 1:1s over 4 active weekdays (one day out of office). Recurring 1:1s = 4 ÷ 4 × 5 = 5.0 h/wk.
One-off 1:1s aren't here: a non-recurring meeting between two people counts as Ad-hoc.
A declined 1:1 instance doesn't count for anyone: if your manager declines one instance, it has only one non-declining invitee, so it doesn't qualify.
Declined invitees still set the size: a 9-person invite where 3 people decline stays in Recurring 8+.
Extra invitees change the category: the same person invited at two email addresses, or, on Google Calendar, a booked meeting room on the invite, can add an invitee and move a 1:1 into Recurring 3-7. Microsoft (Outlook) meeting rooms aren't counted as invitees.
Excluded meetings: events over 4 hours (including all-day events and offsites), solo blocks, declined meetings, meetings marked free, tentative or cancelled events, weekends, and out-of-office days. You can't exclude other specific meetings.
Why totals don't match your calendar: Span uses a 5-day weekly rate, leaves out out-of-office days, merges overlapping meetings, and drops the excluded events above.
Categories can add up to more than All meeting time: each category merges overlaps only within itself.
Two calendar emails for one person: Span merges overlaps per address, so a meeting on both calendars can count twice.
Good practice. Review meeting load monthly, compare similar roles and teams, and use the numbers in retrospectives to consolidate redundant meetings, add no-meeting blocks, decline non-essential series, and move updates to async.
Related articles
Need help?
Contact your Span account team or reach out to support@span.app.