One event plan a university could apply to every event

The situation

Events across the campus were being secured case by case, by different people, to different standards. A graduation, a protest, a visiting speaker and a music event were being planned as though they had nothing in common, which meant the lessons from each stayed with whoever ran it.

The work

• A single security management plan was written for events as a class, with the decisions that change by event isolated from the ones that never change.
• Crowd management, ingress and egress, medical arrangements and the escalation path were set out once, so an organiser inherits them rather than reinventing them under time pressure.
• The plan names who authorises what, which is the part that fails on the night when the person on the ground does not know whether the call is theirs.

What was delivered

A plan an event organiser with no security background can follow, and a security adviser can audit against.

This engagement is described by sector rather than named, and carries no outcome statistic, because a number nobody measured is not evidence. The other engagements · Talk to a consultant