Read the solution: ETAs, distance, loadCopy link

After a solve, the Optimize page shows the solution at three levels: the whole plan (the metrics strip), each vehicle's day (the route cards), and each stop (the stop rows).

The examples use the ready-made Time windows plan; load it to work from the same data:

Tutorial - Time windows
Twelve stops with morning and afternoon delivery windows, covered by two vans on day shifts.
Open in app

The metrics strip: the whole plan in one lineCopy link

The plan header card: Plan 1 IN SYNC, Export and Optimize buttons, and the metrics strip with orders, routes, distance, duration, and cost

Across the top of the page:

  • ORDERS: how many orders the plan contains.
  • UNASSIGNED: shown in red only when at least one order could not be served. Click into the red panel below for the reasons; see Why an order went unassigned.
  • ROUTES: how many routes the solution uses. When any vehicle reloads at a depot mid-day, this becomes ROUTES / TRIPS.
  • DISTANCE, km (or mi): total driving across all routes.
  • DURATION, Hrs: total working time across all routes.
  • COST: the plan's total cost under your vehicle cost model. See Vehicle costs and the COST metric.
  • # PROBLEMS: shown only when the solution contains constraint violations, usually after manual edits. See Problems and warnings, explained.
  • TIME LEFT: countdown, only while a solve is running.

Route cards: one vehicle's dayCopy link

A route card with per-route stats and stop rows showing ETAs, travel legs, time windows, service times, and loads

Each route gets a card with its color swatch and vehicle id, plus a row of per-route stats:

  • STOPS: how many stops the route visits.
  • DISTANCE and DURATION: this route's share of driving and time.
  • LOAD: the total load delivered on the route.
  • PROBLEMS: in red, only if this route has violations.

The card header also holds the route's actions: Share route, show or hide this route on the map, isolate it (zoom to just this route), and the route actions menu used for manual editing.

Stop rows: what happens at each stopCopy link

Inside a card, stops are listed in visiting order. Each row reads:

  • The stop number in route order. A D marks the depot at the start and end of a route.
  • ETA: when the vehicle arrives, plus the travel time and distance of the leg from the previous stop.
  • The order id and its address.
  • The order's rules where they apply: time window, service duration, release time.
  • The load delivered or picked up at the stop.

Two kinds of annotation can appear under a stop:

  • Red problem lines flag a constraint violated at this stop, for example "Misses a delivery time window by 12 min". These are explained one by one in Problems and warnings, explained.
  • A blue line like "Waits 25 min for the window to open" means the vehicle arrives early and idles. Not an error, but long waits indicate that a window or the shift start could move. On the tutorial plan above, the morning and afternoon windows produce visible waits.

Trip dividersCopy link

When a vehicle returns to a depot to reload mid-route, the stop list shows a divider: ↻ Trip 2, with that trip's own distance. Everything below it is the second loop out of the depot. Reloading is covered in Multiple depots, open routes, and reloads.

Decluttering a big solutionCopy link

Three controls change what the list shows:

  • The filter box above the routes narrows the list to matching orders and routes.
  • Show/Hide all statistics collapses the per-route stat rows; each card also has its own toggle.
  • Show/Hide all stops details collapses the per-stop detail lines to bare rows, also available per route.

Hiding details does not change the solution, only the display. For map-side reading, see the isolate and layer controls in View a single route vs. all routes.

Next stepCopy link

If the numbers look right but a stop sits in the wrong place: Edit routes by hand: drag, split, merge.