90-second worked example
One Cape Town–
See how a road-freight request can move from requirement to operator approval, pickup evidence and delivery proof without losing the commercial history between inboxes and chat threads.
Illustrative workflow and sample data. This is not a live shipment, quote, tracking feed or service guarantee.
Movement example
CS-DEMO-CTJHB-001
Cape Town
Epping
Johannesburg
City Deep
- Cargo
- Palletised goods
- Equipment
- Tautliner
- Mass
- 12,400 kg
- Evidence
- Pickup + POD
The movement record
Four operational moments stay connected.
CargoSpace keeps the requirement, decision and evidence in sequence, so the next action is visible and the completed job can strengthen the operator's record.
- 08:02
Step 1
Request captured
18 pallets · 12,400 kg
Shipper records the lane, cargo, mass and timing once.
- 08:11
Step 2
Operator approved
Tautliner · GIT evidence requested
The operator confirms suitable capacity and the agreed movement terms.
- 16:42
Step 3
Pickup recorded
Epping, Cape Town
Collection evidence is attached to the same movement record.
- 10:18
Step 4
Delivery proved
City Deep, Johannesburg
Delivery and proof close the loop without rebuilding the history from chat messages.
What survives the trip
The proof becomes a business asset.
The example shows the intended CargoSpace workflow. Actual availability, approvals and evidence depend on the participants and the live movement.
- One agreed movement reference
- Named shipper and operator
- Cargo, route and timing captured
- Pickup and delivery evidence linked
- A reusable operating history
Controlled design-partner release
Run one real movement and measure what the workflow improves.
Suitable Cape Town–Johannesburg operators can evaluate the workflow with CargoSpace. Participation, commercial terms and any real movement are agreed separately—nothing on this page creates a transport booking.