The wage claim never arrives on the night the timesheet goes wrong. It arrives eleven months later, from a floor tech you let go in the spring, and it says he was on the clock for hours you never paid.
So you pull the GPS logs, because that is exactly what you bought them for. Then you read them closely and realize they are not your defense. They are the other side's exhibit.
GPS time tracking is legal in all 50 states when it captures employees during working hours and they have been told about it in writing. What is not legal: tracking off the clock, skipping written notice in states like Connecticut, or requiring a personal phone without reimbursement in California or Illinois.
The legality question almost never turns on the tracking itself. It turns on everything you built around it: notice, acknowledgment, who paid for the phone and the data, and whether the minutes your geofence recorded ever made it onto a paycheck.
The leak nobody prices: unpaid gap time between accounts
Here is the failure mode that costs real money, and it has nothing to do with privacy. When a cleaner clocks out at Account A and clocks in at Account B during the same shift, the minutes in between are compensable under federal law.
Travel from home to the first site and from the last site home is generally not paid time under the Portal-to-Portal Act. Travel between job sites during the workday is a different animal: 29 CFR 785.38 treats it as hours worked.
Geofenced clock-in creates a beautifully precise, timestamped record of exactly how many of those minutes you did not pay. Before GPS, that time was invisible. After GPS, it is documented in your own system.
Worked example: a six-person split route
Take a fictional operator, Meridian Facility Services, running six cleaners on two-stop nightly routes across a metro area. Average windshield time between the two accounts is 18 minutes. Payroll pays clocked minutes only.
| Line item | Illustrative value |
|---|---|
| Cleaners on split routes | 6 |
| Unpaid gap per cleaner per night | 18 minutes |
| Nights per week, weeks per year | 5 nights, 50 weeks |
| Unpaid hours per year | 450 |
| Straight-time value at $17 per hour | $7,650 |
| Plus FLSA liquidated damages (equal amount) | $15,300 |
| Two-year lookback | $30,600, plus plaintiff attorney fees |
Every figure above is an assumption stated on its face, not a study. Change the crew size or the drive time and rerun it for your own routes. The wage rate is set near the BLS median for janitors and cleaners so the arithmetic is not fantasy.
If those added minutes push anyone past 40 hours in a week, they are owed at time and a half, which moves the number again. And if a court finds your time records inadequate, Anderson v. Mt. Clemens Pottery Co. lets the employee prove hours worked by reasonable inference and shifts the burden to you.
Why good operators end up on the wrong side of this
Nobody sets out to run an illegal tracking program. Three specific shortcuts produce almost all of the exposure.
- The rollout was a text message. The policy lives in a group chat, not in the handbook, and no employee ever signed anything acknowledging it.
- The tracker was bought to solve one problem. You wanted buddy punching to stop. You were not thinking about travel time, personal-device reimbursement, or notice statutes, so none of those got designed.
- Nobody owns the exceptions. When the geofence rejects a clock-in, a supervisor fixes it by hand at midnight, with no note and no employee confirmation, and that edited record is now the weakest document in your file.
The common thread is that GPS made your operation more precise without making your payroll rules more precise. Precision cuts both ways.
Which states require written notice before you track a cleaner
There is no federal statute that says "you may not GPS your employees." What exists is a patchwork of notice laws, device laws, biometric laws and expense laws that each catch a different part of a typical janitorial deployment.
| Legal area | What the rule requires | Where it bites a janitorial operation |
|---|---|---|
| Electronic monitoring notice (Conn. Gen. Stat. 31-48d) | Prior written notice describing the types of monitoring, posted in a conspicuous place | Civil penalties of $500 for a first violation, $1,000 for a second, $3,000 for a third and each after. Your "conspicuous place" is a client building you do not control. |
| Notice at hire (N.Y. Civil Rights Law 52-c) | Written notice at hire with employee acknowledgment, plus posting. Written around phone, email and internet monitoring | Same penalty ladder as Connecticut. Counsel routinely folds GPS into the same notice rather than arguing about scope. |
| Vehicle tracking devices (Cal. Penal Code 637.7, Tex. Penal Code 16.06 and similar) | No hardware tracker on a vehicle without the owner's consent | Hits you the day you put a plug-in tracker in a supervisor's personal truck instead of a company van. |
| Biometric clock-in (740 ILCS 14 BIPA, Texas CUBI, Washington) | Written release and a published retention schedule before collecting fingerprints or face geometry | BIPA carries $1,000 per negligent violation and $5,000 per reckless or intentional one. Fingerprint kiosks in Illinois accounts are a live risk, not a theoretical one. |
| Personal device expenses (Cal. Lab. Code 2802; 820 ILCS 115/9.5) | Reimburse a reasonable percentage of the phone and data bill used for work | Cochran v. Schwan's Home Service held reimbursement is owed even when the plan is unlimited and the employee pays nothing extra. |
| Recordkeeping (29 CFR 516.2) | Accurate records of hours worked each day and each workweek | A GPS log is evidence of location, not a lawful time record on its own. The two have to reconcile. |
| Union workforces (NLRA) | Surveillance and monitoring changes are commonly a mandatory subject of bargaining | NLRB General Counsel Memorandum GC 23-02 (2022) signaled close scrutiny of electronic surveillance and algorithmic management of workers. |
Notice statutes are cheap to comply with and expensive to ignore. A one-page acknowledgment signed at hire closes most of this exposure permanently.
Can you require crews to clock in on their own phones?
Generally yes, and most cleaning companies do, because handing out company phones to a 30-person night crew is not realistic. The condition is that in reimbursement states you pay something toward the device.
California and Illinois are the clearest. A modest monthly stipend, applied consistently and documented on the pay stub, is the standard practical answer. What you cannot do is treat the requirement as free because the employee already owns a phone.
You also need a real plan for the cleaner whose phone is dead, out of data, or a five-year-old device with terrible GPS. If your only fallback is "text your supervisor," your time records will be full of undocumented manual edits.
Where GPS tracking genuinely crosses the line
Three practices move you from "legal with notice" to "hard to defend in any state."
- Tracking off the clock. Continuous background location on a personal phone at 2 p.m. when the shift starts at 6 p.m. is the fact pattern that turns a wage case into a privacy case. Capture location at clock-in and clock-out only.
- Using location as the sole basis for discipline or pay deductions. If a nonexempt employee worked, you owe them for the time, full stop. Pay the hours, then address the conduct separately through your disciplinary process.
- Tracking that reaches protected activity. Monitoring that would reasonably tend to interfere with employees discussing wages or organizing is a separate problem under the NLRA, and it applies to nonunion shops too.
Data minimization is not just a legal posture. It is also the cheapest one. A system that only knows where someone was at two timestamps has far less to disclose, far less to breach, and far less to explain in a deposition.
Warning signs your GPS clock-in is building a case against you
These are the tells that show up months before a claim does. If three or more are true this week, you have an exposure, not a program.
- Same-shift gaps are never paid. You can find shifts where someone clocked out of one account and into another 20 minutes later, and payroll shows only the two clocked blocks.
- Manual clock-in edits are routine. A supervisor is correcting more than a handful of punches per week, and the edits have no reason code and no employee sign-off.
- The handbook says nothing. Search your employee handbook for the word "location." If it is not there, and your crews cannot produce a signed acknowledgment, you have no notice trail.
- Pre-rollout hires never signed anything. The 12 people hired before you turned tracking on were told in a huddle. That is not written notice in Connecticut.
- Crews are working before the app lets them clock in. If the fence is tight and the cleaner starts hauling equipment while standing outside it, that is unpaid work time. California rejected the federal de minimis defense for small increments in Troester v. Starbucks (2018).
- Exit conversations mention being watched. In an industry where replacing a cleaner costs you recruiting time, training hours and a rough first week at the account, a badly explained tracker is an expensive way to lose people.
- Nobody can say how long location data is kept. If you cannot answer that in one sentence, you cannot answer a subpoena either.
The fix: a GPS policy and geofence setup that survives an audit
This is a half-day of work, once, plus a signature from every employee. It is dramatically cheaper than the alternative.
GPS time tracking compliance checklist
- Write a one-page policy stating exactly what is collected: latitude and longitude at clock-in and clock-out, nothing between, nothing off the clock.
- State who can see the data (payroll, the direct supervisor, the owner) and how long it is retained. Align retention with FLSA rules: three years for payroll records, two years for the underlying time records.
- Get a signed acknowledgment from every current employee, not just new hires, and reissue it whenever the policy changes.
- Publish the policy in the languages your crews actually read. A signature on a document someone cannot read is worth very little.
- Post the notice where employees report, and give it in writing before monitoring begins in states that require prior notice.
- Set a written BYOD stipend, or issue devices. Show the stipend as a separate line on the pay stub.
- Define the fallback procedure for a failed clock-in: who to call, what gets written down, and who confirms the corrected time. Require the employee to confirm every edit.
- Write the gap-time rule explicitly: mid-shift travel between accounts is paid, and payroll adds it automatically rather than waiting for someone to ask.
- Add one line stating that location data alone will not be the sole basis for discipline.
- If any site is unionized, check the bargaining obligation before you flip the switch, not after.
What geofence radius should you set?
Radius is a compliance decision disguised as a settings field. Too wide and the record proves nothing. Too tight and you generate false rejections, off-the-clock work, and a pile of manual edits.
GPS.gov notes that GPS-enabled smartphones are typically accurate to within about a 4.9 meter radius under open sky, and that accuracy degrades near buildings, bridges and indoors. Urban canyons and underground loading docks are exactly where your crews clock in.
| Site type | Practical radius | Failure mode to watch |
|---|---|---|
| Standalone suite, own parking lot | 100 to 150 meters | Rare. Tighten only if a neighboring account is within the fence. |
| Multi-tenant tower with garage entry | 150 to 250 meters | Clock-in attempts from the garage where signal drops. Expect edits if you go tight. |
| Medical or campus with several buildings | Separate fence per building | One large fence hides which building the crew actually served, which kills the record's value in a client dispute. |
| Rural or industrial site, poor coverage | Widen, plus a documented manual fallback | Repeated failures that quietly become paper logs nobody reconciles. |
The payroll close that keeps this from coming back
The policy is a one-time fix. The gap time is a recurring one, so it needs to live inside a routine that already happens every pay period.
- Export the period's punches to a spreadsheet before you run payroll.
- Sort by employee and date, then flag any employee with two or more locations on the same calendar day. Those rows contain your gap minutes.
- Add the gap minutes to paid hours unless the employee genuinely went off duty, was free to use the time for their own purposes, and the break meets your state's rules.
- Count manual overrides by location. Any site producing repeated overrides gets its radius revisited, not its crew disciplined.
- Once a quarter, confirm every person hired that quarter has a signed GPS acknowledgment on file. That reconciliation takes ten minutes and closes the notice gap permanently.
Where CleanTrack360 fits
CleanTrack360 includes geofenced GPS clock-in and clock-out that runs in the phone browser, so there is nothing for crews to install. Location is captured at clock-in and clock-out only. There is no breadcrumb trail between punches, which is the narrower and more defensible design described above. The default radius is 150 meters and is configurable per location, so a downtown tower and a standalone suite do not have to share a setting. Reports export to CSV, which is what you need for the same-day multi-location review at payroll close.
Plans are Starter at $99 per month for up to 5 team members, Pro at $199 for up to 20, and Business at $249 for up to 50, priced per plan rather than per user. The interface runs in English, Spanish and Portuguese, which matters when you need a crew to understand what the system records. There is a 14-day free trial with no credit card. The written policy and the signed acknowledgments are still your job, and no software substitutes for them.