Intelligent Route Planning
I developed the interface for a working field-sales planning product, connecting ordered stops, synchronized list and map views, and route geometry that makes travel decisions visible.
Overview
A working route-planning product that connects provider selection, an ordered itinerary, a route map, and travel summaries. My work brings account selection, office locations, filters, and route adjustments together in one planning workspace.
- My contribution
- Interaction design, interface development, and planning behavior
- Technical focus
- Route state, map geometry, derived metrics, and stop insertion
- Core model
- Provider → visit location → ordered stop → route leg
- Scope
- Field-sales route planning, provider selection, and trip management
One itinerary, several views
The central model is an ordered collection of stops. The provider list controls selection, the itinerary exposes order, and numbered map markers connect that order to geography. These views stay connected to the same plan as stops are added, removed, or reordered.
Provider identity and visit location are separate decisions. A provider may have several offices, but a route needs a specific coordinate for each visit. Making that distinction explicit connects the account a rep wants to see with the place the route must actually reach.
Make the route inspectable
Route geometry provides the path between stops; leg distance and drive time explain its cost. Visit duration belongs to a separate part of the plan, so travel and time spent with providers can be considered together without confusing the two.
The interaction exposes route overlap and backtracking as feedback the rep can inspect alongside the map. Pharmacy insertion uses proximity to a provider stop as a practical heuristic. Geographical closeness is a useful starting point, but the resulting driving route still needs to be reviewed.
Planning logic
Every planning action has a consequence for stop order, geometry, or derived travel metrics.
- 01
Separate discovery from the itinerary
Territory and account filters narrow the candidate providers. The selected route remains a distinct planning object so searching for another opportunity has a clear relationship to the trip already being assembled.
- 02
Resolve a visit into a stop
Choosing a provider and office determines the visit location. The itinerary and map use the same stop order, letting a rep relate each numbered marker to the corresponding account and address.
- 03
Recalculate after a change
Adding, removing, or reordering stops changes the route. The path, leg distances, drive times, and overlap feedback update together so the summary continues to describe the visible itinerary.
- 04
Make insertion understandable
A pharmacy is inserted after the geographically closest provider. Showing its new position and the resulting route lets the rep assess the detour and adjust the order when local knowledge suggests a better plan.
- 05
Carry the plan into reuse
The save and scheduling flow groups the route name, ordered stops, recurrence, and calendar state into a trip the rep can revisit. It extends the planning model beyond a temporary selection on the map.
Route planning system
From visit locations to a route
A shared planning model connects selected accounts to the geography of a trip.
What changes when a stop changes
Provider↝Account identity
Office↝Visit coordinate
Stop order↝Routing input
Route legs↝Distance and time