Week 1
Week 1
Week 1
✅ Tasks - Set up stops with multiple consignments for Group loading and unloading actions
Drivers no longer have to repeat the same loading or unloading action for every consignment at a location. The Stops with multiple consignments setting now also works on the standard loading and unloading actions, so the action is shown once for the group. In the subcontractor portal, stops at the same location with the same activity appear as one block, with one section per order. You set it per action in the Show on stops card of a task under Configuration > Tasks > Trips, and editing tasks requires an admin role.
What's included:
Setting available on Loading at pickup, Unloading at delivery, Loading at hub and Unloading at hub
Option 1 action for the stop activity group, completing all consignments, while Separate action per consignment stays the default
Consecutive stops at the same location with the same activity form one group
✅ Tasks — Create conditions on stop tasks
Stop tasks can now carry creation conditions, just like order, trip and consignment tasks. A stop task is only created for the stops that match its conditions, so drivers and subcontractors only see the tasks and questions that apply to their job. You set the conditions in the Creation conditions block of a task under Configuration > Tasks > Trips.
What's included:
Conditions on the order, the goods, the route and the stop itself, such as its location, collection or delivery, requested weekday and bank holidays
Location condition with the operator Is not, to keep a task away from specific depots or addresses
Recalculate tasks on the order checks the conditions again after a change
📍 Planning — Tracking and ETA updates on a trip
You can now see how recent the tracking of a trip is. The Events row in the Execution section shows Last ETA update and Last tracking update, and the new Execution events window lists the recorded events of the trip next to the trip map.
What's included:
Last ETA update and Last tracking update with a coloured dot: green under 15 minutes, orange up to 1 hour, grey when older or not received yet
Execution events window, opened from the clock icon on the Events row, with the tabs All, Driver activity, Geofencing and ETA recalculations
Actual arrival and departure times of each stop
Actual route on the trip map: a dashed line through the ETA updates, which needs PTV ETA calculation and at least 2 ETA updates
🚫 Planning — Set up Do not dispatch for multiple stops
Planners can now exclude several stops of a trip from dispatch in one go, straight from the planning board. Right-click a stop, choose Do not dispatch > Multiple stops, tick the stops the driver should not get and save. The driver app or fleet system receives one update for the trip. An AI-based stop rule under Configuration > Rules can also set Do not dispatch on new stops automatically.
What's included:
This stop and Multiple stops options in the right-click menu of a stop
One row per group of consecutive stops at the same location with the same activity
AI-based Stop fields rule that sets Do not dispatch on new stops, available when Qargo Intelligence is active