Clock-meVisit Website →
← Back to blog

Geofence Attendance Policy: What to Write and How

October 21, 2026
Geofence Attendance Policy: What to Write and How

A geofence attendance policy is a short written document that tells employees where they can clock in, what location data you collect at that moment, who sees it, and what happens when a punch falls outside the zone. Write it before you switch the feature on. Keep it to location at the time of the punch, say plainly what you do not track, and give people a way to clock in when the technology fails.

Below you will find the clauses to include, sensible defaults, the legal points to check with counsel, and a template you can adapt.

Clock-me
Put Geofenced Clock-Ins Into Practice
Clock-Me offers verified GPS clock-ins, geofencing and live attendance dashboards for teams working in the field.
Visit Clock-Me

TL;DR

  • Collect location only when someone clocks in or out. Do not track people through the shift.
  • Name each geofence, its radius and the sites it covers. Start wide enough to absorb GPS drift.
  • Flag out-of-zone punches for review instead of silently rejecting them, so hours worked are still recorded.
  • Give notice in writing, state what data you keep and for how long, and keep an inventory of your monitoring tools.
  • Have a legal professional review the final text, especially if you have employees in California.

Table of Contents

What a geofence attendance policy covers

A geofence is a virtual boundary drawn around a place, such as a job site, yard or office. When an employee punches in, the system compares the phone's location with the boundary and records whether the punch was inside or outside. That is the whole mechanism. The policy exists to say how you use that result.

A good policy answers eight questions:

  1. Who is covered (hourly staff, crews, subcontractors, remote supervisors).
  2. Which locations are geofenced and how large each zone is.
  3. When location is captured (at clock-in and clock-out, and any random checks you use).
  4. What happens with an out-of-zone punch.
  5. What you do not collect.
  6. Who can see the data, and for how long you keep it.
  7. What employees do if their phone, signal or battery fails.
  8. How employees raise a question or dispute a record.

If a clause does not answer one of these, it probably does not belong.

Set the scope: events, not streams

The most important choice is when location is read. There are two models. In an event-based model, the app reads location only at the moment of a punch. In a continuous model, it follows the device through the shift.

Event-based and continuous location tracking compared

For attendance, the event-based model is almost always enough. You want to know that someone started work at the site, not where they had lunch. Researchers on workplace tracking describe privacy by design as balancing attendance verification against minimal intrusion, and note that tracking on personal devices can blur the line between work and private life, a common root of resentment toward monitoring software. Employers who roll out these tools without transparency or procedural fairness often see their strongest performers disengage first, whatever the technical accuracy.

Write the scope clause in plain words:

The app records your approximate location only when you clock in, clock out, or respond to a random location check. It does not record your location at any other time.

We go deeper on this distinction in our guide to event-based geofencing time tracking and on why events beat streams for legal risk.

If you want a design reference for the same principle in other monitoring contexts, this overview of privacy by design principles for surveillance systems is a useful read.

Choose radius and zones

GPS on a phone is not exact. Signal bounces off buildings, indoor positions drift, and a crew standing at the gate can show up on the wrong side of a tight line. A policy that promises a 30 meter boundary will generate false flags every morning.

Sensible defaults for most field teams:

Site typeStarting radiusWhy
Small office or shop100 m (about 330 ft)Tolerates indoor drift
Construction or landscaping site100 to 150 mCovers the gate, trailer and work area
Large campus, yard or farm150 m or more, or several zonesOne circle may not fit the property
Roaming crews (route work)Zones per customer locationEach stop is its own site

These numbers are starting points, not rules. Our geofence playbook recommends beginning at 100 to 150 meters and tightening only after you have seen a few weeks of real punch data.

In the policy, list each site by name and state that radii may be adjusted with notice. For teams that move between locations, see how to handle multiple job sites without breaking payroll rules.

Decide what happens when a punch is out of zone

