A real-time multi-event operations dashboard that shows all of today's events on one screen with live updates, alerts, and at-a-glance crew and job stats.
A real-time multi-event operations dashboard that shows all of today's events on one screen with live updates, alerts, and at-a-glance crew and job stats.
Command Centre is designed for operations leads and incident commanders who need a high-level picture of everything running simultaneously across your team. Where individual event pages give you deep detail on a single event, Command Centre gives you the full picture at once — all today's events side by side, live job counts, automated alerts for conditions that need attention, and the ability to drill into any event without losing sight of the others.
It's also built for display screens and projectors — fullscreen mode, auto-rotate, and audio alerts make it practical as a wall-mounted operational display.
Navigate to /command-centre in your browser, or look for the Command Centre link in the Operations section of the sidebar. The page opens in your team context and shows all events running today.

Directly below the page header, a row of six tiles gives you an instant summary across all of today's events combined. The strip is sticky - it stays visible as you scroll.
| Tile | What it shows |
|---|---|
| Events | Total number of events running today |
| Crews | Total crew count across all events |
| Jobs | Total jobs logged across all events today |
| Completed | Jobs that have been marked as done |
| Active | Crews currently assigned to a job |
| Hospital | Patients conveyed to hospital |
All six numbers update in real time as WebSocket events arrive from each event's dashboard channel.

Below the KPI strip, each of today's events appears as a card. Cards are automatically sorted by attention score — events that need your eye most urgently appear first.
IndieBase calculates an attention score for each event and sorts the cards accordingly. The score rises with the number of active alerts, active jobs, pending jobs, and hospital conveyances. Events marked as system events are deprioritised slightly. You cannot set this manually — the sort order updates automatically as conditions change.
Header — The event name and venue (if set), plus the earliest shift start time and latest end time. A Live badge appears when jobs are in progress; a Not started badge shows when no crew activity has been recorded yet.
Status counts — Four large numbers across the middle of the card:
| Count | Colour | What it means |
|---|---|---|
| Active | Amber | Jobs in progress (dispatched, on scene, or with a patient) |
| Pending | Grey | Jobs waiting for crew assignment or dispatch |
| Done | Green | Completed jobs |
| Hospital | Red | Patients conveyed to hospital |
Meta row — Total crews registered for the event, how many are currently available, and the average dispatch-to-scene response time.
Attention highlight — When the attention score is high (which typically means multiple alerts are active or there are many active jobs simultaneously), the card gains an amber ring with a subtle pulse animation to draw your eye.
Stale indicator — If a card has not received a live update in over 60 seconds, a small amber dot and time counter appear on the card to let you know the data may not be current.

Each event card includes two visual strips at the bottom.
A small bar chart showing the hourly distribution of jobs throughout the event. Each bar represents one hour, scaled relative to the busiest hour. Hover over a bar to see the hour label and job count. This gives you a quick read on whether job volume is ramping up, peaking, or tailing off.
A thin horizontal bar representing the full span of the event (earliest shift start to latest shift end). Each shift is rendered as a proportional segment, so you can see at a glance how shift coverage maps across the day and whether you are early, mid, or late in the operational period.

The alerts strip appears between the KPI row and the event cards whenever a condition requiring attention is detected. Each alert shows the title, a plain-English message, and the event it relates to.
There are four alert types:
Severity: Critical (red)
Fires when an event has zero available crews and at least one job is in Waiting status. This means there are incidents logged with nobody to send.
Severity: Warning (amber)
Fires when one or more jobs have been on scene for more than 45 minutes without clearing. Extended on-scene times can indicate complications, resource needs, or a job that needs escalation.
Severity: Warning (amber)
Fires when an event has 5 or more patients conveyed to hospital. A rising hospital conveyance count can signal pressure building at receiving units.
Severity: Warning (amber)
Fires when 80% or more of an event's crews are currently active on jobs. At this level, your margin for handling new incidents is low.
Alerts are calculated live. They appear as soon as a threshold is crossed and disappear automatically once the condition resolves - you do not need to dismiss them manually.

