TradeProStack is reader-supported. This article contains no affiliate links. The vendor links below are plain links to vendor help and product pages, included so you can check each claim yourself. Nothing on this page is legal advice.
GPS tracking crew communication works only if the crew trusts what it does and what it does not do. The most common mistake is switching it on first and explaining it later, after a disputed punch or a missed stamp has already turned into an argument. Tell the crew the limits before day one, in writing, and say the same thing to everyone.
The short version: name exactly what is recorded, say when tracking starts and stops, give one plain reason for using it, say who can see the data, and give a clear fix path for a wrong location or a dead phone. The five points below cover each of those, with what four vendors actually state on their own help pages, so you can match your notice to your own setup.
Quick Take: what should you tell the crew before day one?
Tell them five things, in this order: what is tracked, when tracking starts and stops, why the business is using it, who can see the data and how long it is kept, and what to do when the location is wrong or the phone dies. Do not promise more privacy than the mode you chose actually gives. The biggest trap is describing a continuous tracking mode as if it were a punch-only snapshot, because the crew will notice the difference the first time a route shows up on a map.
One gap to close before you write the notice: none of the four vendors in this article state a location data retention period on the pages checked for this article on October 28, 2026. Confirm your own retention setting in your account before you tell the crew, and write that setting into the notice instead of guessing a period.
How do Connecteam, Hubstaff, Homebase, and Jobber differ on GPS tracking?
The four vendors do not mean the same thing by GPS tracking. One takes a snapshot at each punch, one can record a route while the crew member is clocked in, one records waypoints only when specific actions happen, and one changes completely with the mode you pick. The table below uses only vendor help page statements checked October 28, 2026. Where a vendor does not state a detail, the cell says so.
| Vendor | What is recorded | When tracking is active | What managers see | What happens off shift |
|---|---|---|---|---|
| Connecteam | A GPS stamp at clock in and clock out. Breadcrumbs records a route while the user is clocked in, updating every 5 to 10 minutes and after about 80 feet of movement. | While the user is clocked in. An optional geofence can control where clock in and clock out are allowed, and leaving the fence can auto clock the user out if that setting is on. | The Breadcrumbs route on the Time Clock map while the user is clocked in. | Location is not saved or shared while the user is not clocked in. When not clocked in, location information stays on the device and is not shared with Connecteam. |
| Hubstaff | GPS positions of the team during the work day, in the mode chosen. Uploads reach Hubstaff servers about every 10 minutes depending on connectivity. | Depends on the mode: Off, Tracking time (only while the timer runs), Also during shifts, or Always. Always mode may keep recording GPS locations in the background while the app is installed and location permissions are enabled, even when the team member is not tracking time. | Only organization owners and managers can view team location data. A regular user sees only their own personal location data. | Depends on the mode. Tracking time mode stops uploading live data when the timer stops and reports the last recorded location. Always mode may keep recording in the background while the app is installed and permissions are enabled. |
| Homebase | A GPS snapshot at clock in, clock out, and breaks. It does not track continuously during a shift. | At punch events only: clock in, clock out, and breaks. One geofence per location; an out-of-fence punch attempt is blocked and the admin gets an alert. | Snapshots are stored in the GPS timesheet. Viewer roles beyond the admin who receives the out-of-fence alert are not stated on the pages checked. | Not stated beyond the snapshot-only design: no continuous tracking during a shift, and snapshots happen at punch events only. |
| Jobber | GPS waypoints only, at listed actions: clocking in or out, starting or stopping a timer on a visit, adding a note or attachment, marking a visit complete, marking an on-site assessment complete, and marking a task complete. Waypoints are logged on select plans. | Location timers start, stop, or remind near a visit, triggered within 200 meters (656 feet) of the visit geofence, with up to 3 minutes to update on exit. Auto detection needs an internet connection. | Live location is not shared with other team members or the account owner. Waypoints attach to the time entry and can be viewed alongside tracked time. | Live location is not shared. Waypoints are logged only at the listed actions, not continuously. |
Retention period for all four vendors: not stated on the pages checked. Confirm your own setting before you tell the crew.
1. What exactly is tracked?
Start with the events, not the label. GPS tracking sounds like one thing, but in these four products it covers a snapshot at a punch, a route while clocked in, a waypoint at a specific action, or continuous positions in a chosen mode. Name the exact events in your own setup, because the crew cannot give a fair reaction to a label that hides the difference.
If you use Connecteam, say whether Breadcrumbs is on, because a stamp at clock in and a route while clocked in are different promises. If you use Homebase, say snapshot, and say plainly that it does not track continuously during a shift. If you use Jobber, say waypoint, and list the actions that create one. If you use Hubstaff, name the mode, because the mode is the answer.
Practical advice, not a vendor claim: show the crew a sample timesheet entry so they can see what a stamp or a waypoint actually looks like. A crew member who has seen the record will ask better questions than one who has only heard the word tracking.
2. When does tracking start and stop?
This is the point crews care about most, and it is where a vague notice does the most damage. Give the start and stop rule in one sentence per mode, and do not blur the modes together.
- Connecteam: Breadcrumbs shares location with admins only while the user is clocked in. When not clocked in, location is stored locally on the device and is not shared with Connecteam. Note the permission catch: Breadcrumbs needs Location Access set to Always so stamps continue while the app is in the background or closed, while the user is clocked in.
- Hubstaff: Tracking time mode records only while the timer runs. Always mode is different: it may keep recording GPS locations in the background while the app is installed and location permissions are enabled, even when the team member is not tracking time. If you chose Always, say so plainly and say why. Hubstaff itself flags Always mode for written notice to team members.
- Homebase: snapshots happen at clock in, clock out, and breaks only. There is no continuous tracking to start or stop during a shift.
- Jobber: location timers act near a visit, within 200 meters (656 feet) of the visit geofence, with up to 3 minutes to update after leaving the fence. They need an internet connection to detect entry or exit, and only an admin on Jobber.com can turn location timers off.
If your notice says tracking stops at the end of the shift but your mode keeps recording in the background, the notice is wrong, and the crew will find out. Match the sentence to the setting, not to the sentence you wish were true.
3. Why are we turning GPS tracking on?
Give one plain reason, in your own words. Payroll accuracy and verifying presence at the job site are the reasons vendor pages point to, and Jobber describes location timers as a way to keep timesheets up to date without manual work. Pick the reason that is actually true for your shop, for example payroll accuracy or proving site attendance for client billing, and state it in one sentence.
Then state what the data will not be used for. General guidance from payroll providers ADP and Paychex, labelled here as guidance rather than law, supports stating the business purpose, the devices covered, when the system is active, and who has access. That guidance is useful for drafting a notice, but it is not a statement of any one jurisdiction’s law.
A location stamp also has a hard limit that belongs in this section: a stamp shows where a device was at punch time, or at a waypoint action. It does not prove what work was completed. Do not tell the crew, a client, or yourself otherwise, because that claim will fail the first time a stamp and a finished job disagree.
4. Who can see the location data, and how long is it kept?
Name the roles, not just the word manager. Hubstaff states that only organization owners and managers can view team location data, and that a regular user sees only their own personal location data. Connecteam states that admins see Breadcrumbs on the Time Clock map while users are clocked in. Jobber states that live location is not shared with other team members or the account owner, while waypoints attach to time entries. For Homebase, viewer roles beyond the admin alert are not stated on the pages checked, so do not invent a viewer list for that product.
On retention, be direct about the gap: no retention period is stated for any of the four vendors on the pages checked for this article. Tell the owner to confirm the retention setting in their own account, then write that setting into the notice. A notice that skips retention leaves the question open for the crew to answer themselves, usually with the worst guess.
Practical advice: limit access to people with a clear business need to know, and say that limit in the notice.
5. What should a crew member do when the location is wrong or the phone dies?
Wrong locations and dead phones are normal, and the notice should treat them as normal. Connecteam’s help pages state that GPS accuracy can be affected by service, device, location, and connectivity, and advise moving further into the fenced area so the whole location circle sits inside the fence. If location services are off while clocked in, the user stays clocked in but no location is tracked, and gaps may show as a straight line between two known points. If the phone is off or has no service, the user stays clocked in but no updates are sent.
Jobber has its own version of the same problem: location timers need an internet connection to detect entry or exit, and offline they will not start or stop automatically, though manual timers still work and sync once a connection returns.
Practical advice: give the crew a named contact and a simple fix path. Check the location permission, move inside the fence, flag the entry for correction the same day, and never edit another person’s entry. Treat a missed stamp as a payroll fix, not a disciplinary event, unless your own policy says otherwise and you state that policy in the notice. If a corrected punch changes pay, run the numbers through the TradeProStack free tools hub before payroll day so the fix is checked, not guessed.
What should your GPS tracking crew communication say on day one?
Put the five points in writing as your GPS tracking crew communication, hand it out before tracking starts, and keep a copy with the policy. A short checklist covers it:
- What is tracked: the exact events in your setup, by product and mode.
- When it starts and stops: the start and stop rule for your chosen mode, including any background recording.
- Why it is on: one plain business reason, plus what the data will not be used for.
- Who sees it and how long it is kept: the roles with access, and your own confirmed retention setting.
- What to do when it is wrong: the named contact, the same-day flag, and the payroll fix path.
- The rules check: check the rules that apply where you operate and confirm with a local adviser before switching tracking on.
What should you not promise?
- Do not promise that tracking is off outside work hours unless your mode actually stops. Hubstaff Always mode may keep recording in the background while the app is installed and permissions are enabled, even when the team member is not tracking time.
- Do not promise that GPS proves work was done. A stamp or waypoint shows where a device was at a recorded moment, not what work was completed.
- Do not promise a retention period you have not confirmed in your own account. None is stated for these four vendors on the pages checked.
- Do not promise a viewer list for Homebase beyond what is stated. Viewer roles beyond the admin alert are not stated on the pages checked.
- Do not present general guidance as law. Rules vary by where the business operates, so check the rules that apply where you operate and confirm with a local adviser before switching tracking on.
If you are still choosing a tool rather than announcing one, the companion comparison, Geofenced Time Tracking for Payroll, compares these products side by side on features and payroll fit. This piece is the notice to write once the choice is made. Tell the crew first, in writing, and let the first week of stamps prove that the notice matched reality.
Sources checked October 28, 2026: Connecteam Time Clock geofence, Breadcrumbs, and GPS location tracking help pages; Hubstaff fleet tracking, FAQ, mobile location tracking, and location services help pages; Homebase mobile GPS time clock page and mobile time clock setup article; Jobber location timers and timesheets help pages. General communication guidance from ADP and Paychex is labelled as guidance in this article, not as law.







