“The approved requirements do not define which ride stages allow cancellation, what reasons are required, or when a fee applies.”
MetroMove pilot management requirements
Open complete sourceRiders expect cancellation, but requirements and service rules do not define permitted stages, reasons, or fees after matching.
Source alignment
Every quote below is an exact substring of its linked fixture source and is checked against stable chunk offsets.
“The approved requirements do not define which ride stages allow cancellation, what reasons are required, or when a fee applies.”
MetroMove pilot management requirements
Open complete source“Riders said they need to cancel when a driver is delayed or moving away from the pickup point, but they do not know when cancellation stops being available.”
Rider support feedback summary
Open complete source“The service contract does not define permitted cancellation transitions after matching or after a driver starts toward pickup.”
Current architecture and feature summary
Open complete sourceOperational / business
Riders and support staff may receive inconsistent outcomes, increasing disputes and failed trip expectations.
Technical
The application cannot enforce a complete transition policy until product and operations make the missing decisions.
Approve a cancellation decision table covering ride stages, actors, reasons, fees, and user messaging before expanding the interface.
Acceptance criteria
Linked deployment workstream
Make wallet activity auditable and cancellation behavior operationally consistent.