Dispatch Board
The three columns, dragging freight onto a run, assigning a unit, and the detail pane underneath.
Sidebar → Dispatch. Three columns, because that is the shape of the decision: what has to move, what is moving it, and who is free to drive it.
| Column | What is in it |
|---|---|
| Connotes (left) | Freight that is booked and on nobody’s truck. |
| Manifests (middle) | The runs. This is the column where a run is actually built, which is why it is the widest. |
| Dispatch Units (right) | Trucks and crews, and whether each can take work. |
The two outer columns are registers you scan to find a row; the middle one is the work. On a wide monitor the extra width goes to Manifests rather than being shared out evenly. Below about 992px wide the three stack into one column.
Putting freight on a run
Section titled “Putting freight on a run”- Select connotes. Click one to select it, shift-click for a range, ctrl/⌘-click to add one to the selection.
- Drag the selection onto a manifest card. The card you are over is highlighted with a dashed ring while it will accept the drop; the cards you are dragging are outlined and lifted.
- Drop. The connotes are allocated to that manifest and leave the Connotes column.
To take freight back off a run, hover the connote chip on the manifest card and click the ✕. The connote returns to the Connotes column.
Assigning a unit
Section titled “Assigning a unit”Drag a card from Dispatch Units onto a manifest, or set it from the manifest’s Assigned unit panel in the detail pane. The board will tell you when the load is already over the unit’s recorded payload — and will say so in terms of the recorded figures, because that is all it has.
Creating a manifest
Section titled “Creating a manifest”New manifest in the page header. It asks for a manifest number, service date, unit, origin, destination and notes — and none of them is required. The number is generated if you leave it blank, and a manifest can exist before anyone has decided who drives it: leave the unit empty and drag one onto the card later. Either way it is raised as a draft.
Creating a unit
Section titled “Creating a unit”+ Build Unit, at the top of the Dispatch Units column rather than in the page header — it is where you are already looking at the moment you discover the truck you want is not listed. See Units and rebuilds.
Filtering
Section titled “Filtering”Each column has its own search box:
- Connotes — connote number or customer
- Manifests — manifest number or lane, plus a status filter that defaults to All live
- Units — alias, driver or rego
Manifest statuses
Section titled “Manifest statuses”| Status | Meaning |
|---|---|
| Draft | Being assembled. Not committed to. |
| Planned | Built and intended to run. |
| Pending approval | Waiting on a human decision. |
| Dispatched | Handed to the driver; the run has started as far as the office is concerned. |
| In transit | Moving. |
| Completed | Finished. |
| Cancelled | Abandoned. |
Dispatched and in transit are the two that make a unit live, and a live unit is treated differently — see the mid-run rule in Units and rebuilds.
The detail pane
Section titled “The detail pane”Selecting a manifest card opens a pane across the bottom of the screen. The columns keep working above it. The expand button in the pane’s header gives it more height on a laptop or tablet, and gives it back with the same click.
| Panel | What it shows |
|---|---|
| Stop timeline | Planned against actual on a time axis, with the stops along it. |
| Assigned unit | The unit, its crew, its availability, its capacity. |
| Vehicle | Registration, type, depot. |
| Cargo | The allocated connotes, and what they consume. |
| Load plan | Where each item sits on the deck — see Load plan. |
| Route map | The stops drawn on a map. |
| Route stops | The stop list, reorderable. |
An unplaced count sits in the pane’s header, next to the manifest number. It is there rather than beside the drawing on purpose: a picture of a well-packed deck with a hidden “3 unplaced” underneath it is the exact failure this feature exists to avoid. When the plan is clear the chip is empty — a permanent “0 unplaced” would only train you to stop reading it.
Staying current
Section titled “Staying current”The board polls for changes every ten seconds and applies them card by card, so it does not flicker or lose your selection. The badge in the header shows the state of that feed. When the tab is in the background polling pauses and resumes when you come back, so a board left open overnight does not hammer the server.
What the board deliberately does not show
Section titled “What the board deliberately does not show”Speed, fuel, traffic-adjusted ETA, driver hours remaining and on-time percentage are absent, not blank. No routing service is called anywhere in the application and driver hours are not recorded, so any figure in those places would be invented. They will appear when there is something real behind them.