It is 6:04 pm on a Tuesday. Your four-person crew is scheduled from 6:00 to 10:00 at a 60,000 square foot office park, and the payroll report says they were all on the clock at 5:52. Two of them were still in the parking lot at 6:15.
You do not know that, because a punch on a wall clock or a text message to a supervisor tells you when someone said they arrived, not where they were. That gap between reported time and actual time on site is where janitorial margin quietly disappears.
GPS clock-in closes the gap, but only if you set it up like an operations system instead of a surveillance gadget. Radius settings, exception handling, consent language, and payroll reconciliation matter far more than the technology itself. Here is how to do all of it.
What GPS Time Tracking Actually Captures
Most janitorial GPS time tracking works on a geofence: an invisible circle drawn around a job site address with a set radius. When a cleaner opens the clock-in screen on a phone, the device reports its coordinates and the system checks whether those coordinates fall inside the circle.
Inside the fence, the punch is accepted and stamped with a time and a location. Outside the fence, the punch is blocked or flagged as an exception for a supervisor to review.
That is the whole mechanism. It is a location check at a moment in time, not a live map of where your people are.
Location capture versus continuous tracking
There is a meaningful difference between capturing a coordinate at clock-in and clock-out and tracking someone's movement all shift. The first is a timestamped verification of arrival and departure. The second, sometimes called breadcrumb tracking, records a trail of positions throughout the shift.
For commercial cleaning, arrival and departure verification answers nearly every question you actually have: did the crew show up, did they show up on time, and did they stay for the scheduled duration. Continuous tracking adds battery drain, employee resistance, and privacy exposure without answering a question your inspection program should not already be answering.
How accurate is a phone's location, really
GPS.gov states that GPS-enabled smartphones are typically accurate to within a 4.9 meter (16 foot) radius under open sky. That accuracy degrades significantly indoors, in stairwells, in basements, and in dense downtown blocks where signals bounce off buildings.
When satellite signal is weak, phones fall back to Wi-Fi positioning and cell tower triangulation, which can place a device anywhere from tens of meters to several hundred meters from its true position. This is the single most important technical fact behind every setup decision that follows.
Before You Turn It On: Prerequisites
Rolling out GPS clock-in without these five things in place is how you end up with a payroll dispute and three resignations in the first month.
Pre-Launch Checklist
- Accurate site addresses and coordinates: A geofence built on a mis-geocoded address will reject every legitimate punch. Verify the pin on a map, not just the mailing address, especially for suites inside office parks and industrial condos.
- A written time-tracking policy: One page covering what is collected, when it is collected, who sees it, and what happens when a punch fails. Have every cleaner sign it.
- A device plan: Decide whether crews use personal phones or company devices, and confirm your reimbursement obligation. California Labor Code section 2802 and the reasoning in Cochran v. Schwan's Home Service (2014) require reasonable reimbursement for work-related personal cell phone use, and Illinois has a similar expense reimbursement provision in its Wage Payment and Collection Act.
- Supervisor coverage for exceptions: Someone has to approve or correct failed punches within 24 hours. If nobody owns this, cleaners stop trying and go back to texting.
- A parallel run period: Two full pay periods where GPS punches and your existing method run side by side, so you can compare before anyone's paycheck depends on the new system.
The wage-hour rules that apply
Under the Fair Labor Standards Act, 29 CFR Part 516 requires employers to keep the hours worked each day and the total hours worked each workweek for every non-exempt employee. The regulation does not prescribe a format. GPS timestamps satisfy it as well as paper cards, provided the records are complete and accurate.
Rounding is where operators get into trouble. Federal regulation 29 CFR 785.48(b) permits rounding to the nearest increment, commonly a quarter hour, when the practice averages out neutrally over time and does not systematically favor the employer.
State law is moving away from that allowance. In Troester v. Starbucks (2018), the California Supreme Court rejected the federal de minimis defense for small increments of off-the-clock work, and in Camp v. Home Depot U.S.A., Inc. (2024), it held that neutral rounding is not acceptable when an employer actually captures exact minutes. Once you install GPS clock-in, you are capturing exact minutes. The defensible policy is simple: pay to the minute.
Step-by-Step Setup
Step 1: Set the radius per site, not globally
A 150 meter default radius, roughly 500 feet, works for most standalone commercial buildings. It is wide enough to absorb indoor signal degradation and tight enough that someone cannot clock in from a coffee shop three blocks away.
Then adjust site by site. Tightening every fence to 50 meters feels rigorous and produces a flood of false rejections from crews standing in a basement mechanical room.
| Site type | Suggested radius | Why |
|---|---|---|
| Standalone suburban office, 10k to 80k sq ft | 100 to 150 m | Good sky view in the lot, moderate indoor drift |
| Suite inside a multi-tenant office park | 150 to 200 m | Shared address, imprecise geocoding, interior corridors |
| Downtown high-rise | 150 to 250 m | Urban canyon reflections push positions off by a full block |
| Warehouse or distribution center | 200 to 300 m | Large footprint, metal roof, deep interior dead zones |
| Medical clinic or dental office in a strip center | 100 to 150 m | Neighboring tenants are close, so keep it tight |
| School or multi-building campus | Separate fence per building | One giant circle destroys your ability to tell buildings apart |
| Retail center with multiple contracted stores | 75 to 125 m per store | Prevents clocking into the wrong client from the same lot |
Step 2: Decide what happens when a punch fails
Every GPS system produces exceptions. Your policy for handling them determines whether the system builds trust or destroys it.
The two viable models are hard block, where an out-of-fence punch is refused entirely, and soft flag, where the punch is recorded with a location note and routed to a supervisor for approval. Hard blocking is cleaner on paper and worse in the field, because a cleaner who cannot clock in still has to work, and now you have unrecorded hours, which is exactly the FLSA problem you were trying to solve.
Start with soft flags for the first 60 days. Once exception volume drops and your radii are calibrated, tighten to hard blocks on your highest-risk accounts if you want.
Step 3: Build an exception triage table
Give supervisors a decision rule so they are not improvising at 11 pm.
| Exception pattern | Most likely cause | Action |
|---|---|---|
| Punch accepted, but coordinates sit 300 m off | Wi-Fi or cell tower fallback indoors | Approve. Widen the radius for that site. |
| Repeated failures at one building only | Bad geocode or a fence that is too tight | Re-pin the location, retest, adjust radius |
| Failure from one person across all sites | Browser location permission denied, or Low Power Mode | Reset permissions on the device, retrain |
| Clock-in on time, clock-out 40 minutes early, every visit | Crew is leaving early and self-reporting full hours | Site visit and a documented conversation |
| Clock-in 12 minutes before scheduled start, consistently | Early arrival drift, now compensable time | Cap punch-in windows in the schedule, not in payroll |
| Clock-out missing entirely, frequent | Phone died, or the tab was closed | Supervisor edit with a written reason attached |
Step 4: Set punch windows tied to the schedule
Location verification only answers "where." You still need to control "when." Tie each punch to a scheduled shift and define an allowable window, for example clock-in permitted no earlier than 10 minutes before the scheduled start.
The math matters. If eight cleaners clock in an average of 9 minutes early on 12 shifts per month, that is 14.4 paid hours per month that were never in your bid. At a fully burdened rate of $22 per hour, that is $316.80 monthly on one account. Run that number for your own portfolio before you decide punch windows are a small detail.
Step 5: Reconcile GPS hours against your bid
Time data is only useful when it is compared to something. Three calculations turn punch records into management information.
| Metric | Formula | What it tells you |
|---|---|---|
| Schedule variance | (Actual hours - Scheduled hours) / Scheduled hours x 100 | Whether the site is running over or under the plan you priced |
| Productivity rate | Cleanable square feet / Actual hours on site | Square feet per hour, comparable to ISSA production rates |
| Labor cost per cleanable sq ft | Burdened labor cost for the month / Cleanable sq ft serviced | Direct comparison against the labor line in your quote |
| Attendance reliability | Shifts with on-time clock-in / Total scheduled shifts x 100 | Early warning on accounts heading toward a complaint |
For the productivity rate, use published production times as your reference point rather than a number you invented. ISSA's cleaning times data provides task-level and area-level rates that most commercial estimators already use to build bids.
If your bid assumed 3,200 cleanable square feet per hour and your GPS data shows the crew is actually running at 2,400, you have a real problem with a real number attached to it. You can now decide whether to add labor, reduce scope, or reprice at renewal.
Step 6: Roll out to crews without a revolt
Announce it two weeks before launch, in person or on a call, not by text. Explain three things: it records location only at clock-in and clock-out, it protects them when a client claims the crew never showed, and it means they get paid for every minute they are actually on site.
That last point is not spin. Cleaners who routinely stay 15 minutes past scheduled end to finish a floor have been donating that time. GPS timestamps make it visible and payable.
Note also that GPS avoids a category of legal exposure that fingerprint clocks carry. The Illinois Biometric Information Privacy Act requires written consent and a published retention schedule before collecting fingerprints or face scans, and it allows a private right of action. Location data is not biometric data, which is one reason many multi-state janitorial operators skip biometric hardware entirely.
Common Mistakes to Avoid
- Setting every geofence to the same tight radius: The building that works at 75 meters and the warehouse that needs 250 meters do not share a setting. Calibrate per site.
- Treating GPS as proof of work: A punch inside the fence means a phone was near the building. Pair time data with an inspection program using photo evidence, or you are measuring presence and calling it performance.
- Rounding punches after installing exact-minute capture: This is the fastest route to a wage claim, particularly in California. Pay actual minutes.
- Assuming location data prevents buddy punching: It does not eliminate it. A cleaner can hand a phone to a coworker, and consumer tools can falsify device location. Pair GPS with one-device-per-person enforcement, unannounced supervisor visits, and inspection photos that show a real person in a real space.
- No offline fallback: Basements and mechanical rooms have no signal. Define a written backup procedure and a supervisor edit trail before it happens, not after.
- Letting exceptions pile up until payroll day: Approving 60 flagged punches at 4 pm on Friday is not review, it is rubber-stamping. Handle them daily.
- Skipping the consent form: A signed acknowledgment costs nothing and resolves most disputes before they start.
- Using time data as a weapon: If the first thing the crew hears about GPS is a disciplinary write-up, adoption dies. Lead with fixing broken schedules and paying accurate overtime.
How Often to Review the Data
GPS time tracking generates data continuously and delivers value only on a review cadence. This is the schedule most operators can sustain.
| Frequency | What you review | Owner |
|---|---|---|
| Daily | Missed clock-ins, missed clock-outs, out-of-fence flags from last night | Area supervisor |
| Weekly | Schedule variance by site, overtime trending, repeat exception offenders | Operations manager |
| Each pay period | Full punch audit before payroll close, all edits documented with a reason | Payroll or office manager |
| Monthly | Productivity rate and labor cost per square foot versus bid, per account | Owner or GM |
| Quarterly | Geofence radius audit on sites with high exception counts, policy refresh | Operations manager |
| Annually | State wage-hour and privacy law review, retention schedule check | Owner, with counsel |
On retention: the Department of Labor requires payroll records to be kept for three years and the underlying time records, including the raw punch data, for two years. Confirm your system's export path before you need it in a dispute.
Troubleshooting the Three Problems You Will Actually Hit
"The browser keeps asking for location permission"
Mobile browsers prompt for location the first time a site requests it, and iOS Safari will re-prompt if the site was not granted persistent access or if the page was loaded over an insecure connection. Have crews bookmark the clock-in page, load it once with a supervisor present, and grant permission for the site rather than "allow once."
"It says I am not at the site and I am standing in the lobby"
Nine times out of ten this is indoor signal fallback, not dishonesty. Check where the recorded coordinate landed. If it landed a few hundred meters away, widen the radius and move on.
"Crews clock in from the parking lot and sit there"
A geofence cannot distinguish the lot from the janitor's closet at typical radii. Solve this with scheduling and inspection, not with a smaller circle. If the shift is four hours and the inspection score at that site is sliding, the time data has told you where to look, which is what it is for.
How CleanTrack360 Handles This
CleanTrack360 includes geofenced GPS clock-in and clock-out that runs in the phone browser, so crews use whatever device they already carry and there is nothing to install. The default geofence radius is 150 meters and is configurable per location, which is exactly the per-site calibration described above. Location is captured at clock-in and clock-out only, not between punches, and there is no native mobile app yet.
Punch data feeds the same system that holds your drag-and-drop schedule, recurring shifts, and quality inspections with photo evidence, so schedule variance and inspection scores sit side by side instead of in two disconnected tools. Reports export to CSV for payroll and recordkeeping. Plans start at $99 per month for up to 5 team members, and there is a 14-day free trial with no credit card required.