From security concept to working event operations

A security concept describes how risks are to be controlled. For the planned measures to take effect during an event, they have to be turned into specific tasks, available resources and tested procedures. This article shows how to put a security concept into operation and how to check operational event safety before and during the event.

Turning measures into operational tasks

The requirement “inform visitors in the event of a hazard” initially leaves important questions open: who recognises the situation? Who assesses it and decides on an announcement? Who operates the system? Which areas need to be reached?

To implement it, each of these tasks needs a named person or role responsible, the information required and suitable equipment. Deputies and reporting lines must also be agreed. The HSE describes clearly assigned emergency roles and responsibilities as part of planning [1] and stresses that those involved receive the information they need for their task [2].

A list of responsibilities on its own, however, does not show whether those involved know their procedure and can carry it out. It records who is supposed to act – not whether the parts work together.

Question from the concept	What must be settled for operations
Who recognises the situation?	Areas to be observed, reporting line, deputy
Who assesses and decides?	Named role, basis for decision, availability
Who carries it out?	Operating the means, e.g. announcement or closure
Who needs to be reached?	Affected areas, means of communication per area
Who reports back?	Feedback on implementation and effect

Read more: Measuring security quality: why functions matter more than equipment.

Testing the whole sequence

A fictitious example: an area of the event site is to be closed to visitors temporarily because of a local hazard. A security officer reports the observation to the operations lead. The operations lead assesses the situation, initiates the planned measures and has the affected visitors informed. Afterwards, feedback confirms whether the measures were carried out and had the intended effect.

Before the event opens, this sequence can be worked through using a suitable scenario. The hand-overs between report, decision and action deserve particular attention, as this is where responsibility changes.

Means of communication should also be tested in practice. The UK Health and Safety Executive recommends testing emergency plans, for example through scenario-based exercises, and checking radio and public address systems before they are used [1]. A functional test of this kind at the event shows whether an announcement reaches every intended area and whether radio links work where they are needed.

Read more: Emergency PA at events: intelligible, multilingual and resilient.

Recording results so they can be traced

A short test record can document which function was tested under which conditions, which deviations occurred and who is responsible for resolving them. One possible structure:

1. Function tested and scenario
2. Conditions (location, time, staffing, equipment used)
3. Result and deviations found
4. Person responsible and deadline for resolution
5. Confirmation after re-testing

A functional test of this kind supplements any mandatory inspections and acceptance tests; it does not replace them.

Checking implementation during the event

Checking remains relevant while the event is running. Blocked routes, changing noise levels or failed means of communication can alter the conditions on which a previously working measure depended. Checking implementation and effectiveness is therefore part of running the event; the HSE also describes ongoing monitoring and review as part of managing an event [2].

In practice, this means collecting feedback from the areas, spotting deviations and passing them on to whoever is responsible. Changes during operations feed into the assessment of the situation.

Read more: Integrated security infrastructure, not isolated measures.

How MOVETOS OPS supports this

MOVETOS OPS is the platform that connects cameras, loudspeakers and the team during event operations. When putting a security concept into practice, these features help most:

• Report, decision and announcement in one flow: warnings appear with a photo as evidence on the map, together with a prepared announcement. The system suggests, a human approves.
• Reaching the team: team coordination also works without mobile networks via the local network on site.
• Reaching visitors: announcements are available in five languages, also offline.
• Traceability: the operation is documented in full – a basis for the test record and the debrief.

Responsibilities and decisions remain with the organiser; MOVETOS OPS supports carrying them out.

Checklist: functional test before the event

• Every measure in the concept has a named person or role responsible and a deputy.
• Reporting lines and decision-making authority are known to everyone involved.
• At least one scenario has been worked through from first report to feedback.
• Radio and announcements have been tested in practice in the intended areas.
• Deviations are recorded in the test record, with a person responsible and a deadline.
• It is clear who checks implementation and effectiveness while the event is running.

Conclusion

A robust transition from planning to operations is achieved when those involved know their tasks, the resources they need are available and the way everything works together has been tested in practice.

The HSE guidance serves as a technical source on operational practice; UK legal requirements are not presented as German obligations. The example is fictitious and the record structure is an editorial illustration.