Ride-hailing app
The order: from, to, when, party size, tariff. Vehicle and driver assignment, status (accepted, en route, on site, closed), payment for the ride. The client sees progress. This is a ride order — not a ticket for a fixed departure.
Capabilities · Operational platforms
Rides — a ride-hailing app and a fleet planner
This is not ticket sales and not a public timetable. The client orders a ride. A dispatcher or an algorithm assigns a vehicle and a driver. In parallel the fleet planner holds the cars: who can drive, which vehicle has valid motor liability and an inspection, who is on shift. One record from order to payment — without a marketplace brand.
Ride · fleet · driver
Where the fleet and the ride order break
The order arrives by phone. The driver sits in another messenger. Inspection and motor liability live in a folder or in the bookkeeper’s calendar. The car goes out even though cover expired yesterday. The dispatcher does not know who is free. The client cannot see status. The shift settlement is three lists. When order volume grows the manual model fails — and a ticket desk will not fix it.
Modules
What sits in this process
Fleet planner
Which vehicle is free, in service, on shift, withdrawn. The planner lays the day: who leaves with what, when they return, what stays in reserve. A clash (two orders on the same car) is visible at save time, not after start.
Vehicle: inspections and motor liability
The car record: registration, periodic inspection, motor liability, motor damage cover, tests, driver personal-accident cover, end dates. The planner will not release a vehicle with expired cover or inspection — or it requires an explicit override. Documents sit on the vehicle, not in a cupboard.
Drivers
Licences, medicals, working time, assignment to a vehicle and a shift, status (free, on a ride, break). Sickness or a missing licence reaches the planner: that car does not get the next order.
Dispatch and the driver app
The order queue, manual or automatic assignment, a swap, a breakdown. An Android app: accept the ride, arrive, start, close, a protocol or a photo when the process requires it. Dispatcher and driver see the same order.
Ride settlement
Tariff, supplement, client payment, the driver or subcontractor share, invoice. The shift and the day close on the same orders. Finance does not stitch SMS messages to a bank statement.
Integrations
- Ride payment — gateway, cash, company transfer, a B2B invoice.
- Notices: order accepted, arrival, close.
- Map and geolocation when in scope — status on the order, not in a separate app.
- An Android app for the driver; a web panel for the dispatcher and the corporate client.
- Reports: ride count, idle time, cost per vehicle, motor-liability and inspection dates, driver use.
Directed solutions
- An on-demand ride operator — own app, own fleet, no marketplace intermediary.
- A carrier with a fleet planner — vehicles, inspections, motor liability and drivers in one place, before a client app is added.
- Corporate B2B transport — orders from a counterparty, the same planner and settlement.
Example first stage
One fleet or one team: vehicle records with motor-liability and inspection dates → the day’s planner → a ride order → driver assignment → payment. Acceptance: a car without valid cover does not get an order, dispatcher and driver see the same status, finance sees the ride. A client app or a second tariff — the next stage. We do not build a ticket desk or a public timetable.
Related areas
Describe your business need — we will propose the right technology and the next work stages. Contact: [email protected]
Go to contactView all capabilities