Talking to Employees About GPS Tracking in Company Vehicles

GPS fleet tracking can help businesses improve dispatching, protect vehicles, verify completed work, respond to emergencies, and better understand how their fleets operate. However, drivers and field crews may initially see tracking technology as workplace surveillance rather than an operational tool.

That reaction should not be dismissed. Location records can reveal where a vehicle travelled, when it stopped, how long it remained at a location, and when it was used. In Canada, the Office of the Privacy Commissioner has confirmed that GPS information associated with an identifiable employee can constitute personal information.

The most effective way to introduce fleet tracking is therefore not to avoid privacy questions. It is to answer them before the system is activated. A clearly defined policy, a straightforward crew meeting, and sensible limits on data use can turn a potentially contentious rollout into a practical safety and productivity initiative.

Begin the Conversation Before Tracking Begins

Employees should not discover that a vehicle is being tracked by noticing a device under the dashboard or hearing about it from another driver. Inform the crew before installation and give employees enough time to understand the system, review the policy, and ask questions.

Canada’s Office of the Privacy Commissioner recommends that employers create clear monitoring policies and communicate them to affected employees before implementing the practice. The policy should explain what information will be collected, why it is needed, how it will be used, what consequences could result, and how long the information will be retained.

An early conversation also gives management an opportunity to learn what employees are worried about. Those concerns may reveal issues that have not yet been addressed, such as:

• Whether tracking continues when a take-home vehicle is used outside working hours
• Who can view a driver’s current location
• Whether supervisors can review historical trips without a specific reason
• How GPS information could be used in a disciplinary investigation
• How an employee can challenge an incorrect record
• Whether information will be shared with customers, insurers, or other third parties

Management should have definite answers before the system goes live.

Explain the Business Reasons in Plain Language

Avoid introducing GPS tracking with vague statements such as “We need greater accountability.” Employees may interpret that as an accusation that management does not trust them.

Instead, identify the operational problems the system is intended to solve. Depending on the business, legitimate purposes might include:

• Dispatching the nearest available vehicle
• Giving customers more accurate arrival estimates
• Locating a driver during an emergency
• Recovering a stolen vehicle or piece of equipment
• Confirming that a service visit or delivery occurred
• Identifying unauthorized or after-hours vehicle use
• Planning maintenance from recorded mileage or engine hours
• Reviewing routes, stops, idling, and fuel-use patterns
• Investigating collisions, complaints, or disputed events
• Reducing the number of manual check-in calls drivers receive

These are understandable goals tied to the operation of the fleet. The federal Privacy Commissioner has previously found that GPS may support appropriate purposes such as dispatch efficiency, employee and public safety, and asset protection, provided the business need is properly balanced against employee privacy.

Whenever possible, connect each type of data to a specific purpose. For example, current location may be needed for dispatching, while historical trip information may be reviewed only when investigating a customer complaint or collision. This is more reassuring than giving supervisors unrestricted access simply because the information is available.

Describe Exactly What the System Can See

“GPS tracking” is too broad to serve as a meaningful explanation. The information available depends on the installed hardware, connected sensors, and platform configuration, but it may include:

• Current and historical vehicle locations
• Routes and trip history
• Start and stop times
• Speed and mileage
• Ignition or movement status
• Stops and their approximate duration
• Entry into or exit from defined geofences
• Idling and other vehicle events
• Sensor or vehicle information supported by the installation

Wialon provides functions such as real-time vehicle tracking, reports, geofences, notifications, route tools, and driver-behaviour monitoring. A company does not need to activate or routinely use every available function. Configuration should reflect the purposes stated in the fleet’s policy.

Employees should also understand the technology’s limits. A GPS record shows what was reported about a vehicle, but it may not explain why an event occurred. A long stop could represent a lunch break, a delayed customer, road construction, an emergency, or a poor GPS signal. Location data provides evidence, but not always the complete context.

Be Clear About Working Hours and Personal Use

Off-hours tracking is one of the most sensitive parts of any fleet-tracking program. A driver using a take-home vehicle may reasonably be concerned that the company could see visits to a medical clinic, place of worship, family member’s home, or another private destination.

The policy should define:

• Whether personal use of company vehicles is permitted
• When a driver is considered on duty
• Whether the system continues reporting outside working hours
• Whether employees may use a privacy or personal-use mode
• When management may review off-hours information
• What employees should do if a vehicle must be used during an emergency
• How the policy applies to employees’ privately owned vehicles or phones

Collecting information simply because the technology permits it is difficult to justify. The Privacy Commissioner’s workplace guidance recommends that employee monitoring be specific, targeted, proportionate, and minimally intrusive. Where possible, fleets should avoid collecting or reviewing personal-use information that is unrelated to a legitimate business purpose.

Tracking an employee-owned vehicle or personal phone introduces additional privacy concerns and should not be treated as equivalent to installing equipment in a company vehicle. Before using location services on personally owned property, employers should obtain advice based on the laws, employment arrangements, and consent requirements in their jurisdiction.

Put the Rules in Writing

A verbal promise from a manager is not enough. Supervisors may change, memories fade, and employees need a reliable document they can consult later.

A fleet-tracking policy should identify:

