Process Hub · Business scenarios to work through
Business example: plan and complete a delivery route
Take a two-stop warehouse delivery from planning through driver evidence and completion.
On this page
Before you start
- Use a training profile and synthetic data. NovaNest Living is a fictional home-goods business; names, records and amounts below are examples, not installed customer configuration.
- Ask your administrator to prepare the approved runtime connection and member roles. Use the linked build guide before this walkthrough; only authorised people should publish/deploy.
- This example needs working Azure Maps and an authorised driver in the profile. Use safe test addresses and training records; do not send people on a real delivery for a configuration test.
Sample plan
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Start | NovaNest demo warehouse depot. |
| Stop 1 | Demo customer for order SO-1001; valid safe test address. |
| Stop 2 | Demo customer for order SO-1002; valid safe test address. |
| Evidence | Configured delivery note/photo/answer fields using synthetic data. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Create a Route process named Daily Deliveries. Configure a start depot and two demo stop sources/addresses, a driver and the intended vehicle fields using the Route build guide.
- Configure fixed instructions: Route Start safety check, During stop delivery evidence, and Return check. Decide which steps are mandatory and whether an exception may be skipped with a reason.
- Map stop identity/address/display values. If using Create process for delivery evidence, deploy that process first and configure required bindings; otherwise use route-native instruction fields.
- Save, publish and deploy. Grant planner/driver access plus any evidence-process access. As planner, create a draft with two demo deliveries for SO-1001 and SO-1002.

This route is still Not calculated. Calculate it after setting planning values; changing those values requires recalculation before confirmation. - Choose the driver, depot and stop order, then Calculate route. Save draft and reopen it to verify the plan persisted. Edit a planning value, recalculate and Confirm plan once valid.
- As the driver, find the assigned route work and select Start Route. Complete the start check, travel/Confirm arrival and each configured evidence step in order for both stops.

Follow the current execution step. Confirm arrival records that step; it does not complete the entire route. - Record an allowed exception on a separate training run and verify the reason is retained. If a step waits for approval, have the authorised approver act online before proceeding.
- Complete the return requirements and Complete Route. Review both stops, evidence, exceptions and history against the planned work.
What to verify
A calculated route is temporary until saved/confirmed. A completed run should show the configured stop evidence and any exception reasons. Carrier booking, customer tracking messages and accounting updates require their own supported configuration.
What you should see
The confirmed route is assigned to the driver and completion is backed by the configured ordered evidence.
If something goes wrong
The route will not confirm after changing the driver
The calculation is stale after relevant planning edits. Recalculate and verify driver/bindings before confirming.
A skipped stop was counted as successful delivery
A permitted skip is exception evidence, not delivery success. Review the actual recorded result.
A driver cannot open an evidence record
Check the driver’s access to both the route and dependent process/record in this profile.