Why Strategic Meetings Management?

Ask a Head of Procurement how the organisation buys IT, professional services or facilities and you will get a clear answer: a category owner, a supplier list, contract terms, a review cycle. Ask how it buys meetings and events and the answer is usually a pause, followed by a description of what one particular department does.

That is not an oversight by the people involved. It is structural, and worth understanding before arguing for a remedy. This page is about whether the remedy is warranted; what that remedy consists of is set out separately.

Procurement governance is built around size and predictability. A category gets attention when the spend is large enough to justify the effort, concentrated enough to negotiate against, and visible enough to notice. Meetings fail all three tests individually and pass all three collectively.

The spend arrives in small pieces — a training day, an away day, a client dinner, a regional sales meeting — each below the threshold that would trigger a sourcing exercise, each urgent, each commissioned by someone whose job is not buying. Nobody has done anything wrong by booking a venue for eighty people next month. The problem is that forty people did the same thing this year and nobody added it up.

It also arrives from everywhere: marketing, HR, sales, learning and development, executive support, regional offices. There is no single requisitioner, no obvious owner, and frequently no cost centre that captures it all. By the time the category becomes visible it is an invoice — the one point in the process where none of the decisions can be changed.

We are not going to attach a percentage to this. Any figure we published would be either someone else’s research restated or a number invented to be persuasive, and neither would tell you anything about your organisation. What can be described honestly is the shape of the cost.

Not a dashboard — a defensible number. The difference between “we think meetings are around this much” and a figure you can put in front of a board with the workings attached is the difference between a conversation about opinions and one about facts.

Visibility also has a tense problem. Most organisations can produce historic spend with enough effort; very few can see what has already been committed for the next nine months. Spend visibility is where this starts.

Aggregation changes the conversation with suppliers, but the more reliable gain is consistency. A preferred venue programme settles rate, inclusions and contract terms in advance, so an individual booking applies an agreed position rather than opening a fresh negotiation at a fortnight’s notice.

We will not promise a saving, because the answer depends on what you do now. An organisation already using a small number of venues on negotiated terms has less to gain than one using forty at standard rates. Meetings procurement covers the mechanics.

A consistent process is usually argued for on compliance grounds and delivers most of its value elsewhere. With one route in, the people raising requirements stop having to work out who to ask, what they may spend and whether they need approval — which is where a surprising amount of internal time goes.

It also makes exceptions visible: a process nobody follows cannot distinguish a considered exception from a bypass. Meetings policy and the approval process are where this is defined.

Visibility tells you what was spent. Insight tells you what the pattern means: which events recur without anyone reconsidering them, which departments book late and pay for it, where the same requirement is met three different ways.

It is the slowest benefit to arrive, because it needs a period of consistently captured data, and the one that keeps producing value after the initial gains are taken. Meetings data and reporting and meetings KPIs.

Centralisation has genuine costs, and a business case that does not acknowledge them tends to fail at the first sceptical question. Three objections are worth answering properly.

It makes simple things slower. Often true, and the fastest way to lose a programme. If booking a room for six people now requires a form, an approval and a two-day turnaround, people will route around it and be right to. The answer is proportionality: a fast lane for routine requirements, structure where the value or the risk justifies it.

Internal resistance is real, not irrational. A department that has used the same venue for five years has a relationship, knows the room and gets a good result. Telling them a central route knows better, without evidence, is not persuasive. Demonstrate on their next requirement rather than mandate, and let the preferred arrangement include the venue they like where it stands up commercially.

It is a process someone has to own. A programme is not self-sustaining. Someone maintains supplier arrangements, reviews the policy, runs the reporting and handles exceptions. If nobody has capacity, the programme decays into a document and the organisation is worse off, because it now believes it has one. That is a fair argument for outsourcing part of it, and an equally fair argument for not starting until ownership is settled.

It tends to be worth it when meetings activity is spread across several departments or offices, when the annual total is significant enough that a finance or procurement lead has asked about it, and when nobody can currently answer basic questions about the portfolio without a data-gathering exercise.

It tends not to be worth it when activity is genuinely low volume, when it is already concentrated in one capable team with good supplier arrangements and reliable records, or when the organisation is mid-way through something — a merger, a finance system replacement — that will change the answer within a year. In that last case, improve data capture now and design the programme afterwards.

There is an honest middle case too. Some organisations need better sourcing and do not need governance at all; buying help with venues is a legitimate answer, and dressing it up as a programme adds cost without adding much. Is SMM right for your business? separates these cases in ten questions.