When a Moved Deadline Costs a Qualified Petition

On September 23, 2026, the Montana Supreme Court ordered a Butte-Silver Bow ballot initiative restored to the November ballot after county election officials had disqualified it. Two days later, on September 25, the same court vacated that order, and the measure came off the ballot for good. It did not lose because the petition failed on the merits. Organizers had collected more signatures than the law required. It lost because the ballots that would have carried it were already printed, and some had already been mailed back by voters. What happened in between is a plain lesson in what a moved deadline can do to a petition everyone agrees is otherwise qualified.

A deadline that moved after signatures were already in hand

406 People First, the citizens' group behind the initiative — which would require voter approval before any new data center could be built or expanded in Butte-Silver Bow — submitted signatures in early August 2026 believing the filing deadline was August 14. The county's Clerk and Recorder initially accepted and certified the petition as sufficient; organizers had gathered more than the 3,652 signatures required. On August 10, the clerk's office notified organizers that a new state law had actually moved the real cutoff to July 13, retroactively treating a submission the county had already certified as untimely. Organizers sued to stop the county from applying the new date. A district court ruled against them.

The law behind the date

The law is Senate Bill 11, passed unanimously by both chambers of Montana's 2025 Legislature and titled, plainly, an act to revise local government ballot issue laws. It replaced four older sections of the Montana Code with a single consolidated timeline: signed petition sheets for a local government ballot issue must now be submitted no later than four weeks before the certification date, a real compression from the calendar campaigns had planned around before. That rule governs city and county measures like Butte-Silver Bow's data center initiative — a separate track from Montana's statewide constitutional and statutory initiative process, which this site's Montana ballot access guide covers and which runs on its own house-district signature math untouched by this case.

Why a qualified petition still lost

The Montana Supreme Court's first ruling, on September 23, put the initiative back on the ballot on a straightforward equitable theory: leaving the measure off the ballot and later finding it met every legal requirement would leave no way to fix that, while including it and striking it later if courts found it deficient at least left a remedy on the table. Two days later the court reversed itself, after learning that ballots carrying that decision had already gone to print and, for some voters, had already been returned by mail. The justices wrote that Montana's election statutes “do not contemplate this decision” — state law has no mechanism for adding a measure back onto ballots already mailed, or for issuing a supplemental ballot to voters who already voted. The court called the situation “entirely avoidable,” pointing to a clerical delay that held up the appeal for weeks and to the county's failure to flag sooner that ballots were already in production. Organizers filed an emergency petition for reconsideration; as of this writing it remains pending, though the printed ballots mean the outcome for November is already fixed regardless of how that petition is resolved.

The broader lesson: deadlines move, and legislatures don't always announce it loudly

SB 11 passed with unanimous support in both chambers over a year before this petition was ever filed, which is exactly the problem. A bill that draws no opposition and no controversy rarely makes news outside the statehouse, and a campaign tracking only the calendar it has always used can miss that the calendar itself changed underneath it. It is the same discipline this site's guide to why ballot initiatives fail to qualify and its companion piece on Missouri's compressed referendum clock both point to from different angles: the legal deadline that matters is the one in force on submission day, not the one a campaign has always used, and a firm that hasn't confirmed the current statute this cycle is guessing.

What this means for planning a local ballot issue

Two things follow directly. First, confirm the current filing deadline against the actual statute every cycle, not against last cycle's calendar or a prior campaign's timeline — a law like SB 11 can change the number without any corresponding change to how far out a campaign starts planning. Second, treat the certification date, not the election date, as the real deadline anchor; a four-week cushion before certification is not a buffer to plan into, it is the wall itself. A statewide initiative still gets the roughly year-plus runway Montana's own guide describes. A local government ballot issue runs on a different, tighter clock, and the two should never be planned on the same schedule.

Butte-Silver Bow's data center initiative will not appear on the November 2026 ballot no matter how the pending reconsideration is resolved, because the printed ballots already exist. Nothing about that outcome required a defective petition, a signature shortfall, or a loss on the merits. It required one deadline moving by a matter of weeks, one organization operating off the date it had always used, and a gap of a few weeks between when that stopped being true and when anyone caught it.