195 incidents on record · 2026 Headlights Incident reports by Ellie Harris · Melbourne
11 new this week Library last updated 12 September 2026
← The incident library
HD-INC-176
Employment tribunal · Australia · 2026 · Unverified AI generated submissions from a self-represented party

A self-represented worker relied on AI generated material that argued the wrong date, and was ordered to pay costs

By Ellie Harris · Filed Costs decision issued 19 August 2026 and reported from 20 August 2026; guidance note announced 24 August 2026 and effective 20 October 2026

Alleged: Fair Work Commission developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

A self-represented worker relied on AI generated material that argued the wrong date, and was ordered to pay costs

What happened

It was reported in August 2026 that the Fair Work Commission ordered a former Aldi worker to pay 1,230 dollars towards his former employer’s legal costs after he continued an unfair dismissal claim the Commission found he could not win.

The case turned on one date. He was notified of his dismissal three days before he reached the six month minimum employment period. That was the date that mattered under the Fair Work Act, not the later date when his dismissal took effect.

It was reported that his AI generated submissions kept focusing on the later date, even after the Commission had explained the problem and warned him that he could face costs. The Deputy President described the costs order as a very rare step and said his conduct had caused Aldi unnecessary legal costs. The worker later told ABC News that he had used a paid version of ChatGPT to help understand the cases Aldi and the Commission had cited.

What an auditable version would have shown

The Commission found the problem by reading what had been filed. Its decision records that the applicant’s AI generated material kept addressing the wrong date, including after the Commission had explained which date mattered.

A record attached to the filing could show that AI had been used and that the person filing it had checked the facts, authorities and argument before submitting it. That would make the verification visible rather than leaving the Commission to discover the problem when it read the material.

Where the gap was

The Commission’s response is now quite direct. From 20 October 2026, anyone using generative AI to prepare a document for a Commission case must disclose that use and explain how AI was used. They must also check that the document is correct and relevant. Witness statements and declarations have additional requirements.

A ConstraintGate is designed to check whether the required AI declaration is present before a document is filed. A CitationVerifier is designed to check whether an authority exists and supports what the document says. A ConductRecord keeps the declaration and the results of those checks.

None decides whether someone can use AI to prepare their case.

What governance should have looked like

The Commission does not say using generative AI is inherently improper. Its own guidance provides prompts to help people use it and says generative AI should not be used as a substitute for legal advice. It also requires people using it to take responsibility for checking what they file.

Where an institution accepts documents prepared with AI, best practice would be to make that checking visible. If AI helped prepare a document, the person filing it should disclose that use and confirm that the facts, authorities and argument were checked before filing.

Failure Pattern: it was reported that a self represented worker relied on AI generated material that repeatedly addressed the wrong date, even after the Commission explained which date mattered.

Governance Principle: where an institution accepts documents prepared with AI, it should be able to see that AI was used and that the person submitting the document has confirmed they checked it.

The reference implementation of ConstraintGate, CitationVerifier and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

No tracking. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Fair Work Commission could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed August 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →