A lot of agencies hear "translate your meetings into every applicable language" and assume that means an open-ended, unaffordable obligation. It doesn't. SB 707 built in a specific, bounded test, and once you understand it, compliance becomes a defined project instead of a moving target.
The Two-Part Test for "Applicable Languages"
A language only triggers the translation requirement if it clears two conditions at once:
- At least 20% of your local population speaks that language.
- At least 20% of that specific language group also speaks English less than "very well," a standard measured through Limited English Proficiency (LEP) data.
Both conditions have to be true. A language spoken widely in your community that's mostly spoken by fully English-proficient residents doesn't trigger the requirement. This two-part structure is deliberate: it targets agency resources at linguistically isolated communities specifically, rather than any community where a second language is common.
Agencies use the U.S. Census Bureau's American Community Survey to make this determination by default. If you're doing this analysis yourself, the relevant data lives in ACS Table S1601, "Language Spoken at Home," which breaks down your jurisdiction's population by language group and self-reported English-speaking ability. You can use a different data source instead of the ACS, but only if your legislative body formally adopts a finding that the alternative is equally or more reliable for your specific area, an option the California Special Districts Association specifically pushed for, since many special district boundaries don't line up cleanly with standard Census tracts.
The Three-Language Cap
If more than three languages meet the two-part test, which can happen in highly diverse regions, you're only required to translate for the three languages with the largest populations. This cap exists specifically so the law doesn't become unworkable for the state's most linguistically diverse cities and counties.
What Actually Has to Be Translated
Two things, specifically:
The meeting agenda. Not the entire packet. Staff reports, technical attachments, and supporting documents don't need translation, just the agenda itself, published at the same time as the English version. The translated agenda also needs to include instructions on how to join the meeting remotely and how to register for public comment, in that language.
Your public meetings webpage. If your agency is subject to SB 707, the webpage dedicated to public meeting information needs to be available in every applicable language, with a clear link from your homepage.
Two Different Interpreter Obligations, Not One
This is where a lot of the confusion happens, so it's worth separating clearly.
SB 707's new requirement is that eligible legislative bodies must provide "reasonable assistance" to a resident who brings their own interpreter or wants to translate the meeting themselves. That assistance is discretionary, meaning your agency decides what "reasonable" looks like, and it can include things like:
- Arranging physical space for the interpreter
- Allowing extra time during the meeting for interpretation to happen
- Making sure the resident can use their own equipment or access commercial interpretation services
This does not require your agency to hire or provide an interpreter. It requires you to accommodate one the resident brings.
Separately, and this predates SB 707, the Brown Act already requires that if your agency limits public comment time, a speaker using an interpreter must be given double the normal time, unless your agency uses simultaneous interpretation equipment that lets the body hear the translated comment in real time without slowing the meeting down. This rule applies broadly, not just to agencies covered by SB 707's new language-equity section.
Knowing the difference matters because the "reasonable assistance" menu is flexible and up to your agency's judgment. The double-time rule is not optional if you cap public comment time and someone shows up with an interpreter.
The Safe Harbor Protection
Translation carries some inherent risk of inaccuracy, especially with machine translation, and the law accounts for that. No legal action can be brought against your agency over the content, accuracy, posting, or removal of a translation, whether your agency produced it, generated it through software, or a member of the public posted it themselves. This protection applies specifically to the language-access obligations under this section.
A Practical Compliance Checklist
- Pull your ACS Table S1601 data now. Identify what percentage of your jurisdiction's population speaks each non-English language, and cross-reference against the LEP rate for each group.
- Run the two-part test. Flag any language where both the population share and the LEP share clear 20%.
- Apply the cap. If more than three languages qualify, identify the three largest by population.
- Set up your agenda translation workflow. Decide whether you're using a human translator, a digital translation service, or both, and make sure the process can run on your normal 72-hour agenda posting timeline.
- Translate your public meetings webpage into each applicable language and link it clearly from your homepage.
- Publish instructions on how a resident requests interpreter accommodation, and make sure front-desk and clerk staff know the process.
- Confirm your public comment procedure accounts for the double-time rule, unless you have simultaneous interpretation equipment in place.
- Designate a physical posting location near where your agenda is posted, where community members can add their own translations.
Frequently Asked Questions
Does SB 707 require translating every language spoken in my community?
No. Only languages that clear a specific two-part test qualify: at least 20% of your population speaks the language, and at least 20% of that group also has limited English proficiency. If more than three languages qualify, only the three largest by population require translation.
Do I need to translate the entire meeting packet?
No. Only the agenda itself needs translation, along with instructions on how to join remotely and register for public comment. Staff reports and supporting attachments don't require translation.
Is my agency required to provide an interpreter for public meetings?
Not exactly. SB 707 requires "reasonable assistance" for residents who bring their own interpreter, things like space and extra time, but doesn't require the agency to hire or supply one. Separately, if your agency limits public comment time, a longstanding Brown Act rule requires double time for speakers using an interpreter.
Can I get sued if a translation is inaccurate?
No. SB 707 includes a safe harbor provision protecting agencies from legal action over the content, accuracy, posting, or removal of a translation, regardless of whether it was produced by the agency, generated by software, or posted by a member of the public.
Can machine translation satisfy the requirement?
Yes. Digital translation tools are explicitly permitted to satisfy the agenda translation requirement under SB 707.
.png)