How much meeting time is actually normal?
There are two ways to find out if you have too many meetings. One is to feel vaguely underwater every Thursday and assume it's just you. The other is to compare your week against an actual number. This is the number.
"How much meeting time is normal?" is one of those questions everybody feels and nobody measures. So they guess — usually generously, in their own favour — and carry on. Here are the actual figures for 2025–26, by role and by country, what they mean, and a way to see exactly where your own week lands.
Meeting hours by role
The pattern across every credible dataset is the same: meeting load rises with seniority and with how "connective" your role is. Managers roughly double IC load. Anyone whose job is coordination — product, engineering leadership, people management — sits at the top of their band.
hours / week
Sources: Fellow.ai, Clockwise Engineering Benchmark Report, Reclaim Smart Meetings Report (2024–25). Figures rounded.
~8 h
Typical IC — about a fifth of the work week
~16 h
Typical manager — roughly double an IC
19+ h
Typical executive — close to half the week
Two caveats worth stating plainly, because most "meeting statistics" posts don't. First, these are averages blended across industries and company sizes — your function and your company's culture move the number more than your job title does. Second, the engineering figures run higher than the cross-industry average for the same level, because technical and product roles attract standing syncs the way low ground attracts water. Product managers in particular hold the longest meetings — over an hour each, on average.
Why product and people-leaders run hottest
If you're a PM, an EM, or anyone whose job is the seam between teams, your calendar is doing exactly what the role demands: every seam between functions tends to become a recurring meeting. Eng-design sync, the stakeholder check-in, the leadership update, the customer call. None is unreasonable on its own. Together they're the "coordination tax," and it's the single biggest reason connective roles blow past their benchmark.
That's not a reason to feel bad about your number — it's a reason to look at it. The benchmark tells you whether you're carrying a normal coordination load or quietly drowning in one nobody decided to give you.
Meeting hours by country
Meeting culture is national as much as it is personal. Here's where it gets interesting if you work in the German-speaking world: the data on wasted meeting time — hours lost specifically to poorly-organised meetings — puts Germany near the top.
wasted hours / week
Source: 2024 cross-country meeting survey data (Flowtrace / industry aggregate).
German professionals lose 8.8 hours a week to badly-run meetings — more than double the UK's 4.1 and well above the US's 5.2. And it's not apathy: 74% of German professionals say they regularly lose time to poorly-organised meetings, and 65% say they play an active role in the meetings they attend (versus ~50% in the US and UK). Germans are more engaged in their meetings — which is exactly why the wasted ones sting more.
More involved in meetings, more frustrated by the bad ones. Awareness isn't the problem here — visibility is.
So… is your number too high?
Here's the honest answer: there's no universal "too many." A founder doing 25 hours of customer calls a week might be doing exactly the right thing. An IC engineer at 18 hours almost certainly isn't. The benchmark isn't a verdict — it's a mirror. What matters is the gap between your number and what your job actually needs.
A rough way to read your own figure against these benchmarks:
- At or below your role's benchmark — you're normal. If you still feel underwater, the problem is meeting quality or fragmentation, not volume.
- 1.5× your benchmark — worth auditing. Find the recurring meetings nobody would miss.
- 2×+ your benchmark — something's wrong with how your calendar gets filled, and no amount of "being more productive" fixes it. This is a cut-meetings problem, not a time-management one.
How to see where you actually land
You can't manage what you don't measure, and almost nobody measures their own meeting load — they estimate it, badly. Meetwrap reads your work Google Calendar and hands you the real figure: hours per week, how many are recurring, which standing meeting has happened dozens of times without anyone skipping it, and what it all costs. You see your number against the only benchmark that matters — last week's you.
It's free, it takes about thirty seconds, and it's read-only: your calendar is read in your browser to build the wrap, and the meeting titles and attendee names never reach a server.
If you want the cost side of this, see what your meetings actually cost. If your number's high because of meetings you don't control, here's how to make the case to your manager.