Setting it up, site by site
- List every site with its street address. Check the pin on a map: for a big building, put it at the entrance the crew uses.
- Choose a radius for each site. Small for a house, larger for an office park. See choosing a geofence radius.
- Choose the rule for punches outside the zone: warn the employee, send the punch to a manager for review, or block it.
- Decide which people each zone applies to, if not everyone.
- Test it: stand at the entrance and clock in, then try from the parking lot.
Warn, review or block
| Rule | What happens | Fits |
|---|---|---|
| Warn | The punch goes through and is flagged as out of area | New setups, while you check the zones are right |
| Review | The punch goes through and waits in a queue until a manager clears it | Most crews: nobody is stopped from working, and odd punches get looked at |
| Block | An out-of-zone punch from the app is refused; the employee can send an override request | Sites where clocking in elsewhere is a known problem |
Telling the crew
Say plainly when location is read and what it's used for. A short note works:
From Monday, clocking in and out on your phone checks that you're at the job site. Your location is read only at the moment you clock in or out, never between jobs and never when you're off the clock. If you're at the right site and it says you're not, clock in anyway and tell me; I'll fix the zone.
What it can't tell you
- Phone GPS can be off by tens of meters indoors or between tall buildings.
- A punch from inside the zone doesn't show who held the phone. Personal logins handle that.
- It says where the punch happened, not what work was done. Your job checklists and client feedback cover that.