One record per shipment
Events, documents, and the owner of the next step live on the shipment, not in five tools that each hold a fragment.
About
Freight is a record-keeping problem with trucks attached.
Manifesto
Most freight software is a form that hopes the shipment behaves. The interesting part is what happens when it does not: a berth moves, a document is missing, a trailer arrives with the wrong pallet.
Haulpoint is built around that second case. One timeline per shipment, one owner per exception, and a public answer that matches the internal one. This demo shows the shape of that idea with sample data.
How the work is organised
Three habits, repeated.
Exceptions get a name
A delay without an owner is a rumour. Every exception carries a reason, an owner, and a due time.
The customer reads the same thing
Public tracking shows the events the tower shows. There is no second, friendlier version of the truth.
What we will not trade
Three lines we keep.
- No number without a sourceEvery figure on this site is counted from the sample file or labelled Sample. Nothing is rounded up to look better.
- No dark pattern in a formNo pre-ticked consent, no fake scarcity, no confirmation that hides what was sent.
- No coverage claim we cannot drawThe network page draws the lanes in the data. If a lane is missing, it is missing on purpose.
A fictional timeline
How the demo got here.
Sample dates, written for this demo. Not a company history.
- Sample 2024
One spreadsheet
A single shipment file, three status values, and a weekly call to reconcile them.
- Sample 2025
The tower takes shape
Charts counted from the same file, an exception list with owners, and a public tracking page.
- Sample 2026
Lanes and services
Lane history, service pages, and a quote request that collects scope without quoting a rate.
- This build
A template, not a product
Two brands, one codebase, sample data throughout. The docs explain how to swap both.
The roles behind the demo
Fictional roles, real responsibilities.
Roles are illustrative. No real person is named or photographed.
-
Network operations
Owns the lane record, the berth windows, and the exception list that starts the day.
-
Customs and documentation
Owns the entry checklist, the hold record, and the release that closes it.
-
Customer operations
Answers the customer with the same events the tower shows, and writes down what was missing.
-
Data and reporting
Keeps the charts counted from the file, and refuses to add a figure that has no source.
Where to go next
See the argument as a working screen.
The control tower is the same story with the sample file loaded.