Ride Requests

Introduction

In Zoyride, a Ride Request is a travel request submitted by a passenger or user before it becomes a confirmed booking or trip. It contains important journey details such as passenger information, travel date, departure time, pickup location, drop location, office, shift, client, request type, route distance, and estimated travel time.

The Ride Requests module is used by administrators to review, approve, reject, and manage passenger ride requests. Admins can check whether a request can be assigned to an existing trip, create a new booking when no suitable trip is available, and review match failure reasons when a request cannot be linked to a trip.

This module helps ensure that passenger requests are properly verified before trip allocation. It supports route matching, seat availability checks, pickup and drop validation, trip assignment, and booking creation, making it an important part of daily commute, shuttle, and employee transport operations.

2. Accessing the Ride Request Module

Navigation

Admin Console > Operations > Ride Requests

The Ride Request listing page will display all ride requests submitted by users.

3. Ride Request Listing Screen

Available Information

Field	Description
Customer Name	Passenger name
Office	Office location
Shift	Assigned shift
Status	Pending / Approved
Client	Associated client
Departure Date	Travel date
Departure Time	Travel time
Request Type	Ride category
Actions	Edit/View/Delete

Available Actions

• Search Ride Requests
• Filter by Date
• Open Request
• Approve Request
• Assign to Existing Booking
• Create Booking
• Delete Request

4. Searching Ride Requests

Steps

1. Open Ride Request Module.
2. Locate the Search Box.
3. Enter: Passenger Name, Ride Request ID, or Route Information.

Matching records will be displayed.

5. Filtering Ride Requests

Steps

1. Click Date Filter.
2. Select Start Date and End Date.
3. Click Apply.

The system will display requests within the selected period.

6. Understanding Ride Request Status

• Pending: The request has been submitted but not reviewed.
• Approved: The request has been reviewed and is ready for booking assignment.

7. Approving a Ride Request

Steps

1. Open Ride Request.
2. Verify: Passenger Name, Travel Date, Departure Time, Pickup Location, Drop Location.
3. Change Status to Approved.
4. Click Save.

The request is now ready for trip allocation.

8. Ride Request Details Screen

When a request is opened, the following information is available:

Passenger Information

• Passenger Name
• Request Type
• Status
• Notes

Journey Information

• Trip Date
• Departure Time
• Pickup Location
• Drop Location

Route Information

• Route Map
• Estimated Distance
• Estimated Travel Time

Action Buttons

• Save
• Create Booking
• Assign in Existing Booking
• Check Trip
• Delete

9. Assigning to an Existing Booking

When to Use

Use this option when:

• A trip already exists
• Pickup and drop locations match
• Trip timing matches
• Seats are available

Steps

1. Open Approved Ride Request.
2. Click Assign in Existing Booking.
3. Review Matching Trips.
4. Select Suitable Trip.
5. Verify: Vehicle, Route, Available Seats.
6. Confirm Assignment.

The passenger will be added to the selected trip.

10. Creating a New Booking

When to Use

Create a booking when:

• No matching trip exists
• Existing trips are full
• Route does not match
• Special vehicle is required

Steps

1. Open Approved Ride Request.
2. Click Create Booking.
3. Verify: Route Number, Pickup Point, Drop Point, Timetable.
4. Confirm Passenger Reservation.
5. Click Save.

A new booking will be created.

11. Understanding Route Map

The Route Map helps administrators verify:

• Pickup Location
• Drop Location
• Route Direction
• Estimated Distance
• Estimated Travel Time

12. Check Trip Function

Purpose

Used to identify why a ride request could not be matched with an existing trip.

Steps

1. Open Ride Request.
2. Click Check Trip.
3. Enter Trip ID.
4. Click Check.

The system displays the failure reason.

Common Match Failure Reasons

Reason	Description
Route Mismatch	Pickup/Drop not on route
Time Mismatch	Departure time differs
Date Mismatch	Travel date differs
No Seats Available	Trip is full
Trip Inactive	Trip unavailable
Different Trip Type	Request and trip type differ

13. Distance and Time Information

• Estimated Distance: Calculated before trip creation using planned route.
• Actual Distance: Recorded after trip execution using GPS data.
• Estimated Travel Time: Expected travel duration.
• Actual Travel Time: Actual duration taken during the trip.

14. Ride Request Workflow

Passenger Creates Ride Request
           │
           ▼
Request Appears in Admin Console
           │
           ▼
Admin Reviews Request
           │
           ▼
Approve Request
           │
           ▼
Check Existing Trips
           │
   ┌───────┴────────┐
   │                │
   ▼                ▼
Trip Found      No Trip Found
   │                │
   ▼                ▼
Assign Trip    Create Booking
   │                │
   └───────┬────────┘
           ▼
Trip Confirmed
           ▼
Passenger Travels
           ▼
Trip Completion

15. Best Practices

Always Verify

• ✅ Passenger Name
• ✅ Travel Date
• ✅ Departure Time
• ✅ Pickup Location
• ✅ Drop Location
• ✅ Vehicle Availability
• ✅ Seat Availability
• ✅ Route Matching

Avoid

• ❌ Approving without route verification
• ❌ Assigning passengers to full vehicles
• ❌ Ignoring trip match failures
• ❌ Creating duplicate bookings

16. Quick Reference

Action	Purpose
Approve Request	Authorize travel request
Assign Existing Booking	Add passenger to available trip
Create Booking	Generate new trip
Check Trip	Identify match failures
Route Map	Verify travel route
Save	Update request details
Delete	Remove request