Each body's calendar is checked several times a day, on
whatever system it publishes to — Legistar, Granicus, CivicClerk, eScribe and
the rest.
2 · Agenda
The agenda is pulled as soon as it posts, so a meeting can
be previewed before it happens rather than only recapped after.
3 · Recording
When the recording appears it is downloaded and
transcribed. Some bodies publish official minutes instead; some publish
nothing at all.
4 · Recap
The recap is written from the best record available and
says which one that was.
Every recap says what it was written from — transcript,
official minutes, or the agenda alone — because that is what determines how much
you can trust it.
Every city council, school board, and district board in the
East Bay that we watch — with the agenda before it happens and a
plain-language recap after.
City, county, transit & utility boardsSchool boardsAgenda posted — click to read what's on it
Coming upagendas posted, meetings not yet held
Already recappedlast seven days
Past meetings
Email Digest Archive
Past SD7 digest newsletters as delivered, each covering one or more meetings. Click any entry to read the full briefing inline. Recent recaps also appear on This week for a week.
Memo
Pick any meeting we've covered and build a fuller staff-memo write-up than the recap: a formal header block, executive summary, attendance, the complete agenda with outcomes and votes, and source links. Print it or save it as a PDF.
Steers the ✨ AI staff memo's emphasis (not the instant memo). Emphasis only — facts still come from the meeting record. Max 500 characters.
Instant memo compiles the stored analysis into a document right here.AI staff memo has your configured summary model (⚙ Delivery → Summary model) write a deeper memorandum from the meeting's stored transcript — allow a few minutes.
Pick a meeting above and press “Instant memo” — the document appears here.
AI Memo Archive
Previously generated AI staff memoranda. Click any entry to open it above.
Who governs the East Bay
My Digest — your personal email subscription. We send at the scheduled delivery time; your copy covers exactly the bodies you choose here, written from the same recaps as the main digest. As the operator you already receive the main digest at its configured address regardless of this subscription — the main digest's own schedule and editorial settings are below.
Main digest — delivery & editorial (operator)
Standing topics to elevate in every digest — emphasis only, max 500 characters
(0/500).
Admin — subscribers, model usage, system health, and the dispatch endpoint. Delivery and editorial settings live on the My Digest tab (with everything else about how the digest reaches you); per-body coverage toggles stay on the “Who we watch” tab (PAS-2 renamed the label; the tab is still bodies).
Subscribers
Loading…
Endpoint & credentials
Must match the DISPATCH_SECRET function secret (Supabase Dashboard → Edge Functions → Secrets — alongside GH_REPO and GITHUB_TOKEN).
The built-in Supabase endpoint handles Save / Deliver / AI memos with no extra setup. Leave this blank. Pointing it at the retired Cloudflare Worker writes coverage to config.json, which every run regenerates — that save is erased within the hour.
Notes
Subscribers manage themselves on their My Digest tab; the toggle here is the admin override (their next visit shows the new state). Accounts and roles live in Supabase → Authentication → Users; granting app_metadata.role = "admin" is deliberately dashboard-only.
About
SD7 Monitor follows local government meetings across the Bay Area.
It finds meetings on its own, transcribes the recordings, and writes plain-language recaps.
We watch 28 bodies — city councils, school boards, transit agencies, and regional authorities — across Alameda and Contra Costa counties.
A digest email goes out on a set schedule, and this site is kept up to date continuously.
Where the meetings come from
We check each agency's own meeting archive every hour. Depending on the agency that means Granicus, Swagit, YouTube, or its official agenda page. A recap is written from the captions, the transcript, or the agenda — and every recap names which one it was written from. A few agencies publish video in a way that blocks automatic downloading; those meetings still get recapped, they just take longer to appear.
Cities & CDPs
Click a city to open its Civic Profile · unincorporated areas open the county profile · Green = monitored (pulse = meets this week)
28bodies tracked
9Bay Area counties
2active counties
How it works
Finds new meetings in the archives governments publish themselves: Granicus, Swagit, YouTube, and Legistar
Downloads the recording and transcribes the audio when there is one
Writes a plain-language recap of what happened
Publishes it to this site and sends the digest email
Sends a confirmation link to the new address; the change applies once confirmed. Your digest subscription follows your account email.
A rough draft of an idea
SD7 Monitor comes from the daily work of tracking hundreds of hours of
local-government meetings — meetings that are public by law, yet often
nearly incomprehensible without training, despite the public-notice
requirements and good-governance reforms of the Brown Act. This site is an
attempt to make that record legible: meetings discovered automatically,
transcribed, and summarized in plain language.
This week — upcoming meetings with their agendas, and recent recaps. Past meetings — the plain-language recap archive. Governments — each government as an organized ecosystem. Memo — turn any meeting we've covered into a formal staff memo. Who we watch — every government we follow; sign in to pick which
ones land in your own emailed digest.
⚠️ This project is in alpha — an early draft, still full of glitches
that will get smoothed out. Spotted one, or have a suggestion? Use
Send feedback in the account menu any time, or
email it now.
Appearance
Visual identity for the whole app. Skins restyle every surface via CSS variables — light/dark mode works inside any skin.