Uber ordered to reactivate Brisbane driver after its own review backed his account of a complaint it still counted against him

The Fair Work Commission has ordered Uber to restore a Brisbane driver’s access after finding his deactivation over four rider complaints was unfair. Uber had already reactivated him once despite three of the same complaints, and its internal review found GPS data supported his version of one of them.

7 min read
Fair Work Commission
Share this storyLinkedInWhatsAppTeamsFacebookX

Uber’s own internal review found that GPS data supported a rideshare driver’s account of a rider complaint. It then counted the complaint against him anyway. That complaint was one of four Uber relied on when it permanently removed him from the Uber Driver app on 18 January 2026.

Deputy President Lake has found the deactivation unfair and ordered Rasier Pacific Pty Ltd, the Uber entity that operates the platform, to restore the driver’s access within 7 days of the order, and no later than 6 November 2026. The decision, [2026] FWC 4247, was handed down in Brisbane on 30 October 2026. The application was made under s.536LU of the Fair Work Act 2009, which allows workers protected from unfair deactivation to challenge being removed from a digital labour platform.

At a glance

  • Parties: A rideshare driver and Rasier Pacific Pty Ltd (Uber)
  • Citation: [2026] FWC 4247, Deputy President Lake
  • Section: Fair Work Act 2009, ss.536LU, 536LH and 536LP; Digital Labour Platform Deactivation Code, ss.8, 9 and 14(4)
  • Outcome: Deactivation unfair; reactivation ordered by 6 November 2026
  • Next step: Submissions and evidence on lost pay due by 5:00pm Queensland time, 13 November 2026

The same complaints, a second time

The driver began working on the platform on 6 November 2024. Uber first deactivated him on 6 October 2025, after three rider complaints. He lodged an unfair deactivation claim, and the parties reached an agreement. He was reactivated on 4 November 2025 and discontinued that claim.

A fourth complaint followed a late-night trip on 3 January 2026. On 9 January 2026 Uber issued a preliminary deactivation notice that listed all four complaints. The final deactivation took effect on 18 January 2026.

The driver asked in his submissions: “After reactivating why these reports were not removed and why i got deactivated again on the basis of same reports?” The Deputy President described this as “a legitimate point”. He said Uber’s description of the reactivation as a “second chance” undermined the claim that it had considered, on reasonable grounds, that the earlier complaints were established.

Uber’s review favoured the driver, then counted it anyway

A September 2025 complaint alleged that the driver made a racially discriminatory remark to a rider. He denied it. He told Uber the same day that he had received only four trip requests that day and could recall each of them.

Uber’s review of the deactivation stated that “the evidence supports the Earner’s version of events over the Rider’s”. It recorded that GPS data showed the driver had waited stationary at the pickup point for about 10 minutes before cancelling. The review then continued: “Erring on the side of caution, this will be deemed a valid Count, particularly given the Earner’s history of Verbal Altercation reports.”

The Deputy President said this “significantly undermines” whether the conduct alleged in that complaint could be said to have been established on reasonable grounds.

Where the Code process failed

A deactivation that complies with the Digital Labour Platform Deactivation Code (the rules platforms must follow before removing a worker) cannot be an unfair deactivation. The Deputy President found Uber did not comply with the deactivation Code on two separate grounds.

First, the warnings. Uber gave no deactivation warning for an earlier September 2025 complaint before it relied on that complaint. The warnings it did send did not tell the driver he could seek help from a delegate or an employee of a registered organisation (a union). Following the Full Bench in [2026] FWCFB 81, the Deputy President found this did not comply with s.8 of the Code. He held that any conduct relied on as a reason for deactivation must either receive a compliant warning or fall within s.9 of the Code, which allows a platform to skip a warning where it considers on reasonable grounds that the conduct warrants immediate suspension or that it is not reasonable to let the worker keep working.

Second, the threshold for termination. Under s.14(4) of the Code, the platform may terminate access only if the reason is valid and it “considers on reasonable grounds that the reason has been established”.

