Guides · Whitepaper
The Meeting Tax: What Recurring Meetings Cost an Organization
Published
Every organization pays a tax it never voted for. It is collected in hours, it is spread across every calendar, and it shows up in no budget.
This paper sets out a simple model for that cost, works through an example for a 50-person organization, and then reruns the same numbers with decisions made in writing instead of in meetings.
Every number in the example is an assumption, chosen to be easy to follow, not a measurement. The model is the point. Put in your own numbers and see where they land.
A cost model
The direct cost of recurring meetings comes down to four inputs:
Cost = headcount × meeting hours per person per week × loaded hourly cost × working weeks per year
Each input deserves a word.
Headcount. The number of people whose time you are counting. You can run this for a team, a department, or the whole organization.
Meeting hours per person per week. The average time each person spends in recurring meetings. The calendar is the best source. The self-audit in How to Know If You’re Having Too Many Meetings shows how to count it.
Loaded hourly cost. What an hour of a person’s time actually costs the organization: salary, plus benefits, taxes, equipment, and overhead. This is meaningfully higher than salary alone. Use the figure your finance team uses for planning if there is one.
Working weeks per year. The weeks people are actually working, after holidays and leave.
Then add one more input, and state it separately, because it is the one people argue about: transition time. A meeting costs more than its booked slot. People do not start focused work shortly before a call, and they take time to get back into their work afterwards. Pick a fixed amount per meeting, apply it consistently, and say clearly that it is an estimate.
A worked example: 50 people
The numbers in this example are illustrative, not measured. They are round values chosen to make the arithmetic easy to follow. Replace each one with your own.
| Input | Example value |
|---|---|
| Headcount | 50 people |
| Recurring meetings | 6 one-hour meetings per person per week |
| Transition time | 20 minutes per meeting |
| Loaded hourly cost | $100 per hour |
| Working weeks | 48 per year |
| Cost of one person in one meeting, with transition time | 80 minutes, about $133 |
The arithmetic, as formulas you can rerun with your own inputs:
- Meeting hours per person per week = meetings per week × (meeting length + transition time)
- Organization hours per year = headcount × meeting hours per person per week × working weeks
- Direct cost per year = organization hours per year × loaded hourly cost
With the example inputs, six meetings at 80 minutes each come to 8 hours per person per week, a fifth of a 40-hour week. Across 50 people that is 400 hours a week, or about 19,000 hours over a year. At $100 an hour, the direct cost is about $1.9 million a year.
That covers recurring meetings alone, before any one-off meetings, and only under these assumptions.
By meeting type
Not all of that time is the same. Break it down by what the meetings are for. For the example, suppose each person’s six weekly meetings split like this:
| Type | Meetings per person per week | Hours with transition time |
|---|---|---|
| Decision meetings | 3 | 4 |
| Information-sharing | 2 | 2 h 40 min |
| Conflict and hard conversations | 1 | 1 h 20 min |
In this example, half the meeting load is decision meetings. In your organization the split will differ. The audit tells you what it actually is.
The split matters because the three types respond to different fixes. Conflict and hard conversations should stay live. Some information-sharing can move to writing. Decision meetings are the largest opportunity, because most of them exist only to gather everyone’s view at once, and there are other ways to do that.
Second-order costs
The direct cost is the part you can calculate. Two other costs are real but harder to pin down. Treat them as ranges, not point estimates.
Fragmented focus. Meetings scattered across a day cost more than their booked time, because they break the day into pieces too short for focused work. Two one-hour meetings at 10am and 2pm can leave a person without a single long block for the whole day. For people whose job is focused work, the lost output can be well beyond the meeting hours themselves. It is hard to measure, so state it as a range: somewhere between “a little more than the transition time” and “most of the day’s deep work.”
Decision latency. A decision that waits for a meeting waits for the next slot when everyone is free. For a weekly meeting, that can be up to a week. If the decision blocks other work, everyone downstream waits too. The cost here is not hours in a room but time lost while work is stalled. It varies widely with how much depends on the decision.
Neither of these appears in the model above. Both make the true cost higher.
The async alternative, on the same numbers
Now rerun the example with decision meetings replaced by decisions made in writing. The pattern is the one from How to Have Fewer Meetings: a Leader frames one question with the context people need, sends one link in the channels people already use, collects everyone’s answer in their own words by a deadline, and closes with a named owner and a written outcome.
Take a typical decision: “Which concept should we take into the next design round?” In a meeting, it costs every attendee the full slot plus transition time. In writing, each person reads the question and the attached concepts, then answers in a few sentences, a short voice note, or a short video.
Keep the other inputs and add one more. Like the rest, it is illustrative, not measured.
| Input | Example value |
|---|---|
| Decision meetings | 3 per person per week |
| Time to respond to a written decision | 15 minutes per person, including reading the context |
| Cost of one person in one decision meeting, with transition time | 80 minutes, about $133 |
| Cost of one person answering one written decision | 15 minutes, $25 |
The formula for what moving decisions to writing saves:
- Hours saved per year = headcount × working weeks × decisions per week × (decision meeting time − written response time)
- Direct cost saved per year = hours saved per year × loaded hourly cost
With the example inputs, each person spends 4 hours a week on decision meetings and about 45 minutes on the same decisions in writing, so each person gets a little over 3 hours a week back. Across 50 people and 48 weeks, that is about 8,000 hours a year. At $100 an hour, decision meetings cost about $1 million a year in this example, the written version about $200,000, and the difference is about $800,000.
The time to a decision changes too:
| Meetings | Decisions made async | |
|---|---|---|
| A decision waits for | The next common meeting slot | The deadline you set |
The last row is the one the model cannot price. With meetings, a decision waits for the calendar. With a written decision, it waits for a deadline you choose, and it can close earlier if everyone has answered.
What the model leaves out
The model is deliberately simple. Some things it does not capture:
- The cost of the Leader’s time to frame the question and write the outcome. It is real, and it is usually small next to the meeting it replaces. Framing a decision well also tends to make it a better decision.
- Decisions that genuinely need a meeting. Some will. The model assumes only that decision meetings are the main candidates, not that every one can move.
- The meetings you keep. Fewer meetings should mean better ones. Make the Meetings You Keep Worth Having covers that side.
Running it for your organization
- Count meeting hours per person for two typical weeks, including transition time.
- Split the hours by meeting type: decision, information-sharing, conflict.
- Agree a loaded hourly cost with whoever owns the budget.
- Run the model for today, then for decision meetings made async.
- Write down your assumptions next to the result, so anyone can check them.
The number you get will not be exact. It does not need to be. It needs to be clear enough that recurring meetings stop being free in the minds of the people who schedule them.