How CrowdSense looks from the control room, not from a sales deck
At 21:00 with three queues building, you need one number you can say over the radio. This is written for that moment, not for the demo.
Who this is for
Venue managers, event ops leads, control-room operators, and the person who already owns the radio net and the run of show.
The first demo is the control-room view and the companion app, on a layout like yours. If a number is not radio-friendly we will not put it on the wall.
What the first event actually looks like
Not a rollout plan. The shape of one event, done properly.
- 01
We map the radios, not the product
Who calls occupancy, who calls queues, who can open a lane. CrowdSense has to fit that net. We will not invent a new channel you have to staff.
- 02
The wall shows what you can act on
Occupancy by zone, gate throughput, queue time at the pinch points you named. Pretty heatmaps stay in the debrief unless you ask for them live.
- 03
A trial weekend with your crew, not ours pretending
Your operators on the companion app. Your language on the labels. We stay on comms for the first one, then we get out of the way.
- 04
The debrief is for the next event, not for us
Where the plan was wrong, which gate was early, which zone sat empty. You already know most of this in your gut. The numbers let you change the site plan with the producer, not argue about it.
Your team, mapped before day one
Every measurement has a named destination, a trigger, a channel and a person who confirmed it arrived.
The control room
The event controller and the operations manager holding the whole site.
- Occupancy by zone against the limit, live, with the rate of change beside it
- Gate throughput and the queue building at each entry
- Every zone threshold crossing, on the board and in the log, with the time it cleared
- The incident timeline as it is written, so the debrief starts already built
On: When a reading crosses a line, When something happens, On a schedule
Through: A screen on the wall, The site dashboard, Push to the crew app
Gate and door crews
The supervisors on the entries who can open a lane or hold a queue.
- The count at their own door against the limit the venue sets
- A call to open or hold, from the controller, with the number that prompted it
- The barrier and queue state at their gate and the one either side of it
On: When a reading crosses a line, When something happens
Through: Push to the crew app
Safety and medical
The crowd-safety officer and the medical lead.
- Density by zone, read the way a safety case reads it, against the thresholds in the plan
- The zones building fastest, ranked, so a crew is moved before the call
- An alert on every threshold crossing, with the zone and the time
On: When a reading crosses a line, When something happens
Through: Push to the crew app, A screen on the wall, The site dashboard
The producer
Whoever holds the budget and answers to sponsors, investors or the board.
- Attendance: unique visitors and entries, by day and across the run
- Dwell at the places you sold: the sponsor activation, the bar, the stage
- Whether the site plan worked, zone by zone, against last year where there is a last year
- The post-event report, written and dated, for the acquittal and the sponsor pack
On: On a schedule, At a milestone, When somebody asks
Through: The site dashboard, A signed document, Email, scheduled
Sponsors and rights holders
The partners who bought a position and need to see what it delivered.
- Dwell and reach at their own activation, for their own dates
- A one-page result they can put in front of their own board
On: On a schedule, When somebody asks
Through: A signed document, Email, scheduled
The venue or the council
The landowner, licensee or authority the licence conditions sit with.
- Occupancy against the licensed capacity, for the licensed hours
- Noise at the boundary against the condition, with the time and the duration
- A compliance summary for the period, dated and exportable
On: When a reading crosses a line, On a schedule
Through: The site dashboard, A signed document
What happens if nobody acknowledges it
Sent
Immediately
The route fires to the people holding that role right now, on every channel that route carries.
Acknowledged
One tap
The first person to acknowledge takes it, and everyone else on the route sees that it is taken. The acknowledgement and the name are logged.
Re-routed
On the window you set
Unacknowledged inside the window, it goes to the next name on that route. Windows are per route: a gate alert is not a coverage report.
Escalated
On the second window
It reaches the escalation contact for that site, and the fact that the first two steps did not land appears in the monthly report.
Questions we will actually ask
These are the same questions in the demo form. We ask them because the answers change the kit, the room, and who needs to sit in.
We will ask
What do you currently look at when a queue builds?
CCTV, a steward at the fence, a guess. That tells us what “better” has to beat, in your units, not ours.
Question 1
We will ask
In-house crew or contracted, and how many on radio?
A six-person net and a sixty-person net need different alert noise. We will not page everyone for a gate that is merely busy.
Question 2
We will ask
Where does the control room actually sit?
A proper room can take a wall. A hatchback takes a phone. We will not design you a video wall you cannot house.
Question 3
We will ask
What must never go on a public screen?
Safety numbers, medical, anything that would move a crowd if it leaked. Crowd-aware signage is optional and gated. Default is ops-only.
Question 4
We will ask
Who on your team needs to know, and how fast?
The control room, the gate crews, safety and medical: naming them here is what turns a dashboard into a wall that already knows who to page.
Question 5
We will ask
What actually gets read after the event?
Gate throughput and the capacity call matter on the night; the licence condition and the year-on-year comparison matter the next morning. We build the debrief around both.
Question 6
We will ask
What do you already run?
Your radio net and your existing CCTV are not replaced. They are joined by a number on the same screen.
Question 7
We will ask
What does the site look like, and what are your constraints?
Gates, zones, power, mounting points, load-in and pack-down windows: the same questions a site walk would ask, just asked before the walk.
Question 8
We will ask
When does the build start, and is there a rehearsal or soft open?
If we need to be live before doors, that is a staffing decision on our side, not yours to chase.
Question 9
Straight answers
Will this add another screen I have to watch?
Only if you want a wall. Most event managers live in the companion app and a handful of alerts. If your control room is already full, we will not fight for pixels.
Does it work when the site has no reliable phone signal?
Yes. Off-grid communications is a product we already run, not a future promise. Tell us in the form if the site is a paddock, a basement, or a tunnel. That changes the kit, not the conversation.
Can security and medical see the same occupancy I see?
Yes, with the same numbers and the same zone names, on their own logins. We will not give medical a different occupancy to the one you are calling on channel 1.
What if I am not the person who signs the contract?
Say so. Bring the producer or the venue owner to the second meeting, not the first, if you want a clean ops look before the commercial one. We will not bounce you to sales in minute five.
What happens if a node fails at 9pm on a Saturday?
The monitoring raises the alert within fifteen minutes, day or night, and most faults are fixed over the air. If a position needs a hand, that runs the same response ladder as any other night. On the night itself your crew lead already has that gap in the production meeting and on the radio, so it is a known gap, not a surprise in the debrief.
How long does load-in actually take?
Tell us the window in the form and we plan the install to fit it, not the other way round. A straightforward site is a walk, a kit plan and commissioning inside a normal bump-in; a tight window is exactly the constraint we want to know about first.
What if the site plan changes on the day?
Say so on the radio and to your named contact. It is a change made with the crew already on site, not a change order that waits for the next event.
Who owns the data from the night?
You do. It is exportable at any time, and the debrief is built from the same record you were watching live, not a separate reconstruction.
What do you collect about the people in the crowd?
We measure crowds, not people. Our sensors count and classify — they do not identify. No facial recognition, no biometric identification of people. Ever. What leaves a camera node is counts and events, not video.
Rather talk it through first?
Book a time and your answers come with you, or call the office line. Either way you get the person who reads the enquiries.
Talk to a person
Wesley Pearson, Managing Director
It's in Brisbane right now.
“You will get a reply from me within a business day, and the first call is the control-room view, not a sales pitch.”
Book a time
Tell us about the event, in your words
The form is seven short steps. A person reads it. If you would rather talk, book a time.
