In development · preparing pilots
FOR PEOPLE WHO ORGANISE ROAD FREIGHT
Understand the trip.See what matters.
Your own vehicle or a subcontracted carrier — you need useful updates either way. We are developing Cargo Polis to bring trip progress, recorded routes and location freshness into a clear web workspace.
An Android app for the driver. A web workspace for the company.
Position age uses the recording time.
TWO WORKING CONTEXTS
Different vehicles. Familiar questions.
FOR CARRIERS
01Your own and hired vehicles
Owners and dispatchers need a shared view: the last known location, how fresh it is and the route that was recorded.
Explore the carrier workflowFOR FORWARDERS
02Their vehicle. Your customer.
A forwarder gathers updates from different people and answers the customer. We start with an agreed view of one subcontracted trip.
Explore the forwarder workflowWHAT MAKES A USEFUL TRIP VIEW
A location is just the start
A timestamp next to the position
A last known location needs its recording time. A recently received message can still contain an old position.
A route with visible gaps
A recorded route helps you review the trip later. Missing data should remain visible, rather than becoming an invented route.
The driver takes part
Work sharing depends on the person's explicit participation. Devices, recipients and access boundaries are agreed before a pilot.
HOW THE WORKFLOW FITS TOGETHER
From the phone to the trip view
We start with one type of trip and a supported Android phone. Available features and limitations are confirmed before onboarding.
A PILOT IN THREE STEPS
Start with one workflow
- 01
Agree who takes part
Choose a trip, a driver, a device and the people who need updates.
- 02
Test recording and visibility
Check position delivery, recording time and the recorded route in the agreed workflow.
- 03
Review a repeat trip
Find out whether the view helps in daily work and how much onboarding support it needs.
BOUNDARIES OF THE FIRST WORKFLOW
Test the essentials. Develop what comes next.
A pilot starts with agreed features on selected devices. Future capabilities are not automatically part of it.
Android, map and history
Agree on the device, recording, position freshness and available view. Test your particular workflow.
A view for the customer
A limited, revocable link-based view. Readiness is confirmed before including it in a pilot.
Journal and notifications
Operational trip notes, events and Telegram notifications. Each workflow is confirmed separately.
Tracker, geofences and ETA
One selected tracker model after validation. Geofences and automatic arrival prediction need separate testing.
Explore the details
Practical trip visibility guides
What information do you need about a hired vehicle's trip?
A practical dispatcher checklist: participants, position recording time, operational updates and what to do when fresh information is missing.
Read guideHow to organise customer updates during a freight trip
Agree on the content of an update, separate facts from expectations and choose information that helps the customer make a decision.
Read guideLast known position: why the recording time matters
Understand position age, distinguish recording from delivery and review gaps in a route when updates arrive late.
Read guideNext step
Start with one of your trips
Tell us how you get updates from drivers and what is missing. We will choose one workflow to test together.