What is Strategic Meetings Management?

Strategic Meetings Management is the practice of managing all of an organisation’s meetings and events as one coordinated programme, rather than as a stream of separate, unconnected purchases. One route in for requirements, one consistent way of sourcing, approving and contracting them, and one set of reliable data coming out the other end.

That is the whole idea. Everything else — policy, thresholds, preferred suppliers, reporting, technology — is machinery built to make it work at your scale. The machinery is where people get lost, because much of the writing on the subject describes the apparatus of an enterprise programme as though it were the concept itself.

Most organisations do not arrive here because somebody read an article. They arrive because a Finance Director asked what the business spends on meetings and nobody could answer — or because the same venue turned out to have been booked three times in a year, by three departments, on three sets of terms.

SMM stands for Strategic Meetings Management. SMMP stands for Strategic Meetings Management Programme — the running thing an organisation puts in place, as distinct from the discipline in the abstract. The two get used interchangeably, and little harm comes of it.

The term came out of the United States in the early 2000s, from the corporate travel world: organisations that had brought air, hotel and ground transport under managed programmes noticed that meetings, often a comparable amount of money, sat outside that discipline entirely. The UK adopted the language more slowly, and the same idea is still called meetings management or corporate meetings management.

Be clear which meetings this covers, because the word does a lot of work. Strategic Meetings Management has nothing to say about your Tuesday morning team catch-up. It concerns meetings that consume external money and carry external obligations: conferences, training, sales kick-offs, client seminars, off-site board meetings, exhibitions, hospitality. If it involves a venue, a supplier, a contract, delegates or an invoice, it is in scope.

Picture an illustrative organisation: a 900-person professional services firm with four UK offices. It is invented to explain the idea, but the shape will be familiar to anyone who has looked closely at this category.

Each office arranges its own training days. Marketing runs client seminars. HR organises an annual conference. Partners book private dining. Business development takes stands at two or three exhibitions. Nobody has written down the full list, because no single person has had reason to.

Finance sees the money, but not as meetings: it arrives coded to training, marketing, business development, travel and subsistence, and general overhead. Procurement has never run a category review, because as far as the coding structure is concerned there is no category. Venues are chosen from memory or from whichever agency answered the phone, and contracts are signed by whoever raised the requirement.

None of this is anyone behaving badly. Each individual decision is defensible. The problem exists only at the level of the whole — precisely the level at which nobody is looking.

Follow one requirement through. Someone in the Manchester office needs a venue for sixty people, two days, next March, with overnight rooms for about half. In an unmanaged organisation, that person starts searching. In a programme, that person submits a brief — and from there the requirement is handled by a defined process rather than by whoever picked it up.

Run that sequence a hundred times and something appears that no individual booking could produce: you know what you buy, from whom, how often, at what price and to what standard. One route in. Better visibility out.

Programmes vary enormously in depth. A mid-market organisation might run six of the components below properly and leave the rest alone; a global business might run all of them with a team behind each. Starting with everything at once is a reliable way to finish with nothing.

Only two of those nine are about buying. Strategic Meetings Management is often mistaken for a purchasing exercise — but a programme that improves rates while leaving the organisation just as blind to its own activity has solved the smaller half of the problem.

A programme is a lifecycle rather than a project, because the work does not stop once the framework exists.

Organisations rarely move through these stages cleanly, and almost never all at once. The SMM maturity model sets out the five levels organisations typically occupy — a more honest way of locating yourself than asking whether you “have SMM” as a yes-or-no question.

This is the part most providers skip. A programme carries real overhead: process design, internal agreement, somebody’s time, and a period during which the new route feels slower than the old habit. If the prize does not comfortably exceed that overhead, it is not worth doing.

A single-site organisation running four events a year, where one capable person books everything and knows what it costs, already has a managed programme. It simply lives in one person’s head, and the sensible improvement there is succession planning, not governance. The picture changes when activity is distributed: once meetings are commissioned from several places at once, the organisation loses the one thing holding it together.

The organisations that benefit most sit in the middle: large enough that activity has genuinely fragmented, not so large that an enterprise infrastructure already exists. That is the territory of mid-market Strategic Meetings Management. Distributed structures raise the stakes further — the subject of multi-office meetings management and decentralised meetings management — and regulated sectors tend to reach the same conclusion through compliance rather than cost.

Return to the illustrative 900-person firm. Nothing about the organisation changes — same offices, same events, same people, same budget. What changes is the route those events travel.

