Operations guide

Dispatch jobs and routes

Choose how work reaches drivers, assign one job or an entire run, and know what RouteIQ changes when you press Dispatch.

Updated September 3, 2026
You can dispatch the job directly. Create an unassigned job with the stops the driver must perform, then assign it to a driver without building a route first. The driver's upcoming route is created or reused automatically. If these pieces are new to you, start with How jobs, stops, and routes work together.

What dispatch does

Dispatch connects work to the people who will perform it. The job remains the customer order, its stops remain the individual tasks, and the assigned driver's route becomes the ordered list of stops.

  1. Ready workAn unassigned, pre-start job is available to dispatch.
  2. Driver selectionYou choose a driver or team, let drivers claim the work, or let RouteIQ select automatically.
  3. AssignmentWhen you assign a job, its stops are added to the driver's upcoming route. If the driver does not have one yet, a route is created automatically.
  4. ExecutionThe driver accepts when required, starts the route, and works through its stops.
Dispatching a job also handles its stops.

You do not need to create a separate route first. A direct job assignment adds the job's stops to the appropriate pending route for that driver and scheduled date.

RouteIQ Dispatch Board showing workers, live routes on a map, work requiring attention, suggested jobs, and open jobs
The dispatcher's operating view. Driver availability, live routes, exceptions, and open work stay visible on one board.

Choose the right dispatch flow

FlowBest forWho chooses the driver?
Assign job to driverOne job, urgent work, or a known driver; no route setup requiredYou
Dispatch to teamKeeping work inside a team, or sending a crew togetherRouteIQ selects one member, or the whole team attends
Offer opt-inA single job where drivers should express interestRouteIQ selects the best eligible driver who accepts
Post to poolFlexible work that any eligible driver, or one team's drivers, may claimThe first eligible driver to claim it
Dispatch a routeA planned run whose stop order you want to preserveYou select the driver for the route
Automatic dispatchContinuously assigning new ready jobs at scaleRouteIQ uses your configured strategy

You can mix these flows. For example, automatic dispatch can handle normal ready jobs while a dispatcher manually assigns an exception or builds a planned route.

1. Prepare the work

Before opening the dispatch dialog, confirm:

  • The job is unassigned and has not started, completed, or been cancelled.
  • Its stops have valid addresses, contacts, time windows, and required service details.
  • Any service, vehicle, zone, or driver requirements are correct.
  • The planned start time is correct if the work is scheduled.

For a batch, every selected job must be ready for dispatch. If a selected job is already assigned or in progress, you will be told which job needs attention.

2. Dispatch one or more jobs

  1. Open Dispatch Board or Jobs.
  2. Open a job's actions and select Dispatch, or select several jobs and use Dispatch from the batch actions.
  3. Choose Assign driver, Dispatch to team, Offer opt-in, or Post to pool.
  4. Complete the fields for that flow, review the route preview when shown, and confirm.
RouteIQ Dispatch Job dialog showing Assign driver, Offer opt-in, Post to pool, and Dispatch to team
Four ways to dispatch the same job. Assign it directly, ask drivers to opt in, publish it to the pool, or dispatch through a team.

Assign a specific driver

This is the simplest path for assigning work. Start from the job; RouteIQ handles its route structure automatically.

  1. Select the driver. Review duty status and existing active routes before choosing.
  2. If the job belongs to a zone, RouteIQ initially shows drivers on teams that cover it. Use Include drivers outside this zone only when crossing that boundary is intentional.
  3. Select the driver's personal vehicle or an eligible fleet vehicle.
  4. Set an optional Start At time and choose whether the driver must confirm.
  5. Select Assign Driver.

Dispatch to a team

Select the team, then choose how it should work:

  • One member: RouteIQ selects a driver by fastest ETA, lightest workload, or round robin.
  • Whole team: every member is added to the job, with the team leader acting as lead.
  • Batch distribution: selected jobs are divided among individual team members. Leave route optimization on to group nearby jobs and create a practical route for each driver.

Offer opt-in or post to the pool

  • Offer opt-in is for one job at a time. Eligible drivers receive an offer; accepting expresses interest, and RouteIQ selects the best eligible accepter when the offer window closes.
  • Post to pool supports one or several jobs. Leave the team blank for a site-wide pool, or select a team to restrict who can see and claim the work.

