Skip to content

In development, launching soon

ExchangeEarth
Sign inCreate account

In the app / reference

Reading a load's chain of custody

3 stepsAbout 5 minutesEvery role

Every event on a load (dispatch, acceptance, pickup, delivery, failure) is appended to a chain where each entry carries a hash of its parent. Nothing is edited, ever; corrections are new events. This page is how to read it.
1

Start at the register

Loads is every movement your organisation is party to or hauling: the register to produce when an inspector asks what moved. Each row’s reference (N-BP-2041-1 and the like) is the identity the whole chain hangs off.
The loads register: one row per movement, reference first.
2

Read one load's chain

The load record shows the chain as a table: each event, who recorded it, when, and the hash linking it to the one before. The docket beside it is tinted for whose copy you hold (producer, driver, receiver or the platform’s own), the same convention as the carbonless paper it replaces.
One load: the tinted docket, and the hash-chained events beneath.
3

Trust the PDF the same way

Download e-ticket PDF renders the record to paper: the data is snapshotted, hashed, and stored immutably; regenerating after new events produces a new version, never an edit. The version number on the button is that promise.