What Should Singapore Employers Include in a Location-Tracking Policy?
What Should Singapore Employers Include in a Location-Tracking Policy?
Introduction
Location-tracking technology is increasingly used by Singapore businesses to coordinate field employees, manage mobile workforces, verify customer visits, improve dispatching and monitor operational activities. Companies in maintenance, facilities management, cleaning, construction, security, logistics and sales may use GPS-enabled mobile applications or tracking devices to understand where employees are during work assignments.
Although these tools can improve workforce coordination, they also collect information about employees' movements. Without clear rules, workers may be uncertain about when tracking is active, who can access their location history, how the information is used and whether monitoring continues outside working hours.
A written location-tracking policy helps employers establish transparent expectations and responsible monitoring practices. It should explain why tracking is necessary, which employees and devices are covered, when location information is collected, how the data is protected and how employees can raise concerns.
In Singapore, employers should consider the Personal Data Protection Act 2012 (PDPA) when collecting, using or disclosing employee location information. The PDPA includes an employment-related exception that may apply to personal data reasonably collected, used or disclosed for managing an employment relationship. However, employers must still inform employees of the relevant purposes, and other applicable data protection obligations continue to apply.
A well-designed policy should therefore balance legitimate business requirements with employee privacy, transparency and appropriate data security.

1. Clearly Explain the Purpose of Location Tracking
The policy should begin by explaining why the organisation uses location-tracking technology. Employees should understand the business reasons for collecting location information and how the information supports their work.
Common business purposes include:
- Coordinating field employee assignments.
- Improving dispatching and workforce scheduling.
- Confirming arrival at customer or project locations.
- Monitoring the progress of field operations.
- Supporting employee safety during authorised work activities.
- Managing service appointments and customer visits.
- Verifying attendance at designated work locations.
- Reviewing travel time and operational efficiency.
- Investigating reported incidents or security concerns.
For example, a Singapore facilities management company may track technicians during working hours to identify available employees and assign urgent maintenance requests. A cleaning company may use location-based check-ins to record whether assigned employees have arrived at customer premises.
Employers should avoid vague statements such as "the company may track employees for business purposes." The policy should describe the actual purposes clearly enough for employees to understand how their location information will be used.
The organisation should also review whether each proposed tracking activity is reasonably necessary for its stated purpose.
2. Identify Which Employees Are Covered
The policy should specify which categories of employees are subject to location tracking.
Depending on the organisation's operating model, these may include:
- Field technicians.
- Sales representatives.
- Delivery and service personnel.
- Cleaning employees.
- Security officers.
- Construction site employees.
- Maintenance teams.
- Mobile supervisors.
- Employees travelling between customer locations.
Not every employee necessarily needs to be tracked. Office-based employees who work at a fixed location may have different monitoring requirements from mobile employees who regularly travel between customer sites.
The policy should explain whether tracking applies to permanent employees, temporary employees, part-time employees, contract staff or other authorised personnel.
Where third-party contractors are involved, employers should clarify which organisation is responsible for communicating tracking arrangements and managing the relevant personal data.
3. Define When Location Tracking Starts and Stops
One of the most important sections of a location-tracking policy is the tracking schedule.
Employees should know when their location information is collected and when monitoring stops.
The policy should specify:
- Whether tracking operates only during scheduled working hours.
- Whether tracking begins when an employee starts a shift.
- Whether tracking stops at the end of a shift.
- Whether tracking applies during authorised work travel.
- Whether tracking pauses during breaks.
- How tracking works during overtime.
- What happens when an employee works an overnight shift.
- Whether tracking is disabled during leave or other non-working periods.
For example, a field service employee may be tracked from the start of an authorised shift until the end of the scheduled working period. If the employee is approved for overtime, the policy should explain whether tracking continues during that additional work period.
Employers should avoid collecting continuous location information outside the stated operational requirements. The Ministry of Manpower (MOM) has highlighted concerns about intrusive employee monitoring outside working hours, including location tracking. Its 2025 parliamentary reply states that employees who believe company policies breach their privacy can raise the matter through company grievance channels, their union where applicable, or TAFEP.
The policy should make the tracking schedule understandable and consistent with actual system settings.
4. Specify Which Devices and Applications Are Used
Employees should know how the organisation collects location information.
Location-tracking arrangements may involve:
- Company-issued smartphones.
- Employee-owned smartphones under a bring-your-own-device (BYOD) arrangement.
- GPS tracking applications.
- Vehicle tracking devices.
- Wearable tracking devices.
- Mobile attendance applications.
- Field service management software.
- Dedicated location-tracking hardware.
The policy should identify the approved application or device category and explain whether employees need to enable location permissions.
For BYOD arrangements, employers should explain whether the application collects location information only while employees are working and how personal device information is separated from business information.
The policy should also clarify whether employees are expected to use mobile data, keep the application running in the background or maintain sufficient battery power during assigned work.
Employers should not assume that a company-owned device automatically removes privacy concerns. Location information associated with an identifiable employee can still constitute personal data.
5. Explain What Location Information Is Collected
A location-tracking policy should describe the categories of information the organisation collects.
Depending on the system, this may include:
- GPS coordinates.
- Recorded location timestamps.
- Current or last reported location.
- Route history.
- Travel duration.
- Geofence entry and exit events.
- Customer site check-ins.
- Jobsite arrival and departure records.
- Device identification information.
- Location-related exception notifications.
Employers should explain whether the system records continuous or periodic location updates, or only event-based check-ins.
For example, a sales organisation may use event-based customer visit check-ins rather than continuously monitoring employee movements. A field maintenance company may require more frequent location updates during authorised dispatch periods.
The organisation should collect only the information reasonably needed for its stated purposes. If customer visit verification can be achieved through a check-in event, collecting a detailed movement history throughout the entire day may not be necessary.
6. Explain Whether Tracking Is Continuous or Event-Based
Different tracking methods have different privacy implications. Employees should understand which method their employer uses.
| Tracking method | How it works | Typical business use |
|---|---|---|
| Continuous or periodic GPS tracking | Records location at configured intervals during authorised periods | Field workforce coordination |
| Event-based GPS check-in | Records location when an employee checks in or out | Customer visit verification |
| Geofencing | Records entry into or departure from a defined area | Site arrival monitoring |
| QR code check-in | Records a visit when an employee scans a site-specific code | Indoor site attendance |
| NFC check-in | Records a visit when an employee taps a compatible device against a tag | Patrol and checkpoint verification |
| Vehicle tracking | Records the location of a company vehicle | Fleet and transport operations |
For example, a company may use periodic GPS tracking for mobile technicians who receive changing assignments throughout the day, while using QR check-ins for employees who visit fixed customer locations.
The policy should not describe the system as continuously tracking employees if it only records occasional check-ins. Accurate descriptions help employees understand what the technology actually does.
7. Identify Who Can Access Employee Location Information
Employers should specify which roles are authorised to view employee location data.
Possible authorised users include:
- Operations managers.
- Field supervisors.
- Dispatch coordinators.
- HR personnel, where necessary.
- Security or safety managers.
- IT administrators responsible for system maintenance.
- Designated compliance or investigation personnel.
Access should be based on job responsibilities rather than granted to every manager by default.
For example, a dispatcher may need to view the current or last reported location of available technicians to allocate urgent jobs. An HR manager may need access to attendance-related records but may not require unrestricted access to detailed route histories.
The policy should also explain:
- Whether managers can view real-time location information.
- Whether employees can access their own location records.
- Whether location histories can be downloaded.
- Whether access is logged.
- Who approves access for investigations.
- How access is removed when an employee changes roles or leaves the company.
Role-based access controls reduce the risk of unnecessary viewing, copying or disclosure of employee location information.
8. Explain How Location Data May Be Used for Performance Reviews
Employees should understand whether location information is used only for operational coordination or may also contribute to performance management.
Potential uses include:
- Reviewing travel time.
- Understanding appointment punctuality.
- Identifying missed site visits.
- Reviewing route efficiency.
- Investigating repeated deployment issues.
- Assessing whether scheduled work locations were visited.
The policy should distinguish between operational information and evidence of employee performance.
For example, GPS records may indicate that a technician's device reached a customer site at a particular time. They do not necessarily prove that the technician completed the repair, followed safety procedures or delivered satisfactory service.
Employers should consider other evidence, including job completion records, customer feedback, supervisor observations and service reports.
The policy should also explain whether location information may be used in disciplinary investigations. If so, it should describe the circumstances and require appropriate review rather than treating every location discrepancy as misconduct.
A device may report an inaccurate position, lose connectivity or stop updating in the background. Employees should have an opportunity to explain relevant circumstances before conclusions are reached.
9. Set Rules for Breaks, Personal Time and Off-Duty Periods
The policy should clearly address employee privacy during breaks and non-working periods.
It should explain whether location tracking:
- Stops during scheduled breaks.
- Pauses during approved personal time.
- Stops after employees complete their shifts.
- Continues during authorised work-related travel.
- Applies during approved overtime.
- Is disabled during annual leave and other non-working periods.
For employees using personal smartphones, the organisation should explain how the application handles personal time and whether employees can disable work-related tracking outside authorised periods.
Employers should avoid using work-related location data to routinely monitor employees' personal activities.
This is particularly important for employees who travel between customer sites, work flexible schedules or use their own devices.
10. Establish Data Retention and Deletion Rules
The policy should explain how long employee location information is stored and what happens when the retention period ends.
Retention requirements may differ depending on the type of record and the purpose for which it is collected.
For example:
- Recent location updates may be retained for operational coordination.
- Historical route records may be retained for a defined review period.
- Customer visit records may be retained according to service and contractual requirements.
- Incident-related location records may need to be preserved while an investigation is ongoing.
- Records required for legal or regulatory purposes may need to be retained for the applicable period.
Under section 25 of Singapore's PDPA, organisations should cease retaining personal data, or remove the means of associating it with individuals, when the purpose for retaining it is no longer served and retention is no longer necessary for legal or business purposes.
The PDPA does not prescribe one universal retention period for all employee GPS records. Employers should establish retention periods based on their actual operational, legal and business requirements.
The policy should also explain how data is securely deleted, anonymised or archived when it is no longer needed.
11. Describe How Location Information Is Protected
Employee location data should be protected against unauthorised access, disclosure, modification and loss.
The policy should identify the main security measures used by the organisation.
These may include:
- Secure user authentication.
- Role-based access permissions.
- Encryption during data transmission.
- Appropriate protection of stored information.
- Access and activity logs.
- Device security controls.
- Regular software updates.
- Secure backup procedures.
- Controlled data exports.
- Procedures for managing lost or stolen devices.
For example, if an employee loses a company-issued smartphone containing location history, the organisation should have a procedure to revoke access, secure the account and assess whether personal data has been exposed.
Employers should also review the security arrangements of software providers that process employee location data.
Under section 24 of the PDPA, organisations must make reasonable security arrangements to protect personal data in their possession or under their control.
12. Explain Whether Location Data Is Shared With Vendors or Other Organisations
Many employers use third-party software providers to collect, store and process employee location information.
The policy should explain whether information is shared with:
- GPS tracking software providers.
- Cloud hosting providers.
- Field workforce management vendors.
- IT support providers.
- Approved subcontractors.
- Other authorised business partners.
Employers should identify the relevant categories of recipients and explain why information may be disclosed to them.
Vendor agreements should address data processing responsibilities, security arrangements, permitted uses, confidentiality, incident reporting, retention and deletion.
If employee location information is transferred outside Singapore, employers must consider the PDPA's Transfer Limitation Obligation. The organisation must ensure that the overseas recipient provides a standard of protection comparable to the protection required under the PDPA, subject to the applicable requirements and exceptions.
The policy should not simply state that data is stored securely without explaining the organisation's approach to third-party access and overseas transfers.
13. Establish Rules for Location Data Accuracy and Technical Problems
GPS information is not always perfectly accurate. Location tracking can be affected by mobile device settings, satellite reception, building structures, network conditions and application restrictions.
The policy should explain how the organisation handles technical problems and inaccurate location records.
It should cover situations such as:
- GPS signal loss.
- Weak mobile connectivity.
- Incorrect location readings.
- Application crashes.
- Device battery failure.
- Disabled location permissions.
- Delayed synchronisation.
- Missing check-in records.
For example, a technician working in an underground car park may not receive an accurate GPS position. The company should provide an alternative procedure, such as QR or NFC checkpoint verification, manual supervisor confirmation or another approved method.
The policy should also explain how employees can report technical problems and request corrections to inaccurate records.
A missing location update should not automatically be treated as evidence that an employee was absent or failed to perform assigned work.
14. Provide a Process for Employee Questions and Complaints
Employees should have a clear way to ask questions or raise concerns about location tracking.
The policy should identify:
- The HR contact responsible for employee queries.
- The data protection contact or Data Protection Officer (DPO).
- The process for reporting inaccurate location records.
- The procedure for raising concerns about excessive monitoring.
- The process for requesting access to relevant personal data, where applicable.
- The channel for reporting suspected unauthorised access.
- The internal grievance-handling procedure.
Employers should also explain how complaints will be reviewed and how employees will receive a response.
Under the PDPA, organisations must develop policies and practices to meet their data protection obligations and establish a process for receiving and responding to complaints.
MOM's 2025 parliamentary reply on intrusive employee monitoring also identifies company grievance channels, unions where applicable and TAFEP as avenues employees may approach when concerned about workplace monitoring practices.
A transparent complaint process helps organisations identify problems before they develop into larger workplace disputes.
15. Explain How Location Tracking Works With Attendance and Payroll
Some employers integrate GPS tracking with attendance and payroll systems. The policy should explain how location information may be used in these processes.
Examples include:
- Recording arrival at a designated worksite.
- Supporting mobile attendance check-ins.
- Verifying customer site visits.
- Providing context for travel-time records.
- Supporting approved overtime reviews.
- Identifying missing attendance events for investigation.
However, GPS tracking should not be treated as a replacement for all attendance and employment records.
For example, a location event may indicate that an employee's device reached a worksite, but it does not necessarily establish the employee's complete working hours, rest periods or overtime entitlement.
Where location records are used in payroll-related processes, employers should explain which events are transferred, who reviews them and how corrections are handled.
The organisation should maintain the employment and salary records required under applicable MOM requirements separately from any additional location history collected for operational purposes.
16. Define Rules for Company Vehicles and Personal Vehicles
Businesses that use vehicle tracking should distinguish between tracking a company vehicle and tracking an employee's personal movements.
A vehicle tracking system may record:
- Vehicle location.
- Route history.
- Travel duration.
- Vehicle usage during working hours.
- Departure and arrival events.
- Vehicle-related alerts.
If employees use company vehicles, the policy should explain whether the vehicle is tracked outside working hours and whether employees may use it for personal purposes.
For personal vehicles used for business travel, employers should explain whether tracking applies only to authorised business journeys.
The organisation should also clarify whether location data is associated with the vehicle, the assigned driver or both.
This distinction is important because vehicle location information may reveal employee movements even when the system is primarily designed for fleet management.
17. Explain How the Organisation Handles Security Incidents and Data Breaches
The policy should describe how employee location data is handled when there is a suspected security incident or personal data breach.
Examples include:
- Unauthorised access to location history.
- Accidental disclosure of employee movement records.
- A lost device containing stored location data.
- Compromised tracking application accounts.
- Unauthorised exports of GPS reports.
- Vendor security incidents affecting employee information.
The organisation should establish an internal reporting and investigation process.
It should identify who is responsible for assessing the incident, securing affected systems, preserving relevant evidence and determining whether regulatory notification is required.
Under Singapore's PDPA, organisations must assess whether a personal data breach is notifiable. Where notification is required, the organisation must notify the PDPC as soon as practicable and no later than three calendar days after determining that the breach is notifiable. Affected individuals must also be notified where required.
Employees should know how to report a suspected data breach or unauthorised disclosure involving their location information.
18. Explain How the Policy Applies to Remote and Field Employees
Employees who work away from a fixed office may have different tracking requirements from office-based employees.
The policy should explain how location tracking applies to different working arrangements.
For example:
Field service employees: Tracking may support technician dispatch, customer arrival verification and job coordination during authorised working periods.
Sales representatives: Event-based check-ins may be sufficient to record customer visits without continuous movement monitoring.
Cleaning employees: QR or NFC checkpoints may help confirm arrival at designated customer sites.
Security officers: Patrol applications may record checkpoint visits and support deployment monitoring.
Delivery employees: Vehicle or mobile tracking may support delivery coordination and route planning.
Remote employees: Location tracking should be used only where there is a clearly explained operational requirement. Employers should not assume that working remotely automatically justifies continuous GPS monitoring.
The policy should be specific enough to explain why different employee groups may be subject to different tracking arrangements.
19. Include an Employee Acknowledgement and Policy Review Process
Employees should receive the location-tracking policy before the organisation begins collecting location information for the stated purposes.
Employers can communicate the policy through:
- Employment contracts or relevant notices.
- Employee handbooks.
- HR policy portals.
- Staff intranets.
- Mobile application onboarding.
- Training sessions.
- Written policy acknowledgements.
An acknowledgement can confirm that an employee has received and been informed of the policy. However, acknowledgement should not automatically be described as consent where the organisation relies on an applicable PDPA exception or another lawful basis.
The organisation should also review the policy periodically and whenever there are significant changes to:
- Tracking technology.
- Data collection practices.
- Employee categories covered.
- Business purposes.
- Software vendors.
- Data access arrangements.
- Retention periods.
- Relevant legal or regulatory requirements.
If a new purpose is introduced, employees should be informed of that purpose before the organisation uses or discloses their personal data for it, as applicable under the PDPA.
20. Use a Practical Location-Tracking Policy Checklist
Before publishing a location-tracking policy, Singapore employers should confirm that the document covers the essential operational and privacy requirements.
| Policy requirement | What employers should include |
|---|---|
| Purpose | Clear business reasons for tracking |
| Employee coverage | Roles and categories of employees included |
| Tracking schedule | Start and stop times, breaks and overtime arrangements |
| Devices and applications | Approved smartphones, GPS apps and tracking devices |
| Data collected | Coordinates, timestamps, routes and check-in events |
| Tracking method | Continuous, periodic, geofencing or event-based |
| Access permissions | Roles authorised to view location information |
| Data usage | Dispatch, attendance, safety and performance-related uses |
| Off-duty privacy | Rules for personal time and non-working periods |
| Retention | Storage duration, deletion and archiving procedures |
| Security | Authentication, encryption, access controls and audit logs |
| Third parties | Vendor access, processing and overseas transfers |
| Accuracy | Handling of GPS errors and missing updates |
| Employee rights and queries | Contact details, correction requests and complaints |
| Payroll integration | How location events relate to attendance and payroll |
| Incident management | Reporting and handling of data breaches |
| Policy acknowledgement | Employee communication and review arrangements |
Employers should also test whether the written policy matches the actual configuration of their tracking software. A policy that promises tracking stops after working hours is not effective if the application continues collecting location data outside those hours.
Conclusion
A location-tracking policy is an important document for Singapore employers that use GPS-enabled applications, vehicle tracking systems or mobile workforce management software. It establishes clear expectations about why employees are tracked, when location information is collected, who can access it and how the information is protected.
The policy should cover business purposes, employee categories, tracking schedules, devices, collected data, access permissions, performance-related use, off-duty privacy, retention, security, third-party vendors and employee complaint procedures.
Employers should also ensure that the policy reflects the organisation's actual technology settings and complies with applicable PDPA obligations. Employment-related exceptions may apply to certain workplace data practices, but notification and other relevant data protection responsibilities remain important.
A clear, practical and regularly reviewed policy helps organisations use location-tracking technology responsibly while supporting workforce coordination, operational efficiency and employee trust.
Define purpose, working-time limits, access and retention before rolling out location tools. Use InnBuilt's available settings to support a clear Singapore employee policy.