By default, audio is disabled when you first open Command Centre. A Click to enable sound button appears in the bottom-right corner of the screen.
Click it once to enable audio. From that point, a chime plays whenever a new alert appears in the alerts strip. If alerts were already present when you enabled sound, no chime fires for those — only for alerts that appear after you enabled audio.
Press M on your keyboard to toggle mute on and off. When muted, a speaker-off icon appears in the header. The chime will not play while muted, even if audio has been enabled.
Browsers require a user interaction before allowing audio playback. This is why the enable-sound step is necessary rather than audio simply starting automatically.
Command Centre is designed to be operated with minimal mouse interaction. The following shortcuts work when the focus is not inside a text input, dropdown, or open modal.
| Key | Action |
|---|---|
| 1 - 9 | Expand or collapse the event card at that position (1 = first card, 2 = second, etc.). Press the same number again to collapse it. |
| Arrow Left | When a card is expanded, move to the previous card |
| Arrow Right | When a card is expanded, move to the next card |
| F | Enter fullscreen mode |
| M | Toggle mute on/off |
| T | Toggle auto-rotate on/off |
| Esc | Collapse the currently expanded card |
Press T to enable auto-rotate. When active, a spinning arrows icon appears in the header and Command Centre cycles through event cards one at a time, expanding each for 30 seconds before moving to the next.
Auto-rotate requires at least two events to be running. It is designed for wall-mounted displays and projectors where you want every event to get screen time without manual intervention.
Press T again to stop auto-rotate. You can also press Esc at any time to collapse the current card and pause the rotation until the next cycle triggers.

Click anywhere on an event card to expand it. The card fills the full width of the screen and a list of up to three active jobs appears below the status counts.
Each job in the list shows:
This gives you enough context to decide whether to open the full event page without needing to navigate away.
Click the card again, or press Esc, to collapse it and return to the full grid view.

Each event card has a row of action buttons at the bottom. These work independently of the card expand/collapse behaviour - clicking them does not toggle the card.
| Button | What it does |
|---|---|
| View Event | Opens the full event management page for this event |
| Dashboard | Opens the event's public-facing external dashboard (only visible if the event has a dashboard configured) |
| Share | Copies the public dashboard link to your clipboard (only visible if the event has a dashboard configured). The button label changes briefly to "Copied!" to confirm. |
Press F or click the expand icon in the top-right of the header to enter fullscreen mode. This hides the browser chrome and gives Command Centre the full screen — useful for dedicated display screens or projection setups.
Exit fullscreen with Esc or your browser's native fullscreen toggle (usually F11 on Windows/Linux, or the green traffic-light button on macOS).
On some browsers, pressing Esc while a card is expanded will collapse the card rather than exiting fullscreen. If that happens, press Esc again to exit fullscreen.
The page shows "No events scheduled for today." Command Centre only shows events where today's date falls within the event's start and end dates. Check that your events are set up with the correct dates. If you need to create one, click the Create Event link on the page.
An event card is showing a stale indicator. The amber dot and timer mean the card has not received a live WebSocket update for more than 60 seconds. This can happen if your network connection has dropped briefly or the WebSocket subscription has lapsed. Refreshing the page will reconnect. Cards also poll every 60 seconds as a fallback, so data should recover automatically.
I am not seeing the Command Centre link or getting a "This plan does not include this feature" error. Command Centre requires a paid subscription. If you are on a free or trial plan, upgrade via Billing Portal in the Configuration section of the sidebar. If you believe you should have access, contact your team's account owner.
Audio is not playing even though I clicked "Click to enable sound". Some browsers block audio on pages that have not had recent interaction. Try clicking elsewhere on the page and then triggering an alert (or refreshing to re-enable). If audio still does not work, check your browser's site permissions for this domain.
Only some events are appearing. Command Centre shows events belonging to your current team where today's date is within the event's date range. If you are a member of multiple teams, switch to the correct team using Switch Team in the sidebar. Events from other teams will not appear.