O
Aliso Viejo

Methodology

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

What we hold for Aliso Viejo

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
30
Bodies covered
5
Earliest record
January 7, 2026
Latest meeting
October 21, 2026
Agendas30 of 30 (100%)
Recordings30 of 30 (100%)
Transcripts18 of 30 (60%)
Approved minutes25 of 30 (83%)

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

Meetings with extracted decisions7 of 30 (23%)

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

Known source problems

  • September 23, 2026 · City Council Special Meeting - Aliso Viejo State of the City — Source video returned 404 (clip removed by city): https://alisoviejoca.granicus.com/DownloadFile.php?view_id=3&clip_id=789
  • August 5, 2026 · City Council — Source video returned 404 (clip removed by city): https://alisoviejoca.granicus.com/DownloadFile.php?view_id=3&clip_id=785
  • July 1, 2026 · City Council — Source video returned 404 (clip removed by city): https://alisoviejoca.granicus.com/DownloadFile.php?view_id=3&clip_id=792
  • May 6, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • April 15, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • April 1, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • March 31, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • March 18, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • February 4, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
  • January 21, 2026 · City Council — Transcribe: faster-whisper failed: Command failed: /opt/whisper-env/bin/python3 -c import json import sys from faster_whisper import WhisperModel model = Whis
Bodies covered (5)

City Council · City Council Special Closed Session and Regular Meetings · City Council Special Closed, Study Session, and Regular Meetings · City Council Special Meeting - Aliso Viejo State of the City · City Council Special and Adjourned Meetings

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