This is the most common confusion on the subject, and it matters commercially, because the two are bought from different budgets to solve different problems. Event management is the delivery of an individual event. Strategic Meetings Management is the management of the portfolio those events sit inside. You can have excellent event management and no programme whatsoever, and many organisations do.

The longer treatment, including how each is resourced and which one an organisation usually needs first, is at SMM vs event management. The related distinction between running a programme and simply having someone find venues for you is at SMM vs venue finding.

Procurement teams meet this subject from the opposite direction: not as an events problem, but as a category that has resisted the treatment every other significant spend line has already had. The obstacle is rarely resistance. It is that meetings spend cannot be managed as a category until somebody can see it as one.

Meetings procurement is the commercial discipline applied to this spend — supplier selection, negotiation, contract terms, rate structures. It is a substantial component of a programme, not the whole of it, because a programme also governs what gets commissioned in the first place and procurement rarely holds a mandate over that. The distinction is at SMM vs event procurement, and the numbers side at meetings spend management.

If your immediate need is the buying rather than the governance — better rates, stronger terms, a competitive process for a defined set of requirements — our sister resource Event Procurement goes considerably deeper on sourcing and supplier negotiation than this site does, and is often the more useful place to start.

No. That is worth stating flatly, because much of the material published on SMM comes from companies selling meetings management software, and it consistently conflates the discipline with the tooling.

Strategic Meetings Management is a process discipline. It requires that the same information is captured consistently, that requirements follow a defined route, and that somebody is accountable for both. None of those is a software feature. An organisation with a well-designed request form, a shared inbox, a maintained spreadsheet and a real owner is running a programme. An organisation with an expensive platform that half the business bypasses is not.

Large enterprise programmes do often involve technology, sensibly so: at thousands of meetings a year across multiple countries, manual capture stops being viable and dedicated platforms exist precisely for that. Most UK organisations considering this are not at that scale, and the honest sequence is process first, tooling second. Design the programme, run it, find where the manual effort actually hurts, then buy something to solve that specific problem. Buying the platform first tends to produce an implementation project in place of a programme.

Data is where a programme stops being an administrative tidying exercise and becomes commercially useful. The aim is not to capture everything. It is to capture the same small set of things every single time, so that a year later you have something countable.

Eight fields captured consistently tell you more after twelve months than a forty-field form people abandon halfway through. Start narrow: adding a field later is easy, recovering a year of data nobody captured is not. Turning this into regular output is covered at meetings data and reporting, with a practical method at how to measure meetings spend.

Two of these fields carry obligations beyond the commercial. Delegate information is personal data, and attendance records feed directly into duty of care and meetings risk management. How that data is collected, stored, shared with venues and retained is a question for your own data protection and legal advisers — a programme should apply the position they set, not invent one.

A meetings policy states the rules: what falls in scope, what must come through the programme, who may commit spend and at what level, which standards apply, and how exceptions are handled when something legitimately cannot follow the route.

The common failure is length — a twenty-page policy nobody has read is worth less than a two-page one people can find and follow. The second is writing it before establishing what currently happens, which produces rules describing an organisation nobody recognises. Guidance is at meetings policy, with a drafting method at creating a corporate meetings policy. Where a policy touches employment terms, expenses, anti-bribery obligations or hospitality rules, have your own legal and compliance function review it before issue.

Implementation is less about design than adoption. The framework can be drawn up in weeks; persuading four offices to stop doing what they have always done is what sets the timeline.

The approaches that work begin with a defined subset of activity rather than the whole estate. They make the new route demonstrably easier than the old one, because a route that is merely mandatory gets worked around. They secure a sponsor senior enough that “we did it our way” is not a viable answer. And they report something useful early, so the programme has evidence of its own value before anyone asks. The sequence is at implementing Strategic Meetings Management, step by step at how to build an SMM programme. If the immediate task is persuading a board, start with building the business case.

Programmes get judged on cost, which is understandable and incomplete. Cost is the easiest thing to measure and rarely the most interesting thing a programme produces.

A reasonable measurement set covers commercial performance (rates, terms, variance against budget), process performance (how much activity came through the route, and how quickly), compliance (how much of it followed policy) and outcome (whether the meetings achieved what they were commissioned to achieve). The fourth is the hardest and the most worth attempting. Indicators and how to define them are at meetings KPIs; the harder question of whether a meeting was worth holding at all is examined at measuring meeting ROI.