Product / Rider scheduling
Rider scheduling
Recommendations that protect a rider's earning time.
Rootd returns a suggested swap window that minimizes travel plus wait — surfaced through the operator's own app as a projection, never a separate consumer brand.
Earning time, protected
Point riders at the right station at the right minute.
Swap friction is travel plus queue. Rootd minimizes both — and hands the result to your app.
Suggested window
A window, not just a station.
Rootd reads live station load and returns the swap window with the least combined travel and wait — so a rider spends minutes idle, not a shift.
- Window derived from live station load
- Travel distance factored in
- Updates as conditions change
Less queue
Move riders out of the long tail.
A scheduled window shifts swap demand off the peaks, collapsing the long wait-time tail that quietly eats rider earnings.
- Demand spread off peaks
- Long waits become rare
- Modeled, then validated on your data
Illustrative distribution — modeled, not measured production data.
API output
Output your app owns.
Scheduling is a read API and a projection object. Your swap app chooses whether and how to surface it — Rootd never talks to riders directly.
- Clean projection payload
- Surface it, or don't
- Rootd stays a layer, not an app
01"rider_id": "rdr_8841",02"suggested_window": {03 "start": "13:20", "end": "13:50"04},05"station": "kawangware_hub",06"est_wait_min": 3,07"friction_saved_min": 11,08// recommendation only — your app decides surfacingLess time in the queue — more daily rider earnings retained after swap friction.
See the rider projection API run against your network's live load.