How to build a Strategic Meetings Management programme

A Strategic Meetings Management programme is not a document, a system or a policy. It is a small collection of working parts — a route in, a brief template, a set of thresholds, a supplier list, a data set, a report and a forum that looks at it — arranged so that one feeds the next.

This guide is about those parts. What each one contains, in what order to build them, and the decisions that are easy to get wrong because they look administrative and are not.

It is deliberately separate from implementing Strategic Meetings Management, which covers the organisational side: sponsorship, sequencing, pilots, resistance and pace. That page is about how a programme gets adopted. This one is about how it gets built. You will need both, and most people find the implementation page more useful once they have read this and know what they are actually constructing.

These eleven pieces are built roughly in this order because each depends on what the previous one produces. You cannot set thresholds without a baseline, or build a supplier shortlist without knowing who is already being used.

This is harder than it sounds and it is the single decision most often made by accident. Everything downstream inherits it: the baseline, the reporting, the thresholds, and every argument you will later have about whether something should have gone through the programme.

The difficulty is that meetings and events do not have a natural boundary. A two-hour client briefing in a hired room is obviously in scope. A team lunch on a corporate card probably is not. Between those sit training days, away days, recruitment assessment centres, board meetings held offsite, client entertainment, exhibition stands, internal conferences, town halls and the hybrid arrangement where forty people dial in and twelve travel.

Write a scope statement. It should fit on one page and it should be specific enough that a department head reading it can tell, without ringing anyone, whether their event is in.

Name an adjudicator in the scope statement — normally the programme owner — and give them the authority to rule on edge cases without convening anyone. Scope arguments that require a meeting to resolve are the fastest way to make the programme feel bureaucratic.

Expect to revise this at the first review. The initial version will be wrong in two or three places, and the places it is wrong are useful information.

The baseline is the picture of what is happening now, and it is the thing you will be measured against for the next two years. Build it early, build it honestly, and state its limits in the same document.

It will be incomplete. Meetings spend hides in accounts payable under venue names that look like hotels, in card transactions coded to entertainment, in travel bookings, in catering invoices and in departmental budgets that never touch a purchase order. The full method is set out in how to measure meetings spend; for the purpose of building the programme you need four things.

Three shapes are common. The choice is driven by geography, volume and how much internal capacity exists — not by which sounds most impressive in a steering group.

Most organisations end up at hub and spoke, and most of those start closer to fully central for a pilot group before widening. If you are choosing between the first and the third, the question is not which gives more control but which you can actually staff. A central model without the people behind it produces worse outcomes than a well-specified local one. Decentralised meetings management covers the case where full centralisation is not realistic at all.

Whichever you pick, write down what sits centrally and what stays local. Ambiguity here is what causes people to ring a venue directly — not disobedience, but genuine uncertainty about who they were supposed to ask.

One route in. That is the entire principle, and it is worth more than any other single element of the programme, because it is the point at which data gets captured while somebody still cares about the meeting.

The route can be a form, a shared mailbox, a ticket queue or a page on the intranet. What matters is that there is exactly one, that everybody knows what it is, and that using it is faster than the alternative.

The change-management side of getting people to use it is covered properly in centralising meetings and events. The construction point is narrower: build the response commitment into the route before you announce it, because the first week sets the reputation.

The brief template is the most load-bearing artefact in the programme. It determines what you can source well, what you can report on and what you will be able to compare in twelve months. Get it wrong and every downstream problem traces back to it.

The design tension is real: every field you add improves the data and reduces the number of people willing to complete it. Keep the mandatory set short enough to complete in five minutes, and make the rest optional or filled in by the programme team during the first conversation.

Two fields earn their place more than the others and are the ones most commonly missing. Date flexibility is the largest commercial lever available in venue sourcing and requesters almost never volunteer it. Decision date is what makes a held option worth anything; without it you are collecting quotations rather than securing availability.

Resist the temptation to add fields because somebody might find them interesting. Every field needs a named person who will use it for a named purpose. If nobody can say who reads a field, remove it.

Thresholds tell people what must be authorised before the organisation is committed. The construction rule is simple and frequently ignored: mirror the authority levels the business already uses for other expenditure.

A programme that invents its own thresholds creates a second, parallel authority scheme that finance does not recognise and nobody can remember. A programme that reuses existing delegated authority is immediately legible, and the argument about whether a threshold is right has already been had by somebody else.

The full workflow, including where approval sits relative to sourcing, is covered on the meetings approval process. The construction point here is to write the thresholds into the scope statement at the same time as the scope itself, because the two together define what the programme actually governs.

Build this from the baseline. Not from a blank page, not from a list an agency supplied, and not from a shortlist somebody assembled two years ago for a different purpose.

The reason is credibility. A preferred list derived from your own usage data is defensible to the departments that have to use it, because it contains the venues they already chose. A list assembled centrally without reference to actual usage tends to exclude somebody’s favourite venue for no stated reason, and that single omission is enough for a department to dismiss the whole thing.

How the list is then maintained, reviewed and performance-managed is supplier management, and the specific mechanics of building and running a venue list are on preferred venue programme. The negotiation itself sits with venue procurement.

Contract standards are the least interesting artefact to build and the one most likely to be cited approvingly after something goes wrong. They exist because venue contracts carry commitments that non-specialists accept without recognising them.

What you are producing is a short internal standard — minimum acceptable terms, positions to challenge, and a named list of people who may sign.

The data set is the small group of fields recorded for every meeting, without exception, in the same form every time. Its value is entirely in the consistency: a modest set captured identically for two years is worth far more than a rich set captured differently each quarter.

Most of it comes directly from the brief template, which is why the brief is built first. What gets added afterwards is outcome data — what was actually committed, what it actually cost, and what happened.

Two rules make this survive contact with reality. Define each field once, in writing, including what it excludes — “contracted value” means nothing until somebody decides whether it includes VAT and accommodation. And never change a definition mid-year; add a new field instead, and note the change, so that the comparison holds.

What to capture and why is set out in full on meetings data and reporting.

The reporting pack is what the programme produces for the rest of the organisation. Build it small. A one-page summary delivered every month without fail is worth more than a comprehensive pack delivered twice and then quietly abandoned.

Design it backwards from the audience. Ask each recipient what decision they would make differently if they had a particular number, and drop anything that survives that question badly.

Which measures are worth tracking over time, and which are vanity, is covered on meetings KPIs. The construction rule: every report needs a named recipient and a named date, and the first one should go out while it is still thin. A report that starts late is a report nobody is expecting.

The governance forum is the body that can change the programme. Without one, the framework is fixed at the moment of launch and gradually diverges from how the organisation actually operates until people work around it.

It does not need to be large or frequent. Quarterly is usually right. What it needs is the authority to alter policy, thresholds, scope and supplier arrangements without escalating, and enough seniority that a department cannot simply ignore its decisions.

Who sits on it and how it relates to existing procurement governance is covered on meetings governance. Alongside the forum, set an annual review date in the calendar now, at which the scope statement, the meetings policy, the thresholds and the supplier arrangements are all reopened whether or not anybody has complained about them.

A built programme is a surprisingly short list of things. If you have these, you have one; if any is missing, you have a partial framework and you will feel the gap within a quarter.

Most people constructing this are doing it alongside a full job. If you can only build three things, build the scope statement, the intake route with its response commitment, and the brief template.

Those three produce captured data from the first week, and captured data is what makes every subsequent argument — about suppliers, thresholds, resourcing or a business case — concrete rather than theoretical. Everything else can be assembled later from what they generate.

One route in, better visibility out. The rest of the programme is built on the back of that, not alongside it.