Ride bookings

Start with the rider’s pickup and dropoff addresses, the requested time and the operating service zone. Dispatcher records the booking owner and the requested units, then attaches the ride request to that booking. A clear subject helps the next shift recognize the journey without relying on a separate conversation. Keep the request number available when discussing a change with the rider.

A booking carries the planned start and end of the operating interval. The ride request carries the rider and address details. This separation matters when an address changes after a driver has been considered: the desk needs to revisit the assignment and review the current booking, while retaining the earlier decision and its revision.

• Prepare the request. Dispatcher keeps the booking in Draft while checking addresses, timing and the operating organization. A ride request begins as Planned and stays attached to the booking it supports.
• Ask for review. Move the booking to Review when the reviewer has enough information to decide. Operations Reviewer uses the booking revision and supporting evidence to record the outcome and reason.
• Keep the journey visible. Use the booking schedule for planned intervals and the request board for pickup progress. The booking owner remains accountable for explaining changes to the dispatch desk.

Agree what requested units mean for your service, how long a booking interval should cover and who can change a reviewed journey. Decide how staff record the local operating time zone and how they distinguish a rider’s requested pickup from a later operational change. Prepare service-zone names that dispatchers can use consistently across shifts.

Choose the minimum evidence Operations Reviewer needs before approving a booking. The reason for returning a request should tell Dispatcher what to correct. Review the cancellation policy alongside this setup so a no-show, a cancelled booking and a completed ride remain distinguishable during reporting. Keep any rider-facing booking connection tied to the same booking and request identifiers.

A rider requests a station pickup and later changes the destination before departure. Dispatcher opens the existing ride request, confirms the new dropoff and checks whether the planned interval still fits. If the change affects reviewed scope, return it through the agreed review path before confirming the assignment.

Operations Reviewer checks the revised booking and records the reason for the new decision. The next dispatcher should be able to identify the current address and the revision that was approved. Trip Coordinator should find the same rider and request when recording arrival. Rehearse the case across a shift change, with the incoming colleague explaining the journey from the records alone.

• Active Bookings — Approved journeys being coordinated by the dispatch desk.
• My ride bookings — The current staff member’s bookings with their planned interval and revision.
• Ride booking schedule — Planned ride intervals for coordinating the upcoming shift.

Use booking to assignment to rehearse preparation and review. Continue with trip to completion after a driver has accepted the work.