How to use this template
Copy the ten clauses below into your own document and replace everything in [square brackets]. Each clause has a short note on what to check before you keep it. Edit what your practice does not match, because a policy that describes tracking you do not do is worse than none.
For why this shape holds up, read is employee GPS tracking legal in India and the DPDP Act and employee data article. This page is the wording itself.
The policy, clause by clause
Field staff location policy for [Company name]
1Purpose
[Company name] records the location of field employees so that it can verify attendance at customer and work sites, confirm customer visits, calculate distance travelled for approved travel claims, and keep employees safe while they are out on duty. It does not use location data for any other purpose.
Check: Name the purposes you actually use. Delete any you do not.
2Who this covers
This policy applies to employees assigned the work type [Field] by HR. Employees assigned [Office] or [Remote] use location only to check a punch against the work location HR has set, and are not followed on a live map.
Check: Roles, not names. A short list of roles is easier to defend than a blanket rule.
3When location is recorded
Location is recorded from the moment an employee checks in until they check out, or until the end of the working hours set by HR for their shift, whichever is earlier. Nothing is recorded outside that window. Employees can see on the app when recording is active.
Check: State both the start and the stop. The stop is the sentence employees look for.
4What is collected
Time and position at check-in and check-out, route points and distance during duty, the position from which a customer visit was marked, and the photo and note an employee adds to a visit. [Add: selfie at punch, device identifier, odometer reading, if you use them.]
Check: List only what the system collects. If you add a data type later, update the policy first.
5Who can see it
The employee's reporting manager and [HR role] can see live location and history for the employees who report to them. No one else in the company has access. Screenshots of maps and trails must not be shared outside this group.
Check: Match this to your real access settings. Check them before you publish.
6How long it is kept
Route and location trails are kept for [number] days. Attendance records, approved travel claims and the data they rely on are kept for [period] to meet payroll and audit needs. After that the data is deleted or made anonymous.
Check: Fill in numbers you can keep to. A shorter period you honour beats a long one you ignore.
7How it is protected
Location data is stored in [system name] with role based access and a record of who opened it. Employees must not share their login. [Company name] requires its software providers to protect the data in the same way.
Check: Do not promise controls you have not checked. Ask your vendor first.
8Use of the data in decisions
Before location data is used to question an employee's attendance, visit or travel claim, the manager will show the employee the record and give them a chance to explain, for example a phone with no signal or a detour agreed with a customer.
Check: This clause prevents most disputes. It also supports accuracy duties.
9Questions and complaints
Questions about this policy and requests about your data go to [name, role, email]. Complaints go to the same person, who will reply within [number] working days.
Check: Name a person, not a mailbox nobody reads.
10Acknowledgement
I have read this policy. I understand what is recorded, when recording starts and stops, and who can see it. Name: ____________ Employee ID: ________ Signature: ____________ Date: __________
Check: Keep signed copies with the employee file.
Rules for managers who can see the map
Most complaints about tracking are about how a manager used it, not about the tracking. Give each manager this list when you give them access.
- Open an employee's location only for a work reason you could explain to them.
- Do not look at a map before or after duty hours. If you can, tell HR, because it is a setup fault.
- Ask before you conclude. A gap in the trail is usually signal or battery, not absence.
- Never share a screenshot of a live map in a group chat, to a client or on social media.
- Do not use the trail to comment on an employee's lunch break, route choice or personal stops in front of others.
- Raise a concern with HR first if you think the data shows misconduct.
Answers to what employees ask
Use these in the briefing when the policy is introduced. Change any answer that is not true for your setup.
Can you see where I am on weekends?
No. Recording starts at check-in and stops at check-out or the end of working hours.
Can you see my personal phone?
No. The app records the data listed in the policy while you are on duty. It is not a way to see your messages, photos or other apps.
Who can see my location?
Your reporting manager and [HR role]. Not other colleagues.
What if my phone has no signal?
The trail will show a gap. A gap is not treated as proof of anything. You will be asked, not assumed against.
How long do you keep it?
As stated in the policy: [number] days for trails and [period] for attendance and claims.
Who do I ask if I think something is wrong?
[Name, role, email].
What to leave out
- Any wording that lets the company track employees at all times or without notice.
- A promise of anonymity or deletion you cannot keep.
- Uses you do not have, such as productivity scoring, if you do not score productivity.
- A clause saying the employee consents to everything. A clear notice and a named contact do more than a blanket consent line.
Then set up the system to match. See how GPS tracking for employees works in Zeba, and tracking field employees live during working hours. For roles that do not need a trail, geofencing attendance is the lighter option.
FAQ
Is this policy legal advice?
No. It is a drafting aid for HR. Have your counsel read it against your contracts, standing orders and any client site rules before you issue it.
Do I need employees to sign it?
A signed acknowledgement is good practice because it shows the employee saw the policy before tracking began. Whether it is required for your case is a question for your counsel. See the DPDP article for the duties around notice and data.
How long should a tracking policy be?
One to two pages. If it needs more, the practice is probably too broad.
Should the policy name the software?
Name the type of data and the system that holds it, so that a change of tool does not need a rewrite. Update the policy when the data collected changes.
Can I use one policy for office staff and field staff?
Use one document with two groups, as clause 2 does. Office staff checked against a work location and field staff followed during duty are different practices and should be described separately.
Next: see how site visit management records each visit with a photo and position, or read what the DPDP Act means for attendance data.
