A support worker clocks on from a client’s driveway. A hospitality manager needs to confirm a late shift has arrived. A security provider must respond when a patrol check is missed. GPS consent sits at the centre of these everyday operational moments: it helps businesses use location data to solve real staffing problems without making employees feel watched every minute of the day.
For shift-based teams, GPS monitoring can provide useful evidence of attendance, improve safety and reduce disputes about where and when work happened. But the technology only works well when people understand it, know its limits and can see the reason for it. Vague expectations create resistance. Clear consent and clear processes build accountability.
What GPS consent means at work
GPS consent is an employee’s informed agreement to the collection and use of their location data. In practice, that means staff should receive plain-language information before location tracking begins. They need to know what is being collected, when tracking occurs, why it is needed, who can see the information, how long it is kept and what to do if they have a concern.
A tick box buried in an app setup screen is not a strong foundation for trust. Nor is a broad statement that a business may monitor staff ‘as required’. Consent should be specific enough for a reasonable person to understand what they are agreeing to.
This matters particularly where staff use their own mobiles, move between client sites, work alone or have shifts that extend outside a traditional workplace. The more personal the device or the more sensitive the setting, the more care is needed.
Consent is also not a substitute for good judgement. A business should have a legitimate operational reason for collecting location data and use the least intrusive approach that will achieve it. Tracking a worker only while clocking on and off may be enough for one operation. Live location during a lone-worker shift may be justified in another. It depends on the work, the risks and the service obligations.
Why location tracking becomes an operational issue
Managers rarely introduce GPS monitoring because they want more data. They do it because the current process is failing. Paper timesheets arrive late. Staff clock in before reaching the site. A coordinator spends an hour chasing a worker who has not turned up to a client. A payroll dispute has no reliable record behind it.
Used appropriately, location-enabled clocking can reduce these problems. It can verify that a clock event occurred at or near the approved work location, create a time-stamped record and give coordinators a clearer view of exceptions that need attention. For NDIS and aged care providers, this may support service delivery records where client visits happen across a wide area. For hospitality, it can help managers confirm attendance across venues without relying on phone calls during a busy service.
The benefit is not constant surveillance. The benefit is faster, fairer action when something does not match the roster.
That distinction should be visible in your policy and in the way managers use the system. If GPS data is introduced to verify shift attendance but later used to scrutinise every stop a worker makes, staff will quickly lose confidence. Scope creep is one of the fastest ways to turn a practical tool into a workplace problem.
Set the rules before you switch tracking on
Start by defining the precise job GPS data needs to do. It may be confirming a clock-on location, supporting employee safety during specific work, validating travel between scheduled sites or investigating a genuine attendance exception. Avoid collecting data simply because the platform can collect it.
Then turn that purpose into workable rules. Explain whether location is captured only at clock-on and clock-off, at scheduled intervals during a shift or through live tracking. Be equally clear about when tracking stops. Staff should not be tracked during unpaid breaks, after a shift or while off duty unless there is a clearly communicated and justifiable exception.
Your written process should address four practical questions:
- Which workers and devices are covered, including company-issued and personal mobiles.
- What location information is captured and at what times.
- Who may access it, and when access is appropriate.
- How long records are retained, secured and eventually deleted.
These rules make onboarding easier and give supervisors a consistent reference point. They also help prevent a well-meaning manager from accessing location data out of curiosity rather than operational need.
Privacy and workplace surveillance obligations can differ across Australia and may depend on your organisation, the state or territory where staff work, the device used and the type of monitoring involved. The employee records exemption under the Privacy Act is also not a blanket permission to collect or use any employee information without care. Obtain advice that fits your circumstances, particularly if you operate across jurisdictions or provide regulated care services.
Make consent informed, not rushed
Employees are more likely to accept location tracking when the conversation is direct. Explain the problem the business is trying to solve, show how the process works and give staff an opportunity to ask practical questions before they are asked to acknowledge the policy.
For example, a worker may want to know whether a manager can see their home address when they clock in for a remote first visit, whether the app follows them after work, or what happens if their mobile has poor reception. These are reasonable questions. Answering them clearly is part of implementation, not an administrative extra.
Use a standalone acknowledgement that refers to the GPS policy, rather than relying solely on a generic employment contract clause. Keep a record of the acknowledgement, the version of the policy provided and the date it was issued. When the way you collect or use location data changes materially, communicate the change and seek a fresh acknowledgement where appropriate.
Consent in an employment relationship can be complicated because employees may feel they have limited choice. That is another reason to be transparent, proportionate and prepared to explain the business need. A clear process gives people confidence that the system is about doing the job properly, not catching them out.
Build in fair handling of GPS exceptions
GPS is helpful evidence, but it is not perfect evidence. A location pin can be inaccurate around high-rise buildings, regional areas and poor reception zones. A worker may have clocked in from the footpath outside a client property because the mobile signal would not reach indoors. A rostered address may be out of date. A staff member may have attended an urgent alternate location at a supervisor’s request.
For this reason, GPS data should trigger a conversation or an exception workflow, not an automatic accusation. Give staff a simple way to explain a mismatch and give managers a process for reviewing it alongside the roster, messages, client records and other relevant information.
The same principle applies to performance management and disciplinary action. Location information may form part of a record, but decisions should be fair, documented and based on the full context. A system that flags exceptions consistently can protect both the business and the employee from assumptions.
Train managers as carefully as staff
The quality of GPS consent can be undermined by poor manager behaviour. A coordinator who checks a live map outside work hours, shares screenshots in a group chat or uses a location trail to embarrass someone damages trust and may create a more serious issue for the organisation.
Managers need practical boundaries. They should know when they are permitted to view location information, how to respond to an unexplained clocking exception, how to record a discussion and when to escalate a privacy concern. Access should be limited to people with a genuine operational need, rather than made available broadly because it is convenient.
It is also worth reviewing access regularly. As roles change, former managers, casual supervisors and administrators should not retain visibility of staff location records they no longer need.
Choose technology that supports the policy
Your policy should guide the system configuration, not the other way around. If your stated purpose is location-verified clocking, configure the platform around clock events rather than leaving continuous tracking on by default. If workers move among approved sites, ensure location settings reflect those sites and give managers a clear exception process.
A workforce platform such as Tommy can bring scheduling, shift notifications, clocking and GPS records into the same operational view. That can reduce the need to chase information across texts, spreadsheets and separate apps. The value comes from matching the setup to your workflow, then supporting staff through the change.
Before rollout, test the process with a small group of workers and managers. Check mobile battery impact, reception issues, clocking accuracy and the wording staff receive. A short pilot often exposes the practical details that a policy alone cannot predict.
The best GPS process feels predictable to staff: they know when it operates, why it operates and how to raise an issue. That gives managers cleaner records, gives employees fairer treatment and leaves more time for the work that actually keeps clients and customers well supported.