The meeting audit: which recurring meetings to cut, shorten, or make async

Recurring meetings are sticky for three reasons. They are on the calendar, so cancelling one feels like an event. They have an invitation list, so removing a name feels like a snub. And they started for a reason that was true once, such as a launch or a reorganization, and nobody wrote down the date when the reason expired.

On a remote team the cost is larger than it looks, because the call replaces the hallway. People attend to stay visible and informed, not because the agenda needs them. A meeting that exists mostly to reassure people that work is happening is a status ritual, and a status ritual can usually be done in writing.

An audit is a sorting job, not a purge. Some meetings earn their place. The point is to know which ones, and to be able to say why. The three jobs a meeting can do are covered in every meeting has three jobs, which is a useful frame before you start.

Start with an inventory. Export the team's calendar for the last month and list every recurring meeting with four facts: the name, the owner, how long it runs, and how many people are invited. Do not skip the owner. A meeting with no owner is a candidate for cutting before you ask anything else.

Then ask the meeting's owner to answer the four questions in the next section, in writing, in one sentence each. If the owner cannot answer, that is an answer. Bring the results to the team in a single short session and sort each meeting into one of four outcomes:

• Keep as is
• Shorten, or reduce the invitation list
• Make async, which means move it to a written update or a shared document
• Cut, which means stop holding it and say so

For a view of what a good live meeting needs once it survives the audit, see what is meeting facilitation.

Ask these four questions about each recurring meeting, in this order:

1. Is a decision needed? If the meeting produces a decision that needs more than one voice, it earns a live slot. If it only shares information, it probably does not
2. Who must be live? List the people whose presence changes the outcome. Everyone else gets the notes. Cut the invitation list to that group
3. Can it be written? Could the content go into a shared document, a recorded message, or a thread that people read on their own time? If so, try that first. Reserve live time for what writing cannot do, such as disagreement, nuance, and relationship
4. What breaks if it ends? Name a concrete consequence. “We would lose visibility” is a reason to fix visibility another way. “The release would ship without sign-off” is a reason to keep the meeting

Score the meeting simply. Mostly no answers to questions one to three, and nothing concrete in question four, means cut. A decision with a small group means keep and shorten. Information without a decision means make it async. A real decision with a large group means keep it, restructure it, and put a decision log behind it as described in how to run a virtual annual planning session.

Use this quick rule. Go live when the work needs real-time disagreement, when the topic is emotionally loaded, or when the group is forming a shared view for the first time. Go async when the content is an update, a status, a request for input on a draft, or anything that benefits from people thinking before they respond.

Async needs structure to work. Give a deadline, name who reads, say what response you need, and say where the answers go. An async update that nobody answers is a meeting that failed quietly, not a success.

Time zones change the math. If a live meeting forces half the team into early mornings or late nights, the bar for keeping it should be higher. Live sessions and time zones covers how to be fair about it, and hybrid rooms are two rooms covers what to do when some of the team is together and some is not.

Treat the changes as an experiment with an end date. Announce it, run it for two weeks, and decide with evidence.

• Day 1 to 2: finish the inventory and the four questions, sort each meeting, and tell the team exactly what will change and on what date
• Day 3: set the baseline. Write down the hours the team spends in the audited meetings, the decisions it expects to make, and the blockers it is carrying
• Week 1: run the cuts, the shortened meetings, and the async replacements. Keep one lightweight channel open for people to flag anything that fell through
• Week 2: hold steady. Do not add meetings back in a panic. Collect the evidence
• Day 14: hold a 30 minute review. Compare against the baseline and decide what stays cut, what comes back, and what changes shape

Measure three things and nothing else: hours returned to the team, decisions made on time, and blockers that surfaced late. Use your own numbers from your own team, collected simply, and do not borrow anyone else's. If a blocker surfaces late because a meeting was cut, restore the meeting or fix the information path, and say so openly. A pilot that can only succeed is not a pilot.

Meetings return the way weeds do. Set three guards:

• Every new recurring meeting needs a named owner, a written purpose, and an end date or a review date
• Run the four-question test again every quarter, in 15 minutes, on any meeting more than a quarter old
• Write the team's meeting norms in a short page: what goes async, what goes live, and how a person can decline an invitation without penalty

If you want a model for who runs the live meetings that remain, nobody is coming to facilitate your meetings is the next read, and how to facilitate an all-hands meeting covers the biggest recurring call of all.