1. The business purposes for introducing tracking
2. The vehicles, devices, and employees covered by the policy
3. The categories of information being collected
4. When collection begins and ends
5. Whether take-home or personal use is monitored
6. Which positions can access live and historical information
7. The circumstances in which information may be reviewed
8. Whether information may be used for coaching or discipline
9. The retention period for each relevant type of record
10. The parties to whom information may be disclosed
11. The safeguards used to protect the information
12. How an employee can request access or correction
13. How an employee can raise a privacy concern
14. The process for notifying employees of policy changes

Under PIPEDA’s fair-information principles, organizations subject to the legislation must identify their purposes, limit collection to what is necessary, restrict later use and disclosure, and retain personal information only as long as required for those purposes. The complete principles are set out in Schedule 1 of PIPEDA.

Privacy and employment requirements vary by location and industry. For example, Ontario employers with 25 or more employees on January 1 must maintain a written electronic-monitoring policy. The provincial guidance explains the information that an electronic-monitoring policy must contain. However, the Ontario requirement is primarily a transparency measure and does not, by itself, create a general right not to be monitored. Employers should review all applicable federal, provincial, state, collective-agreement, and employment requirements with qualified counsel.

Limit Who Can Access the Information

Drivers may be more comfortable with tracking when they know the entire office cannot casually view their movements.

Access should be based on job responsibilities. A dispatcher may need current vehicle locations, while a maintenance coordinator may need mileage and engine-hour information. Historical trips or driver-level reports might be restricted to designated fleet, safety, human-resources, or senior management personnel.

Recommended safeguards include:

• Individual accounts rather than shared passwords
• Strong passwords and multi-factor authentication where available
• Role-based permissions
• Prompt removal of access when responsibilities change
• Periodic reviews of user permissions
• A documented procedure for exporting or sharing reports
• Confidentiality training for authorized users
• Secure deletion when records reach the end of their retention period

The Privacy Commissioner recommends physical, organizational, and technological protections, including passwords, encryption, and access limited on a need-to-know basis. Wialon also describes security practices that include permissions management, least-privilege access, and need-to-know controls, but the fleet operator remains responsible for configuring accounts and using the information appropriately.

Do Not Let a Data Point Become an Automatic Verdict

GPS information should not replace communication or human judgment. Before using a record to coach or discipline an employee, verify that:

• The correct driver was assigned to the vehicle
• The time, location, and event were recorded accurately
• The hardware was functioning properly
• The employee had an opportunity to explain the circumstances
• Other relevant evidence was considered
• The proposed action follows the written policy and any collective agreement

This is especially important when a conclusion is based on an inference. A parked vehicle does not prove an employee was avoiding work, and a route deviation does not establish misconduct. The driver may have encountered a closure, followed dispatch instructions, stopped for safety reasons, or responded to a customer request.

The Privacy Commissioner’s GPS findings caution against routinely evaluating employees through assumptions drawn from incomplete location records. A fair process uses GPS as one source of information, not as an unquestionable verdict.

Show the Benefits for Drivers

A tracking rollout should not be presented as something that benefits only management. Used responsibly, GPS information can also help employees.

It may reduce calls asking where a driver is, confirm arrival at a customer site, support a driver facing a false complaint, locate a stranded employee, provide evidence after a collision, and allow dispatchers to assign work more efficiently. Historical records may also help resolve disagreements about routes, completed visits, working time, or vehicle use.

Be careful not to promise that tracking will never be used for accountability. That promise may be unrealistic and could undermine trust later. A better commitment is that the information will be used only for disclosed, legitimate purposes and that employees will have an opportunity to provide context when a record could affect them.

Use a Straightforward Crew-Meeting Script

The opening of the conversation can be simple:

“We are introducing GPS tracking in company vehicles to improve dispatching, driver safety, service verification, maintenance planning, and vehicle security. The system may record vehicle location, trips, stops, speed, mileage, and other supported vehicle events. It is not being introduced for unrestricted monitoring of employees. We have written rules covering when the information is collected, who can access it, how long it is kept, and when it may be reviewed. We want everyone to understand those rules and raise questions before the system begins operating.”

After the introduction, demonstrate the platform using a test vehicle. Show employees what a dispatcher sees, what appears in a trip report, and what the system cannot determine. Review a few realistic scenarios, including a theft, customer complaint, emergency, and take-home vehicle used outside normal hours.

Conclude by giving employees the policy, the name of the person responsible for privacy questions, and a clear method for submitting concerns privately.

Keep the Conversation Going

Privacy management does not end after the initial meeting. Review the program periodically to determine whether the collected information is still necessary and whether it is being used as promised.

The policy should also be revisited when the company adds new sensors, activates additional reports, begins monitoring a new group of employees, changes its retention period, or starts sharing information with another organization. A new capability can create a new privacy impact even when the tracking hardware remains unchanged.

Ask employees whether the system is creating practical problems or unintended pressure. Their feedback can help identify excessive notifications, inaccurate driver assignments, unclear personal-use rules, and cases where managers are drawing conclusions without sufficient context.

Fleet tracking works best when employees understand its purpose, know its limits, and trust the process surrounding the data. Forall Tracking can help your business configure a Wialon GPS tracking solution that supports operational visibility while respecting the boundaries established in your fleet policy. To discuss your vehicles, reporting needs, access controls, and implementation goals, contact us today.