For producers
You are spending people against a measurement. Allocate is the console. Command is the log you can hand to a rights holder. Board is what the room (and, if you want, a sponsor) can see without standing in the radio net.
Not a responder stack. Communication and allocation, fed by the nodes you already put in the ground. Five apps, one live picture.
The person on the ground, the team at the gate, the owner of the site, the console that assigns, and the wall the room is facing. Every one of them sees the same occupancy, the same job, the same names.
For personnel
People on the ground
Status, messages, the next job, and the occupancy of the zone you are standing in. One tap, not a radio relay.
Phones (native + PWA)
For apparatus and crews
A gate, a vehicle, a team
Live location, the job queue for this gate, voice, and the map. One tablet the whole crew looks at, not five phones with five versions of the truth.
Tablets and desktop
Event command
The person running the site
Take the site, name the zones, put people on them, and keep a timeline you can hand to the debrief. Offline-first, because command does not wait on venue wifi.
Tablets and desktop
For the board
The person putting people on work
Create a job from a live occupancy or a radio call, see who is actually free, put a crew or a Zone team on it, and keep it moving. Built to run all day.
Desktop and web
Situational awareness
The room
A grid of live tiles: people, teams, jobs, map, occupancy, weather. For the wall in the compound, the desk in the room, or a tablet walking the site.
Big screens (tablet and phone too)
| App | Who uses it | Optimised for | Platforms |
|---|---|---|---|
| Crew | Stewards, security, medical, brand hosts, anyone with a radio and a job | Phones (native + PWA) | iOS · Android · Web / PWA |
| Zone | Shared tablet at a gate, in a vehicle, or on a desk in a compound | Tablets and desktop | iOS · Android · Web · Desktop · Docker |
| Command | Event managers, duty managers, the producer who has taken the site | Tablets and desktop | iOS · Android · Web · Desktop · Docker |
| Allocate | Producers, ops leads, anyone who turns a live number into a person moving | Desktop and web | Web / PWA · Mobile · Desktop · Docker |
| Board | Control rooms, compounds, EOCs, a wall in the bay | Big screens (tablet and phone too) | Web · iOS · Android · Desktop |
The nodes count. Allocate turns that into a job. Crew and Zone take it. Command and Board watch the same thing.
Anonymous occupancy, queues and flow, on the device. Only metrics leave the box.
A threshold, or a person in the room. A job with a zone and a reason.
A phone in a pocket, or a tablet on a gate. Status moves. Voice if they need it.
The owner of the site, and the wall the room is facing. One backend. One timeline.
You are spending people against a measurement. Allocate is the console. Command is the log you can hand to a rights holder. Board is what the room (and, if you want, a sponsor) can see without standing in the radio net.
You already run this on radios. Crew and Zone are the people and the gate. Command is your board. Allocate is who you trust to send the next three stewards without asking the whole net.
Companion and the Control Room are how you watch the site. These five apps are how you talk and how you put people on the number. Same backend. Crew is a person. Zone is a team. Command is the owner. Allocate is the console that assigns. Board is the wall.
No. A small activation might be Crew plus Board. A precinct day is usually Allocate, Command, Zone on the busy gates, Crew on everyone else, Board in the compound. We will say if a fifth app is theatre.
Sense Nodes, Vision Nodes, Optic Nodes, and the Vision Engine on cameras you already have. Occupancy, queues, flow. The apps do not invent a second count. They put a person on the count you already trust.
Five apps is the shape. Which ones you actually mount depends on the radio net and the gates.
