Meetings risk management

Event risk management, as usually practised, means the risk assessment for a specific event: crowd safety, fire evacuation, electrical testing, contractor insurance. That work is necessary and it is not what this page is about.

This page is about risk that only becomes visible when you look at the whole programme at once, and which is structurally invisible where each event is arranged by whoever needed it. Risk to people is treated separately on duty of care.

Consider a hypothetical organisation running forty meetings a year across six departments. Each booking is individually modest, each contract individually reasonable, and nobody has done anything wrong.

Now ask the questions that only make sense at programme level. What is committed under contracts signed but not yet delivered? How much of that would be payable if every event were cancelled tomorrow? How much of the year’s spend sits with one hotel group? Has anyone accepted an attrition clause without knowing what attrition means?

In an organisation with no central record, none of those can be answered — not because the answer is bad but because the data does not exist in one place. That is the argument for programme-level risk management, and the same structural argument made about money on meetings spend visibility.

The table below is an illustrative structure. It is a prompt for your own risk function, not a completed assessment — the likelihood and impact of each line depend on your portfolio.

Venue contracts are not simple purchases. They routinely include a sliding cancellation scale rising towards the event date, an attrition provision on contracted room blocks, a minimum food and beverage spend, and force majeure wording determining what happens when neither party can perform.

Each is negotiable to some degree, and far more so at the point of sourcing than after a verbal agreement — the commercial argument for sequencing set out on meetings approval process.

What a programme view adds is the ability to see these terms together. If contracted exposure peaks in one quarter because three large events fall in the same period, that is worth knowing in advance. The attrition clause entry explains the mechanic; what it means for your contracts is a legal question.

There is a tension here worth stating plainly, because much writing on the subject pretends it does not exist. Consolidating volume with fewer suppliers is how a programme obtains better terms — the basis of a preferred venue programme and of meetings procurement generally. It is also, by definition, concentration.

The answer is not to avoid concentration but to make it deliberate and review it. Concentration resulting from a negotiated agreement with a supplier whose performance is monitored is a commercial decision. Concentration that emerged because one department always uses the same hotel and nobody added it up is an accident. The second is what produces unpleasant surprises.

Practically, this belongs in the quarterly review alongside supplier management.

The least discussed risk here is internal. In many organisations the practical knowledge of how meetings get arranged — which venue does what well, what rate was agreed last time, who to call — sits with one or two people, usually in executive support or a small events function.

They are typically very good at it, which is why it has not been a problem. The exposure appears the week they leave, when the organisation discovers the supplier relationships, rate history and contract copies were personal rather than institutional.

The fix is unexciting: records held centrally, agreements documented, and more than one person who understands the programme — one of the quieter arguments developed in decentralised meetings management.

Every organisation that ran events through 2020 and 2021 learned what force majeure wording was worth, and many learned it expensively. The lesson worth retaining is not a clause but a habit: at the point of contracting, someone should ask what happens if this cannot go ahead.

Programme-level continuity planning is modest work. Know who decides whether an event proceeds. Know the cancellation position on each committed booking and when each scale steps up. Know which events could run in a different format and which are contractually rescheduleable.

None of this prevents disruption. It changes how quickly and how expensively the organisation responds, which across a programme is not a small difference.

Programme risk is one of the more persuasive arguments for a coordinated approach, because unlike savings it needs no baseline to demonstrate. An organisation that cannot state its committed event exposure does not need a benchmark to recognise that as a gap.

If you are building an internal argument, this sits alongside building the business case and the outcome measures on meetings KPIs. Read it with duty of care, which covers the risks attaching to people rather than money.