> ## Documentation Index
> Fetch the complete documentation index at: https://docsv4.mile.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Routing Schedule

> Run route optimization automatically for a configuration profile, on a repeating schedule.

A **routing schedule** runs route optimization for you at the times you choose. Instead of opening the Visit page every morning, picking a configuration profile and clicking **Optimize**, you set the schedule once and the result is ready by the time your team needs it.

It is the routing counterpart of [Task Schedule](/pages/planning/schedule/task-schedule): the same repeat cycles, applied to route optimization instead of task creation.

## When to use it

A routing schedule is worth setting up when a hub's routing follows the same pattern every day:

* **The route must be ready before anyone is at a desk.** A schedule set for 04:00 runs at 04:00, whether or not anyone is signed in.
* **Nothing about the daily run is a decision.** Same profile, same hub, same time, so clicking Optimize by hand adds nothing.
* **Drivers should get their route at a predictable time.** Runs happen on the minute they are scheduled, so routes reach field workers at a consistent hour.

## What happens on each run

When a schedule comes due, the following happens on its own:

1. **The visits are collected.** Every active visit at the profile's hub is included, both those still waiting to be assigned and those already in progress. There is no extra filter to set.
2. **The configuration profile is read.** The vehicles, geotags, constraints and optimization settings all come from the profile you selected. The hub comes from it too.
3. **The optimization runs**, and the outcome is saved as a normal routing result in [Planning › Routing › Result](/pages/planning/routing/result/introduction).
4. **The routes are dispatched**, but only when **Auto Dispatch** is on for the schedule. Otherwise the result waits for you to dispatch it by hand.

Every run records what it did. The outcome of the most recent run appears in the **Last Execution** column of the schedule list.

## What a schedule does not change

* **Results look the same.** A scheduled result is created, named and stored like a manual one, and you work with it the same way: open it, review it, move visits and dispatch it.
* **Drivers do nothing differently.** Dispatched routes arrive in the field app as they always do.
* **Manual optimization still works.** You can still optimize a hub by hand at any time, even when it has a schedule.

## Permissions

The Routing tab and each of its actions has its own permission, granted per role in **Settings › Permission** under **Routing Schedule**:

| Permission | Allows |
| - | - |
| **View Schedule** | Seeing the Routing tab and the list of routing schedules. |
| **Create Schedule** | Creating a routing schedule. |
| **Edit Schedule** | Changing an existing routing schedule. |
| **Delete Schedule** | Deleting a routing schedule. |

Without **View Schedule**, the Routing tab shows *You don't have access*.

The four permissions are linked. Turning on **Create Schedule**, **Edit Schedule** or **Delete Schedule** also turns on **View Schedule**, and turning **View Schedule** off turns the other three off.

## Before you start

A routing schedule points at a configuration profile, so the profile must exist first and must be usable.

<Note>
  The profile must have **at least one vehicle selected**. A schedule whose profile has no vehicle can't produce a route, so each of its runs is skipped.
</Note>

See [Configuration](/pages/planning/routing/configuration/introduction) for how profiles are set up.

## In this section

* [Creating a Routing Schedule](/pages/planning/schedule/routing-schedule/creating)
* [Managing Routing Schedules](/pages/planning/schedule/routing-schedule/managing)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.