Every trip on the record, from the tracker and the app
A trip is planned by the office or logged by the tracker, and both land on one list. Each trip keeps who drove, where and when, as the record a summons or a fuel fill is matched against.
Planned and logged trips on one list
Trips planned by the office and movements logged by the tracker sit on one list, with planned against actual km and whether the pre-trip check was done. An unplanned movement is a row with a question for the driver, not an alarm.
- Movement outside the working day is flagged
- Under way, done, cancelled or reassigned, with the reason a trip was cancelled
The trip record
A timeline from the tracker and the app: the pre-trip check, ignition and odometer, each stop and each toll. The route driven shows against the route planned, with the toll, parking and estimated fuel for the trip.
On a trip, in the app
The driver sees the next stop and one button per stop, with nothing to type while driving. Directions stay in the phone's own maps app, and after the trip the driver sees the distance, stops, toll and driving events in plain words.
Driving events, not scores
Harsh braking, speeding and idling are recorded for each trip and rolled up per driver by month. They are not scored in the app, and what is done with them is the organisation's own HR policy.
The trackers you prefer
The organisation buys trackers from the supplier it prefers, and asasii fleet reads the common tracker protocols. Every tracker shows on one list with its model, firmware, last position, ignition and status.
- A live map of the fleet, refreshed every 30 seconds
- A tracker offline over 24 hours on a vehicle that moved becomes a defect on the vehicle
- A driver's location shows to the office only on duty
See it on your own fleet
Send us the number of vehicles and drivers, the trackers and fuel cards you use, and how defects and renewals are tracked today. An engineer replies with a rollout plan, an integration list and a proposal.