GPS Time Clock for Employees: The Complete Australian Guide

The Real Problem Is Not Time Theft

GPS time clocks are usually sold on time theft. Staff rounding up, buddy punching, the eleven minutes that becomes fifteen. That does happen, and it is not the main reason most Australian businesses need this.

The main reason is that a roster is not a time record, and most employers are treating it as one.

Your roster says Priya worked 9:00 to 17:00. What actually happened is she started at 8:52 because the previous shift needed handover, took 22 minutes for lunch instead of 30, and left at 17:15 finishing a note. None of that is unusual and none of it is anybody behaving badly. It is just the gap between a plan and a day.

Pay from the roster and you are paying from a document that describes an intention. In most weeks it is close enough that nothing surfaces. The problem arrives eighteen months later when somebody disputes their hours and the only evidence you have is what you planned to happen.

What Fair Work Actually Requires

The Fair Work Act 2009 and the Fair Work Regulations require employers to keep records of hours worked, and most Modern Awards require the actual start and finish times of each shift, including unpaid breaks. Records must be kept for seven years, be legible, be in English, and not be false or misleading.

The provision worth knowing by name is section 557C. Where an employer has failed to keep or produce required records and has no reasonable excuse, the employer carries the burden of disproving an allegation about those matters in proceedings. That reverses the usual position.

Read that consequence carefully, because it is the whole compliance argument. An underpayment claim normally requires the employee to demonstrate they were underpaid. Without records, you are instead required to demonstrate that you paid correctly, about shifts worked years ago, using evidence you do not have. A record-keeping lapse converts into a wages liability without anyone ever proving the underpayment happened.

That is why time records matter more than the time theft framing suggests. You are not primarily buying surveillance. You are buying evidence. Broader obligations are covered in Fair Work rostering requirements.

How the Options Compare

The honest weakness of the phone-based approach is that it depends on staff phones. Flat batteries, no signal in a basement or a regional area, and workers who reasonably object to using a personal device for work. Have an answer for each before rollout: an offline mode or a manager override path, and a policy position on personal device use. A business where a meaningful share of staff have no suitable phone is a business where a fixed clock still makes sense.

Being clear about our own product, since previous versions of this page were not: GetMyRoster's GPS time clock is a paid feature. It is not part of the free plan, which covers up to 5 users at one location with the dashboard, mobile apps, notifications and certificate management. If attendance records are what you need, you are looking at a paid plan from the start.

Privacy, and the Conversation You Need to Have

Location data about an identifiable person is personal information under the Privacy Act 1988 (Cth). That brings obligations: tell staff you are collecting it, explain why, collect only what you need for that purpose, and keep it secure. Several states also have workplace surveillance legislation with its own notice requirements, so check your jurisdiction rather than assuming the Privacy Act is the whole picture.

The practical line is between capturing location at clock events and tracking someone continuously. Recording where a worker was when they started and finished a shift is proportionate to verifying attendance. Following their movements through the day is not, and it is the thing staff will assume you are doing unless you tell them otherwise.

Which is the part most rollouts handle badly. Announcing GPS tracking without context reads as an accusation, and staff hear it as management assuming they are stealing time. Two things make the conversation go better. Be specific that location is captured only at clock-in and clock-out, and say what it is for. And make the case that accurate records protect them too, because when a worker says they stayed back forty minutes, a timestamped record is the thing that proves it. In a s.557C world the employee benefits from good records at least as much as the employer does.

Write the policy down, tell people before you switch it on, and do not use attendance data for purposes you did not disclose.

What to Check Before You Buy

Does it feed payroll directly? A time clock that produces a CSV you re-key has solved half the problem and left the half where transcription errors live. Confirm the export carries award-adjusted amounts rather than raw hours, and that it reaches Xero, MYOB or QuickBooks without manual handling.

Is it award-aware? Raw hours are not pay. Something has to apply the SCHADS Saturday rate of 150%, the Sunday rate of 200%, the loading for a casual. If the time clock does not and payroll does, that is workable, just know where the calculation happens and who owns it.

Can employees see their own records? Underrated, and it prevents disputes. A worker who can check their own timestamps raises a discrepancy the same week rather than six months later when nobody remembers.

How are corrections handled? Someone will forget to clock out. The question is whether the fix is auditable, showing who changed what and when, or whether a manager can silently edit a timestamp. Silent edits undermine the evidentiary value of the whole system, which was the point of buying it.

Where does the data live and for how long? You need seven years of retrievable records. Ask about export and retention before you sign, not when you leave.

Rolling It Out Without a Revolt

The technology is the easy part. Introducing it to people is where these projects go wrong, and they go wrong in fairly predictable ways.

Tell staff before you switch it on, not after. Discovering a tracking feature by opening the app is the single fastest way to make this adversarial. Say what is collected, when, and what it is used for, and say it in a meeting rather than in a policy attachment nobody opens.

Start with one team or one site. A pilot surfaces the practical problems, the basement with no signal, the worker whose phone is six years old, the site where everybody arrives in the same two minutes, while they are still cheap to solve. Fixing those quietly in one location beats discovering them across the business in week one.

Decide the rounding and lateness policy before the data arrives. This catches people out. Once you have timestamps to the minute, you will see that several staff routinely start four minutes late and finish six minutes late. You now have to decide what, if anything, that means. Work it out in advance, write it down, and apply it consistently, because making the call retrospectively against named individuals turns a system into a grievance.

Agree the missed-clock-out process. People forget. Have a defined route for correcting it, with the correction logged and visible. An auditable amendment trail preserves the evidentiary value of the records; an unlogged manager edit destroys it.

Watch the first pay run closely. Reconcile paid hours against clocked hours for one full cycle before trusting the pipeline. This is also where you discover whether break deductions are behaving the way you assumed, which is the most common configuration error.

A last point on tone. If the only message staff hear is that the business wants to stop them stealing time, you have framed a compliance tool as an accusation, and the resentment will cost you more than the eleven minutes ever did. The accurate framing is that the business needs defensible records and everybody benefits from the hours being right. Most workers accept that readily, because most workers are not the problem and know it. Related reading: staff availability management and roster hacks that cut labour costs.