“Meeting Audit: How to Audit Your Team’s Meetings”

What is a meeting audit?

A meeting audit is a systematic review of all recurring meetings on a team’s calendar, scoring each one on cost, purpose, attendance, and decision output, then deciding whether to keep, shorten, convert, or end it.

It is not a survey about how people feel about meetings, although sentiment is one input. It is not a productivity purge either. A good audit usually keeps more meetings than a bad one, because it can show which ones are load-bearing and therefore deserve better preparation, better attendance, and better time slots.

The output is a table: every recurring series, its annual cost, its decision output, and a decision with an owner and a date. If the audit ends with opinions but no table, nothing will change.

Why do meetings accumulate?

Meetings accumulate because they are cheap to create and expensive to remove. Adding a series takes one calendar invite. Removing one requires telling a colleague that their meeting is not worth the money, which is a social cost most people avoid.

The scale is well documented. Microsoft’s 2023 Work Trend Index, based on a survey of 31,000 workers in 31 markets, reported that people attend three times more Teams meetings and calls per week than they did before February 2020 — a 192% increase. The same research found 68% of people say they do not have enough uninterrupted focus time during the workday, and that inefficient meetings rank as the number one productivity disruptor, with too many meetings at number three.

Two further findings are useful for anyone designing an audit. Only 35% of people think they would be missed in the majority of their meetings, and 55% say next steps at the end of a meeting are unclear. That second number is an indictment of meeting design, not meeting volume: a meeting that ends without a decision or an owner has produced a conversation, not work.

> Important note: “Inefficient meetings” beating “too many meetings” in that ranking matters. Deleting half the calendar without fixing the remaining half produces a quieter version of the same problem.

How do you calculate the real cost of a meeting?

You calculate a meeting’s cost by multiplying its duration by the number of attendees by a loaded hourly rate, then multiplying by how often it recurs. Loaded means salary plus employer costs — benefits, payroll taxes, overhead — not gross salary.

The formula:

Meeting cost = duration (hours) × attendees × loaded hourly rate × occurrences per year

For a team with a blended loaded rate of $55 per hour, a one-hour weekly meeting with eight attendees costs:

• Per session: 1 × 8 × $55 = $440
• Per month: $440 × 4.33 = $1,905
• Per year: $440 × 48 = $21,120

That is one recurring meeting. Ten of them is $211,200 a year, which is roughly the fully loaded cost of one senior employee. This is the number that changes the conversation, because it is comparable to things the organization already treats as budget decisions.

Notice the daily standup: short meetings are not automatically cheap, because frequency multiplies. Fifteen minutes with seven people, five days a week, costs more per year than a one-hour weekly meeting with eight.

> Practical tip: Use a blended rate rather than arguing about individual salaries. The point of the number is comparison, not accounting precision. If HR will not give you a loaded rate, multiplying gross hourly pay by about 1.25–1.4 is a reasonable approximation for most salaried roles.

What does a full audit look like, step by step?

A full audit takes about two weeks of calendar time and four to six hours of actual work. It runs in five steps, and the order matters because each step narrows the next.

Step 1: Build the inventory

Pull every recurring event from the team calendar for the last 90 days. Include the ones you attend, the ones your team attends, and the ones that only exist on someone’s personal calendar but consume team time. For each, record: name, owner, duration, frequency, attendee list, and whether a written agenda exists.

Expect the list to be longer than you think. Twelve to thirty series is typical for a team of eight to fifteen people.

Step 2: Attach cost

Apply the formula from the previous section. Sort descending by annual cost. The top five usually account for more than half of total meeting spend, which tells you where the review effort should go.

Step 3: Score output

For each meeting, ask the owner one question in writing: “What decision or output did this meeting produce in the last four sessions?” Read the answers carefully. “Updates” and “alignment” are descriptions of activity, not output. A decision, an approved document, a resolved blocker, or a changed plan is output.

Step 4: Decide, with four options

For each series, choose one of four outcomes and assign an owner and a date.

Step 5: Publish and implement

Send one message to the team listing what changed and why, with the cost numbers included. Then actually change the calendar invites the same week. An audit announced but not implemented teaches the team that the next audit is also optional.

How do you score each meeting?

You score each meeting against a short set of yes/no questions, then use the score to pick one of the four options. Keep the questions blunt, because subtle scoring systems invite debate about the scoring rather than the meeting.

Seven questions, each scored 0 or 1:

1. Did this meeting produce a decision in the last four sessions?
2. Could the information have been shared in writing without losing anything?
3. Is every attendee’s presence required for the decision or the work?
4. Does the meeting start and end on time with an agenda?
5. Do the last five minutes produce named actions with owners?
6. Would anything break if this series were cancelled for one month?
7. Is the current time slot the best available one for the participants’ focus?

Scoring: 6–7 is healthy, keep it and protect the slot. 4–5 needs a redesign — shorter, fewer people, or a real agenda. 2–3 should be converted to async or merged with another series. 0–1 should be ended.

The fourth and fifth questions are the ones that most often expose a fixable meeting rather than a pointless one. A meeting with a genuine decision, no agenda, and no recorded actions scores 5 and looks mediocre — but it can usually be repaired in one session with a template.

What does a real audit find?

A real audit typically finds that a small share of meetings produces most of the decisions, and that the largest cost sits in meetings nobody defends. The numbers below come from a fifteen-person product team’s audit; the shape is common even when the amounts differ.

