AI translation for local government is no longer an experiment; it is a tool clerks can turn on for the next council meeting. Like any tool, it does some jobs well and others poorly, and knowing the difference is what makes it useful instead of risky.
What AI translation in government actually does
For public meetings, AI translation is usually two steps chained together. Speech recognition turns what people say into English text, and machine translation turns that text into other languages. With SentraCaptions, English captions appear about one second after speech, and translated captions follow in up to 8 languages per meeting, chosen from 75 languages and regional variants.
The output is text: captions on a chamber screen, on residents' phones, on a YouTube Live stream (one language), and in transcripts afterward. It is not a synthetic voice and not spoken interpretation.
What it does well
- Every meeting, not just the big ones. Because nothing has to be scheduled per meeting, translated captions can run at a routine planning commission as easily as at a budget hearing. See captioning commissions and committees.
- Several languages at once. A single meeting can show English plus several translations side by side on the chamber screen, while each resident picks their own language on their phone.
- Reading at your own pace. Residents choose their text size on the phone page, with no app and no sign-in.
- A record afterward. Transcripts in every language, as TXT or SRT files, help staff prepare minutes and let you add subtitles to posted recordings. They are not official minutes.
- Several rooms at once. Concurrent meetings each get their own screen and link.
What it can't do
- Be perfect. Automatic captions and translations contain errors. Every SentraCaptions screen labels captions as automatic and says they may contain errors. Treat the captions as a way to follow along, not as the authoritative record.
- Translate every language equally well. Quality varies by language. Have a fluent speaker review the languages that matter most before you promote them.
- Cover every language. Hmong and Khmer are not supported. Communities that rely on those languages need another approach.
- Understand every speaker. Speech recognition is English, with Spanish speakers at public comment recognized too. A resident speaking another language at the podium won't be captioned accurately; an interpreter is the better tool there.
- Speak. SentraCaptions provides text only. If a resident needs to hear the meeting in their language, that's interpretation, usually by a human interpreter. See translation vs. interpretation.
- Replace CART for every situation. If a deaf or hard-of-hearing resident requests CART (a human stenographer captioning live) as an accommodation, the agency should consider that request under the ADA's effective communication rules, which give primary consideration to the person's choice. See machine captions vs. CART.
Using AI translation responsibly
A few habits make a big difference:
- Fix the input. Good microphones and a glossary of local names (council members, streets, neighborhoods, programs) improve the English captions, and better English captions mean better translations. See building a caption glossary.
- Get a human review. Ask a bilingual staff member or community partner to watch a recorded meeting in their language and tell you what reads well and what doesn't.
- Be honest with residents. Describe the captions as automatic. Don't present them as certified translation.
- Keep people in the loop for high-stakes moments. For a contentious hearing or a resident who needs to testify in another language, schedule an interpreter as well.
- Pause when the public meeting stops. During recess or closed session, pausing means nothing is captioned, translated, stored or billed, and screens show “Paused.”
The policy backdrop
AI translation sits inside a shifting set of rules, so check with your city attorney or county counsel before relying on any of the following summary.
- SB 707. For eligible city councils and boards of supervisors, most new requirements start July 1, 2026. Agendas must be translated into up to three applicable languages, and digital translation tools are allowed. Bodies must reasonably assist members of the public who want to translate a meeting or receive interpretation, without being required to provide interpretation themselves. SB 707 does not itself require live captions; translated captions are a practical way to support its language-access goals.
- Title VI. Title VI of the Civil Rights Act of 1964 prohibits national-origin discrimination by programs that receive federal funds, and meaningful access for people with limited English proficiency has long been treated as part of that. Executive Order 14224 (March 1, 2025) designated English the official language and revoked Executive Order 13166, and DOJ's LEP guidance was withdrawn. Title VI itself did not change, and state law, grant conditions and local policy still apply.
- California's Bilingual Services Act. The Dymally-Alatorre Bilingual Services Act (Government Code §7290 and following) applies to state and local agencies that serve a substantial number of non-English-speaking people, and local agencies have discretion over what “substantial” means and how far services go.