How to Audit Recurring Meetings

What success looks like

Find the meetings worth keeping and redesign or remove the rest. The practical test is whether the people involved can point to a lighter recurring meeting system without reconstructing the whole conversation.

A practical method

Set the boundary for the work

Write a lighter recurring meeting system as the boundary. Keep only the evidence, authority, and participation needed to produce that specific result.

Work through the sequence

Score every series on purpose, attendance, preparation, output, cadence, and cost; keep only meetings with a distinct job. Place that instruction in the shared workspace and use it to distinguish the real work from background discussion.

Create a usable record

A durable record should make sense beside this example: A weekly coordination call becomes fortnightly after the team moves routine progress into a shared update. Name any owner, due point, decision rule, or review trigger needed for another person to act.

Worked example

A weekly coordination call becomes fortnightly after the team moves routine progress into a shared update.

Copy this example

The example connects directly to a lighter recurring meeting system. Put similarly concrete wording in the invitation, agenda, or record so the result can be checked later.

A failure to avoid

Watch for Asking whether people like a meeting instead of whether it produces a necessary result. If it appears, pause and compare the discussion with a lighter recurring meeting system before more meeting time is used.

If recovery also requires a confident keep, change, or cancel decision, use When to Cancel a Meeting as the next method.

A useful recovery question

Ask: “What is the smallest responsible move that would still create a lighter recurring meeting system?” If the answer depends on missing evidence, record that evidence, one owner, and the exact return condition.

Final checklist

• The stated goal is a lighter recurring meeting system.
• The working method is visible to everyone involved.
• The record is specific enough to support an example such as: A weekly coordination call becomes fortnightly after the team moves routine progress into a shared update.
• The design actively guards against Asking whether people like a meeting instead of whether it produces a necessary result.

Next, use the meeting health check to turn the method into a working artifact.