Route planning capabilities

Plan routes around the work your team needs to complete

Your routes depend on more than addresses. A service visit takes time, a delivery changes the load, and some jobs need a particular team. The Flowtlas engine models these requirements alongside travel. Contact us to confirm generation availability and integrations for your workspace.

The operational problem

Bring places, people and vehicles into the same plan

A task describes the work: one service visit or an ordered chain of stops. A tour connects a vehicle and any assigned people with dated work windows. The horizon defines the overall period the engine considers.

Product capability

The inputs and rules behind the plan

01

Prepare the inputs

Supply verified locations, realistic service durations, visit windows, available vehicles and people. Add skills, consistent capacity units and stop order where the operation needs them.

02

From work list to reviewable plan

Prepare the work and its locations. Define tours, dated working periods and start/end requirements. Set eligibility, capacity and commitment rules. When generation is enabled, review assignments, stop sequences and any unassigned work.

Practical workflow

From prepared work to a plan you can review

  1. 1

    Prepare the work

    Supply locations, service durations, visit windows and resource requirements.

  2. 2

    Define the tours

    Specify vehicles, assigned people, start locations and dated working periods.

  3. 3

    Apply the rules

    Include consistent capacity units, eligibility and stop order where needed.

  4. 4

    Review the result

    When generation is enabled, inspect assignments and estimates, including any work left unassigned.

Operational benefits

Know what to review

  • Check coverage, tour assignments, arrival and departure estimates, travel and service totals, and omissions. A complete plan covers the active tasks; it does not prove that no better route exists.

In practice

Example: a service team with a morning appointment

Two vans have work windows from 08:00 to 17:00. One visit has access between 09:00 and 11:00; another needs a specialist skill and 90 minutes on site. The request must account for travel, work duration and eligibility together.

This fictional setup illustrates inputs. It is not a solved route or a customer result.

Questions

Frequently asked questions

What is Flowtlas used for?

Flowtlas organizes locations, resources and work for route planning. Its engine models service visits, ordered pickup and delivery tasks, and tours with one or more dated working periods. Check current product access and enabled workflows when discussing a specific deployment.

Can the engine account for appointment windows?

Yes. Stops can have supplied time windows, and tours have dated work windows. Include service duration and travel requirements as well so the model reflects the time the work actually needs.

Can tasks require specific skills or vehicles?

Yes. Tasks and places can restrict eligibility, and resources can carry supplied skills. The engine uses those requirements when determining eligible tours. It does not independently verify professional qualifications or equipment records.

Why can some work remain unassigned?

Work may lack an eligible tour or fail to fit capacity, time or route constraints. When the request permits partial work, the result can report unassigned tasks and reason categories. Review those reasons together with the task and resource data.

Work with operational context

See how Flowtlas can support your operational setup.

Back to top