How automatic scheduling works

Scheduling takes the unassigned trips for a day, the vehicles that are active for that day, and your operational constraints, and produces a proposed plan: which vehicle runs which trips, in what order.

Hard constraints

These are never traded away to produce a tidier plan. If they cannot all be met, the trip is left unassigned with a reason rather than placed somewhere unsuitable.

• Vehicle capability must cover the trip's service type.
• Appointment times must be met.
• Pickup windows must be respected.
• Driver shift limits must not be exceeded.

What it optimizes for

Within those constraints the objective is a balanced, low-deadhead day: reduce empty running between stops, avoid loading one vehicle while another idles, and keep each route geographically coherent so a delay early in the day does not cascade across the whole fleet.

Running it

1. 01Open the day you want to build in Trips.
2. 02Start scheduling. It runs as a background job — you can keep working while it does.
3. 03When the job completes, the proposed plan appears. Nothing is sent to drivers yet.
4. 04Review it, adjust anything that needs a human decision, then publish.