Every recurring meeting needs an expiration rule

A recurring meeting rarely announces that it has stopped being useful.

It simply gets a little thinner. One week there is no real decision to make. The next week half the attendees give updates that could have been read. Eventually the meeting survives because it is already on the calendar, and being on the calendar is mistaken for having a purpose.

This does not mean recurring meetings are bad. Some work genuinely needs a dependable rhythm: reviewing risks, making cross-team decisions, resolving blockers or coordinating a changing plan. The problem is not recurrence. It is recurrence without a condition for continuing.

Every recurring meeting should therefore begin with an expiration rule: a date when the team must choose to keep it, change it or end it.

A calendar series is not a permanent decision

Most recurring meetings begin in response to a real need.

A project enters a difficult phase. Two teams need tighter coordination. A manager wants a reliable place to review priorities. Creating a weekly meeting is reasonable because the underlying problem is active and repeated conversation helps.

But the invitation usually has a different lifespan from the problem. The project stabilizes, the teams develop a simpler handoff, or the decisions become routine. The calendar series continues because nobody is explicitly responsible for asking whether the original need still exists.

That is how a temporary coordination tool becomes a standing obligation.

“Recurring” should describe how often the meeting happens, not how long the team has committed to holding it.

Write the expiration rule when the meeting begins

Do not wait until people are visibly tired of the meeting. By then, cancellation feels like a judgment on the organizer or on everyone who has attended it.

Set the review rule when the series is created, while changing course still feels normal.

A useful meeting invitation can include four lines:

• Purpose: Resolve cross-team launch risks that cannot be handled asynchronously.
• Expected output: A decision, an owned intervention or confirmation that no action is needed.
• Initial run: Weekly for six weeks.
• Review rule: After the sixth session, keep, change or end the series based on the last four meetings.

This is not a promise to cancel the meeting. It is a promise to examine it.

The review date gives the meeting a provisional lifespan. The expected output gives the team something observable to inspect when that date arrives. Together, they replace the vague question “Do people still like this meeting?” with the more useful question “Is this meeting still doing the job we created it to do?”

Review the outputs, not the mood

A meeting can feel pleasant and still be unnecessary. It can also feel difficult because it is resolving genuinely difficult work.

Attendance, energy and satisfaction matter, but none of them proves that a meeting deserves to continue. The review should begin with its intended output.

Look at the last four sessions and ask:

1. What decisions were made?
2. What blockers were resolved?
3. What work changed because the group met?
4. Which agenda items required live discussion?
5. Who contributed to those outcomes?

The answers reveal different failure modes.

If the meeting regularly produces consequential decisions, it may deserve to continue unchanged. If it produces useful outcomes only once a month, the cadence may be wrong. If the results matter but only three of eight attendees contribute, the attendance may be wrong. If the meeting produces updates but no interaction changes the work, the format may be wrong.

This is why keeping or canceling is too narrow a choice. The review needs three possible outcomes.

Choose keep, change or end

At the review date, make one explicit decision.

Keep it

Keep the meeting when its original purpose remains active, its outputs appear regularly and the people in the room are necessary to produce them.

Then set the next review date. A useful meeting is not exempt from future review; it has simply earned another period on the calendar.

Change it

Change the meeting when the need is real but the current design is wasteful.

That might mean:

• moving from weekly to fortnightly;
• shortening sixty minutes to twenty-five;
• replacing status updates with written preparation;
• inviting decision-makers only for the relevant section;
• removing attendees who need the outcome but not the discussion;
• splitting one broad meeting into a focused decision forum and an asynchronous update.

A meeting does not have to be failing completely before it deserves redesign. Often the purpose is sound while the cadence, attendance or agenda has drifted.

End it

End the series when the original problem is gone, the same discussion repeats without changing the work, or the useful information can now move through a simpler channel.

Record the decision briefly: when the series ended, why it ended and where any remaining updates will live. This prevents somebody from recreating the same meeting a month later because they cannot tell whether it was deliberately retired or merely forgotten.

Ending a recurring meeting is not admitting that creating it was a mistake. A meeting can be useful for six weeks and unnecessary in week seven. That is a successful temporary mechanism, not a failed permanent institution.

Make the organizer responsible for the review

A review rule without an owner is only decorative.

The person who creates the series should own the review by default. Their job is not to decide alone. It is to bring the evidence, ask the group for a keep/change/end decision, record the result and update the calendar.

Add the review as an agenda item before the expiration date rather than relying on someone to remember it. The review can be short:

We created this weekly meeting to resolve launch risks. Across the last four sessions, we made two decisions, resolved one blocker and canceled one session because there was no agenda. Should we keep the cadence, change it or end the series?

That question is specific enough to answer. “Is this meeting still useful?” usually produces polite silence because it asks people to challenge a shared habit without giving them a standard.

Allow cancellation without ending the series

An expiration rule governs the life of the series. A cancellation rule governs an individual occurrence. Useful recurring meetings need both.

If there is no agenda that matches the meeting's purpose, cancel that session. Do not fill the time with updates simply because the room has been reserved.

For example:

• agenda items are due one working day before the meeting;
• each item must name the decision, blocker or coordination need;
• if no qualifying item exists, the organizer cancels the session and posts a brief notice.

This keeps a valuable forum available without forcing it to perform usefulness every week. It also creates evidence for the next review. If four of six sessions are canceled, the team may still need the meeting—but probably not at that cadence.

What a healthy recurring meeting looks like

A healthy recurring meeting is not one that lasts forever. It is one whose current form matches a current need.

Its invitation states what it is for. Its agenda contains work that benefits from live interaction. Its outputs survive after the call as decisions and owned next steps, supported by a deliberate post-meeting workflow. Empty sessions are canceled. At a known date, somebody reviews the evidence and the team decides what happens next.

That small rule changes the default. Instead of continuing until somebody gathers enough courage to object, the meeting continues only after the team has looked at what it produces.

The best recurring meetings are not protected from expiration. They are made stronger by having to earn their renewal.