App demo
Redgrave TourRedgrave Haulage, Denver
Stop 09 — Sheridan
What has to happen at the loading bay: count, scan, get it signed. The signature only opens once all three consignments are scanned — one is still missing.
- In the hands of
- Driver on local delivery rounds
- Shown on
- Android — title on the left, three system buttons below
- Replaces
- Replaces the printed round sheet on the passenger seat, the delivery note to be signed and the call to the office at every second loading bay. The office sees where the round stands without ringing the driver.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
Redgrave Haulage, Denver is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
Redgrave Haulage runs local groupage deliveries. The driver gets a printed stop list on the passenger seat each morning, signs off on a paper delivery note, and anything off-plan gets phoned through from the bay. The work happens standing up, one-handed, in work gloves — and between two villages the signal is gone. That is the requirement everything else hangs on.
Decisions
The signature only opens after the last scan
The checklist at the stop is not decoration: while a consignment is unscanned, the receipt cannot be opened at all. A signature covering a quantity nobody counted is no signature when it is disputed — the block is inconvenient and that is precisely why it is there.
The duplicate scan shows up on the device, not in the depot
The scan list stays in the order things were read and marks the second scan of the same number as a duplicate. A device that silently de-bounces loses the difference between “scanned twice” and “two packages” — and that difference is what the depot needs in the evening.
Manual entry asks why
Labels ruined by rain need a keypad, or the driver is stuck at the bay. The reason travels to dispatch with the number, because otherwise manual entries pile up unnoticed — and eventually nobody scans anything.
Deliberately left outNo vehicle tracking and no time capture by position. On a delivery round both would be technically trivial, and both are the kind of monitoring a union contract usually has something to say about. What gets recorded is what happens at a stop, not where the vehicle sits between two of them.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 17
- Languages
- 4
Navigation responds, including the route from the round into a single stop and back. Scanner, signature pad, exception report and checklist are fully rendered and inert; the four states have a view of their own.
How it would go on
Connection to dispatch
Rounds, stops and consignments come out of the freight system; receipts, exceptions and returned pallets have to travel the same way back. A second status kept by hand is worse than none.
Signatures and evidential value
How long a proof of delivery is kept, who may see it and what it is worth in a dispute is settled by the business before the first paper note disappears.
Devices in the cab
Mount, power, mobile contract, a spare unit when one dies — and the question of who has the device at the weekend and who disables it when it goes missing.
An app like this for your business?
Redgrave Tour is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.