If you hold the budget
Producer
This is how you spend people against the thing you are measuring. A queue at the south gate is not a chart. It is three stewards, assigned, timestamped.
Apps · Allocate
The console that turns a number into a person
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.
Jobs from live data
Who is actually free
Map the work
All-day console
If you run the night
Event manager
You already do this on a radio. Allocate is the same job with the live number on the same screen as the roster, so you stop guessing who is free.
What the hardware puts on this screen
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.
Who it is for: Producers, ops leads, anyone who turns a live number into a person moving. Optimised for Desktop and web.
- Web / PWA
- Mobile
- Desktop
- Docker
What it actually does
Jobs, not tickets
Open, update, close. From a node threshold or from a radio call. One screen, the context a dispatcher of people needs.
Who is actually free
Crew status and Zone staffing, live. You send the people who are green, not the people who were on the 09:00 list.
Send a team, not a name
Put a Zone unit on a job the same way you put a person. Their tablet updates. Their phones update.
A map of the work
Pin the job on the site plan. The people you send already have the pin.
No refresh, all shift
The console moves when the field moves. Built to sit open for twelve hours without turning into sludge.
Browser, desktop, or your box
PWA in the room, desktop if you want a dedicated machine, Docker if you host it. Mobile if you are walking.
A job, from number to done
- 01
A number crosses a line
Or someone calls it in. Either way, a job exists with a zone and a reason.
- 02
You look at who is green
Crew and Zone status, on this screen. You assign. They get it on the phone or the tablet.
- 03
It closes in one place
Command’s timeline, the Board, the Crew app. The radio can stay quiet.
What we will ask before we put this on your site
Plain questions. The answers change which app we mount, and where.
We will ask
Who currently decides who walks to a gate when a queue builds?
If that is you, this console is yours. If it is a radio net with no owner, we need to name one.
We will ask
Which numbers should be allowed to open a job on their own?
A capacity warning, yes. A heatmap, no. We will be strict about what is allowed to page people.
Straight answers
Is this a CAD system?
It is the allocation half of one, for events. Create work, put people on it, keep it moving. It is not a public-safety call stack unless you want it to be.
Will this add noise?
Only if we let every chart open a job. Default is: you open the job, or a threshold you named does. Pretty pictures stay on the Board.
Walk Allocate on your site plan
Tell us who is in the room and which gates get a tablet. We will not invent a fifth radio channel.
