Skip to content

Manifests

The manifest record — every run ever, sortable and filterable on any column, with your own column layout, export and print.

Dispatch → Manifests. The board’s sibling, not a tab inside it.

The board is a picture of live work in cards. This is the record in rows: every manifest on file, including the completed and cancelled ones the board has finished with.

Column
Manifest NoThe reference.
StatusDraft, planned, pending approval, dispatched, in transit, completed, cancelled.
ConnotesHow many connotes are allocated.
RouteOrigin → destination.
StartPlanned, and the actual, and the deviation between them.
FinishThe same three, at the other end.
DriverWho is on it.
FleetThe unit and vehicle.
LoadWhat it is carrying, against what it can carry.
ETAWhere it is expected.
ProgressHow far through the run it is.

Start and Finish can each be sorted three ways — by the planned time, the actual time, or the deviation between them. Sorting on deviation is how you find the runs that went wrong, and it is not the same list as sorting on the actual time.

Lateness is read from the manifest, not recalculated on this page, so a run this list calls late and a board that colours it late cannot disagree with each other.

Click a column heading to sort. Every column carries a filter — a text match, a status picker, or a minimum, depending on what the column holds.

Choose which columns you see, and in what order. The layout is saved per user, so the arrangement you set is the one you get back tomorrow, and it does not affect anyone else. It uses the same mechanism as the dashboard widget layout.

Export CSV writes what is currently on screen — your filters, your sort, your visible columns — to a file. Print does the same to paper, and the printed page carries a line stating what was filtered and when it was printed, because a printed table with no statement of its filters is a table that gets quoted out of context.

An export carries at most 5,000 rows. If more than that match, you are told before the download starts rather than handed a short file that looks complete.

The board deliberately shows live work only. Keeping completed and cancelled manifests in the same columns would push the runs that need attention down the screen, and dispatch is a screen you scan rather than read. The record is a different job, so it is a different page.