The team had 23 recurring series. Total annual meeting cost, using a $62 loaded rate: $486,000. That is 25% of the team’s fully loaded payroll, which works out as 15 people × 2,080 hours × $62 = $1,934,400.

The distribution:

• 4 series produced 80% of the recorded decisions: weekly product review, sprint planning, the customer escalation call, and the monthly roadmap session. Annual cost: $96,000.
• 9 series distributed information: standups, status syncs, project updates. Annual cost: $244,000. Six of these converted to written updates with a 24-hour comment window.
• 6 series could not be justified by any owner. Annual cost: $82,000. Four were cancelled outright; two were merged into existing reviews.
• 4 series were 1:1s and coaching conversations, kept in full despite producing no “decisions,” because retention is not measured in decision counts.

Net effect: $214,000 of annual meeting cost removed — 44% of the total — with no decision-making series touched. The team also shortened two kept meetings from 60 to 30 minutes and moved the weekly product review from Monday 9 a.m. to Monday 2 p.m., protecting the sharpest hour for individual work.

The honest caveat: the team’s first estimate of savings was 60%, and it shrank as they discovered which meetings were doing invisible work — onboarding, conflict resolution, and the informal check-ins that prevent small problems from becoming escalations.

What should you do with the meetings you keep?

Kept meetings need a design upgrade, not just a reprieve. The cheapest improvements are an agenda sent in advance, a named owner, a fixed end time, and a written record of decisions and actions within an hour of the meeting.

Four practices do most of the work:

• Agenda or cancel. No agenda 24 hours before means no meeting. This one rule eliminates a large share of low-value sessions without any audit at all.
• Name the decision. Every agenda item ends with “decide,” “inform,” or “explore.” Items marked “inform” belong in writing.
• Cap attendance by role, not seniority. Invite the person who decides, the person who does the work, and the person who needs to know. Everyone else gets the notes.
• Close with owners and dates. The last five minutes produce a list of actions with names attached. A meeting that ends without them has not finished.

Amazon’s well-known practices — small “two-pizza” teams and replacing slide decks with written memos read silently at the start — are worth studying not because they are fashionable but because they make the same trade: more preparation cost, less live meeting time.

What are the risks of cutting meetings?

Cutting meetings has real costs, and a team that ignores them will end up reinstating the meetings informally. The main risks are onboarding, belonging, and unresolved conflict.

Onboarding suffers first. New hires learn culture, norms, and unwritten rules by overhearing. A team that moves everything to async must replace that with deliberate onboarding: pairing sessions, a mentor, and explicit documentation.

Belonging and trust erode quietly. Remote and hybrid teams use meetings partly as social infrastructure. Removing all of it produces efficiency metrics that look fine and a retention problem six months later.

Conflict goes underground. A written thread can escalate faster than a conversation, because text strips tone and nobody can see the other person thinking. Keep synchronous time for anything emotionally charged.

Coordination cost moves rather than disappears. Async updates require writing discipline and reading time. A team without that discipline will simply add the meeting back in two months.

> Common mistake: Cutting one-to-ones to “save meeting time.” They rarely show measurable output and are among the highest-return meetings a manager has. The audit should protect them explicitly.

What mistakes do teams make in a meeting audit?

Five mistakes turn a good audit into a resented exercise.

1. Auditing other people’s meetings but not your own. Start with the series you own. It buys credibility.
2. Counting attendance as engagement. A room full of silent people is a cost, not a signal of importance.
3. Publishing a verdict without a reason. “We cancelled the sync” creates anxiety; “we cancelled it because it produced one decision in eight sessions and now runs as a written update” creates understanding.
4. Forgetting the recurring trap. A meeting cancelled for one month often returns with the same attendees and no agenda. Cancel the series, then re-create it deliberately if needed.
5. Never measuring again. Meeting load regrows at roughly the rate it was cut, usually within two to three quarters.

How do you keep the audit from decaying?

You keep it from decaying by making meeting cost visible at the point of creation and by re-auditing quarterly. Both are small habits; neither survives as a one-off project.

At the point of creation, add three fields to any meeting request: the decision it supports, the owner, and a review date. A recurring meeting with a review date is a rental, not a permanent fixture.

Quarterly, re-run steps 1 and 2 only: inventory and cost. That takes about ninety minutes and shows whether the calendar drifted. If total meeting cost rose more than 10% without a corresponding new initiative, something crept back in.

This is also where keeping meeting output in the same system as the work pays off. Doitify is our product, so we know this part: meeting notes, decisions, and the tasks that come out of them can live alongside the project they belong to, with owners and due dates attached, and recurring meetings show up in the same calendar as the work they consume. That makes the audit’s key question — what did this meeting produce? — answerable from the record rather than from memory. For a single audit, a spreadsheet is enough; the value appears when the review repeats every quarter.

Conclusion

A meeting audit is not an argument against meetings. It is an argument against meetings that nobody can justify, in a calendar nobody is allowed to question.

Start with the inventory and the cost formula this week — that alone usually produces one uncomfortable conversation and one obvious cancellation. Then score, decide, and publish the changes with the numbers attached. Re-run the cost calculation every quarter, because the meetings you remove will try to come back, and the calendar has no memory of why they left.

If this post on meeting audit was helpful, you might also enjoy A Day in the Life of a Project Manager (Realistic Walkthrough) and Project Collaboration Software: What to Look For.