Producer
You care that a queue became three people assigned, timestamped, and still in the log next week. Allocate and Command are your proof. Board is optional for a guest.
South Bank demo
Five apps on a precinct day, not a responder stack
Communication and allocation, with the occupancy you already want to measure. Open this on the projector. The product pages are one tap away.
Who is in the room
A producer is spending people against a measurement. An event manager is running the radio net. These apps have to work for both, or they will not be on at 16:00.
Event manager
You care that Gate 3 got help before the radio got loud. Crew and Zone are the people. Command is your board. Allocate is who you trust to send them.
The five, in precinct language
- 01
CrewPeople on the ground
Status, messages, the next job, and the occupancy of the zone you are standing in. One tap, not a radio relay.
Sense and Vision nodes in the zone the person is rostered to. Occupancy, queue time and a capacity warning land on the phone they already have in their hand.
- 02
ZoneA 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.
The Vision or Sense Node on that gate, plus the team’s location. Queue time and occupancy for this zone only. Not the whole site, unless they ask.
- 03
CommandThe 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.
Every Sense and Vision node on the site plan, plus Crew status and Zone location. Occupancy is a lane on the board, not a separate dashboard.
- 04
AllocateThe 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.
Thresholds on Sense and Vision nodes can open a job on their own: occupancy, queue time, a gate that has stopped flowing. You still decide who goes.
- 05
BoardThe 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.
Every node on the site can be a tile: occupancy, queue, a small heatmap. Next to the roster and the open jobs, so the number and the people are one glance.
The day, in four moves
- 01
Start with the number, not the radio
Sense and Vision nodes on the lawns, the river edge and the gates. Occupancy and queues are already a fact. The apps exist to put a person on that fact.
- 02
Allocate watches the board
A threshold at a pinch point opens a job, or ops opens one from a radio call. They see who is actually free. They send a Crew or a Zone team.
- 03
Command owns the site
Named zones that match the radio net. A lead on each. A timeline that writes itself. That is the pack South Bank can keep after the day.
- 04
The wall is for the room
Board in the compound: people, teams, open jobs, the map, the occupancy tiles. Not a sponsor laptop unless you build a second layout without names.
Questions we will actually ask today
If we leave with answers to these, we can scope a first weekend. If we do not, we will not pretend we can.
We will ask
Which pinch points already blow out, and who currently walks to them?
That is the first Zone tablet and the first Allocate rule. Everything else is optional.
We will ask
Who takes the site at 07:00, and who can they hand to at 16:00?
Command needs one owner. If that is two people, we set a handover, not a shared notepad.
We will ask
How many people on radio, and which channels are already full?
Crew messaging is for what the radio cannot hold. We will not invent a sixth channel.
We will ask
What must never appear on a wall a visitor could photograph?
Medical jobs, names, anything that would move a crowd. Board default is ops-only.
Open the apps, then book the walk
The pages are the product. The next hour is your site plan, your radio net, and which gates get a tablet.
