Trip leg

A trip leg is the smallest unit a dispatcher can assign: one vehicle, one pickup, one drop-off. A simple airport transfer is a booking with one leg. A road show with six stops across two days might be one booking with six legs, each dispatched and billed on its own.

Operators have always thought in legs even when their software did not. The run board lists legs, not bookings, because a driver can only be in one place at a time. The manifest for Tuesday shows Tuesday's legs. A farm-out hands a leg to an affiliate, not the whole order.

Where it goes wrong is when the booking and the leg share one status field. Mark the booking complete after the outbound and the return disappears from tomorrow's board. Price the booking as one number and the affiliate on leg two cannot be paid correctly. Keeping the leg as its own record is what makes multi-leg work manageable.

How liverybook handles it

Each leg is a BookingTrip record under its Booking. It has 11 statuses (unassigned, assigned, driver_notified, en_route_pickup, arrived_pickup, passenger_on_board, arrived_dropoff, completed, cancelled, late_cancelled, no_show), and the 25 allowed transitions are enforced in the service layer with every change written to an append-only event log. A leg can be assigned to the operator's own driver and vehicle or farmed out to an affiliate, in which case Sub Driver and Sub Vehicle appear on the run board. The leg total is base rate + gratuity + tolls + parking + wait time charge + extras − discount, and invoice lines are created as legs complete. See bookings.

Related terms

• Multi-leg trip
• Status transition
• Passenger on board
• Base rate