If you cannot explain geofencing to a new hire in two minutes, you will not get adoption. Use this page as the script.
geofencing time clock explained: Try geofencing free for 14 days with Cloq-it. Try it free for 14 days. Start free →
The moving parts
Job pin + radius. Phone permission. OS geofence API. App logic (auto vs prompt). Server validation. Manager alerts. That is the whole machine.
Battery and privacy, honestly
Modern OS geofences are event-based, not “GPS every second.” Continuous tracking modes are different — and Cloq-it is not trying to be a breadcrumb tracker.
- Only pinned jobs
- Visible in phone settings
- Stops on sign-out
- No data sale
| Word | Meaning |
|---|---|
| Enter / arrive | Crossed into the fence |
| Exit / depart | Left the fence |
| Dwell | Stayed long enough (if used) |
| Punch check | One-time fix at button press |
Common questions
Is geofencing the same as live GPS map tracking?
No. Live maps watch constantly. Geofences wait for boundary crossings.
Why did my arrive not fire?
Permission not Always, fence too small, phone asleep with aggressive battery savers, or mock location blocked.
Try geofencing free for 14 days with Cloq-it.
Set up your company, invite your team, and be clocking in within the hour. Cancel anytime after the trial.