The abbreviation SMMP gets used for three things: a way of thinking about meetings spend, a category of technology, and an actual programme with documents and owners behind it. This page is about the third.
If you want the discipline explained, what is Strategic Meetings Management does that. If you need the sequence for standing one up, that is implementing Strategic Meetings Management. What follows is the anatomy — what a programme is made of, who holds each part, and what you would point at if somebody asked to see yours.
An SMMP is a defined set of arrangements
Definition
Strategic Meetings Management Programme (SMMP)
The formal structure through which an organisation commissions, buys, approves, records and reviews its meetings and events. It exists as named arrangements — policy, briefing route, thresholds, supplier terms, data standards, reporting and governance — rather than as an intention.
The test is blunt: if the person who set it up left tomorrow, would it still run? If not, what you have is a capable individual, not a programme.
That test matters. Many organisations have someone — in executive support, procurement or an events team — who quietly holds the whole thing together: which venues work, which rates are reasonable, who to call when a room falls through. None of it is written down, and it works right up until that person changes role.
The constituent parts
A working SMMP is assembled from nine components. Not all nine need formalising on day one, but a decision has to be made about each — including the decision to leave one deliberately loose.
Briefing route
- What it is
- The single defined way a requirement enters the programme — a form, a mailbox, a request type. One route in.
- Usually owned by
- Programme owner
Meetings policy
- What it is
- The written rules: what is in scope, what is permitted, what must be authorised. See meetings policy.
- Usually owned by
- Procurement, with HR and Finance
Approval thresholds
- What it is
- Value, headcount and meeting-type triggers deciding who signs off and when. See approval process.
- Usually owned by
- Finance
Preferred supplier arrangements
- What it is
- The agreed venues and suppliers, and what they have committed to. See preferred venue programme.
- Usually owned by
- Procurement
Contract standards
- What it is
- Standard terms, your position on cancellation and attrition, and who may sign.
- Usually owned by
- Legal, with Procurement
Data capture fields
- What it is
- The fields recorded for every meeting — cost centre, numbers, venue, category, purpose — regardless of size.
- Usually owned by
- Programme owner
Reporting cycle
- What it is
- What is reported, to whom, how often. See meetings data and reporting.
- Usually owned by
- Programme owner
Ownership and governance
- What it is
- The named individual accountable, and the forum that reviews it. See meetings governance.
- Usually owned by
- Executive sponsor
Review cadence
- What it is
- The scheduled points at which policy, thresholds and suppliers are reopened rather than left to drift.
- Usually owned by
- Governance forum
| Component | What it is | Usually owned by |
|---|---|---|
| Briefing route | The single defined way a requirement enters the programme — a form, a mailbox, a request type. One route in. | Programme owner |
| Meetings policy | The written rules: what is in scope, what is permitted, what must be authorised. See meetings policy. | Procurement, with HR and Finance |
| Approval thresholds | Value, headcount and meeting-type triggers deciding who signs off and when. See approval process. | Finance |
| Preferred supplier arrangements | The agreed venues and suppliers, and what they have committed to. See preferred venue programme. | Procurement |
| Contract standards | Standard terms, your position on cancellation and attrition, and who may sign. | Legal, with Procurement |
| Data capture fields | The fields recorded for every meeting — cost centre, numbers, venue, category, purpose — regardless of size. | Programme owner |
| Reporting cycle | What is reported, to whom, how often. See meetings data and reporting. | Programme owner |
| Ownership and governance | The named individual accountable, and the forum that reviews it. See meetings governance. | Executive sponsor |
| Review cadence | The scheduled points at which policy, thresholds and suppliers are reopened rather than left to drift. | Governance forum |
How the parts fit together
Employees and departments
A requirement exists: a conference, a training day, a board meeting, a client event.
Central meetings process
One brief, one route, one set of rules about what happens next.
Venues, suppliers and event delivery
Sourcing, negotiation, contracting and — where needed — running the event itself.
Data capture
What was requested, what was bought, from whom, at what value, on what terms.
Procurement and finance reporting
Programme-level information that can be reviewed, challenged and acted on.
The reporting layer feeds back into the central process. That feedback loop is the difference between collecting data and managing a programme.
Read left to right, the components stop looking like a governance wish-list and start looking like a route. A requirement arrives. Policy and thresholds decide what happens to it. Sourcing runs against the preferred supplier arrangements. Contract standards govern what gets signed. The data fields are captured as a by-product of the booking.
That last link is the one most often missing. Organisations frequently have a policy and no data, which means the policy cannot be enforced or even evidenced. Meetings spend visibility is what makes every other component real.
Who owns an SMMP
Ownership stalls more programmes than any technical issue. Meetings spend sits across procurement, finance, HR, marketing and whichever department is running the event this week, and none of them naturally owns the category.
- Executive sponsor — usually a COO, Finance Director or Procurement Director. The authority that makes the briefing route mandatory rather than optional.
- Programme owner — the named person who runs it. Often procurement, sometimes an events function, sometimes an external team.
- Category ownership — procurement holds the supplier relationships, as for any other category. See meetings procurement.
- Budget holders — department heads keep the budget and the decision on whether a meeting happens. A programme changes how they buy, not whether they may meet.
- Governance forum — a small, scheduled group reviewing performance, exceptions and suppliers. Quarterly is usually enough.
What a programme looks like on paper
To know whether an organisation has an SMMP, ask to see the documents. A real programme produces a specific set:
- The meetings policy, dated and with a named owner.
- An approval matrix — thresholds, approvers, escalation triggers.
- A briefing template, with mandatory fields marked.
- The preferred supplier list, with terms attached rather than just names.
- Contract standards: what the organisation will and will not accept.
- A data dictionary, so “delegate” means the same thing in every report.
- The standing reporting pack and its distribution list.
- Terms of reference for the governance forum, including review cadence.
That is a realistic full set, not an aspirational one. Most organisations starting out have two or three and a shared drive of things that nearly count. The Strategic Meetings Management checklist is a faster way to see which you have.
How organisations actually develop one
Programmes are assembled rather than designed. Almost nobody starts from a blank page: there is already an informal preferred venue, an unofficial approval habit and a spreadsheet somebody maintains. The first version is usually that behaviour written down and given an owner. What changes as it matures is not the number of components but how many are defined rather than assumed — the SMM maturity model sets out that progression.
One caution. A programme built policy-first, with no data and no sourcing capability behind it, produces a document nobody follows. Starting with the briefing route and the data fields gives you something to govern.
What an SMMP is not
- Not a technology platform. Software can hold a programme but cannot be one. A system bought before the policy and data fields are agreed gets configured around the old process.
- Not a ban on meeting. A programme that reduces the number of meetings an organisation holds has answered a different question from the one it was asked.
- Not a centralised events team. Centralising the buying is not centralising the delivery. See centralising meetings and events and SMM vs event management.
- Not a savings target with a number attached. A programme makes the commercial position visible enough to act on. What that turns into depends on what the visibility reveals.
Frequently asked questions
01What is the difference between SMM and an SMMP?
SMM is the discipline: managing meetings as a portfolio rather than a series of unrelated purchases. An SMMP is one organisation’s implementation of it — the actual policy, route, thresholds, supplier arrangements and reporting. SMM is the idea; the SMMP is the thing you can point at.
02How big does an organisation need to be to justify a programme?
Size matters less than fragmentation. A 300-person business with four offices each sourcing its own training days has a clearer case than a 2,000-person business where everything routes through one competent team. Is SMM right for your business? works through it in ten questions.
03Do we need software to run an SMMP?
No. Many working programmes run on a defined form, a shared register and a quarterly report. What matters is consistent capture of an agreed set of fields; whether they live in a specialist platform, your finance system or a well-governed spreadsheet is a separate decision.
04Who should own the programme internally?
Procurement most often, because category discipline and contract standards sit there naturally. Ownership by an events or executive-support function works where that team already sees most of the activity. What does not work is joint ownership with no named individual.
05Can a programme cover only part of the organisation?
Yes, and one region, division or meeting type is often the sensible start. It produces real data and a precedent. The risk is that a partial programme becomes permanent by default — see multi-office meetings management.
Related reading
- 01The disciplineWhat is Strategic Meetings Management?The discipline, rather than the programme structure.
- 02SequencingImplementing SMMThe sequence for standing a programme up.
- 03GuideHow to build an SMM programmeA step-by-step guide to the components.
- 04Our frameworkThe SMM maturity modelFive levels, and what each looks like.