Flexible Scheduling Mode to Reduce Ride Cancellations and Churn
Fixed departure times were driving cancellations on scheduled rides, so this write-up loosens them into windows
✳The problem they went after
Scheduled rides on Adrenox demand an exact departure time, which puts the coordination burden on the rider and drags down match success for the platform. When no driver is available at that precise minute, or plans shift slightly, the booking gets cancelled. Riders who go through that a few times start using the product unevenly week to week, and eventually stop.
✳What they actually did
A flexible scheduling mode lets riders pick a 15 to 30 minute departure window instead of a single time. A recurring commute option saves ride patterns that already worked so daily commuters stop re-entering the same details. Smart pickup optimisation suggests adjusted pickup points based on live driver availability to lift match rates. Four-week retention is the primary metric, backed by weekly active riders and time-based cancellation rates, with on-time arrival and driver drop-off as guardrails. Rollout starts at a 20 percent pilot.
✳What you can take from it
Worth stealing
- 15 to 30 minute departure windows replace fixed times
- Saved recurring commutes remove re-entry friction
- On-time arrival guardrail protects service reliability
- 20 percent pilot gated on guardrails staying stable
Read this if
Marketplace PMs where match failure, not demand, is causing cancellations
The transferable bitRelaxing a constraint on one side of a marketplace improves matching for both sides at once. The discipline around it matters as much as the idea: flexibility is paired with reliability guardrails, and expansion beyond the pilot is explicitly conditional on those guardrails holding rather than on the retention number alone.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