This is the clause that causes the most trouble, so be specific. You have two options:

  • Hard block: the app refuses the punch outside the zone.
  • Flag and review: the app accepts the punch, marks it out of zone, and routes it to a supervisor.

We favor flag and review for attendance. If someone really worked and the app refused to record it, you now have a gap between hours worked and hours recorded, and in the United States employers are generally expected to keep accurate records of hours worked under the FLSA. Our article on audit-ready FLSA timekeeping walks through that record-keeping duty.

Some regulators have gone further. Chile's labor directorate, for example, allows capturing location at the time of a punch but does not allow that information to be used to block the record when a worker is outside the expected place. That is a Chilean rule and does not bind US employers, but it shows where regulators' thinking points: location is evidence for review, not a gate on recording time.

A workable clause reads:

If you clock in outside an assigned zone, the punch is still recorded and marked for review. Your supervisor will contact you within one business day. You will not be disciplined solely because the app flagged a punch.

That last sentence matters. GPS drift, a dead zone or a last-minute site change should not turn into a write-up.

Write the exceptions clause

Technology fails. Your policy should say what to do when it does, because employees who cannot clock in will otherwise guess.

Include:

  • No signal or dead battery: tell the supervisor, then submit a manual entry with a reason when back online.
  • Approved off-site work: a supervisor assigns a temporary zone or approves the punch in advance.
  • Travel between sites: state whether paid travel time starts at the first zone exit or at the next site entry, consistent with your wage rules.
  • Phone changes or new devices: how an employee re-registers.
  • Location Services turned off: what the app can and cannot do.

On that last point, many employees assume switching off location in phone settings is the only way to "block" geofencing. It is a blunt tool: Apple's guidance shows that location settings are controlled per app and can be set to share approximate rather than precise location. A mature policy tells employees which setting the app needs, and why, rather than leaving them to find out through a failed punch. State, too, that the app needs access only when it is in use.

A policy only protects you if employees have actually seen it. The practical standard in privacy guidance is the same everywhere: explain why you collect location, collect no more than you need, and tell people what you hold, for how long and who can see it.

Put these items in writing:

  • Purpose: verifying attendance and preventing inaccurate or false punches.
  • Data collected: time, approximate coordinates at the punch, in-zone or out-of-zone status, device information used for fraud checks.
  • Not collected: location between punches, location off the clock, personal content on the phone.
  • Access: named roles, such as site supervisors and payroll.
  • Retention: a stated period, aligned with your payroll record retention obligations. Confirm the period with counsel.
  • Acknowledgment: a signed or in-app acceptance, stored with the employee record.

Precision matters legally in California, where the CCPA treats precise geolocation as location that identifies a person within an 1,850-foot radius, and classes it as sensitive personal information. Because a 100 to 150 meter geofence punch can fall inside that definition, treat attendance location data as sensitive and ask counsel how notice duties apply to your workforce.

California and other state risks

The US has no single federal law on employer location tracking, so the rules sit mostly at state level. Employment lawyers at Skadden warn that state constitutional privacy rights, particularly in California, Florida and Louisiana, can create litigation risk that outweighs the savings from automated time tracking. Their advice: monitoring policies should be clearly communicated and consistently enforced.

California is also moving toward more documentation. A 2025 legislative committee analysis of SB 238 describes a proposal that would require employers to give an annual notice to the state's Department of Industrial Relations listing the workplace surveillance tools they use. AB 1221 uses a broad definition of a "workplace surveillance tool": any system, application or device that collects worker data, activities or behaviors. Bills change as they move, so check current status before relying on either one.

Whatever passes, the direction is clear. Keep an inventory of every tool that touches worker data, including your geofence. For each, record what it collects, how the data is interpreted and who can see it. That inventory also makes your attendance policy easier to write.

This article is general information, not legal advice. If you have employees in California or in states with their own privacy statutes, have an employment attorney review your final policy.

California and other state risks — overview diagram

Our perspective

