Best default for mixed delivery and service operations with moderate exception volume.
Fleet Deck
Sunday 15 March 2026, week 11. Multi-segment route design with detailed planning depth where it matters.
Adaptive workflow
Balance deliveries, service time and return flow in one planner.
Keep the same navigation for every customer, but let the route mode control which KPIs, constraints and warnings are brought forward. This makes the platform easier to learn without flattening the domain detail.
Prioritizes time-window pressure, route density, delivery capacity and service-level risk.
Primary planning focus
94%
on-time feasibility across committed windows
Why this shell works
Stable information architecture for all customers, but each mode raises the right exceptions early instead of burying them in configuration pages.
Cross-segment health
Utilization
82%
Window risk
17
Route outliers
6
Average buffer
19m
Actionable exceptions
Critical
Vehicle 14 exceeds weight by 7%
Shift two chilled drops into Van 07 or open a late wave after 10:30.
Attention
08:00 to 09:00 window cluster is overbooked
22 stops compete for 6 feasible slots in the central Copenhagen zone.
Healthy
West route has usable reserve
32 minutes slack can absorb traffic or a same-day insertion.
Spatial overview
Clustered map plus route layers should always be visible. This carries over the strongest element from the current customer screen, but upgrades it from static plotting to decision support.
Map + list linked
Dense cluster handling
Outlier detection
Planner timeline
The right-hand panel combines execution status, scenario feedback and dispatch-level change points.
07:40
Data ready for calculation
931 tasks validated. 12 addresses flagged as close duplicates and grouped into micro-clusters.
08:05
Hotspot detected in city center
Overlapping windows create a conflict burst. System recommends resequencing Route 04 and opening vehicle reserve.
10:15
Slack preserved on west corridor
Reserve stays above threshold, which keeps room for acute jobs or return pickups later in the day.
13:30
Critical deadline wave
Final lab or medical pickups surface here with exact countdown and expected depot arrival.
Capacity utilization
Show actual capacity pressure by vehicle, not only route length. Volume, weight and temperature zones should be visible when relevant.
Vehicles inside limit
21/24
Peak load
93%
Time-window realism
Let planners see where promised windows become mathematically optimistic before the route is released.
08:00 to 09:0076%
09:00 to 12:0054%
12:00 to 17:0033%
Route progression
For outbound flows, the load curve should decline smoothly. For collection, it should rise. For two-way, planners need to see both crossing curves.
Human continuity
When people are the bottleneck, task duration, travel time and repeat-customer continuity must appear as first-class planning objects.
Continuity match
87%
Insertion response
22m
Mixed resource board
This view handles both vehicle-heavy logistics and people-heavy service organizations. The table stays generic, while the badges and health columns adapt to the selected mode.
Drivers and technicians
Vehicle + person constraints
Status-rich, not form-heavy
Resource
Mode
Availability
Primary risk
Planning signal
Van 04 / Jonas Mikkelsen
Cold-chain capable. North depot.
Deliver
Ready 07:00
Window pressure
84% full by volume, but only 12 minutes slack before city-center wave.
Team B / Maria + service van
Certified electrical service. Repeat-customer cluster.
Service
Booked 6.4h
Continuity high
Same technician retained for 9 of 10 repeat clients. Good candidate for acute insertion after 14:00.
Truck 12 / Return cage setup
Rear compactor. Waste and recyclable fractions.
Collect
Ready 06:30
Fill-up risk
Expected to hit 96% capacity before final loop. Suggest mid-route unload point at 11:20.
Linen Route 03 / Lars Petersen
Two-way textile swap. Restaurant and hotel network.
Two-way
Ready 08:00
Swap balance
Outbound load is safe, but return cages push rear axle estimate above preferred range after stop 18.
Scenario shelf
Keep saved routes, but make them easier to compare. This takes the existing “saved route” concept and turns it into a scenario shelf with operational trade-off summaries.
Protects early time windows at the cost of more empty kilometers and less afternoon slack.
Retains employee-customer matching and lowers context switching for field-service teams.
Design principle: generic navigation, specialized insight. The platform should not ask users to choose a different product for each segment. It should let them operate in one environment, then progressively reveal the constraints that matter for their business model.