Status transition

A status transition is one step in a trip's life, assigned to en route, en route to arrived, and a well-run operation permits only a defined set of them. liverybook permits 25. The point of the limit is that a trip cannot go from unassigned to completed, or from completed back to en route, by a slip of the mouse.

Two things live in the transitions: the dispatcher's picture of the day, and the money. Completed triggers the invoice line. Late cancelled triggers the late-cancel fee. No-show triggers the no-show fee. If the status is wrong, the invoice is wrong, and the bookkeeper finds out a month later when the customer disputes it.

The common mistake is software that treats status as a free-text dropdown. A trip marked completed by accident, then quietly changed back, leaves no trace, and the invoice it created does not undo itself.

How liverybook handles it

Bookings have 7 statuses (draft, confirmed, in_progress, completed, cancelled, late_cancelled, no_show) and each leg has 11 (unassigned, assigned, driver_notified, en_route_pickup, arrived_pickup, passenger_on_board, arrived_dropoff, completed, cancelled, late_cancelled, no_show). The 25 allowed transitions are enforced in the service layer, every transition is appended to an event log, and the run board receives a trip.status_changed event over the WebSocket. Affiliate drivers may move a farm-out from en route to completed but cannot cancel or mark no-show.

Related terms

• En route
• Passenger on board
• Run board
• Late cancel