For delivery platform fleet partners

The problems

• Couriers rotate weekly, and nobody is sure who holds which vehicle and keyfob.
• Vehicles go down and deliveries stall before anyone knows which ones.
• The platform asks for uptime and you rebuild it from spreadsheets.
• Batteries and chargers disappear across hubs.
• Cost per vehicle is a monthly guess rather than a live number.

How RideControl solves them

• Control Tower shows vehicles on route against fleet size, live, per hub.
• Service Flow moves repairs across a kanban so downtime is planned, not discovered.
• Keyfobs and user management make courier rotation an administrative action with a record.
• Battery and asset inventory keeps packs, chargers and racks countable per hub.
• BI dashboards produce uptime and cost per vehicle you can send to the platform.

Typical setup

1. Step 1

   Group tree

   Country node per market, hub node per depot, and a client account node for the platform you deliver for.

2. Step 2

   Roles

   Hub leads scoped to their hub, an operations manager per country, finance with read access across the tree.

3. Step 3

   Zones

   One zone per hub plus the delivery area, so off-shift use and vehicles leaving the city are caught.

4. Step 4

   Service

   Your own workshop on the kanban, or servicing run with RideCare under agreed SLA and uptime targets.

5. Step 5

   Reporting

   Weekly uptime and utilisation export for the platform, straight from the dashboards.

Results operators see

• 97% fleet availability tracked on the dashboard.
• Zero-gap delivery slots because down vehicles are known before the shift.
• Cost per vehicle visible per hub instead of at month end.

Which plan fits