Skip to content
2pizza.teamBlog

Australia's Voluntary AI Safety Standard, Plainly

Ivan Bolonikhin
Founder, 2pizza.team

Not legal advice - this is an engineering read of the standard. The Voluntary AI Safety Standard is exactly that: voluntary. The reason to care is that its guardrails closely track what has been proposed as mandatory in high-risk settings, so treating it as a design brief now is cheaper than retrofitting later.

The Australian Government published a Voluntary AI Safety Standard, built around ten guardrails for organisations deploying AI, alongside a proposals paper on mandatory guardrails for AI in high-risk settings. For most businesses reading this, none of it is currently binding. It is still the clearest available statement of what 'responsible' will be measured against, which makes it useful whether or not it ever binds you.

The ten guardrails, compressed

Stripped of policy language, they cluster into four things: know who is accountable, know what could go wrong, be able to show your work, and tell people when AI is involved.

  • Accountability - a named owner, an internal policy, and someone whose job it is. Not a committee.
  • Risk management - identify and mitigate the specific harms of the specific system, documented, and revisited rather than done once.
  • Data governance - know what data trains and feeds the system, its quality, its provenance, and its legal basis.
  • Testing and monitoring - evaluate before deployment against defined criteria, then keep monitoring, because models drift and inputs change.
  • Human control - a person can intervene, override, or stop the system. This has to be real, not a button nobody has authority to press.
  • Informing end users - people are told when AI is materially involved in something that affects them.
  • Contestability - a person affected by an AI-influenced outcome has a route to challenge it, and that route reaches a human.
  • Supply chain transparency - you know what is in the AI you bought, and you can tell your own customers.
  • Record keeping - documentation sufficient for someone else to assess compliance later.
  • Stakeholder engagement - consider the people affected, particularly on safety, diversity and fairness.

Which ones cost real engineering effort

Most of the list is organisational and costs meeting time. Four of them are genuine engineering work, and they are the four that are painful to add late.

  • Testing and monitoring - needs an evaluation set, a defined pass criterion, and drift monitoring on inputs and outputs. If you have never built this, it is a real project, not a checkbox.
  • Human control - an override path has to exist in the data model, not just in the interface. A system that cannot record 'a human overrode this, and why' cannot demonstrate human control.
  • Contestability - requires that you can reconstruct why a specific decision came out the way it did, for a specific person, months later. That is a logging and explainability requirement.
  • Record keeping - the documentation only exists if it is generated as you go. Nobody successfully writes it retrospectively.

The model choice this pushes you towards

Contestability and human control are much cheaper to satisfy with a model that can explain a specific decision. Gradient boosting on your own tabular data returns per-feature attribution for every prediction, so 'why was I declined' has a real answer. A language model asked to produce the same score gives you a plausible sentence that may not describe the actual computation, which is worse than no explanation because it looks like one.

This is the same conclusion we reach for reasons that have nothing to do with regulation - determinism, cost at volume, auditability. It is convenient when the compliant choice and the engineering choice are the same choice, and it is worth noticing when they are not.

What is proposed as mandatory, and where

The mandatory proposals target high-risk settings rather than AI generally. The consistent thread in how high risk gets defined internationally is the severity of the impact on a person: decisions about employment, credit, essential services, health, education, and law enforcement tend to land inside. A chatbot that answers questions about your opening hours does not.

The practical question for an SMB is therefore not 'do we use AI' but 'does our AI make or materially influence a consequential decision about a person'. If yes, design against the guardrails now. If no, take the four engineering ones anyway because they are just good practice, and skip the governance overhead.

A proportionate response for a small business

The failure mode here is a small company building an AI governance programme it does not need, and the opposite failure mode is a small company automating a hiring decision with no logging at all. Both are avoidable.

  • Write down what each AI system does, who owns it, and what happens if it is wrong. One page per system is enough to start.
  • Decide explicitly whether any of them influence a consequential decision about a person. That answer sets the effort level for everything else.
  • For anything that does: log the inputs, the output, and any human override, and make sure you could explain one specific decision a year from now.
  • Tell users when AI is materially involved. This is cheap, it is increasingly expected, and it is the thing customers notice you hiding.
  • Do not write a policy you will not follow. An unfollowed policy is worse evidence than no policy.

Verify the current status of the mandatory proposals before making a compliance decision - this area is moving and a blog post is the wrong source for a date. The engineering advice above holds regardless of how the timing lands. If you want us to look at a system you already run, the audit at /audit is free. Ivan / 2pizza.team

Want us to look at your setup?

Free 30-min audit. We tell you what to automate first and what it would cost.

Book a free audit
GEO & AI Search
2,591 Bytes: The Shop That Did Not Exist for AI Crawlers
9 min read
Australia
The Privacy Act and AI Automation: What an Australian Business Actually Has To Do
13 min read
Automation Tools
Make vs Zapier vs n8n in 2026: Honest Comparison from 80+ Shipped Projects
16 min read