Process Hub · Build by process type

Build a Route process for planning and execution

Configure stops, driver work and ordered evidence steps, then test a confirmed route.

On this page

Before you start

  • Have deployed stop sources/lookups where needed, profile users for drivers and the required Azure Maps deployment/configuration. Use safe test addresses and an approved training environment.

Step types

On smaller screens, scroll the table sideways to see all columns.

SettingHow to use it
InstructionRoute-native instructions/fields and evidence.
Create processCreate the configured process draft at confirmation for the step.
Use existing processBind the step to an existing compatible record.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Open Builder → New process → Route. In Route setup configure identity and the intended planning/execution behaviour; add route fields, depots and the required driver/vehicle data.
  2. Configure Stops and Stop sources. Choose Manual address, Published Process or List, or Lookup table as appropriate. Map address, identity and display fields from deployed same-profile sources.
    Daily Deliveries builder with Route setup, planning and driver execution.View full size ↗
    Choose the route experience and configure stops, planning and execution requirements in the builder steps.
  3. Configure Instructions using templates or fixed steps. Fixed-step phases are Route Start, Before stop, During stop, After stop and Return.
  4. For each step choose Instruction, Create process or Use existing process. Map the required record/evidence fields and configure any permitted skip with a reason.
  5. Review execution requirements, stop bindings, approval dependencies and optional preload. Preload uses one enabled source when configured; it is not manual multi-source selection.
  6. Save, preview, validate, publish and deploy. Grant planner/driver and dependent-process access. Create a route draft, add safe stops and choose Calculate route/Recalculate.
    Route planning draft with driver, vehicle, two stops and Calculate route.View full size ↗
    This route is still Not calculated. Calculate it after setting planning values; changing those values requires recalculation before confirmation.
  7. Save the draft or Confirm plan to persist the intended plan. Confirmation requires a driver, current calculation and valid bindings. Driver, vehicle, depot or order changes require recalculation.
  8. As the driver, test Start Route, travel/Confirm arrival, evidence steps, any online approval wait, return and Complete Route. Inspect the saved execution evidence.
    Driver execution panel showing the current stop and Confirm arrival.View full size ↗
    Follow the current execution step. Confirm arrival records that step; it does not complete the entire route.

Try a complete business example

What you should see

A planner can confirm a calculated route and the assigned driver can complete the configured ordered work with evidence.

If something goes wrong

The calculated plan disappears

Calculation is temporary until Save draft or Confirm plan persists it.

Confirm plan is blocked

Check selected driver, current calculation, stop bindings and dependencies. Recalculate after planning edits.

A skip is shown but delivery was not completed

A permitted skip records an exception with its reason; it does not prove successful delivery.

Preview has no live map/routing result

Provider configuration and deployed runtime access are needed. Builder Preview alone does not verify Azure Maps or offline route execution.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help