Aslan Kurierdienste is the operational reality behind Fleet by Elevera. Every workflow in the platform was pressure-tested in their yard before it shipped to anyone else.
The problem before Fleet
Like most DSPs, Aslan ran shift handovers on WhatsApp photos and a spreadsheet. Damage claims came down to "who said what" weeks after a vehicle was already back on the road. Maintenance lived in the dispatcher's head. Cost per vehicle was something you found out at month-end, not something you could act on.
How Fleet works for Aslan
Drivers start every shift with six mandatory photos in Fleet Go — Left, Right, Front, Back, Dashboard, Cargo. Dispatchers review the set against the previous day, tag damage, and convert anything new into an Incident with photo evidence attached. Maintenance, repair jobs, and per-vehicle cost flow into the same record. The audit trail is the photos themselves.
What changed in operations
Disputes are now resolved at handover, not at month-end. Damage that used to surface after a customer complaint shows up in the dispatcher review the same day. The team makes vehicle-by-vehicle cost decisions instead of fleet-wide guesses. Concrete numbers are being measured for the next case study update.
“Fleet replaced our WhatsApp groups, our spreadsheet, and three different paper forms with one workflow the drivers actually use. The photos are the evidence — there is no more arguing about damage.”
Run your DSP like Aslan does.
Photo-based shift starts. Structured incidents. Real cost visibility per vehicle.