3. Dispatch a planned route

Creating a route first is optional. Use a route-first workflow only when you need to control the full run before assigning it, for example, a morning delivery wave, a service territory, or a route with strict time windows.

  1. Select the jobs and choose Create Route, or open Routes and create one.
  2. Add or remove stops, set the start time and starting or ending locations, and arrange the stop order.
  3. Preview optimization and review time-window or feasibility warnings.
  4. Save the route.
  5. Select a driver and vehicle, then choose Dispatch to driver.

Assigning the route also dispatches each active job represented by its stops. If a job is already assigned to a different driver, the route cannot be dispatched, so the same work is not placed on two drivers' routes.

Review partial-dispatch warnings.

If an individual job cannot be dispatched, RouteIQ identifies the affected job and reason. Resolve those exceptions before treating the whole run as ready.

4. Decide whether the driver must confirm

Turn on Require driver confirmation when the driver needs to acknowledge a direct or team assignment before proceeding. The driver can accept or decline:

  • Accepted: the confirmation requirement is cleared and the assigned work remains with that driver.
  • Declined: RouteIQ removes the assignment and returns the job to Ready for another dispatch.
  • No response: when your site has a confirmation timeout, RouteIQ returns the job to dispatch after that window. Without a timeout, it stays assigned until someone acts.

This is different from Offer opt-in. Confirmation asks one assigned driver to acknowledge work; opt-in asks a group of eligible drivers who is willing before RouteIQ makes the final assignment.

5. Turn on automatic dispatch

Use the dispatch control in the top bar to switch from Manual to Auto, then select a strategy:

RouteIQ dispatch mode panel with Auto selected and the Best ETA, Driver load, Round-robin, and Driver opt-in strategies visible
Choose how ready work is dispatched. Keep dispatch manual, switch to Auto, choose the automatic assignment strategy, or run dispatch immediately.
StrategyHow RouteIQ selectsUse it when
Best ETAFastest estimated arrival among eligible driversResponse time matters most
Driver loadDriver with the lightest current workloadYou want assignments spread more evenly
Round-robinRotates through eligible driversYou want predictable assignment rotation
Driver opt-inOffers the job, then selects the best eligible driver who acceptsDrivers should choose whether to participate

Automatic dispatch watches for jobs in Ready. Scheduled work can wait until the chosen lead time before its start. You can run automatic dispatch for the whole site, one team, or the team that covers the job's zone.

Select Run dispatch now to process the current ready work immediately with the selected strategy. If no eligible driver is found, the job stays ready and is tried again according to your settings. After the last attempt, it is flagged for a dispatcher.

Manual dispatch remains available.

Turning on Auto does not prevent a dispatcher from assigning a job directly, sending it to a team, or building and dispatching a route.

Reassign, unassign, or cancel

  • Change the driver on a job: unassign the current driver first. This removes the job's stops from that route and returns the job to Ready; then dispatch it again.
  • Unassign a route: RouteIQ reopens the route, clears its driver and vehicle, and returns its unfinished jobs to Ready. Completed work is preserved.
  • Cancel the work: cancel the job only when the customer work itself should stop. Cancellation removes its unfinished stops from active routes.

Unassigning and cancelling are not interchangeable: unassigning keeps the work available for another driver, while cancelling ends the work.

Troubleshooting

Dispatch is unavailable

The job is already assigned, has started, is completed or cancelled, or its latest state is not available. Refresh the list and confirm you selected only unassigned, pre-start jobs.

No drivers are listed

Check driver duty status, schedules, vehicles, team membership, required capabilities, and zone coverage. For a zoned job, deliberately include drivers outside the zone only if your operating rules allow it.

The selected vehicle is unavailable

Choose a fleet vehicle or one assigned to the selected driver. A normal individual assignment needs an eligible vehicle.

Automatic dispatch did not assign a ready job

Confirm Auto is on, the job has not been excluded from automatic dispatch, its scheduled lead time has arrived, and at least one driver meets the scope, distance, zone, vehicle, schedule, and capability requirements.

The driver cannot start another route

A driver may have multiple pending routes but can run only one started route at a time. Complete or otherwise resolve the current route before starting the next one.