Skip to content
Apps · Command

A live board for the person in charge

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.

Take the site
Zones and leads
Who is where
A timeline

If you hold the budget

Producer

You get a record of who was in charge, what was assigned, and when it moved. That is the pack a rights holder or a council can actually read.

If you run the night

Event manager

This is your board. Establish command, name the gates, put crews on them, see who has gone quiet. The number from the node sits next to the name of the person you sent.

What the hardware puts on this screen

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.

Who it is for: Event managers, duty managers, the producer who has taken the site. Optimised for Tablets and desktop.

  • iOS
  • Android
  • Web
  • Desktop
  • Docker

What it actually does

Take and hand over command

One person owns the site. Hand over with everyone notified. Close it when the last gate is down.

Zones, not org-chart theatre

Gates, arenas, medical, security, river, precinct. Leads, colours, who is on rotation. Built like a real radio net.

Put people on a number

Assign a crew or a Zone team to a job the node created. Work time and rotation sit on the assignment.

Accountability you can see

Check-in timers go green, then warn, then critical. If someone has gone quiet, the board says so before the radio does.

What we are trying to do

Objectives and needs: more stewards at the south gate, medical to the lawn, a vehicle to overflow parking.

A timeline that writes itself

Every assignment, move and close is stamped. The debrief is the log, not a memory.

A job, from number to done

  1. 01

    Take the site

    Command is open. Zones match the site plan. Leads are named.

  2. 02

    A node speaks

    Occupancy at the south lawn is climbing. Allocate offers a crew. You put them on that lane.

  3. 03

    The log is the debrief

    Who went, when, what the number was. You do not rebuild the night from radios.

What we will ask before we put this on your site

Plain questions. The answers change which app we mount, and where.

  1. We will ask

    Who actually takes the site, and who can they hand to?

    Command is one owner. If that is unclear, the board becomes a shared notepad.

  2. We will ask

    Do you already have zone names the radio net uses?

    We will use those names. We will not invent a second map.

Straight answers

Is this ICS for fires?

The structure is the same idea: one person in charge, named zones, named people, a log. The language is gates, lawns and medical, not divisions and strike teams, unless you want that.

What if the wifi dies?

Command keeps working on the tablet. Actions queue and replay when the mesh or the link comes back. That is the point of offline-first.

Walk Command 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.

CrowdSense analytics dashboard