Secure one-time links
Text a link to anyone on site. They open the incident in their phone browser, read it and acknowledge it. No account, no app, no password, and the link is theirs alone.
The platform
Everything below is in every deployment.
There are no feature tiers. What changes between a village fete and a 40,000-capacity festival is the optional modules and what we bring on site — never whether the core system is any good.
Incidents
The log is the point.
Most control room software fails because logging an incident is slower than shouting across the room. This one is built the other way round.
Two-stage capture
Stage one asks for the minimum: what and where. The incident is on the board and visible to everyone before anybody has filled in a form. Stage two adds the detail once the immediate thing is handled.
One line at a time
The shared log takes a single line, timestamped and name-stamped: type, hit enter, done. Every connected operator sees it appear. There is no draft state, no save button and no way for two people to overwrite each other.
Priority, status, linking
Incidents carry a priority and a status, can be pinned to the top of the queue, and can be linked to each other — so the lost child and the found child are visibly the same job.
Attachments
Photos and documents attached directly to an incident, stored with it and included in reports.
Checklists
Structured response checklists — bomb threat and similar — opened from an incident and completed step by step, with the completed checklist retained as part of the record.
Categories
Incident types configured to match how your event actually classifies things, not a fixed vendor taxonomy.
The entity registry
Recorded once, connected everywhere.
The second time somebody appears at your event, you should already know about the first time.
People, vehicles, objects and locations are records in their own right, not free text buried in an incident. Open a person and you see every incident they are connected to, in order. Duplicates can be merged when the same person gets logged twice under different spellings.
For annual events the registry carries forward, so year two starts with everything year one learned.
- Incident
- Person
- Vehicle
- Location
- Object
Live mapping
Your site, not an empty field.
Incidents are pinned where they happened, as they are logged, on a plan your operators actually recognise.
Pinned as they are logged
Every incident carries a location, and the map updates for every operator the moment one is created or moved. Priority is colour-coded, so the shape of the night is readable at a glance from across the room.
Your own site plan
Upload your site plan and position it against the map, and it becomes the background every operator works on — so pins land on your gate numbers and arena names rather than on open countryside. No GIS work, no third-party mapping contract.
what3words
Supported throughout, for the locations that have no useful address — a field entrance, a track junction, a spot on a perimeter fence.
Reaching people
The people who need an incident rarely have a login.
Site medics, contractors, a duty manager who has walked away from the desk. EventControl assumes they have a phone and nothing else.
Acknowledgement tracking
The control room sees who opened the link and who acknowledged, so "I never got that" stops being a conversation.
Notices & wallboard
A notices board for standing information, and a wallboard view for the big screen so the room has a shared glanceable picture without anyone driving it.
Access & safeguarding
People see what their job needs. Nothing else.
Five role levels ship as standard and can be edited, copied or replaced entirely.
| Role | Typical use | Can do |
|---|---|---|
| Read Only | Observers, visiting partners | View incidents, entities and reports |
| Standard Access | Gate stewards, radio desk | Site access sign-in/out, asset issuing, view incidents |
| Control Room Operator | The desk | Create and edit incidents, dispatch units, send SMS links |
| Supervisor | Duty supervisor | Close and restrict incidents, view restricted, export reports, audit log |
| Event Manager | Event control lead | Everything, including users, roles and settings |
Permissions below the role
Roles are a starting point, not a fixed set. Access is granted per module and per action, and individual users can be overridden. A gate laptop can be scoped to the site access log and literally nothing else — no incidents, no registry, no reports.
Restricted incidents
Safeguarding and sensitive incidents can be restricted so only senior roles see them at all, or locked so that opening one requires a written justification. Both the justification and the fact you looked are recorded permanently.
Multi-factor authentication
Available for every account and enforceable across a tenant, using a standard authenticator app.
Audit trail
Every view, change, export and login is recorded with who, what and when. It is exportable, and it is not editable by anyone — including us.
Briefing
A per-event briefing page every operator sees on login, so the shift starts with the same information rather than a huddle somebody missed.
Optional modules
Switched on per event.
Priced per event based on scope, so a one-day fete isn't paying for machinery it will never open.
Site access
Every person and vehicle logged on and off site. Returning visitors are recognised from the registry, so the second visit is a two-tap job. A live count of exactly who is on the ground right now — which is the number you need within thirty seconds of an evacuation being called.
- Sign-in designed for a tablet at the gate, in bad weather
- Vehicle and visitor history at a glance
- Works on a role that can see nothing else
Deployments
Manage operational units — medics, stewards, security, welfare — and dispatch them to an incident in one click. Stand-downs and redeployments are written automatically into every incident involved, so the timeline reconstructs itself afterwards.
- Live status of every unit in one place
- Assignment and stand-down logged without anyone typing it
- Underpins the JESIP co-ordination principle
Asset issuance & tracking
Radios, buggy keys, medical kit, accreditation — anything issuable. See what's out, who has it and when it's due back, with overdue alerts before things go missing rather than at strike when they already have.
- Issue and return against a person in the registry
- Overdue alerting
- Pairs with radio hire from our on-site services
Mass emergency broadcast
Send bulk emergency SMS from one page, with contact lists loaded in advance so nobody is pasting numbers during an incident. Delivery is tracked per message.
- Lists prepared before the event, not during
- Compose and send split by permission
- Per-recipient delivery status
When things go wrong
The system tells you before you find out the hard way.
Connectivity
A live monitor on every screen. The moment an operator's connection drops, their screen says so — because the dangerous failure isn't losing connection, it's not knowing you have.
Hot standby
For events where stopping isn't an option, an on-site mirror of your control room takes over if the internet fails. Offered as an on-site service.
Backups
Your tenant is backed up continuously through the event and held encrypted off-site. Restores are tested, not assumed.
Print-ready reports
If you need it on paper — for a debrief, an insurer or a licensing authority — it prints properly rather than as a mangled web page.
See it running.
A short demo on a real system, and a straight answer on what your event would cost.