What your local government votes on, weekly.
Free, independent, plain-English agenda previews — every dollar figure verified against the original meeting agenda before it ships.
The Gwinnett Docket
1st/3rd Tue business; 4th Tue 7pm zoning hearing (B2B gold)
The Kalamazoo Docket
1st/3rd Mondays; agenda posted Friday prior. Committee of the Whole added 2026-08-11 to catch the City Attorney's data-center-moratorium presentation (see config/stories.yaml: kzoo-data-center-moratorium).
The DeKalb Docket
Auto-added by scout.py on 2026-08-15 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Ann Arbor Docket
Auto-added by scout.py on 2026-08-15 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Ingham County / Lansing Docket
meeting_types tuned 2026-08-29 from a live CivicClerk probe against lansingmi (300 events sampled via the same paginated $orderby=startDateTime desc listing run.py uses, spanning 2026-04-10 through 2027-08-04 -- 18/300 matched; Lansing's real City Council event name is "City Council Meeting", eventName and categoryName agree, no other event type contains "City Council" as a substring). Committee of the Whole, Committee on City Operations, Committee on Ways and Means, Committee on Development & Planning, Committee on Public Safety, Committee on Personnel, and Committee on Equity Diversity & Inclusion deliberately excluded -- these are the separate named-committee event types that were producing the "committee noise" this filter was requested to fix, not this market's scope, for now. Also confirmed live -- despite the market name, this lansingmi feed carries ONLY City of Lansing bodies -- zero events across the sample mention "Ingham" or "County" in eventName/categoryName, so nothing county-level is being filtered out here because nothing county-level exists on this feed at all; flagged separately, not fixed by this change. Launched 2026-09-10 -- config had drifted behind reality, since real Beehiiv subscribers already existed here, including a top B2B lead, with council meeting again ~Sept 22. Staying in coverage mode would have silently stopped this market from ever drafting again under the coverage-is-extraction-only rule shipped 2026-09-09.
The Calhoun County / Battle Creek Docket
Auto-added by scout.py on 2026-08-15 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Fulton Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Cobb Docket
Launched 2026-08-25 via Own Collective request (demand override). meeting_types tuned 2026-08-26 from a live CivicClerk probe (88/222 events matched -- Regular Meeting, Work Session, Zoning Hearing, Special Called Meeting; Cobb's real event names use "BOC", not "Board of Commissioners"). Planning Commission Zoning Hearing and Board of Zoning Appeals Variance Hearing deliberately excluded -- separate bodies, not this market's scope, for now.
The Forsyth Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Oakland Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The DuPage Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Kane Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.
The Naperville Docket
Launched 2026-09-03 by explicit human decision (Beehiiv publication live same day) -- overriding Salman's promotion-gate recommendation, which found meeting_types still unfiltered (live probe found only ~15-19% of Naperville's Legistar activity is City Council) and thin review history (one results issue ever produced, via a manual transcript workaround, not the automated pipeline -- see config/known_failures.yaml's naperville entry for the still-open Legistar video_url gap). meeting_types tuned 2026-09-03 from a live Legistar probe against naperville (webapi.legistar.com/v1/naperville/events, unfiltered/full pagination, 1,939 events currently in the feed, spanning the client's full history through scheduled future meetings) -- the exact EventBodyName string is "City Council" (no "Meeting" suffix, no trailing space -- confirmed by direct field inspection, not assumed from the earlier Cobb/Lansing pattern), 553/1939 (~28.5%) of all events, the single largest body. This supersedes the smaller promotion-time sample (9/58 recent, 181/967 historical, ~15-19%) only because the feed has grown since that probe -- the ratio and the confirmed string are consistent between both probes. 21 other distinct board/commission EventBodyName values were live-probed and are ALL deliberately excluded for now, largest among them Planning and Zoning Commission (345/1939, ~17.8%, second-biggest single body) and Board of Fire and Police (190/1939, ~9.8%). Planning and Zoning Commission was flagged at promotion time as a judgment call on whether to include it alongside City Council -- decided against: it's a separate governing body (its own membership, land-use decisions that recommend to but aren't made by Council), the same shape as Cobb's excluded Planning Commission Zoning Hearing and Lansing's excluded named committees, and this launch's value proposition is general council-decision coverage, not a land-use-specific product. Scoping to City Council only keeps this consistent with both existing single-body launches rather than making Naperville a one-off. Can be revisited later as a deliberate scope expansion, not a default. meeting_types tuning is DONE as of this edit -- the note above no longer describes an owed task.
The Oak Park Docket
Auto-added by scout.py on 2026-08-16 -- meeting_types not yet tuned (unfiltered, may be noisy). Platform confirmed via a live subdomain/client probe, not a guess.