Diary Debt: A 90-Minute Reckoning for Recurring Meetings
Recurring meetings are rarely reviewed with the same rigour as a supplier contract or a capital request. They arrive through a sensible request, acquire a standing slot and then persist long after the original purpose has been served. The result is a form of organisational debt: a recurring obligation that consumes capacity every week, compounds in small increments and is almost invisible on the management accounts.
For UK organisations under pressure to raise productivity without simply adding hours, the diary is one of the few places where capacity can be recovered without redundancy or restructuring. The case for an audit is therefore practical rather than ideological. It is about establishing what the organisation is paying for, what it still needs and what can be replaced by clearer decision rights or asynchronous working.
Why recurring diaries behave like debt
A one-off meeting is a transaction. A recurring meeting is an annuity. Each series begins as a reasonable response to a coordination problem, but the justification is seldom revisited when the problem changes. New attendees are added to protect interests; preparatory work expands to fill the slot; adjacent meetings are created to prepare for the meeting itself.
Unlike project spend, no invoice arrives. The cost is buried in payroll, absorbed by teams and redistributed as delays elsewhere. Seniority compounds the effect. A 45-minute weekly meeting with ten well-paid participants can cost more than a modest software subscription, yet it rarely receives the same scrutiny.
A cost-per-meeting formula that survives scrutiny
The aim is not to produce a perfect accounting figure. It is to create a common language for comparing diary commitments with other calls on capacity. A defensible direct-cost formula is:
Cost per occurrence = attendees × loaded hourly cost × duration in hours + preparation cost
Loaded hourly cost should reflect salary plus employer National Insurance, pension contributions and other employment costs, divided by realistic productive hours. A multiplier of 1.25 to 1.35 on salary, divided by 1,600 to 1,700 productive hours, is a reasonable planning assumption for many UK organisations. Teams should agree the assumption once and use it consistently.
Preparation cost can be estimated as attendee hours spent on pre-reading, papers or status updates. Opportunity cost is real but should not be double-counted; it is better handled qualitatively in the triage discussion.
A worked example for a mid-sized UK organisation
Consider a UK professional services firm with 240 staff and an average salary of £44,000. Using a 1.3 loading factor and 1,650 productive hours, the loaded hourly cost is approximately £34.70.
A weekly 45-minute operations meeting has ten attendees. Direct meeting time costs about £260 per occurrence. If each attendee spends 15 minutes preparing, preparation adds roughly £87. The total is approximately £347 per week. Over 46 working weeks, the series costs about £15,960 per year.
That figure is manageable in isolation. The governance question arises when the pattern is repeated. If the firm has 30 recurring meetings of similar scale, the annual direct cost approaches £480,000. Some of that spend will be justified. Some will be legacy. The audit exists to separate the two.
The triage scorecard
A simple scorecard helps the team move from intuition to a structured conversation. Score each recurring series from 1 to 5 against five questions, where 1 is weak and 5 is strong:
| Criterion | Question |
|---|---|
| decision | Does the meeting make a decision, or only exchange information? |
| unique input | Are the attendees the people whose judgement is genuinely required? |
| cost justification | Is the value of the outcome proportionate to the direct cost? |
| async alternative | Could the information be shared or the decision prepared asynchronously? |
| cadence | Is the frequency matched to the rate at which the underlying work changes? |
A total of 20 or more suggests the meeting should be retained, subject to a clear owner and agenda discipline. A score of 13 to 19 usually indicates redesign: fewer attendees, a shorter slot, a lower frequency or a tighter decision focus. A score of 12 or below should prompt retirement or replacement, unless the meeting is required by regulation, statute or a formal governance obligation.
The 90-minute audit
The audit works best as a facilitated session with a senior sponsor and a small group that can speak for the major diary commitments. Calendar data should be handled in line with the organisation's data protection policies; aggregated patterns are usually sufficient.
Minutes 0–10: agree the scope and assumptions. Confirm the loaded hourly cost, the productive-hours assumption and the review period. Choose one business unit or function rather than the whole organisation.
Minutes 10–30: extract the recurring series. List every standing meeting, its owner, attendee count, duration, frequency and stated purpose. Include the preparatory work that surrounds it.
Minutes 30–55: apply the formula. Calculate the annual direct cost of each series. Rank them from highest to lowest. The purpose is not to shame high-cost meetings but to focus attention where the recovery is greatest.
Minutes 55–75: triage. Apply the scorecard. Assign each series to one of four actions: keep, shrink, shift or stop. Every keep decision should have a named owner and a stated decision right.
Minutes 75–90: assign changes and protections. Agree what will change before the next cycle, who will communicate it and how the team will prevent the diary from refilling. Record the decisions in the governance minutes.
Replacing meetings with decision rights and async defaults
Removing a meeting without clarifying how decisions will be made simply transfers the delay. Each retained forum should have a decision owner, a named accountable executive, a defined set of consultees and a route for informing those who do not attend. If a meeting does not make or prepare a decision, a written brief and a comment window may be sufficient.
Asynchronous alternatives work best when they are bounded. A pre-read with a clear question, a deadline and a named decision owner is more useful than an open document. A weekly decision log can replace several status updates. Office hours can absorb exceptions without recreating a standing forum.
Making the change stick
The audit should become a quarterly governance routine rather than a one-off purge. Track the number of recurring hours, the direct cost of the diary and the proportion of meetings with a recorded decision. Review new recurring requests against the same criteria. The objective is not a emptier calendar for its own sake, but a clearer link between management attention and the work that matters.
