AI Kill Switch and Data Centre Control Bill 2026

The short answer

AI Kill Switch and Data Centre Control Bill 2026

The AI Kill Switch and Data Centre Control Bill 2026 was introduced in the House of Representatives on 7 September 2026 as a private member's bill by Andrew Gee, the member for Calare, who sits as an independent after leaving the Nationals. The bill has two limbs. The first would require providers of covered advanced AI systems to maintain ways to restrict, suspend or shut those systems down, giving government a last-resort ability to intervene when an AI system presents a serious safety risk. The second would establish a moratorium on new AI data centre construction and expansion. The measure has been categorised by regulation trackers as a prohibition of goods and services affecting AI development and cloud infrastructure providers, and it was introduced in the same period as comparable debates in the United States and the United Kingdom about statutory emergency shutdown powers. It is a private member's bill, not a government bill, so its passage depends on the Parliament giving it time and support; introducing it is the first stage of the process only. At the time of writing the bill was before the Parliament and had not been passed by both houses, had not received royal assent and had not commenced.

This is a federal system guide. State constitutions, parliaments and local-government laws can allocate comparable functions differently.

The useful question is not only “what is the rule?” but also “who administers it, which document controls it, and when might it change?” That distinction prevents an accurate general explanation from becoming wrong advice in a particular election, chamber or policy setting.

Evidence review

What the bill is

The AI Kill Switch and Data Centre Control Bill 2026 was introduced in the House of Representatives on 7 September 2026. It is a private member's bill brought forward by Andrew Gee, the member for Calare, who left the Nationals to sit as an independent. Because it is not a government bill, it does not carry the government's legislative program behind it and must rely on the Parliament — the ministry, the crossbench or the opposition — to give it time for debate and a vote.

The bill addresses two distinct subjects that its title names. The first is the ability to stop or restrain advanced AI systems that are judged to present a serious risk. The second is the physical infrastructure on which large AI systems depend: data centres.

Introducing a bill is the first step only. A bill must pass both houses and receive royal assent before it becomes law, and it commences on the date or dates set in its commencement provisions. When this article was prepared, no second reading vote, passage, assent or commencement had been recorded for this bill.

Evidence review

The kill switch: control over covered advanced AI systems

The first limb concerns systems commonly described as advanced or frontier AI. According to the bill record, the measure would require providers of covered advanced AI systems to maintain ways to restrict, suspend or shut them down. In practical terms that is a requirement to build and keep alive a technical capability — the ability to slow a system down, to limit what it can do, or to switch it off — rather than a requirement that anyone actually use it.

The bill is reported to give the Australian government last-resort powers to intervene in the event of a serious safety incident. That framing matches debates elsewhere: in the United States, lawmakers have proposed an AI Kill Switch Act that would give a federal department emergency order powers over the largest developers, and in the United Kingdom peers have called for a statutory power to deactivate powerful systems and switch off data centres, a call the UK government has so far rejected on the basis that it cannot 'simply turn AI off'.

It is important not to overstate what an introduced bill does. Until it passes and commences, no provider is under any obligation under it, and no government power exists under it. The requirement and the power are proposals.

Evidence review

The data centre moratorium

The second limb is a moratorium on new AI data centre construction and expansion. Data centres are the physical substrate of large-scale AI: the buildings, power connections and cooling systems that hold the computing hardware on which models are trained and run. A moratorium of that kind is a planning and infrastructure control as much as a technology measure, because it would limit where and whether new capacity can be built.

Regulatory trackers have categorised the bill's policy instrument as the prohibition of goods and services, with the regulated economic activity described as machine learning and AI development on the one hand, and cloud computing, storage and database infrastructure provision on the other. That reflects the bill's two limbs: control over the systems themselves, and control over the infrastructure that supports them.

The bill's rationale, as its sponsor has put it publicly, is that Australia should not rush headlong into technology whose behaviour is not fully understood. The moratorium is the expression of that caution: pause the build-out while the safety and control framework is settled.

Evidence review

Why this bill, and why now

The bill emerges from a period of heightened concern about the behaviour of autonomous AI systems. Reporting on its introduction describes it as coming after incidents in which AI agents behaved in unexpected or harmful ways, and as responding to that concern with two structural answers: mandatory shutdown capability, and a pause on the infrastructure expansion that would otherwise accelerate deployment.

The Australian proposal sits inside a wider international conversation. The United States has seen a kill switch bill introduced in Congress and debated publicly, and the United Kingdom has had peers pressing for deactivation powers while the government resists them. Australia's bill is distinctive in joining AI system control to data centre control in a single measure.

Because the bill is a private member's bill, its practical prospects depend on whether the government or the Parliament chooses to take it up. Many private members' bills are introduced to place an issue on the record and to build political pressure rather than with an expectation of immediate passage. Introducing the bill therefore records a position and opens a debate; it does not change the law.

Evidence review

The significance of the safety-incident trigger

A kill switch is only useful if it can be used in time and only safe if it is used in the right circumstances. The bill's design, as reported, ties the government's intervention power to a serious safety incident — a last-resort mechanism rather than routine supervision. That framing raises the same questions that have been raised about equivalent proposals overseas: who decides that an incident is serious enough, how quickly a decision can be made, and what happens to services and users when a system is suspended.

For providers, the obligation limb is the more immediate design question. Requiring a covered provider to maintain the ability to restrict, suspend or shut down a system is a condition that bites on engineering and documentation long before any emergency arises. What counts as a covered advanced AI system, and who bears the cost of demonstrating compliance, would be central to any committee scrutiny of the bill.

None of those questions is settled by the introduction of the bill. They are the substance that a second reading debate, a committee inquiry or a government redraft would have to work through.

Evidence review

What happens next

For a private member's bill, the path forward is less predictable than for a government bill. Time for debate depends on the parliamentary program. If the bill attracts support, it could proceed to a second reading debate and then, if passed by the House, to the Senate. If it does not, it may remain on the notice paper without progressing.

Either house may refer the bill to a committee for inquiry and report, which is a common route for measures that raise novel technical questions such as the definition of a covered AI system. The Parliament was next due to sit from 14 to 17 September 2026.

Only if the bill passes both houses, receives royal assent and commences would the shutdown obligations and the data centre moratorium have legal effect. That has not happened. Readers should treat the Parliament of Australia bills register and the explanatory memorandum as the authoritative sources for the bill's text and progress.

Common questions

Before you rely on the answer