O
Kent

Methodology

How OpenOhio sources, transcribes, enriches, and indexes public meeting records.

What we hold for Kent

These are coverage figures — how much of the public record we have published. They are not an accuracy measure, and we do not currently publish one.

Meetings
136
Bodies covered
25
Earliest record
January 5, 2026
Latest meeting
November 4, 2026
Agendas36 of 136 (26%)
Recordings25 of 136 (18%)
Transcripts25 of 136 (18%)
Approved minutes25 of 136 (18%)

Minutes are published on the body's own schedule, often weeks after the meeting.

Meetings with extracted decisions22 of 136 (16%)

112 published motions. A decision can only be extracted where minutes exist.

Next scheduled meeting on record: November 10, 2026.

Bodies covered (25)

August 3, 2026, Sustainability Commission Meeting · Board of Health Special Meeting · Board of Zoning Appeals · Board of Zoning Appeals Special Meeting · City Council · City Council Committee Meeting · City Council Special Meeting with Franklin Township Trustees · City Council Work Session (time approximate) · Civil Service Commission · Civil Service Meeting · Council workshop immediately following Regular Council Meeting · Democracy Day Public Hearing · Fair Housing Board · Health Board · One Time Event · Parks and Recreation Board · Planning Commission · Shade Tree Commission · Special City Council Meeting · Special Council Committee Meeting · Special Council Meeting (Immediately following Council committee meeting) · Special Council meeting · Standing Rock Cemetery · Sustainability Commission Meeting · Sustainability Commission Special Meeting

Where the records come from

We pull official meeting videos from city platforms — Granicus, CivicPlus, PrimeGov, Swagit, and YouTube — once per city per day. Agendas come from the city's public agenda system. Nothing is republished without an official source.

How transcription works

Every meeting is transcribed with word-level timestamps, then enriched with AI to extract decisions, agenda items, public comments, and civic issues. Transcripts may contain errors; video and original audio remain the authoritative source.

How search works

Search is hybrid — keyword matching plus vector similarity — inside Meilisearch. Results are real records (meetings, agenda items, dev applications). The summaries on each result card were produced during enrichment and are reviewed periodically. Written answers come only from the assistant, described next.

How the assistant answers questions

The “Ask about” assistant answers plain-English questions from the same records search uses: agendas, minutes, transcripts, recorded decisions and development applications. It does not answer from general knowledge about your city. It is free with a sign-in.

Every statement in an answer links to the meeting it came from, so you can open the agenda, minutes or the moment in the video and check it yourself. When the records do not cover a question, it says so instead of guessing.

It keeps a recommendation separate from a decision. A planning commission that votes to recommend denial has not denied anything; the council decides next, and the answer says which body acted and which body acts next.

Known limits. Until a body approves its minutes, a vote may be known only from the recording; answers label those votes as recording-based. Not every meeting has a transcript or minutes yet, and coverage differs by city (see the coverage figures at the top of this page). Like the summaries, answers can contain errors.

Before a change to the assistant ships, we rerun a fixed set of real residents' questions with checked answers and compare the results. Passing that set does not guarantee every answer is right, which is why every answer shows its sources.

AI limitations

AI summaries can contain errors. Always verify legal actions, vote counts, and named-person attributions against the official video, transcript, and minutes. Where records are incomplete, we mark the gap rather than guess.

Corrections

Spotted a problem? Email corrections@opencityrecord.org with a link to the page and a description of the issue. We review every correction and update the affected record.

← Back home