Six o'clock, the trunk is due out, and the manifest is not right
The collection drivers are back. The bay by the door has a mix of full pallets, half pallets and a stack of quarters shrink-wrapped by customers who were not quite sure what they were sending. Somebody in the office is working down the collection sheets, checking each consignment has been keyed onto the network system, and adding the ones that came in by phone after lunch.
Then the warehouse shouts that there are two pallets for Aberdeen that nobody can find on the list, and one on the list that never came in. The trunk driver is sitting in the cab. Every night ends the same way: a manifest that is being corrected while the wagon is being loaded, and a nagging feeling that something will turn up at the hub as unmanifested.
The manifest is built at the end, not as the day goes
The manifest is usually treated as an end-of-day document. Bookings arrive all day through different routes, but nothing joins them to what is physically on the floor until someone sits down to compile the list.
- Account customers book on the network portal, some email a spreadsheet, and a few still phone.
- Collection drivers bring back extra pallets the customer added on the day.
- Pallet sizes on the booking do not always match what was actually collected.
- The inbound scan at your depot is not checked against the bookings until the evening.
So the one person who compiles the manifest is also reconciling three sources of truth under time pressure, which is when mistakes get made.
What a late, wrong manifest costs the depot
Unmanifested pallets at the hub create queries, delays and sometimes a charge or a mark against your depot on the network's scorecard. Pallets on the manifest that never left create a different problem: a consignment the network thinks is travelling and the customer thinks is on its way.
There is also the quieter cost of staff time. The evening shift in the office exists partly to fix the manifest, and the trunk sometimes leaves late while it happens, which puts pressure on the hub slot.
How we build a manifest that keeps itself current
- We pull every booking into one list as it arrives: from the network portal where it offers an export or API, from customer spreadsheets through an inbox reader, and from phone bookings keyed on a simple screen.
- Collection drivers confirm pallets and sizes on a phone app at the customer's premises, including extras added on the day.
- The inbound scan at your door is matched against the list, so each pallet is marked as on site the moment it is scanned.
- A live board shows three columns: booked and on site, booked and not yet in, and on site but not booked.
- At trunk time the manifest is generated from the 'on site' column, with exceptions listed for a person to resolve.
- Where the network accepts a file or API submission, the confirmed manifest is sent from the same screen.
| Moment | Today | With the build |
|---|---|---|
| Afternoon phone booking | Written on a pad | Keyed once, appears on the board |
| Extra pallet at collection | Found in the evening | Added by the driver on site |
| Pallet scanned in | Checked at trunk time | Matched immediately |
| Trunk departure | Manifest rebuilt | Exceptions checked, manifest sent |
Nothing overrides the network's rules. If the network portal must remain the system of record, the build feeds it rather than replacing it.
What the evening looks like afterwards
The manifest is mostly complete by mid-afternoon. The last hour is spent on the handful of exceptions on the board, not on compiling a list from scratch. Warehouse staff can see which pallets are expected and which are unknown, so the conversation with the office happens earlier.
When the hub asks about a pallet the next morning, you can see when it was booked, who collected it, when it was scanned in and which trunk it went on.
Signs this is your depot
- The trunk manifest is compiled after the last collection is back.
- Pallets turn up at the hub unmanifested more often than you would like.
- Collection sheets and the network portal regularly disagree.
- One person is the only one who can finish the manifest.
- The trunk has left late because the paperwork was not ready.