Nobody schedules a bad recurring meeting on purpose. It gets added when a real problem exists, three people need to sync on a launch, a team is new and needs alignment, a client wants a weekly touchpoint, and it earns its slot at the time. The problem is nobody ever removes it once the reason is gone. Eighteen months later the launch shipped, the team matured, the client relationship changed, and the meeting is still on everyone's calendar every single week. A standing meeting audit is the fix: a quarterly, deliberate pass through every recurring meeting on the company calendar, asking whether it still earns the slot it holds.
I run this exercise with clients roughly once a quarter, and it almost always turns up the same thing: a calendar that grew by addition and never once by subtraction. Meetings don't have a natural expiry date the way a project does, so they survive by default, not by merit.
The real cost of a weekly meeting, calculated honestly
Most leaders underestimate what a standing meeting actually costs because they only count the hour on the calendar. The real number is bigger, and it compounds weekly.
Take a fairly ordinary weekly meeting: eight people, one hour, mid-level to senior staff. The loaded cost per person, salary plus benefits plus overhead, typically lands somewhere in the range of Rp 150,000 to Rp 400,000 per hour depending on seniority and location. Eight people at that rate is roughly Rp 1.2 million to Rp 3.2 million per week, just in the hour itself. Multiply by 48 working weeks and you're looking at Rp 58 million to Rp 154 million a year for one recurring meeting.
That's before you add the parts nobody puts on a spreadsheet:
- Prep time. If two of the eight people spend 20 minutes preparing a status update, that's real hours nobody accounted for.
- The context-switch tax. A meeting in the middle of a focused morning doesn't cost an hour, it costs the hour plus the 15 to 20 minutes it takes to get back into deep work afterward, for everyone who was in flow before it started.
- The meeting-about-the-meeting. Standing meetings that consistently run long or go nowhere often spawn a smaller follow-up conversation to actually resolve what didn't get resolved.
None of this means meetings are bad. It means every recurring meeting should be priced like the recurring expense it is. A team that would never approve a Rp 100 million annual software subscription without a review will let a Rp 100 million meeting run unreviewed for years.
Why standing meetings never get killed on their own
Recurring meetings survive for reasons that have nothing to do with whether they're useful:
- Nobody owns the calendar invite as a decision, only as a habit. The person who created it moved to a different role or left, and the invite just kept firing.
- Cancelling feels like a political statement. If a director created the meeting, junior staff won't be the one to suggest killing it, even when half the room is quietly checking email during it.
- Attendance feels safer than absence. Nobody wants to be the person who wasn't in the room when something important got decided, so people keep showing up to a meeting they privately think is pointless, and that mutual pretending is exactly how staff quietly resist a process without ever saying so out loud.
- It's easier to add a meeting than to remove one. Adding takes one calendar invite. Removing requires someone to publicly declare that a thing the organization has been doing for a year wasn't worth doing.
This is why a standing meeting audit has to be a scheduled, structural exercise, not something you hope happens organically. Left alone, the calendar only grows.
How to run the audit: keep, kill, shorten, or make async
Once a quarter, list every recurring meeting on the company calendar: name, frequency, duration, attendee count, and owner. Then run each one through four questions, in this order, and stop at the first one that gives you a clear answer.
1. Does a decision or coordination actually need to happen live?
If the honest answer is that the meeting is mostly status updates that could be read, not discussed, it's a candidate for async. Replace it with a shared written update, a short async check-in doc, or a Slack/WhatsApp thread with a deadline for input. This is the same instinct behind treating your internal processes as something worth documenting rather than re-explaining live every time: if the same information gets communicated the same way every week, write it down once instead of performing it live fifty-two times a year.
2. Is the original reason this meeting exists still true?
If the meeting was created for a launch that shipped, a crisis that resolved, or a team structure that no longer exists, it's a kill. Nobody needs to defend killing a meeting whose original purpose is gone; that's not a political call, it's just closing a loop, the same discipline as running an honest kill-or-continue pass on a project roadmap that quietly kept funding dead initiatives.
3. Does it need the full time and the full room?
If the meeting reliably wraps in 20 minutes but is booked for an hour, or if four of the twelve attendees never speak, it's a shorten: cut the duration, or cut the invite list to only the people who make decisions or need to react in real time. Everyone else can get the notes.
4. Is it still solving the problem it was built for?
If yes, and it clears the first three questions, it's a keep. Don't apologize for that. Some meetings genuinely earn their slot every week, a live client touchpoint, a cross-functional sync where real-time back-and-forth actually saves time. The audit isn't an anti-meeting campaign; it's a filter that should let good meetings pass through untouched.
Running the audit without it becoming political
The reason most teams never do this isn't the analysis, it's the fear that killing someone's meeting reads as killing their relevance. Two things keep it clean:
- Frame it as a calendar cost review, not a performance review. You're auditing the meeting, not the person who created it eighteen months ago under different circumstances. Say that explicitly at the start.
- Let the meeting owner make the first call. Send the list to each meeting's owner with the four questions attached and ask them to self-classify before a leader overrides anything. Most owners, given real permission, will kill their own meeting once they see the loaded cost written down next to it. It's much rarer for someone to defend a meeting once they're the one holding the number.
If a good chunk of your meeting notes and status updates already sit in AI-generated summaries, the audit gets easier, because you can see at a glance which meetings actually produced decisions worth acting on and which ones produced a transcript nobody reread; that pattern is one of the quieter operational wins AI note-taking tools have delivered once teams stopped treating them as a novelty.
What actually changes after the audit
Most teams that run this seriously for the first time cut somewhere between 3 and 6 hours a week per person off their calendar, sometimes more for managers who sit in multiple standing syncs. That's not a productivity hack, it's just removing a cost nobody had reviewed in a year or more. The bigger shift is cultural: once a team sees that a meeting can be killed without drama, the next quarter's audit takes a fraction of the resistance the first one did, because killing a meeting stops feeling like an event and starts feeling like normal maintenance.
Practical takeaway
Run the standing meeting audit once a quarter, put a real number next to every recurring meeting, and force a keep, kill, shorten, or async decision on each one instead of letting default inertia decide. The goal isn't fewer meetings for its own sake, it's making sure every hour on the calendar is still earning the slot it was given. If you want a second set of eyes on where your team's time is actually going before your next quarterly review, reach out through /partner.