We build attendance software for field teams, and we see the same pattern. Companies adopt geofencing to stop buddy punching and false clock-ins, then lose employee trust because the policy is vague or the tool seems to watch more than it does.

We design around the opposite approach. Clock-Me verifies a punch with GPS at the moment it happens, adds identity checks and device-based fraud detection, and does not rely on continuous background tracking. That is why the policy can be short and honest: location at the punch, nothing between punches.

Three habits make the difference in practice:

  • Treat out-of-zone flags as questions. Most are drift or a changed site, not misconduct.
  • Publish the policy where people clock in. In the app, in onboarding and on the crew board, in the languages your crew speaks.
  • Review the data on a schedule. A weekly look at flags tells you whether the radius is wrong before it becomes a dispute.

If a clause would make you uncomfortable explaining it to a new hire on their first morning, rewrite it.

— Clock-me

A policy template you can adapt

Copy this, replace the brackets, and have counsel review it.

1. Purpose. [Company] uses location verification so that recorded work time reflects actual work at assigned sites.

2. Who is covered. All hourly employees who clock in with the [app name] mobile app.

3. What we collect. When you clock in or out, or answer a random location check, the app records the time, your approximate location, and whether you are inside your assigned work zone. The app also uses device information to detect fraudulent punches.

4. What we do not collect. We do not track your location between punches or outside work hours.

5. Work zones. Each site has a zone of [100 to 150] meters around its address. Zones are listed in the app. We will tell you before we change them.

6. Out-of-zone punches. Your punch is recorded and sent to your supervisor for review. You will not be disciplined solely because of a location flag.

7. When the app does not work. Tell your supervisor. Submit a manual time entry with a reason. Your supervisor approves or corrects it.

8. Access and retention. Supervisors and payroll can view location data for punches of employees they manage. We keep it for [period] and then delete it.

9. Questions and disputes. Contact [name or role] at [contact]. You can ask us to review any time record.

10. Acknowledgment. I have read this policy. [Signature or in-app acceptance, date]

Roll it out without friction

  1. Draft with your supervisors. They know which sites have bad signal.
  2. Run a pilot week with flags on but no consequences. Check which sites flag the most and widen those zones.
  3. Brief your team in person and in the app. Explain what is and is not collected.
  4. Collect acknowledgments and store them.
  5. Review weekly for the first month, then monthly.
  6. Update the policy whenever you add a tool, change a radius or alter retention.

Our guide to verifying field employee location without live tracking shows how this works day to day, and the piece on real-time attendance dashboards explains how supervisors spot no-shows without watching a map all day.

Put the policy into practice with Clock-Me

Clock-Me gives field teams one-tap, GPS-verified clock-ins, geofencing, identity verification, random location checks, live dashboards, timecard attestation, timesheet approval and payroll export, with features built for California labor law compliance. You can start with the Free plan at $0 per month and move up as your team grows: Starter is $31.99 per month, Growth $54.99, Business $99.99, Pro $224.99 and Corporate $439.99, all per month. Enterprise pricing is not published. See the features or compare plans.

FAQ

What should be included in an attendance policy?

Cover who is covered, work hours and how to clock in, how lateness and absences are handled, what to do when the system fails, and how records are corrected. For a geofence policy, add the zones, what location data you capture, who sees it and how long you keep it.

Can an employer require geofenced clock-in?

In most US states, employers can use location verification for legitimate timekeeping with clear notice, but rules differ by state and are changing, especially in California. Limit collection to the punch, document it, and have counsel review your policy.

How does geofencing work for attendance?

The employer draws a virtual boundary around a work site. At a punch, the app compares the phone's location to that boundary and records whether it was inside or outside. Good systems then log or flag the result for review.

Should out-of-zone punches be blocked?

We recommend recording them and flagging them for review. Blocking can leave real work unrecorded, and some regulators outside the US, such as Chile's labor directorate, do not allow location to be used to prevent a punch. Check your own jurisdiction's rules.

Sources