Janitorial Geofence Setup for Night-Shift Cleaning Crews

The economics of night-shift commercial cleaning are brutal if your geofence setup is wrong. Empty buildings, no supervisors on site, crews working 9 PM to 5 AM — every weakness in your time tracking gets exploited. Buddy punching, late arrivals logged as on-time, ghost shifts where the lead clocks in five people and only one shows up. Operators routinely lose 5-12% of payroll to these patterns and never see the leak directly.

The fix isn’t just “turn on geofencing.” It’s setting up geofences that match the operational reality of janitorial night shifts — and pairing them with PinShot and Live Map so the data is defensible.

This is the playbook.

Why night-shift geofences need their own setup

Daytime construction geofences and night-shift janitorial geofences look similar on paper but have to behave differently.

Dimension	Daytime construction	Night-shift janitorial
Supervisor on site?	Usually yes	Almost never
Building access	Open	Locked, keypad, badge
Lighting	Daylight	Low — affects PinShot capture
Crew arrival pattern	Clustered at shift start	Staggered, by site, by route
Geofence radius	100-200m	50-150m, site-specific
Buddy-punch exposure	Medium	High
Live Map utility	Dispatch coordination	Verification and safety

The night shift case is more about verification than coordination. Nobody is on site watching, so the geofence has to do that work.

The right radius for each site type

A common mistake is using a single global geofence radius across all customer sites. The right radius depends on the building type:

• Single-tenant office (5,000-15,000 sq ft). 50m geofence centered on the building entrance. Workers cross the geofence on the way to the door — the clock-in event fires the moment they’re in PinShot range of the entrance.

• Multi-tenant office building (15,000-50,000 sq ft). 75m geofence centered on the building. Includes the main entrance and the loading dock.

• Corporate campus (50,000+ sq ft, multiple buildings). Multiple overlapping geofences, one per building, 100m each. Treat the campus as one customer with multiple sites in Klees so reporting consolidates.

• Retail center / mall janitorial. 150-200m geofence centered on the main service entrance. Wider radius accommodates the parking-lot-to-service-corridor walk.

• Medical office or clinic. 50-75m tight geofence. Strict access patterns make the tighter geofence work.

• Industrial / warehouse cleaning. 100-150m, often offset toward the loading-dock entrance the crew uses, not the main customer entrance.

Klees lets you set geofence radius per site, not just per customer. That’s the configuration unlock — three buildings under one customer can all have different radii.

The PinShot pairing

A geofence alone doesn’t prove who clocked in. It proves the phone was in range. PinShot ties identity to the geofence event by capturing a verified selfie at clock-in (and optionally at clock-out).

For night-shift janitorial, PinShot is non-negotiable. The Alta Janitorial deployment documented in the Alta case study eliminated buddy-punch incidents inside two weeks once PinShot was enforced. The mechanism is simple: a worker can no longer hand their phone to a friend or clock in from home.

PinShot at night shift has one additional consideration: low light. Klees PinShot is calibrated for low-light capture and works in the dim lighting typical of cleaning crew entrances. If the entrance is unlit, position the clock-in to happen just inside the building after the worker passes the badge reader.

Common geofence mistakes for night shifts

The same mistakes show up across operators auditing their night-shift setups:

1. Geofence too wide. A 500m geofence around an office building includes the highway, the gas station, and the worker’s car parked two blocks away. The clock-in event proves nothing.

2. Geofence centered on the wrong entrance. Cleaning crews use service entrances, loading docks, badge-access side doors. Centering the geofence on the front lobby misses where the crew actually arrives.

3. No PinShot enforcement at clock-out. Workers can clock out from the parking lot 20 minutes early. Without PinShot at clock-out, the geofence at clock-in is the only verification — and it’s not enough.

4. No exception monitoring. Geofence events fire constantly but nobody reviews exceptions. Set up the dispatcher to see anomalies in Live Map in real time.

5. One-size-fits-all radius. Hospital cleaning needs a different geofence than warehouse cleaning. Site-specific configuration matters.

Live Map for the night dispatcher

Geofence + PinShot data is most valuable when surfaced in Live Map for the night dispatcher. The night supervisor watching 8-15 crews across a metro sees:

• Each crew’s clock-in status, color-coded by geofence event.
• PinShot capture results in real time, flagged for any anti-spoof failures.
• Late arrivals before they cascade into customer complaints.
• Early departures before they bleed paid hours.

The Live Map for supervisors piece covers the operational mechanics. For janitorial night shifts, the dispatcher reclaims 4-6 hours per night that used to go to phone calls and texts checking in.

How to roll out tighter geofences without crew pushback

If you’re tightening from a previously-loose setup, the rollout matters. Don’t surprise the crew at midnight with a stricter geofence.

A clean rollout looks like this:

1. Audit current geofence radii by site. Pull the average distance between clock-in events and the building center. Anything past 100m is suspect.
2. Announce the change. Tell foremen and crews two weeks ahead. Explain the why: clean data, accurate hours, no audit problems with customers.
3. Roll out one site at a time. Start with a site where the geofence is most-obviously wrong. Tighten to the correct radius. Watch a week of data.
4. Adjust for false positives. Some sites have legitimate edge cases — workers arrive via a side parking lot that’s outside the geofence. Adjust the geometry rather than widening the radius.
5. Roll forward across all sites. Once you have a working pattern, replicate it.

Most operators complete a full geofence audit and re-tightening across 30-50 sites in one to two weeks.

Compliance: what the audit trail proves

A properly configured geofence + PinShot setup produces a defensible audit trail for several compliance use cases:

• Customer billing disputes. Hours billed against the SLA can be proven by clock-in event, geofence position, and PinShot capture.
• Workers’ comp claims. When an injury claim references a specific shift, the audit log proves the worker was on-site at the time.
• State DOL audits. Time records tied to verified identity hold up against challenges.
• Insurance underwriting. Carriers increasingly discount premiums for operators with verified time-tracking audit logs — see the SHRM overview on workforce compliance technology for the broader trend.

Klees Pro retains geofence event logs, PinShot captures, and clock-in metadata in audit-ready exports.

FAQ

What’s the smallest reliable geofence radius?

50 meters works for tight single-tenant sites. Below that and GPS variance starts producing false negatives — workers actually at the door get flagged as off-site.

Does PinShot work in low light?

Yes. Klees PinShot is tuned for low-light capture and is calibrated against the lighting conditions typical of night-shift commercial cleaning entrances. Anti-spoof scoring continues to work in low light.

What if the geofence covers two customers in a single building?

Configure each customer as a separate site in Klees, even if they share a building footprint. The geofence can overlap but the customer attribution is correct.

Can a worker disable GPS to dodge the geofence?

GPS disabled means clock-in fails. Klees requires location services for any geofence-enforced clock-in, with a manual-override path that flags the entry for supervisor approval — making fraud harder, not easier.

How does this work with offline mode?

Klees offline mode queues clock-in events with the last-known GPS fix and PinShot capture. When the device returns to a signal, the event syncs with the geofence evaluation applied retroactively. See offline time tracking for the full mechanic.

---

Want help auditing your current geofence setup against night-shift best practice? Book a 20-minute setup call and we’ll review your top 5 sites live.