docket.pub
Public meeting intelligence
/
Corrections

Corrections policy

Docket.pub indexes thousands of records automatically, and some of them will be wrong. If you spot an error, we want to fix it.

What counts as an error

Anything that doesn't match the source

A wrong vote tally, a misattributed sponsor, a misread dollar amount, an item linked to the wrong meeting, a council member's term shown incorrectly — anything that doesn't match the original public document.

Editorial summaries are generated from the source text and may paraphrase imperfectly. If a summary materially misrepresents what an item or meeting was about, that's an error too.

How to report

Open an issue or send a note

The fastest way to report an error is to open an issue on GitHub ↗. Please include a link to the page you saw the error on and, where possible, a link to the original source document so we can verify.

If GitHub isn't an option, email hello@docket.pub.

What happens next

We fix it, or we explain why we can't

If the source document supports the correction, the record is updated. If the underlying public document is itself incorrect or ambiguous, the discrepancy is preserved and annotated rather than rewritten — docket.pub does not silently reconcile disagreements between sources.

Colophon

Docket.pub indexes public meeting records from Alabama municipalities. Every figure on this page is hyperlinked back to its original document. Where automated extraction disagrees with official minutes, both readings are preserved — never silently reconciled.

© 2026 docket.pub · An open-source civic transparency project Built with public data · Made in Alabama
Source of truth
SOURCE OF TRUTH
Pinned · updates on click
[1] · CITY · docket.pub

docket.pub

Provenance for everything you see on this page. Tap any vote, dollar figure, or meeting card to see the underlying source — agenda PDF, official minutes, or the city's CMS.

tip Pick a city to see its sourced meeting data.
Menu
More