The deadline nobody is counting comes first

Kansas City has spent the summer watching a clock that runs out on August 31.

There is a second clock. It is not in any of the coverage, and it runs out on August 25, five days from today.

Under Missouri law, the city cannot put a question to voters at the November 3 general election unless it notifies the county election authorities by 5:00 p.m. on the tenth Tuesday beforehand. Counting back ten Tuesdays from November 3 lands on Tuesday, August 25.

The sixty days the City Council has to act on the two citizen petitions certified to it do not expire until August 31. The ten days the petitioners then get to demand an election run to about September 10.

Both of those dates fall after the notice deadline. Which means that if the Council keeps doing what it has done since July 2, which is nothing, the practical effect is not that these questions go to voters in November. It is that they do not.

The sixty-day clock is real, and we have already counted it

We reported on August 14 that Section 702 of the city charter started the sixty-day clock on July 2, when the Council received the City Clerk’s certificates for both petitions and referred the resulting ordinances (260609, the stadium-vote measure, and 260610, the forty-year transit taxes headed by an airport monorail) to the Special Committee for Legal Review. Day sixty is Monday, August 31. Forty-nine of the sixty days are gone.

That article also reported the deadline after the deadline: Section 702 gives the committee of petitioners ten days after the sixty expire to require that their ordinances go to the voters anyway. That window closes around September 10.

What we had not yet read was Section 703, the provision that says which election those ordinances would actually appear on. It contains the whole problem.

The charter rules out its own escape hatch

Section 703 sends a petition the Council will not pass to “the next available municipal or state election held not less than thirty (30) days after such certification … for which the City can lawfully provide required notices to the election authorities without seeking a court order.”

That last clause does the work. Missouri’s election-notice statute, RSMo 115.125, offers two deadlines. Subsection 1 requires notice “not later than 5:00 p.m. on the tenth Tuesday prior to any election.” Subsection 2 allows a later notice, up to the eighth Tuesday, “pursuant to court order.”

Kansas City’s charter takes the first and expressly declines the second. For November 3, the tenth Tuesday prior is August 25. The court-order fallback the charter refuses to use would have run to September 8.

Laid side by side, the dates are in the wrong order:

The charter gives the Council sixty days and the petitioners ten more. State law needed the answer seventy days before the election. The two schedules do not fit inside each other, and the only way they ever fit is if the Council acts early.

What is on the calendar

The Council met every Thursday afternoon from July 16 through August 13. Today is a Thursday. There is no Council meeting on the city’s legislative calendar today, and as of this morning’s pull there is none scheduled on any future date, on the same calendar where the Board of Police Commissioners posts its meetings eleven months out.

The Special Committee for Legal Review, the body holding both ordinances, has met once this year, on March 23, 150 days ago. It has nothing scheduled. Both ordinances sit where they were referred, their records untouched in the city’s legislative system since July 13.

That may mean very little. This same Council took three weeks off between June 11 and July 2 and posted nothing in the interval, and city calendars fill in a week at a time. It is not evidence that the Council will not meet before August 25, and it should not be read as any.

It does mean that with five days left before the November ballot becomes unreachable, no meeting of any body that could act is on the books.

It qualified on 2,282 signatures

The monorail petition’s route to this moment is documented in the city’s own certificates, which we pulled and archived this week.

The City Clerk’s sworn, notarized certification of June 12 tallies the four county election boards’ reviews: 2,247 valid signatures in Jackson County, 26 in Clay, 9 in Platte, none in Cass — 2,282 in all, against a threshold of 2,068. A margin of 214 signatures, or about ten percent. The Kansas City Board of Election Commissioners reviewed 2,848 signatures across all 170 pages of the petition: 2,247 accepted, 500 rejected, 101 duplicated.

One reading of those two documents together, and we label it as our arithmetic rather than either document’s statement: all four boards checked the same 170 pages, and 566 of the 2,848 signatures submitted, about one in five, were valid in no county at all.

We can also now say, without anyone squinting at a scan, that the tax ordinance and the monorail petition are the same document. The city files the identical four-part petition attachment under both ordinance 260610 and the June 2 clerk’s communication whose own title names the airport monorail. We downloaded the first part from each record and hashed them: the same file, byte for byte (7,751,688 bytes, identical SHA-256), served under two different attachment IDs.

Four documents, three spellings

A small thing, worth exactly one paragraph. The city’s legislative database titles the petition “KC UNCL.” The clerk’s certification, the Kansas City election board, the Clay County board and the Platte County board all render it “KC INCL.” The clerk’s cover letter to the petitioners lifts the words “Airport Monorail” out of the middle of the title and strands them at the bottom of the page. The petition itself says INCL. It is the kind of small thing that tells a reader how closely a 170-page filing was read on its way through the machine.

The sentence this piece will not write

The record shows a referral to a committee that has not met since March, a Council calendar that goes quiet the week the notice deadline lands, and two deadlines that fall in an order that forecloses November. It does not show that anyone chose any of that, and this article does not say that anyone did.

A referral to a dormant committee needs no motive to work. Inaction alone runs out the sixty days, and the notice deadline passes on its own. What the mechanism produces, whether or not anyone intended it, is this: waiting out the clock does not delay these two questions until November. It delays them past November.

Five residents signed as the committee of petitioners, and the September 10 deadline belongs to them. As of today, the city’s file contains no indication that anyone has told them the date that mattered came first.

---

Reporting method: the charter text quoted above is Article VII, Sections 702 and 703 of the Charter of Kansas City, Missouri, as codified in Municode Supplement 139. The election-notice deadlines are RSMo 115.125, in the version effective August 28, 2026, pulled from the Missouri Revisor of Statutes. Legislative statuses, action histories and the Council’s meeting calendar were pulled from the City of Kansas City’s Legistar API on the morning of August 20, 2026, and archived; matter statuses for 260522, 260577, 260609 and 260610 were re-checked the same morning. Signature counts are transcribed from the City Clerk’s certification of sufficiency of June 12, 2026, and the four county election boards’ result letters filed with it; the clerk’s tally table was transcribed from a rendered image because the PDF’s text layer interleaves its columns. The petition attachment comparison is a SHA-256 hash match of the city’s own files. Underlying records are open under the Missouri Sunshine Law, Chapter 610 RSMo. Corrections: corrections@kcstare.com. Something we missed? tips.