We are not going to tell you what share of your team’s week goes to meetings. Nobody outside your calendar can say that honestly, and every industry average you have read was calculated on a sample that did not include your team.
So here is the alternative. Count it yourself, in three passes over the same calendar: log it, cost it, score it. Four weeks of data, one spreadsheet, and a list at the end with a disposition written next to every recurring meeting you own.
Most meeting audits hand you a tracker. This one hands you a name. The third table assigns each meeting a disposition, and one of those dispositions points straight at a manager’s decision habit rather than at a scheduling pattern.
Written for HR and L&D leaders, and for any manager who owns a team’s calendar.
Why counting beats estimating
Two numbers are worth knowing before you start, mostly so you stop reaching for them.
Leslie Perlow, Constance Noonan Hadley and Eunice Eun, writing in Harvard Business Review in 2017, put the executive meeting load at nearly 23 hours a week. Steven Rogelberg, a UNC Charlotte professor and the author of The Surprising Science of Meetings, has a name for the drag that follows a bad one. He calls it a meeting hangover, and UNC Charlotte reported in 2025 that about 90% of workers in the US and UK get one at least some of the time.
Neither number describes your team. Both are population figures, which makes them good for establishing that the problem exists and useless for deciding which Thursday invite to kill. That call needs your calendar, your attendee lists and your team’s own rate.
The three-step meeting audit
Set aside an hour to build the sheet and four weeks to fill it in. The audit is three tables, and each one only works if the one before it was filled in honestly.
Step 1. Log it
Open the calendar, take four weeks of it, and give every recurring meeting one row. One-offs stay out, with a single exception: if the same one-off has now happened three times, it is a recurring meeting nobody has admitted to yet.
Seven columns.
| Meeting | Owner | Recurrence | Duration | Attendees | Your role | Skippable (Y/N) |
|---|---|---|---|---|---|---|
| Weekly product sync | Product lead | Weekly | 30 min | 8 | Inform | N |
| Pipeline review | Sales director | Fortnightly | 60 min | 6 | Decide | N |
| Design critique | Design lead | Weekly | 45 min | 5 | Contribute | Y |
Two of those columns carry the whole audit.
Your role takes exactly three values, and only three. Decide means you make the call in that room. Contribute means the discussion needs something only you have. Inform means you are there to hear the outcome, not to shape it. Most people find this column harder than they expect, and the meetings where you genuinely cannot pick a value are usually the ones Step 3 catches.
Skippable is a yes or no, answered before you have seen a single cost figure. Give it five seconds a row and do not go back and revise it once the money shows up.
Four weeks is the minimum that works. Two weeks catches the weeklies and misses everything fortnightly. Anything longer than a month tends to get abandoned around day nine.
Do this pass before you cost anything. It is a time management exercise before it is a money exercise, and the log on its own will change two or three of your habits before any dollar figure appears.
Step 2. Cost it
Get the rate right and the rest is arithmetic anyone in the room can check.
Use a fully loaded salary rather than base pay. Fully loaded means base plus benefits, payroll taxes, and whatever else your finance team attaches to a headcount. Divide that by 2,080, the hours in a 40-hour, 52-week year.
fully loaded salary / 2,080 = hourly rate
attendees x hours x hourly rate = cost per occurrence
cost per occurrence x occurrences per quarter = quarterly costWorked example, using the weekly product sync from Step 1:
| Meeting | Attendees | Hours | Rate | Cost per occurrence | Occurrences per quarter | Quarterly cost |
|---|---|---|---|---|---|---|
| Weekly product sync | 8 | 0.5 | say $75/hr | $300 | 13 | $3,900 |
That $75 is a placeholder. It is not a benchmark. Plug it in, watch the arithmetic work, then swap it for the number your own finance team uses. A rate you borrowed from a blog post produces a quarterly cost you cannot defend in the meeting where somebody asks where it came from.
Two rules for the output. First, always carry the number out to the quarter. Cost per occurrence is small enough to shrug at, while 13 occurrences of a $300 sync is $3,900 for one recurring line on one calendar. Second, stop at the meeting level. Do not sum the sheet into a company-wide waste figure. That number is unfalsifiable, everyone who reads it knows it, and it is the fastest way to get the whole audit dismissed.
HR and L&D readers who have to carry a number like this into a budget conversation can start from our business case builder.
Step 3. Score it
Steps 1 and 2 produce data. This one produces a verdict, which makes it a decision-making exercise wearing a spreadsheet.
Read the five rules top to bottom and stop at the first one that matches the row. Every meeting gets exactly one disposition.
| Pattern in your log | Disposition | The rule |
|---|---|---|
| No decision was reached in the last three occurrences | Cut | Kill the recurring invite. If the topic comes back, it earns a new meeting, not the old slot |
| One person holds most of the airtime, and it is a status update rather than a debate | Make async | Replace it with a written update on a fixed day, with a named owner |
| Most attendees are logged Inform rather than Decide or Contribute | Shrink | Keep the meeting, cut the invite list to the Decide and Contribute people, send everyone else the notes |
| Your own role is Inform and you attend to approve, not to decide | Delegate | Hand the decision to whoever is closest to the work. You review the outcome, not the discussion |
| A real decision gets made, by the right people, inside the time box | Keep | No change |
Cut and Shrink are prioritization calls before they are anything else. Something on that sheet has standing permission to take 30 minutes of eight people’s week, every week, and the only question the rule asks is whether it has kept earning that standing.
The Delegate row behaves differently from the other four. They describe a meeting. This one describes you. When that row matches, the meeting is not the problem, your delegation habit is, and killing the invite fixes nothing because the approval simply moves to Slack.
Score the whole sheet in one sitting. Spreading it over a week gives you time to argue yourself back into the meetings you scored Cut on Monday.
Where the Delegate row breaks
The audit can tell you a meeting belongs in Delegate. It cannot make the handoff clean, and this is the row where the sheet quietly overstates its own usefulness.
When managers first mark a meeting “Delegate” on the audit, we see the same pattern: they hand off the meeting invite but keep the decision, so the report runs the discussion and still waits for a sign-off afterward. The illustrative version, a composite of that pattern rather than one real manager, sounds like this: “I gave Rachel the hiring debrief. I just want to see where it lands before we put a number in front of the candidate.” Both halves of that are defensible on their own, which is exactly why it survives review.
The meeting did move. The decision did not, and Rachel now runs a debrief whose outcome she cannot commit to in the room, which is a harder job than the one she had last quarter. Handing over the decision rather than the task is a skill in its own right, and the art of delegation covers why letting go feels like losing. What it cannot tell you is which meeting on your sheet to try it on. Naming the row takes four seconds. Telling someone which decisions they now own without you is a different piece of work, and this sheet does not do it for you.
Running this across a team
One calendar is a diagnosis. Eight calendars from the same team, logged in the same four weeks, is a map.
Have every manager fill in their own sheet, using the same three role values. Do not centralize the logging. A calendar audit completed by somebody’s assistant produces a very tidy sheet and no honesty at all in the Your role column, which is the column everything downstream depends on.
This post never explains how to run a good meeting. It works one level up: which meetings should exist in the first place, and whose habits keep putting them back. For running one well once you have decided to keep it, see how to run a meeting that ends early. It also decides, agenda item by agenda item, what should not be discussed live at all. This sheet makes that call one level up, on the whole invite.
The Make async rows need somewhere to land on the day you cancel them, or they reappear inside a month as “quick syncs” with four people on them. Pick the written format before you cancel the invite. Our guide to asynchronous communication has the templates, including what a written update has to contain to genuinely replace a standing meeting. It also carries a shorter audit of its own: cancel your least informative meeting and see whether anyone misses it. This sheet tells you which one that is, and what the other twelve are worth.
Then there is the question nobody asks until about week three: what is the reclaimed time actually for? Two hours back on a Wednesday, scattered as three twenty-minute gaps between the meetings that survived, is not two hours of work. It is three interruptions in a new arrangement. Block it as one piece or it evaporates, which is the case deep work makes at more length.
The quarterly cost total from Step 2 is the number that gets forwarded to a VP. It travels well, it fits on a slide, and on its own it changes nothing. The list sitting next to Delegate in Step 3 is the one that changes something, because it has a name attached to it instead of a dollar amount. Every row on that list is one manager, one decision they are still holding, and one conversation somebody now has to have.
Merlin will walk you through that conversation before you have it. Try Merlin free and start with the first name on the list.