Event security control on a single tablet

A regional event security contractor took on a three-day waterfront festival: six talkgroups, agency staff who met at briefing, and a client who wanted paperwork if anything went wrong near the water.

They had been hiring radios and running a WhatsApp group for anything the radios missed. WhatsApp worked until a photo queue buried an urgent message about a gate breach, which was the incident that pushed them to look for something better before the next event.

For this event they kept hired radios as backup but moved primary voice to RevoNet on agency phones. Talkgroups were named by zone: north gate, south gate, pit, medical liaison, supervisor, logistics.

Setting up before doors opened

The control point supervisor ran the dashboard on a rugged tablet with a mobile data dongle. Map markers showed last positions for team leads. When a medical call came in, they created an incident, assigned the nearest pit team, and spoke on the supervisor talkgroup without typing coordinates into a chat.

Devices were paired the afternoon before the gates opened, during hi-vis and radio collection, so nobody was waiting on pairing once the site went live. Talkgroups mirrored the channel card handed out at briefing, which meant agency staff who had never used the platform before could match what they heard in briefing to what appeared on their phone.

Running the event

Busy and idle status mattered at the day-to-night handover. Outgoing leads confirmed channel status before new staff keyed up, avoiding the confusion of a new shift talking over a handover still in progress.

Afterwards the client wanted a timeline of two notable incidents. The contractor pulled it from incident records instead of reconstructing WhatsApp timestamps. Insurance correspondence went faster, since the timeline already had creation time, assignment, and closure notes in one place rather than scattered across screenshots.

Agency feedback was mixed but mostly positive. Phones were familiar. Training took about twenty minutes because talkgroups mirrored the channel card in briefing, and the small number of staff who found the app unfamiliar picked it up within the first hour on site.

What changed on the invoice

Radio hire stayed for redundancy, but terminal count dropped. Software for thirty active users on Pro pricing came in below the saved hire line on the client invoice, which made the business case straightforward for the next contract rather than something that needed re-justifying event by event.

The client also noticed the difference in reporting. A written timeline pulled directly from incident records read as more credible than a reconstructed account, which mattered for a client already sensitive about anything happening near the water.

Handling the parts that did not go to plan

Not everything ran smoothly. On the first afternoon, a small number of agency staff kept both radio and phone switched to receive, which meant they heard some traffic twice and occasionally answered on the wrong channel. The fix was simple once spotted: brief staff to treat the phone as primary and the radio as backup only, rather than monitoring both as equals.

Mobile data also dipped briefly near the main stage during the busiest period of the second evening, when the site's overall phone traffic spiked. The team had radios as backup for exactly this reason, and the dip lasted only a few minutes before service normalised. It was a reminder that even solid urban coverage can wobble under a large crowd's combined phone use, which is why the contractor kept radio redundancy rather than removing it entirely for this event.

What they would repeat

Brief talkgroups before gates open. Pair devices before hi-vis collection, not during it. Keep WhatsApp for social chat if you must, but put shift traffic on PTT and incidents, since mixing the two is exactly the habit that caused the original gate breach message to get missed.

The contractor now treats the pre-event pairing session as a fixed part of their setup checklist, alongside radio collection and briefing, rather than something arranged separately each time.

Applying it to the next contract

The contractor has since used the same zone-based talkgroup structure, roughly one group per physical area plus a supervisor channel, as the starting template for other multi-day events. Naming groups by what staff already call the area in briefing, rather than an internal reference code, remains the detail that made adoption fast on the day. Staff who have never used the platform before can match a talkgroup name to a location on a map within the first few minutes of a shift, which is what actually determines how smooth day one feels.

Running seasonal events? Contact us or pilot with two users before your next load-in.