Phone check-in that is not live GPS tracking

Field people often need a punch, not a second hidden tracker. VisibleHours mobile check-in is a phone-sized web page. Operations turns the policy on. The employee opens /checkin, pastes an invite, and punches in or out. A location is stored only if they share coordinates — or if you require GPS for that punch.

That is not live GPS. The Windows tray still does not log location. Native store apps are a follow-up. This slice is the web punch.

Turn the policy on (off is the default)

Read /features/mobile first, then the signed-in mobile tutorial.

1. Send the employee notice and fill in the mobile section.
2. Turn mobile check-in on in Mobile / GPS.
3. Optionally require GPS and set a site name, coordinates, and radius.
4. Employees open /checkin, paste an invite code, and punch in or out.
5. Managers see who is punched in and the last inside / outside flag.

The mobile tip on the manager screen is a VisibleHours reading of your settings, not a live language model. VisibleHours does not email employees from that screen.

What a geofence does — and does not do

A named geofence marks a punch inside or outside a radius. It does not follow someone around town. It does not run in the background on a personal phone. If GPS is optional and the person declines, you still get the punch without a point.

Company Windows PCs keep using the tray agent for apps and idle. Mobile check-in does not replace that install. People who only need a field punch never need the exe.

What this is not

• Not on by default. A new org has mobile check-in off and no punches.
• Not live tracking. A location is stored only on a punch.
• Not a store app. Native mobile is a follow-up.
• Not a Windows GPS logger. The tray still does not collect location.
• Not outreach. VisibleHours does not email employees from this screen.