Casual employment after Workpac v Rossato: GPS as conversion-protection evidence

A long-engaged casual in your Adelaide manufacturing operation has just claimed they were a permanent employee all along, and are owed back-paid annual leave, personal leave and redundancy. They worked Monday to Friday, eight to four, for two years. They received the twenty-five percent casual loading on every single payslip. Your defence rests on showing the casual pattern, the irregular shifts, the absence of a firm advance commitment, the worker’s genuine ability to refuse. And your roster system shows the same hours, the same days, the same supervisor, for twenty-four straight months.

That is the uncomfortable shape of a casual misclassification claim. The loading you paid does not save you. The contract that called the worker a casual does not, on its own, save you either. What saves you, or fails to, is the record of how the engagement actually ran, week by week, and most employers never kept that record because nobody told them it was the case.

Workpac v Rossato, and what the reforms settled

The High Court’s decision in Workpac v Rossato held that the worker in that case was a casual under the Act: what mattered was the absence of a firm advance commitment to continuing and indefinite work, read from the express terms of the contract, and the Court declined to weigh implied terms or later conduct. The 2021 amendments then codified that approach into a statutory definition of casual employee and built the casual-to-permanent conversion regime around it.

But the story did not stop there, and this is the part employers miss. The 2024 Closing Loopholes reforms added a new pathway: the worker can seek conversion based on the actual pattern of the engagement, regardless of what the contract language says. So in 2026 the contract wording alone no longer defends. The employer has to be able to show, in evidence, that the real pattern was irregular and that the worker genuinely could turn down shifts. The casual loading is relevant, but it offsets damages, it does not establish the casual status. Paying the loading and writing “casual” on the contract is not a defence, it is a starting position that the evidence then has to support.

---

What the casual pattern looks like in evidence

The casual pattern that survives a misclassification claim has four hallmarks. Irregular shifts, with real variation in days, start times and duration from one week to the next. A genuine ability to refuse, with documented instances of the worker turning down offered shifts and nothing bad following. No firm advance commitment, so the roster is a request for availability and not a contractual obligation. And the casual loading clearly identifiable, separately stated, on every payslip.

A workforce platform captures the first three by simply doing its job. The shift offer goes through the platform, the worker accepts or declines, the decline is logged rather than forgotten, and the week-to-week variation sits visible in the roster history. And where the pattern starts drifting toward regular and systematic, the platform can surface the conversion-offer trigger to HR before the worker reaches it first. The difference between a defence and a liability is often just whether someone was watching the pattern while it formed.

The conversion trigger as risk management

The reforms require the employer to offer conversion to permanent after twelve months of regular and systematic engagement, unless there are reasonable grounds to refuse. Missing the offer is a breach. Making the offer and having it refused is, usefully, documented evidence of casual status. Making the offer and converting moves the worker to permanent, with backdating questions to be handled deliberately rather than by accident.

The sensible move is to monitor the engagement pattern continuously rather than waking up at month twelve. At nine months the system flags the casuals who are showing a regular, systematic shape. HR looks, decides whether to vary the pattern or prepare the conversion offer, and either decision is recorded in the audit log. The breach pathway is closed before it has a chance to open, which is the only comfortable time to close it.

The back-pay arithmetic, and what defends against it

A successful misclassification claim produces back-pay for annual leave, personal leave and, where it applies, redundancy. The casual loading you paid is generally offset against that back-pay, but the offset is not always complete, and the interest and penalty exposure stack on top of whatever remains. It is rarely a small number, and it is never a planned one.

The Australian businesses that defend these claims successfully share one documentary pattern: an irregular roster history, declined-shift logs, the casual loading stated separately on every payslip, and conversion offers made and then either accepted or refused with reasons recorded. GeoTapp’s casual-engagement module captures each of those elements week after week, so that when the claim arrives the defence reads as evidence rather than as a reconstruction assembled under pressure. Start a free fourteen-day trial, with no card, and keep the record that a misclassification claim will one day ask you to produce.

Have you had a casual whose pattern quietly drifted toward looking permanent, and how did you handle it? Tell us in the comments below. The drift is slow and easy to miss, and what you write helps other employers notice theirs while it is still a roster question and not a claim.