Planned vs actual route
A territory manager compares a rep's planned route with actual check-ins and distances from store, and finds a day that ran long for a reason.
Dan · Territory manager · Inner West territory
Dan reviews Marco's Tuesday. Twelve visits were planned and ten were completed. The report shows check-ins in the planned order until 1:00, then one visit lasting 1 hour 50 minutes against a usual 40. The note on that visit explains a full range reset requested by the store. The two missed visits were moved to Wednesday with a reason. Every check-in was within 60 meters of its store. Dan's question becomes how to plan resets, not where Marco was.
Dan reviews the day on Wednesday morning.
- Plan against what happenedThe planned order sits beside actual check-in times for each visit.
- Distance from storeEach check-in shows how far it was from the store, so presence isn't in question.
- Time in store explains the dayA long visit with a note shows why the plan changed.
Everything this visit sent back to Salesforce.
Each line is a record in your own org, under your permissions, reportable with the tools your team already uses.
Features in this example