---
metadata:
  - name: generator
    content: Diplodoc Platform v5.52.0
alternate:
  - https://yandex.kz/routing/doc/en/vrp/result-excel.md
  - https://yandex.kz/routing/doc/kk/vrp/result-excel.md
  - https://yandex.kz/routing/doc/ru/vrp/result-excel.md
  - https://yandex.kz/routing/doc/tr/vrp/result-excel.md
  - href: en/vrp/result-excel.md
    type: text/markdown
    title: Markdown version
  - href: llms.txt
    type: text/markdown
    title: llms.txt
title: RouteQ — working with the interface — planning result
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.kz/routing/doc/en/llms.txt


# Planning result

{% list tabs %}

- Export via the interface

  On the page with the [resulting solution](https://yandex.kz/routing/doc/en/vrp/interface-result.md):

  1. Click **Export** in the upper-right corner.
  1. Select **Solution in Excel**.

- Direct link export

  `https://yandex.ru/courier/companies/<company_id>/depots/all/mvrp/<task_id>/export/excel`, where:

  - `<company_id>` is the company ID. You can find it in **Settings** → **Company** → **Company ID**.

  - `<task_id>` is the task `id`.

{% endlist %}


You can use the exported file for analysis or upload it to another system. Please note that the structure and the order of columns in the file may change.

The Excel file with the results contains several sheets:

- **Routes**
- [Extended routes](#extended-routes)
- [Metrics](#metrics)

Information from the **Routes** sheet is fully duplicated on the **Extended routes** sheet. For this reason, we'll only describe **Extended routes** below because this is where you can find more information.


## Extended routes {#extended-routes}

The **Extended routes** sheet contains information about the routes planned for vehicles or couriers.

A route is a list of locations that need to be visited in a certain order to deliver all orders. The sheet lists the locations from top to bottom as planned in the route, from the first to the last to be visited. Routes are separated from each other by an empty row.

You can plan multiple shifts and runs (including multiple runs within the same shift) for one vehicle or courier. This depends on the company or depot settings.

The fields on the **Extended routes** sheet can be combined into several groups:

{% cut "Order parameters" %}

- **Order number** (`ref` in the API).
- **Client's address** (`description`).
- **Comment** (`comments`).
- **Client's phone number** (`phone`).
- **Client** (`title`).
- **Time of arrival at the order location/depot** (`arrival_time`).
- **Departure time** (`departure_time`).
- **On-site service duration** (`total_service_duration`).
- **Handling time at location** (`shared_service_duration`).
- **Order handling time (sec)** (`service_duration_s`).
- **Service duration for location (sec)** (`total_service_duration_s`).
- **Handling time at location (sec)** (`shared_service_duration_s`).
- **Time of arrival (sec)** (`arrival_time_s`).
- **Departure time, sec** (`departure_time_s`).

{% endcut %}

{% cut "Vehicle and courier shift parameters" %}

- **Vehicle ID** (`vehicle_ref` in the API).
- **Shift** (`shift_time_window`).
- **Vehicle ID** (`vehicle_id`).
- **Shift ID** (`shift_id`).
- **Transportation method** (`routing_mode`).
- **GPS tracker number** (`vehicle_imei`).
- **Custom units** (`shipment_size_custom`).
- **Custom capacity units** (`vehicle_capacity_custom`).
- **Vehicle properties** (`vehicle_tags`).
- **Vehicle requirements** (`required_tags`).
- **Optional tags** (`optional_tags`).

{% endcut %}

{% cut "Route and route point information" %}

- **Route number** (`run_number` in the API).
- **Transport stop number** (`stopIndex`).
- **Location type** (`location_type`).
- **Break duration** (`break_duration`).
- **Delivery interval / depot operating hours** (`time_window`).
- **Hard time window** (`hard_time_window`).
- **Order handling time** (`service_duration`).
- **Travel time to destination** (`transit_duration`).
- **Order transit time** (`on_board_duration_s`).
- **Distance to destination (km)** (`transit_distance_km`).
- **Waiting time before interval starts** (`waiting_duration`).
- **Late arrival type** (`failed_time_window_how`).
- **Late arrival duration** (`failed_time_window_duration`).
- **Vehicle load capacity (kg)** (`vehicle_capacity_weight_kg`).
- **Vehicle carrying capacity (units)** (`vehicle_capacity_units`).
- **Order weight (kg)** (`shipment_size_weight_kg`).
- **Order size (capacity)** (`shipment_size_units`).
- **Order volume, m³** (`shipment_size_volume_cbm`).
- **Picked orders** (`picked_orders`).
- **Location ID** (`id`).
- **Distance to destination (m)** (`transit_distance_m`).
- **Break duration, sec** (`break_duration_s`).
- **Travel time (sec)** (`transit_duration_s`).
- **Waiting time (sec)** (`waiting_duration_s`).
- **Latitude** (`point_lat`).
- **Longitude** (`point_lon`).
- **Zones** (`zones`).
- **Excluded zones** (`avoid_zones`).

{% endcut %}

For more information about these parameters, see the description of the [Orders](https://yandex.kz/routing/doc/en/vrp/excel-fill-guide.md#orders) and [Vehicles](https://yandex.kz/routing/doc/en/vrp/excel-fill-guide.md#vehicles) sheets for the planning file.


## Metrics {#metrics}

The data from the **Metrics** sheet is used to analyze planning effectiveness and build more accurate routes.

Metrics are calculated both for all routes together (see the **All vehicles** column) and each vehicle route separately.

They can be divided into several groups:

- General metrics of the solution (total number of vehicles or couriers, orders, or unassigned orders).
- Information about vehicles, couriers, and shifts (IDs, shift time windows).
- Vehicle utilization (weight, volume, units).
- Route information (start and end time, mileage, total route time, travel time, and waiting time on the route).
- Information about violations of time windows (orders, shifts).
- Route cost information (cost for the algorithm, algorithm penalties).

### Popular metrics {#popular-metrics}

The most common metrics to look at when analyzing routes are:

- `used_vehicles`: The number of vehicles or couriers involved.
- `dropped_locations_count`: The number of unallocated orders.
- `failed_time_window_locations_count`/`total_failed_time_window_duration`: The number of time window violations and the total duration of time window violations.
- `orders_count`: The number of orders in the route.
- `weight_perc`/`units_perc`/`volume_perc`: Vehicle utilization by weight, volume, or units.
- `total_transit_distance_km`: The length of the route in kilometers.


## Use cases {#use-cases}

### Geofences {#zones}

If you use [geofence](https://yandex.kz/routing/doc/en/vrp/geozones.md)-based restrictions in your planning, you'll find an additional **zones** column in the uploaded Excel file with the solution on the **Extended routes** sheet. It specifies the geofences the order is located in.

<!-- source: en/vrp/_includes/feedback.md -->
<a href="feedback">
  <span class="button">Contact support</span>
</a>


<!-- endsource: en/vrp/_includes/feedback.md -->