Ad Hoc Hours a Week

Last updated: October 27, 2026

Ad Hoc Hours a Week (shown as "Ad-hoc (h/wk)") is the average number of hours per person per working week spent in one-off, non-recurring meetings, not counting interviews.

Why it matters

Ad hoc meetings show how much of a calendar is driven by reactive, unplanned work rather than structured, scheduled time. High or rising ad hoc hours can point to:

  • A reactive work culture: time spent responding to urgent requests rather than planned work.

  • Calendar fragmentation: unplanned meetings break up focus time.

  • Process gaps: unclear decision-making authority, frequent escalations, or decisions that could happen async.

Individuals can compare their hours with their own history and benchmarks, spot spikes, and set boundaries. Teams can set a baseline, investigate spikes around releases or reorgs, agree on norms such as "no more than 3 hours a week", and track the effect of process changes.

How it works

Ad hoc hours a week = (Total ad hoc hours ÷ Active weekdays) × 5

What counts as ad hoc. A calendar event is ad hoc when it:

  • isn't part of a recurring series, and

  • has no Greenhouse, Ashby, or Lever link in its description (those are recruiting meetings).

Size doesn't matter: one-off 1:1s, group meetings, and single meetings booked from a scheduling link all count.

Which events qualify. As with All meeting time, 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 if Span reads that person's own calendar, they didn't mark the event as free, and they didn't decline it.

Steps:

  1. Span sums each person's qualifying ad hoc hours, merging overlapping ad hoc meetings so double-booked time counts once.

  2. It drops weekends and out-of-office days.

  3. It divides by active weekdays (Monday to Friday, not out of office) and multiplies by 5.

Hours count per participant: a 1-hour meeting with 5 people whose calendars Span reads adds 5 hours across the group. Team values pool everyone's hours and active weekdays.

Setup

Connect Google Calendar or Microsoft (Outlook) calendar. Without a calendar integration, the metric isn't available. Viewing calendar metrics needs the Time permission.

Find the metric in Insights → Productivity → Focus time, in the "Ad-hoc (h/wk)" column, on team and person pages, and in custom dashboards. Values show to one decimal place, for example 2.5.

Signals and targets. Span watches meeting load in two ways:

  • High meeting load signal: when a team's total meeting hours over the past 2 weeks run unusually high and at least 10% above its 30-, 60-, or 90-day average, Span shows a signal on the team overview and in the daily brief. The signal shows recent and usual hours per week and breaks the change down by meeting type, including ad hoc. It's based on all meeting time, not ad hoc hours alone, and it isn't a Targets alert.

  • Meeting Time target: in Targets, the Meeting Time target (by default 15 hours per person-week for individual contributors) raises an alert when a person nears the team's target over the past week.

Things to know

  • Worked example: in one week, a person spends 6 hours in one-off meetings and is out of office on Friday. Ad hoc hours = 6 ÷ 4 active weekdays × 5 = 7.5 h/wk.

  • One-off 1:1s are ad hoc: Recurring 1:1s counts only recurring meetings with exactly two invitees.

  • Interviews without an ATS link in the description count as ad hoc.

  • Edited instances stay recurring: changing one instance of a series doesn't make it ad hoc.

  • Excluded: solo blocks, events longer than 4 hours (including all-day events), declined meetings, meetings marked free, tentative or cancelled events, weekends, and out-of-office days.

  • Overlaps across categories: an ad hoc meeting that overlaps a recurring one counts fully in both categories, so category totals can add up to more than All meeting time.

  • Two calendar emails: if Span reads two calendar addresses for the same person, it merges overlaps per address, so a meeting on both calendars can count twice.

Ways to reduce ad hoc hours. Hold office hours for questions, move non-urgent topics to async channels, ask for an agenda and notice, protect focus blocks, set clear escalation paths, and turn ad hoc meetings that happen every week into a scheduled series.

Related articles

Focus Time

Recurring Meetings Hours Per Week

Recruiting Hours a Week

OOO Person-Days

Need help?

Contact your Span account team or reach out to support@span.app.