Strategy & Leadership

GPS, attendance and privacy: build trust in your field program

Use check-ins and location information proportionately, transparently and for legitimate operational purposes.

ForField directorHR leaderPrivacy officer3 min readReviewed October 26, 2026

We don't provide legal advice. This guide offers general operational guidance only. Rules on privacy, workplace monitoring, employment and safety differ by country and state, so carry out your own independent assessment and get qualified advice for your business before acting on it.

Location and attendance information can help verify coverage, support safety and understand service delivery. It can also undermine trust if workers do not know what is being collected or managers use the data for purposes that were never explained.

Rules on monitoring workers differ by country and state. Before you switch on location features or geofencing rules, carry out your own independent assessment of the purpose, the legal basis and whether the data you collect is proportionate, and get qualified advice for each place you operate.

Start with a purpose statement

Document the legitimate reason for each data element: e.g., confirming that a scheduled visit occurred at the correct outlet, supporting a time-sensitive store visit or meeting a valid safety requirement. Decide whether visit-level check-in location is enough. Continuous location tracking is more intrusive and should not be switched on merely because it is available.

Give workers understandable answers

  • What information is captured, and when?
  • Is location tracking active only during working activities or at other times?
  • Who can see raw records and aggregated reports?
  • How long is the information retained?
  • How can someone challenge an inaccurate reading?
  • What happens when the GPS signal is poor or a visit is legitimately completed away from the nominated entrance?

Explain the policy before use. Include field representatives in testing, especially where work occurs in underground car parks, remote locations or stores with unreliable GPS.

Design fair exceptions

Location accuracy varies. Do not treat an out-of-bound check-in as automatic misconduct. Support legitimate explanations, review the signal quality and ensure a human can assess disputed events. Never use a single uncertain GPS point as the sole basis for a consequential employment decision.

Include safety and retailer rules

Work should not require unsafe phone interaction while driving or disregard store access restrictions. Plan travel breaks, lone-worker procedures and escalation mechanisms as appropriate. Field productivity targets should not encourage risky driving or unauthorized stock handling.

Where FieldKo fits

FieldKo records check-in and check-out on each visit, with location capture if you turn it on. Set it up around a written purpose, limit who can see the data, and follow the law that applies to your employees and contractors.

Next: Coach your field team

See how FieldKo supports this →

Reviewed October 26, 2026. Examples, scores and thresholds are illustrative, not benchmarks. We don't provide legal advice; for privacy, employment, safety or other legal questions, carry out your own independent assessment. See the research and sources library for independent references.

Keep going

Related guides and templates.

Field Team ManagementCoaching field teams for better retail executionMove beyond visit counts to practical coaching on observation quality, commercial judgment and issue resolution.3 min readStrategy & LeadershipThe retail execution maturity modelAssess whether your organization merely records visits or consistently turns store observations into improvements.3 min readStrategy & LeadershipA 90-day plan for improving retail executionPilot a stronger retail execution operating model before trying to transform every store and team at once.3 min read
Browse all best practices →
Examples

See it in practice.

All examples →
Check-in, 40 meters from the storeEvery agency visit records the check-in time and distance from the store, so the brand knows the visit happened where and when it should.Read the example →Check-in flagged, 1.2 km from the storeA check-in made far from the store is flagged with its distance, so managers review exceptions instead of every visit.Read the example →Encrypted on the deviceThe security answer in one page: field data on the phone is held in an encrypted database and governed by Salesforce permission sets.Read the example →

See how FieldKo supports your operating model.

We help teams plan visits, guide store work and report on the results in Salesforce. Book a walkthrough built around how your team works.

Book a Demo