What We Found When We Actually Looked at How a Meeting Got Organised

Nobody thinks of scheduling a meeting as a significant drain on organisational time. It's just something that happens — a few emails back and forth, a calendar invite, done. Except in most organisations, it isn't quite that simple.

A department head at a medium-sized organisation asked us to look at why her team's calendar felt so chaotic. Meetings were being booked with little notice. Key people were regularly unavailable at the times chosen. Preparation materials arrived late or not at all. And a surprisingly large number of meetings ended without clear outcomes, which meant follow-up conversations to agree what had actually been decided.

When we looked at how meetings were actually being organised, the hidden cost became visible almost immediately.

The typical process went something like this. Someone decided a meeting was needed and sent an email to find a time. The replies came back over the following day or two — "I can't do Tuesday", "Thursday works for me but not after 3", "any day except Wednesday". The organiser consolidated the responses, identified a slot that seemed to work for most people, and sent a calendar invite. Two people then replied to say they had a conflict. A new time was found. The invite was updated.

By the time the meeting was in everyone's diary, an average of fourteen emails had been exchanged to organise it. The meeting itself was forty-five minutes. The preparation for organising it — not preparing content, just finding a time — had consumed nearly as much collective time as the meeting would.

And that was before accounting for meetings that were scheduled without checking anyone's actual availability, because the organiser had given up on the email exchange and just picked a time and hoped.

The organisation had Microsoft 365, which meant they had Bookings, shared calendar visibility, and the ability to see free and busy time across the team. Almost none of it was being used.

We made three changes. First, shared calendars were configured properly so that everyone could see their colleagues' availability without sending an email to ask. Second, for recurring internal meetings, a simple Bookings page was set up so that team members could book time directly without any back-and-forth. Third — and most importantly — a short, clear norm was established: meeting invites should include an agenda and any preparation materials at the point of sending, not the morning of.

That third change was the most significant. It sounds obvious. In practice, it almost never happened, because nobody had ever said it out loud as an expectation.

The email volume around meeting scheduling dropped noticeably within a fortnight. Meetings started with people who had had a chance to prepare. Outcomes were clearer because the agenda had been visible in advance and people had thought about it.

The hours saved on scheduling were modest — but the improvement in the quality of the meetings themselves was harder to put a number on and probably more valuable. Meetings where people arrive prepared and the purpose is clear make better decisions in less time. That compounds across every week of the year.

Scheduling is one of those processes that organisations never examine because it feels too small to be worth examining. That's exactly why it's worth examining.