Command Centre

Dispatch → Command Centre. The same board, arranged for a wall.

It is not a second screen with its own data. It is the same components in a different arrangement, with denser, darker chrome so it can be read from across a room. The portal sidebar and topbar are taken off, because a screen on a wall is not being navigated.

The layout

Region	What is in it
Left rail, top	Active Loads — the manifest cards, with a status-coloured accent strip.
Left rail, bottom	Drivers — the units, with the same availability vocabulary, two-up badge and DG badge the board uses.
Right, top	The stop timeline for the selected load.
Right, below	The dispatch editor — assigned unit, vehicle, cargo, load plan, route map, route stops.

Selecting a load in the left rail drives the whole right-hand side.

Everything updates on the same ten-second feed as the board, so a screen left up all day stays current without anyone touching it.

What is deliberately not on it

Speed, fuel, traffic-adjusted ETA, driver hours remaining, driver chat, on-time percentage and efficiency are omitted outright — not stubbed, not dashed, not drawn as an empty gauge.

None of those has a source in this system: no routing service is called anywhere in the application, and driver hours are not recorded. A control tower showing confident zeros is worse on a wall than on a laptop, because nobody standing across the room is close enough to hover the tooltip explaining that the zero is not a zero.

They will appear when there is something real behind them.

A note on the dark theme

The command centre forces a dark palette for its whole area. If you are building or reviewing anything that appears on it, check it here as well as on the board — a colour that reads correctly on a white page can be invisible on this one.