There are two entirely different measurement questions in meetings and events, and conflating them wastes effort.
The first is whether the meetings function is well run: are requirements reaching the right people early enough, are suppliers used sensibly, does activity follow the agreed route. That is this page. The second is whether an individual meeting was worth holding — a different discipline with different evidence, dealt with on measuring meeting ROI.
A programme can score excellently on every metric below while running events nobody needed. These measure the efficiency of the buying, not the merit of the decision.
What a programme KPI is for
A KPI earns its place if a plausible movement in it would cause someone to do something different. That is stricter than it sounds, and most candidates fail it.
Before adopting a measure, answer three questions. What would a good number look like? What would we do if it moved against us? Who has authority to act? A metric with no answer to the third is reporting, not measurement.
The measures worth considering
The third column matters as much as the second. Every measure below can be read the wrong way, and most have been used to support a conclusion the data did not carry.
Number of meetings and events
- What it shows
- Scale of demand, and the denominator for most other measures.
- How it misleads
- Treats a two-hour room hire and a three-day conference as equivalent. Early on, a rising count means better capture, not growth.
- Typical source
- Programme record
Departments commissioning meetings
- What it shows
- How distributed demand is, and how fragmented the buying is.
- How it misleads
- Says nothing about value. One department may hold the money while ten hold the transactions.
- Typical source
- Programme record, cost centre coding
Total and average booking value
- What it shows
- Where the money sits, and which segment justifies procurement attention.
- How it misleads
- Averages hide the distribution. A few large events drag the mean above almost every booking.
- Typical source
- Contract records, purchase ledger
Supplier count and concentration
- What it shows
- Whether volume is aggregated enough to negotiate with.
- How it misleads
- Badly inflated by inconsistent supplier naming. Low concentration is not automatically bad.
- Typical source
- Purchase ledger, contract records
Venue usage and repeat bookings
- What it shows
- Which venues the organisation relies on — evidence for a preferred venue programme.
- How it misleads
- Repeat usage often reflects habit or proximity. Frequency is not endorsement.
- Typical source
- Programme record
Lead time from brief to event
- What it shows
- How much room the programme has to buy well. Usually the most actionable single measure.
- How it misleads
- Distorted by a few long-planned annual events. Report the distribution, not the average.
- Typical source
- Programme record
Cancellation and postponement
- What it shows
- Money lost to change, and whether causes are systemic.
- How it misleads
- Meaningless without reasons. A rate driven by one restructuring is a different problem from habitual over-booking.
- Typical source
- Contract records, variance reasons
Negotiated value and avoided cost
- What it shows
- What sourcing contributes beyond administration.
- How it misleads
- The most abused measure here. It depends entirely on the baseline chosen, and an undocumented baseline is not evidence.
- Typical source
- Sourcing record, proposals received
Preferred supplier adoption
- What it shows
- Whether negotiated terms are actually being used.
- How it misleads
- A low rate may mean poor compliance or an unsuitable list. Read it with the reasons for going off-list.
- Typical source
- Programme record
Route compliance
- What it shows
- What share of activity follows the agreed process — the ceiling on every other measure’s accuracy.
- How it misleads
- Improves artificially when small events are quietly excluded. Define the denominator once.
- Typical source
- Programme record against ledger
Geographical distribution
- What it shows
- Where meetings happen, informing regional supplier and accommodation arrangements.
- How it misleads
- Location of the event is not location of the demand.
- Typical source
- Programme record
Forward commitment
- What it shows
- What the organisation is already obliged to spend over twelve months.
- How it misleads
- Understates exposure if cancellation and attrition terms are not captured too.
- Typical source
- Contract records
| Measure | What it shows | How it misleads | Typical source |
|---|---|---|---|
| Number of meetings and events | Scale of demand, and the denominator for most other measures. | Treats a two-hour room hire and a three-day conference as equivalent. Early on, a rising count means better capture, not growth. | Programme record |
| Departments commissioning meetings | How distributed demand is, and how fragmented the buying is. | Says nothing about value. One department may hold the money while ten hold the transactions. | Programme record, cost centre coding |
| Total and average booking value | Where the money sits, and which segment justifies procurement attention. | Averages hide the distribution. A few large events drag the mean above almost every booking. | Contract records, purchase ledger |
| Supplier count and concentration | Whether volume is aggregated enough to negotiate with. | Badly inflated by inconsistent supplier naming. Low concentration is not automatically bad. | Purchase ledger, contract records |
| Venue usage and repeat bookings | Which venues the organisation relies on — evidence for a preferred venue programme. | Repeat usage often reflects habit or proximity. Frequency is not endorsement. | Programme record |
| Lead time from brief to event | How much room the programme has to buy well. Usually the most actionable single measure. | Distorted by a few long-planned annual events. Report the distribution, not the average. | Programme record |
| Cancellation and postponement | Money lost to change, and whether causes are systemic. | Meaningless without reasons. A rate driven by one restructuring is a different problem from habitual over-booking. | Contract records, variance reasons |
| Negotiated value and avoided cost | What sourcing contributes beyond administration. | The most abused measure here. It depends entirely on the baseline chosen, and an undocumented baseline is not evidence. | Sourcing record, proposals received |
| Preferred supplier adoption | Whether negotiated terms are actually being used. | A low rate may mean poor compliance or an unsuitable list. Read it with the reasons for going off-list. | Programme record |
| Route compliance | What share of activity follows the agreed process — the ceiling on every other measure’s accuracy. | Improves artificially when small events are quietly excluded. Define the denominator once. | Programme record against ledger |
| Geographical distribution | Where meetings happen, informing regional supplier and accommodation arrangements. | Location of the event is not location of the demand. | Programme record |
| Forward commitment | What the organisation is already obliged to spend over twelve months. | Understates exposure if cancellation and attrition terms are not captured too. | Contract records |
Metrics that decide, metrics that decorate
The measures that change decisions are lead time, supplier concentration, route compliance, preferred supplier adoption, variance with reasons, and forward commitment. Each, when it moves, points at a specific intervention: brief earlier, consolidate suppliers, fix the process, tighten contracting. Several feed into supplier management and meetings compliance.
The measures that mostly decorate are event count, attendee headcount, average booking value in isolation, and any savings figure without a documented baseline. They are context, and context presented as performance is how a programme ends up reporting confidently on its own irrelevance.
Keep those in an appendix and put six decision-changing measures on the front page — the basis of the reporting set on event spend reporting.
Baselines, targets and the first year
Setting targets before you have a baseline is guessing. Measure for a full booking cycle, publish without targets, then agree what good looks like. A full cycle matters because meetings activity is seasonal — a programme judged on its first quarter is judged on whichever quarter it happened to start in.
Expect early numbers to look bad in a specific way: more suppliers than anyone believed, shorter lead times than anyone admitted, compliance lower than the policy implies. That is the baseline being honest — the SMM maturity model is a useful frame for reading it without treating it as a verdict.
Six questions that indicate whether your measurement is doing any work:
- 01Can you state how many meetings and events ran last year, within a reasonable margin?
- 02Do you know how many separate suppliers were used, after correcting for naming?
- 03Can you say what proportion of activity went through an agreed sourcing route?
- 04Do you know the typical lead time between a requirement being raised and the event?
- 05When an event costs more than contracted, is the reason recorded in a way you can count?
- 06For each metric you report, can you name a decision made differently because of it?
Answering “no” to most of these means measurement is a reporting obligation rather than a management tool. An SMM Review starts from exactly these questions.
Request a programme reviewFrequently asked questions
01How many KPIs should a meetings programme have?
Around six on the front page, reviewed quarterly — enough to cover demand, supply, process and commitment, few enough that each is watched. Twenty metrics reads as decoration.
02What is the single most useful metric to start with?
Lead time from brief to event. It is cheap to capture, explains much of what goes wrong commercially, and points at an intervention that costs nothing. Supplier concentration is a close second.
03Should we measure cost savings?
Only if you can document the baseline at the point of negotiation — the rate first quoted, the alternative proposals, last year’s rate for the same venue. We do not promise savings, and we are sceptical of any figure derived from a baseline built after the fact.
04How do we measure a programme when compliance is low?
Report the compliance rate alongside everything else and state the denominator. A supplier concentration figure covering part of the activity is still useful, provided nobody mistakes it for the whole. In year one, compliance is often the most important measure in its own right — see meetings spend visibility.
05Are attendee numbers a useful KPI?
As context, yes — they normalise cost comparison between events of different sizes. As a performance measure, rarely, because a programme does not control how many people are invited.
06Where do policy measures fit?
Route compliance and preferred supplier adoption are policy measures as much as commercial ones, and belong in whatever review governs the meetings policy. The point is to find out whether the policy is workable, not only whether people obey it.
Related reading
- 01ValueMeasuring meeting ROIThe other measurement question: was the meeting worth holding?
- 02The data modelMeetings data and reportingThe fields these measures depend on, and how to keep them consistent.
- 03ReportingEvent spend reportingHow measures are packaged for procurement, finance and department heads.
- 04GuideHow to measure meetings spendBuilding the baseline every metric here is calculated against.
- 05The disciplineWhat is Strategic Meetings Management?The full explanation of the discipline this page sits inside.