The Meeting That Wasn't Needed: Five Recurring Sessions UK Associations Should Retire in 2026
Photo: Jonathan Kington, CC BY-SA 2.0, via Wikimedia Commons
A meeting is not a neutral event. It is a claim on staff time, member goodwill and governance attention. Yet many recurring sessions survive because they are in the calendar, not because they change a decision. In 2026, with hybrid working still complicating attendance and volunteers scrutinising how they spend their time, UK associations should be willing to cancel the agenda more often.
The case for cancellation is not anti-governance. It is pro-decision. A meeting that exists only to transmit information is usually a written briefing with a room attached. A meeting that exists to rubber-stamp a paper could be an asynchronous decision. A meeting that exists because it always has is a cost without a clear return.
Five meetings to put on notice
1. The weekly all-staff update. This is often a passive audience listening to status reports that could be read in five minutes. Replace it with a Monday written brief covering priorities, risks and decisions needed. Keep a short exception-only call for matters that genuinely require discussion. Test: if no decision is taken and no debate changes the outcome, cancel it.
2. The standing committee's 'matters arising' session. Many committees spend the first twenty minutes recapping actions that are already recorded. Replace the information item with a written matters-arising log circulated beforehand, and use the meeting only for decisions, scrutiny and contested items. Where the constitution or terms of reference require a meeting, keep the meeting; move the information out of it.
3. The pre-board agenda-setting meeting. A short meeting to agree the agenda for another meeting is rarely the best use of a chair's time. Replace it with a decision paper, a proposed agenda and a chair's sign-off by correspondence. Meet only if the agenda itself is contested or if sensitive sequencing needs discussion.
4. The routine member-engagement catch-up. These calls often drift between anecdote and activity reporting. Replace the routine version with a quarterly pulse survey, a written engagement note and an asynchronous member panel. Convene a live session only when a specific decision about the member offer is on the table.
5. The cross-team project status call. If the only output is a round of updates, a shared exception tracker will do the job. Replace the standing call with a written tracker that flags red items, decisions needed and owners. Meet only on the exceptions. This is not a retreat from accountability; it is a sharper form of it.
The tests: keep, replace or cancel
Before cancelling anything, apply four tests.
Decision test. Does the meeting make a decision, exercise a formal power or record a vote? If not, it is a candidate for written update. Accountability test. Does it provide scrutiny that cannot be achieved in writing? Sensitive negotiations, complex trade-offs and formal challenge may need a room. Inclusion test. Does synchronous discussion materially improve the quality of input? If the same views can be gathered asynchronously, the meeting is optional. Cost test. What is the attendee cost in hours per year, and what outcome does it produce? A 60-minute monthly meeting with 12 people consumes 144 person-hours a year. That is a budget line, even if it never appears in the accounts.
If a meeting fails all four tests, cancel it. If it is information-only, replace it. If it makes decisions but can document them asynchronously, redesign it. If it is formal, statutory or genuinely deliberative, keep it but trim the information items.
Running a meeting audit
A practical audit can be completed in a fortnight. List every recurring meeting in one spreadsheet. For each, record the owner, purpose, frequency, duration, attendee count, last three decisions, and the written alternative. Calculate attendee hours per year. Ask the owner to justify the meeting against the four tests. Then assign one of three verdicts: keep, replace or cancel.
The exercise often reveals that a small number of meetings carry most of the decision value, while a longer tail carries most of the diary burden. The tail is where the savings are. It is also where member volunteers are most likely to feel that their time is being wasted.
Switching to asynchronous updates: a short template
An asynchronous update needs more discipline than a meeting, not less. Use a consistent structure:
Subject: For decision or For information: [topic] Decision needed by: [date and time] Background: Three sentences maximum. Options and recommendation: Two options, one recommendation. Risks and mitigations: Brief and specific. Responses: Where to record comments and by when. Decision log: Link to the record of the outcome.
Set three rules. One owner is accountable for the update. One deadline applies. One place holds the responses and the decision record. Silence is not consent for a decision; if a formal decision is required, the chair or board must record it in line with the association's governance arrangements.
What to keep
Cancel the agenda, not the accountability. Keep meetings that do something writing cannot: formal scrutiny, sensitive negotiation, complex trade-offs and relationship repair. Keep the annual general meeting and any statutory sessions. Keep the board when it is genuinely deciding, challenging or protecting the organisation.
For everything else, ask a simpler question in 2026: if this meeting disappeared, what would be lost? If the answer is only a habit, retire it. If the answer is a decision, a relationship or a safeguard, keep it and make it earn its place.
