Ask at the right time
Request location in the punch flow, not as an unexplained requirement at app launch.
EasyClockGPS clock-in NZ
EasyClock can capture an employee's GPS location during mobile clock-in and clock-out when the company enables Sites & GPS. Location, site matching and device access remain understandable, separate controls.
A clearer field workflow
For businesses with employees working across sites, location context can help a manager understand the punch without relying on a note or later recollection. EasyClock records the available latitude, longitude and accuracy alongside the event when the configured flow requires GPS.
The iPhone app checks the current authorisation state and waits for iOS to report changes, avoiding a synchronous location check that can make the interface unresponsive.
The company controls whether Sites & GPS is active. Punch policies determine how location information participates in the clock-in or clock-out flow.
If site or GPS rules were disabled at clock-in and later enabled, EasyClock can still allow the employee to close the existing work session instead of trapping them in an open shift.
Device registration is separate from GPS. Capturing a location should not produce a message that the iPhone must be registered unless a distinct approved-device policy requires it.
Good location UX
Request location in the punch flow, not as an unexplained requirement at app launch.
Distinguish denied location, unavailable GPS, site mismatch and account access.
Do not block a legitimate clock-out solely because configuration changed after clock-in.
Part of mobile attendance
Read about the mobile time clock, the underlying employee time clock, and the full time and attendance software NZ workflow.
Location with context