Features

Features are broken down by platform and version number. All v2 features are subject to change given analysis of v1 reception.

User Types

1. Rider Represents the user profile CULift Rider.
2. Driver Represents the user profile RR Driver.
3. Admin Encompasses the user profiles RR Scheduler, RR Dispatcher, and SDS Admin

We have decided that scheduler, dispatcher, and SDS admin should be rolled into one user type that has the same level of administrative access to account for overlaps in features/responsibilities of these roles. We have confirmed with Emily, our SDS contact who represents the most stringent of our privacy responsibilities, and she has indicated that this model is permissible.

Platforms

1. Rider Mobile - Our primary rider platform. Ideally, we want all riders to schedule and interact with their rides through this platform.
2. Driver Mobile The sole driver platform. All drivers will use this platform to track their rides and communicate progress with the dispatcher.
3. Admin Web The sole administration platform. The scheduler will schedule rides, the dispatcher will monitor rides, and the SDS admin will set permissions and monitor metrics all via this platform.
4. Rider Web The secondary rider platform. This platform is required by SDS to serve any Riders that do not have access to a smartphone. Functionality of the Rider Web does not necessarily need to reach feature parity with Rider Mobile, merely feature parity with the currently in place CULift system.

Rider Mobile

v1 Features

Scheduling a Ride

• Request rides before 10am before the day of the ride
  • Support repeat rides
• View, edit, and cancel rides (edits only guaranteed if made by 10am the day before the ride)
• Receive mobile notification confirmation of scheduled rides

Waiting for a Ride & On a Ride

• View upcoming rides, and the status of their rides (ie. pending, scheduled, driver en route, running late, in progress, completed)