Event Risk Management: The Plan You Hope Not to Use

Most event risk documents are written to satisfy a venue or an insurer, and are never opened again. A useful one is a single page that somebody can read in the ninety seconds before they have to decide something.

Plan for what actually happens

Ignore the dramatic scenarios for a moment. The incidents that occur at ordinary events, in rough order of likelihood:

• A speaker does not arrive.
• The network fails at the registration desk.
• Someone is taken ill.
• A session overruns badly enough to break the next one.
• Catering is short, late or wrong.
• The power in one room goes.
• A confrontation between attendees, or a code-of-conduct breach.
• Severe weather or a transport strike on the morning.

Each of those deserves two sentences: what we do, and who decides. That is the plan.

Decide the decision-makers first

The expensive failure in a bad hour is not a wrong decision; it is no decision, because three people each thought someone else owned it. Name one incident lead per day, with a deputy, and say out loud in the briefing who it is. They have authority to spend up to an agreed amount without asking.

Three things that make the network failure survivable

It is the most common operational incident, so it is worth its own preparation:

• An offline attendee list. Printed or exported to a device, sorted by surname, produced the evening before — not from memory on the day.
• A wired connection for at least one desk, arranged with the venue in advance.
• A mobile hotspot per desk, tested in the actual room, because coverage in a basement hall is not coverage in the car park.

The details are in getting 500 people in under 30 minutes.

Write the communications in advance

Three short templates, written calmly, with blanks: a delay, a venue change, a cancellation. In the moment, the hard part is not the sending — it is the wording, and nobody writes well under pressure. Keep them where your team can reach them, and know how you would reach every attendee at once: the messaging in your event platform, plus one channel that does not depend on your wifi.

The one-page document

On one side of paper, for every person working the event:

• Incident lead and deputy, with mobile numbers.
• Venue duty manager and first aid, with location.
• Nearest A&E, and the assembly point.
• The eight scenarios, one line each.
• Who speaks to press or to attendees — and that nobody else does.

Print it. The one time you need it is the time the phones are busy.

Debrief while it is fresh

Whatever happened, write it down within forty-eight hours: what we saw, what we did, what we would change. That paragraph is worth more to next year's event than the whole risk register, and it belongs in your post-event report.

Keeping attendee lists, messaging and the agenda in one place means the fallback is one export rather than four. Try Gathervo free and see what your offline pack would look like.