Quick Driver
An on-demand driver-hailing platform — customers book a verified professional to drive their own vehicle. This document specifies the Customer app, Partner (Driver) app, and Admin console.
1. Overview
1.1 Purpose
This document defines the product requirements for Quick Driver, an on-demand driver-hailing platform that connects customers who own vehicles with verified professional drivers. Unlike a ride-hailing service, the customer books a driver to operate the customer's own vehicle. The platform spans three applications: a Customer App, a Partner (Driver) App, and a web-based Admin Console.
1.2 Product vision
To become the most reliable and trusted on-demand driver service by offering instant and scheduled bookings, transparent dynamic pricing, verified drivers, and specialized matching for premium and luxury vehicles — backed by an operations console that gives the business full control over rides, pricing, drivers, and finances.
1.3 Scope
In scope: Customer App, Partner App, and Admin Console covering instant rides, scheduled rides, outstation (one-way and round trip), rentals, and hourly bookings; OTP authentication, Aadhaar KYC, the dynamic surcharge engine, insurance, driver packages, dispatcher tooling, and financial reporting.
Out of scope (v1): Multi-country/multi-currency operations, an in-app vehicle marketplace, and third-party fleet-management integrations beyond defined APIs.
2. Personas
Five primary actors interact with the platform.
| Persona | Description | Primary goals |
|---|---|---|
| Customer / Owner | Owns a car, needs a professional driver on demand or on schedule. | Book quickly, fair price, safe & verified driver, good match for premium cars. |
| Partner / Driver | Professional driver who accepts ride requests. | Steady ride flow, fair payouts, clarity on schedule, easy onboarding. |
| Fleet Owner | Owns multiple vehicles or employs fleet drivers. | Manage fleet drivers, track earnings, assign rides. |
| Dispatcher | Ops staff who manually assign / manage rides. | Resolve unassigned rides, manage rentals & hourly bookings. |
| Admin / Ops | Business operator running the platform. | Control pricing, monitor finances, manage users & content. |
3. Customer App
3.1 Authentication & onboarding
Login and registration use a single unified OTP-based flow on a mobile number, with no password. The OTP is delivered by SMS with auto-read support, configurable expiry (default 5 minutes) and resend cooldown (default 30 seconds); fallback channels (WhatsApp / IVR) are configurable from Admin. New numbers proceed to onboarding; existing numbers go straight to the home screen. A first-launch onboarding carousel communicates the value proposition, how it works, and safety; its content is managed from Admin → Content Management → On Boarding. The profile captures name, optional email, gender, photo, saved addresses, emergency contacts and language preference.
3.2 Vehicle garage
The customer adds one or more vehicles, each with brand, model, type (hatchback / sedan / SUV / luxury), transmission and registration number. Vehicle type drives both matching and pricing at booking time, and luxury vehicles unlock brand-qualified driver matching (§3.6).
3.3 Ride booking — instant & scheduled
Instant booking performs an immediate driver search and assignment from the current location. Scheduled booking lets the customer pick a future date and time; the system reserves a driver and dispatches ahead of the slot, sending reminders to both customer and driver. In either mode the customer selects which garage vehicle the driver will operate.
3.4 Outstation — one-way & round trip
For one-way outstation trips, the fare is the base plus the per-km outstation rate for the full distance, plus the applicable driver allowance and a return-deadhead component as configured. For round trips, the fare accounts for total trip duration, multi-day driver allowance, night charges and waiting time; the return fare is added to the estimate explicitly and shown in the fare breakup. The estimate must itemize base, distance, return-fare addition, allowances, surcharges, taxes and insurance before confirmation.
3.5 Driver schedule feature
Customers can request a specific driver (subject to availability) for recurring or future trips when that driver has published availability. Drivers publish availability windows in the Partner App, and the Customer App surfaces matching slots for scheduling. Recurring schedules (for example a daily office commute) are supported with per-occurrence cancellation.
3.6 Luxury matching (brand + car)
For premium and luxury vehicles, only drivers explicitly qualified for that brand and segment are matched, ensuring competence with high-value cars. Driver profiles carry capability tags — car segment (economy / premium / luxury), eligible brands (e.g. BMW, Mercedes, Audi) and transmission expertise. The matching engine filters the candidate pool by the booked vehicle's brand and segment before ranking by proximity and rating. If no qualified luxury driver is available, the customer is offered a scheduled slot rather than a mismatched instant assignment.
3.7 Trip lifecycle, payments & support
The customer sees live tracking of driver arrival and trip progress with ETA. Payment supports in-app methods (UPI, cards, wallet) and cash, configurable in Admin → Payment Methods, with coupons applied at checkout. After the trip the customer rates the driver and receives a receipt with the full fare breakup including insurance and surcharges. An SOS control is available during the ride, along with trip history and re-book.
4. Partner (Driver) App
4.1 Onboarding & Aadhaar verification
Driver KYC is performed via Aadhaar online verification (OTP-based eKYC / DigiLocker integration) during onboarding. Additional documents are captured and verified: driving licence, address proof, profile photo, and police clearance where required. Verification status (Pending / Verified / Rejected) is tracked in Admin → Settings → Driver Documents, and a driver cannot go live until verified.
4.2 Preferred assignment escalation
When a ride request is not accepted within the first dispatch window, the system escalates to guarantee fulfilment. Tier 1 offers the request to the nearest eligible drivers. If unaccepted, Tier 2 broadens to preferred / higher-incentive drivers and an increased radius. If still unaccepted, Tier 3 routes the request to the Dispatcher for manual assignment from the Admin console. Escalation timers and incentive bumps are configurable from Admin.
4.3 Driver packages
Drivers subscribe to packages (for example daily, weekly, commission-based, or zero-commission subscription). Packages define the commission rate, payout rules and ride-access privileges, and are managed from Admin → Business Setup → Subscription Plan. The driver wallet shows earnings, package status and renewal.
4.4 Before-start & after-start vehicle video
To document vehicle condition and protect both parties, the driver records a short walk-around video at two checkpoints. The before-start video is mandatory, timestamped and geo-tagged, and recorded before the trip begins; the trip cannot transition to In-Progress until it is captured (configurable enforcement). The after-start / end video is recorded at completion to capture final condition. Both are uploaded and linked to the trip record for dispute resolution and insurance claims, with a configurable retention period.
5. Admin Console
The Admin Console is the web-based operations and configuration hub, organized as a grouped left-sidebar navigation.
5.1 Navigation structure
| Category | Items |
|---|---|
| Dashboard | Main landing page with KPIs and metrics. |
| Access Management | Access Control, Live Tracking. |
| Rides & Service Management | Instant Ride Bookings, Rental Bookings, Hourly Driver Bookings, Website Bookings. |
| Dispatcher Management | Dispatcher Rides, Dispatcher Rental, Dispatcher Hourly. |
| Users Management | Customers, Drivers. |
| Owner Management | Owners, Fleet Drivers. |
| Business Setup | Instant Ride Package, Rental Packages, Hourly Package, Subscription Plan. |
| Customer Support | Support, SOS, Notification. |
| Content Management | Banners, On Boarding, CMS Pages. |
| Site Management | Landing Page Template, Terms & Conditions, Privacy Policy. |
| Reports Management | User Reports, Driver Reports, Travel Reports. |
| Settings & Configurations | General Settings, Zones, Tax Settings, Coupons, Business Model Settings, Email Template Settings, Payment Methods, Driver Documents. |
| Payment Management | Payouts, settlements, commission ledger, refunds, reconciliation. |
5.2 Dashboard metrics
The dashboard surfaces total and today's figures across operations and finance: trip volume (Total Trips and Today's Trips); user & driver stats (active counts for Users, Individual Drivers, Owners and Fleet Drivers); financial summaries (Total Earnings and Admin Commission, each categorized by Ride and Rental); and trip status trackers (Completed, Confirmed and Cancelled trips).
6. Dynamic Surcharge Engine
A configurable multiplier engine adjusts fares in real time based on environmental and demand conditions. All factors are managed from Admin and shown transparently to the customer at estimate time, with a maximum combined multiplier to protect customers. See the engine recompute a fare live in the demo →
| Factor | Trigger | Behaviour |
|---|---|---|
| Weather / Rain | Weather API flags rain in the zone, or admin manual toggle. | Applies a rain multiplier to base fare for affected zones. |
| Demand spike | Live demand-to-supply ratio exceeds threshold. | Tiered surge multiplier scales with the ratio. |
| Festival / Event | Admin-scheduled event windows. | Applies an event multiplier for the configured window & zone. |
| Night charge | Trip within configured night hours. | Fixed or percentage night surcharge. |
| Insurance | Per-trip coverage (bundled or opt-in per config). | Premium shown as a line item; certificate stored on the trip. |
Multiple factors combine per a configurable rule and are capped at a maximum total multiplier. The customer always sees a clear surge indicator and the reason before confirming.
7. Ride Status Model
| Status | Meaning |
|---|---|
| Requested | Customer submitted; searching for a driver. |
| Confirmed | Driver assigned / accepted (instant or scheduled). |
| Arrived | Driver at pickup; before-start video pending. |
| In-Progress | Trip ongoing after before-start video captured. |
| Completed | Trip ended; after-start video captured; payment settled. |
| Cancelled | Cancelled by customer, driver or system, per cancellation policy. |
8. Non-Functional Requirements
Performance
Driver-matching response under 5 seconds for instant rides; dashboard widgets load under 2 seconds.
Scalability
Handle peak surge windows (festivals / events) with horizontal scaling of matching and pricing services.
Security & privacy
OTP auth, encrypted PII, masked calling, secure storage of KYC and trip videos, and role-based access control for admin.
Reliability
99.9% uptime target, with graceful degradation of surge inputs (e.g. weather API outage falls back to manual control).
Compliance
Aadhaar eKYC handling per UIDAI norms; insurance and tax compliance per jurisdiction.
Observability
Audit logs for fare changes, surcharge application and admin actions.
9. Open Questions
- Confirm the insurance model — bundled into every fare versus opt-in line item.
- Define the maximum combined surcharge multiplier cap.
- Confirm the Aadhaar verification provider (DigiLocker vs. a licensed KYC vendor).
- Define payout cadence and settlement cycle for drivers and fleet owners.
- Confirm which booking types launch in v1 versus later phases (hourly, rental).