The business already moves goods, and moves them well. What it does not have is a memory. Records and updates live in WhatsApp threads and spreadsheets.
Nobody could say how long a delivery really took, or what a job really earned. Tragline is the record for that: one place to track the work, the delivery time and the profit of every job. It is in build, and most of what follows is the design as specified, ahead of the code.
The job is the unit
Everything hangs off the job: the customer, the agreed scope, the owner, the goods, the movement and the handover. A job runs under one of four services: forwarding goods the customer already owns, buying on the customer’s behalf, supplying and delivering against a tender, or a local pickup and delivery.
Each service has its own steps, and they do not leak into each other. Buying steps never block a forwarding job, because a customer who already owns the goods has nothing to buy.
Receive only what the partner confirms
A job starts with expected items. When the origin warehouse confirms a receipt, it is matched to those items and becomes parcels. An item is not a parcel: three items can arrive as two boxes. A parcel nobody can place stays unmatched rather than guessed onto a customer, and a duplicate receipt links to the one already there.
Parcels then travel in movements. One movement can carry parcels from several jobs, and a job can leave in parts. When only some parcels depart, the rest keep their own stage. Partner reference numbers attach to the parcel, the movement or the leg they belong to.
| Parcel | Stage |
|---|---|
| Expected | Agreed with the customer, not yet seen. |
| Received at origin | Confirmed by the warehouse. |
| Ready to send | Packed and waiting for a departure. |
| Departed | On a movement. |
| Arrived | At the destination warehouse. |
| Ready for handover | Waiting for the customer. |
| Handed over | Done. Delays, holds, damage and mismatches sit beside the stage, each with an owner. |
When it happened, not when it was typed
Every update keeps two times: when the event happened and when someone entered it. Late typing never makes a journey look longer. A backdated event keeps both. A missing time shows as not yet known, never as zero days.
Planned, promised and actual are kept apart. The first promise to the customer stays on record beside the latest estimate, so a slipping job can never quietly rewrite what was said.
- 3 Novwarehousereceived at origin · entered 3 Nov · confirmed
- 9 Novpartnerdeparted by air · entered 12 Nov · partner reported
- 14 Novstaffarrived · entered 14 Nov · visible to the customer
Keep each fact apart
Requested, purchased, received and delivered quantities are four different facts. An order for ten units is not evidence that ten arrived. Money is kept apart the same way: the price to the customer, the cost from the supplier, the company’s own expense, the invoice and the proof of payment.
An order for ten units is not evidence that ten arrived.
Profit stays provisional while costs are still coming in. Cash in the bank is not the profit of a job, and the record never pretends it is.
Tell the customer only what is true
Partner updates are entered by staff and labelled partner reported until they are confirmed. Nothing is inferred from a vague message: “should leave this week” does not mark anything as departed. When two sources disagree, both are kept and only confirmed wording is published.
The customer follows a long, hard-to-guess link that shows approved progress only, and never another customer sharing the same departure. Staff see a preview of exactly what the customer will see before it goes out. Replacing a file keeps the one it replaced, because a decision made on the old file still needs its evidence.
Planning ranges for a route are kept as ranges, not promises. Tragline never tells a customer “sixty days at most”.
What we chose not to build
| Turned down | Why not |
|---|---|
| Extending the prototype | Disposable. It was taken apart into documents and rebuilt on another stack. |
| A universal rule for extra costs | No automatic approval or spending threshold fits every job. |
| The prototype’s buffers and late fees | Numbers from a prototype are not policy. |
| Payment before release by default | Not assumed. Left open until the business decides it. |



