- Why the Privacy Conversation Comes First
- 1. Explain Exactly What Gets Recorded and When
- 2. Show Crews Where the Line Is
- 3. Say Who Can See the Data
- 4. Explain How Long Records Are Kept
- 5. State What the Data Will Not Be Used For
- Know the Legal Baseline Where Crews Work
- Put It in Writing
- Trust Is Part of the Rollout

Before turning on geofenced clock-ins, contractors should explain five things to their crews in plain language: what location data the system records and when, where each jobsite boundary sits, who can see the data, how long it is kept, and what it will not be used for. Putting those answers in writing, covering them at a toolbox talk and giving workers a named person to ask follow-up questions heads off much of the distrust that sinks new field technology. A geofence that checks whether a worker is on site at clock-in is far easier to explain than one that seems to follow people around.
This guide is written for builders and specialty contractors who employ their own field crews and are introducing geofence-based timekeeping on residential, commercial or high-performance building projects.
Why the Privacy Conversation Comes First
Workers arrive at any monitoring discussion with real concerns. A Pew Research Center survey on AI in hiring and evaluating workers found that 81 percent of U.S. adults believe employer use of AI to monitor and evaluate workers would lead to workers feeling inappropriately watched. Majorities also opposed using AI to track workers’ movements while they work.
Federal researchers have heard the same themes. The GAO report on digital surveillance of workers reviewed stakeholder comments and found that geolocation and tracking applications were among the tools commenters raised most often. Commenters said surveillance can breed distrust and make workers feel constantly watched, and stakeholders also said they were unaware of how employers used workers’ data.
| Key insight81 percent of U.S. adults say AI monitoring of workers would leave workers feeling inappropriately watched (Pew Research Center, 2023). On a jobsite, the explanation that comes before rollout often matters as much as the technology itself. |
That second finding is the opening for contractors. Much of the anxiety around location data comes from not knowing what is collected. Clear answers before launch address that directly.
1. Explain Exactly What Gets Recorded and When
Start with the most important question on every worker’s mind: does the company know where they are all the time? The answer depends on how the system is configured, and crews deserve a precise description rather than a general reassurance.
In a typical geofence time tracking setup, the boundary is a virtual line drawn around the jobsite, and the worker can clock in or out only while inside it. The record created at each punch usually includes a time, a location stamp and the identity of the person clocking in. Contractors should confirm with their vendor and then tell the crew specifically:
- Whether location is captured only at clock-in and clock-out or at other times during the shift
- Whether the app collects any location data after the worker clocks out or leaves the site
- Whether clock-ins happen on a shared jobsite device or on workers’ personal phones
- What other information is captured with each punch, such as a photo used for identity verification
If workers use their own phones, explain which app permissions are required and why. Personal devices are where trust breaks down fastest, since the GAO report notes stakeholder worries that tools could track activity on personal devices while workers are at home.
2. Show Crews Where the Line Is
A geofence is easier to accept when workers can see it. During the toolbox talk, show the boundary on a site map and point out what it includes: the gate, trailer, laydown area and any huddle or parking areas. Point out what it excludes, such as nearby businesses or the street where crews park personal vehicles.
Explain what happens at the edge. If a worker cannot clock in from a spot they believe is on site, they need to know who to tell and how the missing time will be added. A clear exception process signals that the boundary exists to confirm attendance, while the company still pays for every minute worked.
3. Say Who Can See the Data
Workers want to know whether location records are visible to their foreman, the project manager, payroll, the general contractor or a client. List each role that has access and what they use it for. Crews generally understand that payroll and their direct supervisor need to see punch times and locations. Fewer are comfortable with broad access across the company or sharing with outside parties.
Set access by role in the system itself, then describe those settings accurately. A written statement that only supervisors and payroll can see location stamps is only reassuring if the permissions match it.
4. Explain How Long Records Are Kept
Timekeeping records are subject to retention requirements, so location stamps tied to punches may be stored for years. Tell workers how long the company keeps these records, why it keeps them and how they are protected. If records are deleted or archived after a set period, say so. If the company has not yet decided on a retention period, that decision belongs in the planning stage before rollout.
5. State What the Data Will Not Be Used For
The most effective part of a privacy conversation is a short list of commitments. Specific promises carry more weight than general assurances. Examples include:
- Location data will be used to confirm attendance at the jobsite and support payroll and job costing
- The company will not use the system to track workers outside working hours
- Location records will not be used to monitor breaks, conversations or off-duty activity
- Location records will not be used to monitor union activity or concerted activity among workers
The last commitment addresses a concern the GAO report identified directly: commenters said surveillance may deter workers from unionizing. Contractors with union crews should also check whether their collective bargaining agreements address the introduction of new monitoring technology and involve union representatives early.
Know the Legal Baseline Where Crews Work
Privacy rules for worker data vary by state, and they are changing. In California, a UC Berkeley Labor Center overview of worker rights under the CCPA explains that the exemption for employee data sunset on January 1, 2023, and California workers are now covered. The overview lists rights that include knowing when employers collect data about them, accessing it, correcting or deleting it and limiting the use of sensitive data, with protection from retaliation for exercising those rights. The same overview identifies geolocation data as personal information.
Contractors working across several states should review the rules in each one and consult employment counsel before launch. A clear written notice is also a useful starting point for meeting any formal notice requirements that apply.
Put It in Writing
A one-page geofencing notice gives crews something to keep and gives the company a record of what was communicated. A practical notice covers:
- The purpose of the geofence and the projects it applies to
- What is recorded at each punch and when location is captured
- Who can access the data and for what purpose
- How long records are kept and how they are protected
- The commitments on what the data will not be used for
- How to report a missed punch or a boundary problem
- The name and contact details of the person who answers questions
Translate the notice into every language spoken on the crew, read it aloud at the kickoff and post it at the trailer. Revisit it whenever the system configuration changes.
Trust Is Part of the Rollout
Geofencing can give contractors accurate, site-verified time records and give workers clear proof of the hours they put in. Whether crews see it as a fair tool or as surveillance depends heavily on what they hear before the first clock-in. Contractors that explain what is recorded, show the boundary, limit access, set retention and commit in writing to what the data will not be used for give the technology a foundation of trust that many rollouts lack.
