SB 707, the Brown Act Modernization Act, took effect January 1, 2026. By the time you read this, you’ve held a few meetings under the new rules and some of the implications are becoming clear. Some are still not.
This is a working summary — what changed, what’s still being figured out, and what your city or district should have updated by now. We’ll keep this article current as the AG and the courts work through the ambiguities.
What actually changed
SB 707 amended several sections of the Brown Act and added new ones. The substantive changes worth knowing:
Special meeting restrictions on certain compensation matters
New §54956(b)(2): a special meeting cannot be used to consider salaries, salary schedules, or compensation paid in the form of fringe benefits for executive employees. This has to happen at a regular meeting, with the disclosure required by AB 1344 (oral summary) still in place.
The intent is to prevent agencies from approving executive compensation on short notice with minimal public attention. The practical effect: agencies that historically used special meetings for salary adjustments need to move those items to regular meetings.
Hybrid meeting rules expanded
SB 707 substantially rewrote §54953 to clarify hybrid teleconference meetings. The key requirements:
- Members participating remotely must be visible and audible to the public attending in person.
- The agency must provide a method for the public to participate remotely (typically video or call-in).
- Each remote member’s location must still be identified, but the “publicly accessible at each location” rule was relaxed for “just cause” absences.
- “Just cause” absences (illness, family emergency, contagious disease, immigration concerns, physical or mental disability) are limited — the AB 2449 cap on these participations was carried forward.
Translation and language access
New §54953.7 requires written notice of available language services on agendas, and translated agendas where reasonably available. This applies to communities with significant non-English-speaking populations under the existing standards in CRC §1.10.
“Reasonably available” is doing a lot of work in this section. The AG has not yet issued guidance on what triggers the translation requirement. Most large agencies are erring toward providing translated agendas; smaller agencies are providing the notice and offering translation on request.
Disruption policy
SB 707 codified the legislative body’s authority to remove disruptive individuals from meetings, requiring a written policy adopted in a public meeting. The policy must include a process for warning before removal and a method for the removed individual to participate remotely if technology permits.
Most cities had de facto disruption practices. The new requirement is that the practice be in writing and adopted publicly. If your city doesn’t have a written policy yet, this is the first agenda item to add.
Meeting webpage requirements
Agencies must maintain a webpage for each legislative body that includes meeting agendas, supporting materials, and (where recordings are kept) links to the recordings. Recordings must be retained for at least 30 days but can be retained longer.
This formalizes what most cities were already doing. The new compliance question: is your webpage architecturally compliant? Direct, prominent link from the homepage; agendas accessible without navigation through multiple sub-pages.
Outreach planning
New §54954.6 requires agencies to develop an outreach plan for engaging the public with meeting information, particularly residents with limited English proficiency, residents with disabilities, and residents in underrepresented communities. The plan is policy-level — not a per-meeting requirement — but it must be adopted publicly.
What’s still being figured out
Three areas where the statute is clear but the implementation isn’t:
The translation trigger. “Reasonably available” for translation services has no AG opinion yet. Conservative practice: maintain a translation policy that defaults to English and provides translated materials within a defined window after request.
The disruption policy. The statute requires a policy but doesn’t specify content. The League of California Cities has published a model; most agencies are adopting variations of it. Expect this to evolve as it gets tested.
Just-cause documentation. The expanded hybrid rules require documenting just-cause absences. Some agencies are documenting in minutes; others are maintaining a separate log. The statute doesn’t mandate one approach but does require the documentation be retained.
The compliance checklist
If you haven’t already, do these now:
- Adopt a written disruption policy, in a regular meeting with public comment.
- Adopt an outreach plan, similarly.
- Update agenda templates to include the language-access notice on every regular meeting agenda.
- Audit your meeting webpage: is the link prominent on the homepage? Does the page contain agendas, materials, and recordings (where available)?
- Move executive compensation items off any standing special-meeting cycle.
- Update your agenda-publishing software to flag agenda items that need new SB 707 disclosures.
- Train staff on the new just-cause documentation requirements for hybrid participation.
Where software automates this
Most of SB 707’s compliance burden is on the clerk: tracking what changed, applying it to every agenda, documenting where required. Modern compliance engines (CivicCA includes one; so do a few others) can flag SB 707-specific issues automatically:
- Special meetings that include compensation-related items
- Missing disruption-policy reference
- Hybrid-participation just-cause logging
- Agendas missing the language-access notice
- Eligibility-body verification (some bodies are excluded from teleconference rules)
The compliance check happens at agenda-publish time, before the public sees anything. The clerk gets a list of issues to resolve.
The bottom line
SB 707 is the largest change to the Brown Act since AB 1234 in 2005. None of the individual provisions are difficult; the volume is what catches agencies out. If you implemented half of the checklist above by January 1 and the other half by your March meeting cycle, you’re in better shape than most.
If you’re still operating on pre-SB 707 templates and procedures in April 2026, you’re accumulating exposure. The cure-and-correct procedure under §54960.1 still applies; one motivated complaint and you’re re-doing actions and paying fees.
For agency-specific guidance, consult your counsel. CivicCA maintains a more detailed SB 707 reference at civicca.com/sb707.