Route History or Stops Are Missing

Customer says:

"The employee visited the location, but I don't see a Stop."

or:

"Why doesn't starting a Task create a Stop?"

Important distinction

Task ≠ Stop ≠ Punch In/Out

TeamTrace's August 2025 update distinguishes:

• Stops
• Punch In/Out Log
• Tasks
• Timeline

It describes Timeline as a combined view while Stops are generated according to location/duration logic.

Troubleshooting

1. Check whether the employee was actually at the location.
2. Check GPS availability.
3. Check the employee's route.
4. Check how long the employee remained near the site.
5. Check synchronization.
6. Check the Stop entry separately from the Task.

TeamTrace's published logic states that a Stop can be recorded when an employee remains within 200 meters of the site for a configured period.

Resolution

Do not tell customers:

"Starting a task automatically creates a Stop."

Instead explain:

Task activity and location-based Stop detection are separate records.