Audit Recurring Meetings With a Five-Question Calendar Review
by ExecutiveAssistantAgency Editorial Team · 5 min read
A five-question review that helps an executive assistant find recurring meetings that no longer earn their place on the calendar.
In this article
- Recurring meetings drift away from their original purpose
- Ask what decision the meeting exists to produce
- Count the people who actually shape the outcome
- Compare the preparation load with the meeting length
- Test a lighter cadence for one cycle
- Record the change and review it again
- Give the executive a short summary, not a lecture
Recurring meetings drift away from their original purpose
A recurring meeting rarely becomes useless in one dramatic moment. It loses a minute here, adds an attendee there, and gradually turns into a status ritual that nobody can quite justify. By the time an executive asks why the meeting still exists, the original reason has usually been forgotten. A calendar review gives the assistant a calm, evidence-based way to ask that question without turning the conversation into a complaint about busywork.
The review should not become an attack on collaboration. Some recurring meetings are the only place where a distributed team makes decisions, resolves conflicts, or maintains trust. The goal is to separate those meetings from the ones that survive only because removing them feels awkward. The same discipline used in a pre-board calendar lock works here: define the purpose, check the evidence, and make a deliberate choice.
Ask what decision the meeting exists to produce
Start with a single question for each recurring series: what decision or commitment comes out of this meeting? A meeting that approves spend, sets priorities, resolves a customer escalation, or coordinates a launch has a clear output. A meeting whose only output is a conversation that could have been a written update is a candidate for change. Write the answer in one sentence and keep it beside the calendar entry for the review.
If the answer is vague, ask the meeting owner rather than guessing. Some executives will say the meeting exists for relationship maintenance, which is a legitimate purpose when the relationships are important. In that case, the review should ask whether the same relationship work could happen less often or with a smaller group. The point is not to eliminate every unstructured conversation but to make the trade-off visible.
Count the people who actually shape the outcome
List the attendees and mark who contributes a decision, a required update, or a specific expertise. Then mark who attends mainly to listen. Listeners are not automatically waste, because context has value and junior staff often learn by observing. However, a meeting with twelve attendees where three people speak is a signal that the invitation list has grown beyond the work.
For each listener, ask whether a written summary would provide the same context. If the answer is yes, offer the summary and remove the invitation. If the answer is no, record why the person needs to be present. This simple note prevents the same debate from returning next quarter and gives the assistant a defensible reason for the change. The record also helps when a new manager asks why the invitation list looks smaller than it used to.
Compare the preparation load with the meeting length
The calendar shows the meeting hour, but the real cost includes the briefing pack, the pre-read, the agenda, and the follow-up notes. Add those tasks to the review and compare them with the value of the decision. A thirty-minute meeting that requires two hours of preparation from three people may still be worth it, but the cost should be understood. A meeting that requires a large pack and produces no decision is a strong candidate for redesign.
Preparation load also affects the assistant's ability to protect focus time. When recurring meetings expand, the work to prepare them often lands in the same small windows that should be used for urgent requests. The weekly one-on-one agenda is a useful place to raise that pattern with the executive. The conversation is easier when the assistant brings a list of meetings and hours rather than a general feeling of overload.
Test a lighter cadence for one cycle
Do not cancel a meeting permanently in the first pass. Change the cadence for one cycle, such as moving a weekly review to every other week, and observe what happens. If decisions slow down or important issues disappear, the meeting may need to return. If nothing changes except the amount of free time, the lighter cadence is probably the better default.
Use a simple test period and a named reviewer. The assistant can track whether the same topics appear in chat, email, or another meeting after the change. A topic that resurfaces elsewhere may still need a home, but that home does not have to be the original meeting. The review should end with a written decision, not a vague promise to revisit the calendar later.
Record the change and review it again
Keep a short record of what changed, why it changed, and when the team will check the result. The record can live in the decision log alongside other operational choices. It should name the meeting, the old cadence, the new cadence, the owner, and the date of the next review. That level of detail makes the change reversible and prevents quiet drift back to the old pattern.
Schedule the next review before the current one ends. A quarterly check is usually enough for stable meetings, while a monthly check may be needed during a busy season. When a new executive joins or a team reorganizes, run the five questions again because the purpose may have changed. A calendar that is reviewed on a regular rhythm stays honest without requiring a crisis to force the conversation.
Give the executive a short summary, not a lecture
The final output of the review should fit on one page. List each recurring meeting, its purpose, its attendees, its preparation load, and the recommended action. Use plain language and avoid framing the review as a judgment about anyone's job. The plainlanguage.gov guidelines are a useful reference for keeping the summary short and direct. The executive can approve, reject, or defer each recommendation in a few minutes, and the assistant can turn the approved changes into calendar edits the same day.
For help building a calendar operating rhythm that holds up across executives and assistants, talk to our team. The strongest calendar systems are not the ones with the most rules. They are the ones where someone reviews the rules often enough to keep them useful. A short review each quarter is usually enough to catch the meetings that have quietly stopped earning their place.
Related Articles
blog
Create a Handwritten Note Queue for Executive Relationship Follow-Ups
A practical queue for getting timely handwritten notes out of the executive office without losing track of who received one.
blog
Run a Quarterly Access Review for the Executive Office Suite
A quarterly routine for reviewing badges, calendar delegates, shared drives, and vendor access in the executive office, with evidence and follow-up steps.
blog
Set Up a Lobby Arrival Script for Executive Guests
A short arrival script that helps reception, security, and the executive office give visiting guests a calm and consistent welcome.