iPhone Precise Location for Time Tracking: Setup Guide
Turn on Precise Location on iPhone for GPS clock-ins, pick the right permission, and fix common accuracy problems. Includes Android steps and a manager checklist.
Turn on Precise Location on iPhone for GPS clock-ins, pick the right permission, and fix common accuracy problems. Includes Android steps and a manager checklist.

For GPS clock-ins to work on an iPhone, Precise Location must be on for your time-tracking app. Open Settings > Privacy & Security > Location Services, tap the app, and switch Precise Location on. With it off, the app sees only an approximate area, and a clock-in tied to a job site can miss the site entirely. This guide covers the steps, the permission choices, what else affects accuracy, and an Android equivalent for mixed-device teams.
Since iOS 14, some apps can ask for your specific location, and you can choose to share only an approximate one. Approximate location tells the app roughly which area you are in. Precise location tells it where you are standing.
For time tracking, that difference decides whether a clock-in can be checked against a place. A geofence is a virtual boundary drawn around a job site, and the app asks one question: was this punch inside the boundary? A rough area reading can land outside the boundary even when the employee is on site. A precise reading gives the check something reliable to work with.
The phone does not rely on a single signal. Location Services uses cellular, Wi-Fi, GPS and Bluetooth information to work out where you are. On an open job site, GPS carries most of the load. In dense areas, the phone leans on the other signals.
Each employee does this once per phone. It takes under a minute.
These are the same steps Apple lists for turning Location Services on or off and adjusting Precise Location per app.
The first time an app wants your location, iOS asks for permission. Apps cannot use your location until they have asked and you have agreed. If a new hire tapped “Don’t Allow” by accident, they can fix it later in the same Settings screen.
Have the employee open the app on site and look at the location shown on the map. If the pin sits on the site, you are set. If it sits in the next street, wait a minute and look again. Apple notes that finding all visible satellites can take several minutes, with accuracy improving over time. A phone just taken out of a bag or a truck cab may need that moment to settle.
iOS gives four options for each app. The options are Never, Ask Next Time Or When I Share, While Using the App, and Always. Here is how they play out for time tracking.
| Permission | When the app can read location | Fit for clock-ins |
|---|---|---|
| Never | Not at all | Location-verified clock-ins cannot work |
| Ask Next Time Or When I Share | After the user approves a prompt | Adds a prompt each time, so it slows the punch |
| While Using the App | When the app or one of its features is visible on screen | Matches a one-tap punch made with the app open |
| Always | Even when the app is in the background | Needed only for features that run when the app is closed |
Apple describes While Using the App as access only while the app or one of its features is visible on screen, and Always as access even in the background. A tap-to-clock-in workflow happens with the app open, so the on-screen permission covers the punch itself.
Pick the narrowest permission that supports the way your team clocks in. Employees are usually more comfortable saying yes when the setting is clearly tied to the moment they punch in or out.
Precise Location is the first switch, not the only one. A phone can have it on and still report a poor position.
GPS.gov lists satellite signal blockage from buildings, bridges, trees, and indoor or underground use as common causes of weaker accuracy. It also names signals bouncing off walls and buildings, known as multipath. Apple says the same in plain terms: walls, vehicle roofs, tall buildings and mountains can block the line of sight to satellites, so the phone falls back on Wi-Fi or cellular networks.
For a field team, that translates into practical advice. Clock in outside the entrance, not in a basement or a parked cab. Dense downtown streets, covered parking and the inside of large structures are the places where readings drift. Roofing and exterior crews often have the best conditions, since they work under open sky. Location blocked by structures is also a topic roofing marketers write about when explaining how blocked satellite signals affect location.
A 2006 field trial in a mid-sized German city measured average GPS error from about 2 meters on an open square to about 15 meters in wide streets lined with four-story buildings. Phones have changed since then, but the pattern holds: the more buildings around you, the more error to expect.

