Open the reservation from Dispatch and confirm you are working on the correct trip.
Assignment check
- Review date, time, route, and requested vehicle or service type.
- Select the intended driver and vehicle from the available resources.
- Re-read the assignment before saving.
- Confirm the board reflects the new assignment.
Trip status should represent what has actually happened. Do not advance status only to remove an alert or make the board look complete. If the expected driver or vehicle is missing, review fleet readiness and active state before creating a duplicate resource.
Review assignment rules
Administrators configure assignment rules under Settings → Operations → Dispatch. Assign without vehicle, Override service type, and Override capacity limit each display Allow, Warn, or Block. Different vehicle type remains a separate switch.
Review the rule that applies to the proposed assignment. If an assignment produces a warning or rejection, investigate the driver, requested service and passenger capacity before proceeding. Do not change an organization-wide rule merely to clear one trip. See Configure operational settings for the settings workflow.
Check an affiliate assignment
A farmed-out reservation can show the affiliate’s Chauffeur & vehicle details, including whether the chauffeur has accepted and the latest relayed status. An offer still awaiting a response or a message that no chauffeur is assigned needs follow-up with the affiliate; it is not a local resource assignment.
Use the booking’s References when coordinating the trip. If a farmed-in trip is sent onward, the affiliate section identifies the originating partner with Sent by and shows the executing partner’s details. Keep the partner’s offer, chauffeur acceptance, trip status, and payment status distinct when deciding the next action.