How to Run a Sunset Review for Recurring Executive Meetings solves a narrow but important executive-office problem: whether a recurring executive meeting should continue, change cadence or participants, move asynchronous, or end.
For this workflow, capture meeting owner, stated purpose, decisions produced, participants, cadence, duration, preparation load, attendance, alternatives, last review, decision, and next review.
The assistant may assemble evidence, survey participants, remove obsolete holds under an agreed rule, and implement approved changes. The meeting owner decides disputed purpose, required governance attendance, and material changes to decision rights.
Consider this case: A weekly leadership meeting has run for two years. Twelve people attend, most updates are read aloud, the CEO joins late, and no one remembers who owns the series or what decision it exists to make.
Useful indicators include recurring series with owners and review dates, meetings ended or redesigned, participant hours returned, decisions per meeting, preparation delivered on time, and repeated agenda items resolved.
Reconstruct the meeting’s original bargain
Every recurring meeting began as a response to some need: a decision had no forum, a launch required coordination, or an executive wanted reliable visibility. Find that original job before judging today’s calendar entry. Ask the owner what the meeting is supposed to produce, which participants supply necessary inputs, and where the output is recorded. If nobody can answer, the series is already relying on habit rather than design.
Review four recent occurrences. Note actual decisions, issues escalated, preparation consumed, attendance, and work that moved afterward. Do not infer value from a polished agenda or senior attendance. A weekly hour that repeatedly ends with “continue offline” may be an expensive status exchange. A fifteen-minute call that resolves a cross-functional constraint can still justify its place.
Examine a leadership meeting that outlived a launch
A product launch meeting started six months before release. It once resolved scope, staffing, and vendor choices. Three months after launch, twelve leaders still attend each Monday. The agenda now repeats dashboard numbers available elsewhere, while the only recurring decision concerns customer escalations handled by two teams.
The owner proposes ending the series, moving the dashboard to an asynchronous Friday update, and creating a twenty-minute exception call only when a customer issue meets stated thresholds. Open post-launch actions receive named owners before the final meeting. The assistant cancels future invitations, links the new update location, and explains how participants can trigger the exception call.
For six weeks, the office watches customer escalation age, missed handoffs, and requests to revive the meeting. One missed issue reveals that the dashboard lacked an owner for regulatory questions. The team repairs that route without restoring twelve-person attendance. The review succeeded because it tested the replacement, not because the calendar became emptier.
Choose the right redesign
Cancellation is one option. A decision forum may need fewer participants and a pre-read deadline. A coordination meeting may need a temporary working group with an end date. A status meeting may become a written update with comments due by a fixed time. A relationship forum may need a lower cadence rather than asynchronous substitution. Match the redesign to the job.
Protect dissent and exception paths. Written updates can hide uncertainty when people fear challenging a senior owner. Name the questions that require live discussion and allow participants to flag them before the cutoff. Conversely, do not schedule a call because one person failed to read. The owner decides whether the issue merits synchronous time.
Time zones and accessibility matter. Replacing a meeting with an update that arrives at midnight for half the team merely moves the burden. Set a reading and response window that works across regions. Provide a route for participants who use assistive technology or cannot access the chosen tool.
Decide with opportunity cost in view
Calculate participant time, preparation, follow-up, and schedule fragmentation, but do not reduce the decision to an hourly cost. Ask what the same people could do with a predictable block returned to them. For executives, the opportunity may be customer work or a decision that only they can make. For specialists, it may be uninterrupted analysis.
Keep a meeting when its decision value and coordination risk justify the cost. End or redesign it when inputs can move without live attendance, authority is elsewhere, or the series no longer changes action. Document the reasoning and a review date so a temporary exception does not become the next permanent habit.
The final communication should be candid: what is ending, why, where information will move, how urgent issues will surface, and when the replacement will be assessed. Participants do not need a ceremonial farewell meeting. They need confidence that important work still has an owner and a path.
Keep the decision reversible for a defined test period without leaving the old invitation active. If the replacement misses a material decision, document which signal failed and who lacked access. Restore only the capability that was missing. A temporary exception call or clearer escalation threshold may solve the problem without recreating the full series. This approach lets the office learn from real use while preventing nostalgia from becoming the evaluation method.
Account for the work displaced by attendance
Calendar cost is not simply duration multiplied by headcount. A thirty-minute meeting can break a two-hour concentration block, force a regional leader into an evening call, or require several hours of pre-reading that never affects the discussion. During a sunset review, ask each role what it postpones to attend and which portion of the agenda genuinely requires synchronous exchange. This exposes costs that an attendance report cannot show.
Consider a weekly forecast meeting where finance reads numbers already posted in the dashboard, then leaders debate only two uncertain accounts. Replace the recital with an asynchronous cutoff and keep a shorter call for the disputed assumptions. If contributors routinely miss the cutoff, fix ownership of the forecast instead of restoring the long meeting. Review the redesigned cadence after a full operating cycle, not after one unusually quiet week. The test is whether decisions arrive with better evidence and fewer side meetings, not whether the calendar contains fewer colored blocks.
Preserve the decision path after cancellation
Canceling a meeting does not cancel the decisions it once carried. Move each live decision to a named owner and channel before deleting the series. Tell former attendees where exceptions will surface and who can call a temporary session. After two cycles, check whether decisions stalled or simply moved into untracked side conversations. Restore a meeting only when synchronous discussion is the missing mechanism, not because participants miss a familiar calendar rhythm.