Do You Have to Consult Your Staff Before Introducing AI or Automation? (Australia)

Detailed Explanation

Many Australian businesses treat an AI rollout as a purely operational decision. That can miss a consultation duty where an applicable award or agreement covers the staff and the proposed technology change is major and likely to have significant effects. The effect on employees, not the presence of AI alone, determines whether this particular duty is triggered.

The clearest working example is the Clerks—Private Sector Award 2020 (MA000002), which covers a very large share of Australian office and administrative workers. Its clause 38, "Consultation about major workplace change," is representative of the wording used across most modern awards.

What the Award Actually Requires

Clause 38.1 of the Clerks Award states that if an employer makes a definite decision to make major changes in production, program, organisation, structure or technology that are likely to have significant effects on employees, the employer must give notice of the changes to affected employees and their representatives (if any), and discuss with them the introduction of the changes, their likely effect, and measures to avoid or reduce adverse effects — commencing discussions as soon as practicable after the decision is made.

Clause 38.2 goes further: for that discussion, the employer must give affected employees and their representatives all relevant information about the change in writing, including its nature, its expected effect on employees, and any other matters likely to affect them. Clause 38.4 requires the employer to promptly consider anything raised in response.

Clause 38.5 lists significant effects including termination of employment; major changes in workforce composition, operation, size or skills; reduced job or promotion opportunities or tenure; altered hours; retraining or transfer; and job restructuring. Assess the actual likely effect of the proposed AI or automation change against that list. A minor tool change without significant effects does not trigger this clause merely because it uses AI.

Why This Applies to AI Specifically, Not Just Layoffs

It's easy to assume consultation obligations are only about redundancies. They're not. The trigger is "major changes in… technology" with significant effects — and clause 38.5's list includes retraining and job restructuring, both of which can happen without anyone losing their job. Introducing an AI assistant that takes over a substantial part of someone's day-to-day tasks, automating a workflow that changes how a team's work is divided, or rolling out a tool that requires staff to learn a materially different way of working can all trigger the duty, independent of whether headcount changes at all.

This means the consultation step belongs in the planning phase of an automation project, not tacked on afterwards as an announcement. By the time a system is built and ready to go live, the point at which discussion could genuinely influence the rollout — timing, training, which tasks change, how adverse effects are reduced — has usually already passed.

The Regulatory Climate Is Actively Watching This

This isn't a dormant clause. The Australian Council of Trade Unions issued a public statement in February 2026 warning employers directly: "Australia is not America. Australian workers have strong rights that require employers to" engage transparently, and that "employers have an obligation in law to meaningfully consult with workers and their" representatives as soon as a decision is made to introduce AI, before implementation. The statement puts employer peak bodies on notice that non-compliant employers can expect coordinated union responses, including disputes lodged with the Fair Work Commission. Whatever a business's view of that framing, it signals that this obligation is being actively monitored rather than treated as a formality nobody checks.

What Consultation Does Not Require

Consultation is a process obligation, not a right of veto. The employer can already have decided to introduce the change — the duty is to discuss it properly before implementing it, not to get employees' sign-off. Clause 38.3 also allows the employer to withhold confidential information from the written disclosure where disclosing it would be contrary to the employer's interests. What the clause does not allow is skipping the discussion, the written information, or genuine consideration of what staff raise.

Things to Consider

• Check the specific award or agreement covering the affected roles, not just the Clerks Award used here as the worked example — most Australian modern awards contain an equivalent clause, but the exact wording and clause number differ by award.
• Build the consultation step into the project timeline, not the go-live announcement. Consultation that happens after the system is already built and configured rarely reflects genuine consideration of what staff raise, and risks not satisfying the obligation at all.
• Put the required information in writing, covering the nature of the change, its expected effect on employees, and anything else likely to affect them — a verbal heads-up in a team meeting does not meet a written-notice requirement.
• This obligation compounds with redundancy law. If an automation project does eventually lead to a role being cut, failing to consult first can independently mean the resulting dismissal isn't a genuine redundancy — see what businesses actually have to do when automation makes a role redundant.

Common Mistakes

• Treating the rollout announcement as the consultation. Telling staff a system is going live is not the same as discussing the change, giving written information, and considering their feedback before it's implemented.
• Assuming consultation only applies to redundancies. A major technology change with likely significant effects can trigger the duty without anyone losing their job, but the effect still needs to be assessed in the applicable instrument.
• Skipping the written-information requirement. Several award consultation clauses specifically require the relevant information to be given in writing, not just discussed verbally.
• Assuming a single small AI tool is too minor to count. The test is the effect on employees, not the size of the technology purchase — a tool that materially changes how someone does their job can trigger the duty even if it's inexpensive or quick to deploy.