A geofence drawn tightly around a building footprint leaves no room for normal drift. Set the radius to cover the entrance, the parking area and the work zone where crews actually stand. Our blog covers this in more depth in multiple job site tracking for payroll managers.
Battery settings can quietly break location-based features. Australia’s Fair Work Ombudsman, in the troubleshooting notes for its Record My Hours app, says Low Power Mode, battery optimization, swiping the app closed, or pausing app activity can disrupt automatic shift recording. The same page notes that iPhone users may see problems after an app has been in the background for a long time. That app records shifts automatically, which is different from a tap-to-clock-in flow, but the lesson carries over: if an employee’s location looks wrong, check power settings first.
Many field crews run iPhones and Android phones side by side. The concept is the same, with different menu names.
On Android, an app can request approximate location or precise location. Google’s help page lists the permission choices as Allow all the time, Allow only while using the app, Ask every time or allow when you share, and Don’t allow. The first two map to Always and While Using the App on iPhone.
The gap between the two accuracy levels can be large. Android 12 and higher lets users share only approximate location, which is typically within about 1.6 kilometers (1 mile), while precise location is typically within about 50 meters (160 feet) and sometimes a few meters. One mile is far too wide for a job site check.
A short Android checklist for employees:
Menu names differ slightly between phone makers, so employees may need to look for “App permissions” or “Permission manager” instead.
Background behavior also differs. Android 8.0 introduced limits that throttle background location to a few times per hour and slow geofence responsiveness to roughly two minutes. If your punches happen with the app open, those limits matter less.
Our view: verify the punch, not the person’s whole day
We built Clock-Me for field teams, and our approach starts from one idea: a time record is strongest when it is tied to a clear moment. A verified GPS clock-in, an identity check and a geofence answer the question a manager actually needs answered: was this person at the right place when they said they were?
That is why our design avoids paper timesheets and continuous background tracking. Precise Location is what makes the verified punch work on an iPhone, so we treat it as part of setup, not an afterthought. We add random location check-ins and device-based fraud detection on top, so buddy punching has fewer places to hide.
For California employers, accurate records matter for compliance, and our platform includes California labor law compliance features and timecard attestation. Employees see a simple one-tap flow. Managers see live dashboards. Both sides know what is being recorded and why.
Clock-me
Location is one of the heavier things a phone does. Android’s developer documentation says battery drain from location is driven by accuracy, frequency and latency, and recommends reserving high-accuracy, frequent updates for foreground use. Higher precision, more frequent readings and faster responses all use more power.
That is a good argument for event-based design. A clock-in app that reads location at the moment of a punch uses far less power than one that follows the phone all day. Our blog explains the idea in using events, not streams, for employee GPS privacy.
Tips for crews:
Employees are more willing to turn on Precise Location when they know what it is used for. Tell them in writing: when location is read, what is stored, who sees it, and how long it is kept. Our GPS tracking policy template helps HR finish that document in one work session.
Rules differ by place, and several regulators take a proportionate view. For example, Germany’s Rhineland-Palatinate data protection authority says that for time recording, GPS tracking must not take precedence over direct reporting such as time clocks or timesheets, and permanent tracking is generally impermissible. The UK’s ICO guidance on monitoring workers, summarized by a law firm, asks employers to be clear about purpose, identify a lawful basis, run a data protection impact assessment for high-risk processing, and tell workers what is monitored. Those are non-US rules, but they show what good practice looks like: a clear purpose, a narrow scope and open communication.
For a deeper look at permissions, transparency and privacy when apps use location for work hours, see this piece on caregiver GPS tracking legality. If employees use their own phones, our guide to running BYOD time tracking legally and accurately covers what to put in place.
For your own situation, ask your employment attorney or state labor agency about notice and consent requirements where your employees work.

When a clock-in shows the wrong place, work through these in order.
If the problem repeats for one employee on one phone, reinstalling the app and approving the permissions again usually resets the setup.
If your crews already have the settings right and you want punches that hold up, Clock-Me brings GPS-verified clock-ins, identity verification, geofencing and random location check-ins into one app. Managers get live dashboards, timesheet approval and payroll export.
Plans are based on the number of active employees. The Free plan costs $0 per month. Paid plans are Starter at $31.99 per month, Growth at $54.99 per month, Business at $99.99 per month, Pro at $224.99 per month and Corporate at $439.99 per month. Enterprise has no published price. Start with Clock-Me and set up your first job site today.

Want more background first? Browse our GPS time tracking articles or read about GPS time tracking benefits for field managers.
Go to Settings > Privacy & Security > Location Services and tap the app. Switch Precise Location on, then choose While Using the App if the app only needs your location when you clock in. Apple describes these steps on its Location Services support page.
Not for a tap-to-clock-in flow. While Using the App gives access when the app is visible on screen, which covers a punch made with the app open. Always allows access in the background, so it matters only for features that run when the app is closed.
Signal conditions are the usual cause. Buildings, covered areas and indoor spaces can block or reflect satellite signals, and the phone then leans on Wi-Fi or cellular data. Step outside, wait a minute and try again, and check that Low Power Mode is off.
Yes. Android calls it precise location versus approximate location, found under the app’s permissions. Choose the option to allow location only while using the app and keep precise location on.
Rules vary by state and country, and they often turn on notice, purpose and proportionality. Put the policy in writing, explain when location is read, and check requirements with an employment attorney in your state.