The Deputy President endorsed Deputy President Bell’s reasoning in [2026] FWC 3368 that this test does not require proof on the balance of probabilities and may involve “surmise and conjecture”. He found it was not met here. In the earlier matter, the allegations were more serious and Uber had spoken to the complainant after the complaint. In this matter, the only evidence from the fourth rider was a single in-app message. That message was sent after the driver had already lodged a complaint about the rider with Uber.

The Code was amended with effect from 12 June 2026. The Deputy President applied the version in force at the date of the deactivation.

Uber argued

that no warning was required because the complaints went to “the core of rider health and safety”. It also relied on “the inherent improbability that four different riders, each unconnected to one another, would independently make complaints of a substantively similar nature” if the conduct had not occurred. It pointed to GPS data and to the absence of fraudulent indicators in the riders’ accounts.

The driver argued

that he had not been aggressive or discriminatory, and that he had given Uber his version of events when he received its warnings. On the fourth trip, he said the rider had started the argument and that he had followed the route the app gave him.

Deputy President Lake found

that hearsay complaints can be relied on, but Uber “puts the evidence too highly”. On the Code test, he found the evidence known to Uber left “room for doubt” beyond what surmise and conjecture could fill.

One complaint proved, one argument without a starter

On the merits, under s.536LH the Commission must decide for itself, on the balance of probabilities, whether the conduct occurred. The Deputy President found it established that the driver pulled over and made riders leave because they were eating in the car. The complaint did not specify how he had “verbally abused” them.

The September complaint alleging discrimination was not substantiated. The rider did not answer Uber’s request for the words used. The racially discriminatory remark alleged in the other September complaint was also not established. The Deputy President applied the Briginshaw standard to that allegation, a principle that findings of serious misconduct are not made lightly.

On the fourth trip, the Deputy President found the driver’s statement that he did not yell was inconsistent with his call to Uber Support, in which he said he started yelling after the rider did. He found a heated argument was likely. He did not find that the driver initiated or escalated it.

In the rider’s own complaint, the rider wrote that he had apologised and said it was his fault and that he had personal problems. Uber’s witness said she had interpreted this as a sign the rider “potentially has some intellectual disabilities or other vulnerabilities”, and accepted this had not been confirmed. The Deputy President said there was no evidence for that. He said it was a reasonable hypothesis, given that the trip was around midnight on a Saturday and headed to Fortitude Valley, that the rider had been drinking, as the driver contended.

Uber’s witness told the hearing that drivers receive de-escalation education and are not expected to react. The Deputy President summarised that position this way:

“The response from the Respondent seems to be that the drivers should be stoically silent and not react even if the Rider initiates the verbal altercation.”

He found no valid reason had been established. The failure to follow the Code also weighed toward unfairness. He treated Uber’s arguments about community safety and the nature of platform work as neutral.

Lost pay still to be decided

The reactivation order deems the driver to have worked on the platform on a regular basis from 18 January 2026 until his access is restored. Uber must also offer him the same terms that applied before the deactivation.

Lost pay will be assessed using the Full Bench method in [2025] FWCFB 214. That method starts from his average earnings before deactivation, then deducts substitute earnings and the expenses he avoided. The driver has worked on other platforms since the deactivation. The Deputy President directed both parties to file submissions and evidence on lost pay by 5:00pm Queensland time, 13 November 2026.

Most of these claims never get to fairness. Of the 91 unfair deactivation decisions OnNotice coded to late July, 71 were decided on threshold points, the 21 day time limit chief among them, before the merits were reached.

Source: [2026] FWC 4247

General information only. OnNotice reports developments in Australian industrial relations, human resources and workplace law. This article is for education purposes only and is not intended to form professional advice. Always confirm against the primary source and seek specific advice relating to your circumstances.

Share this storyLinkedInWhatsAppTeamsFacebookX

Keep reading