Los Angeles County agenda changes

What this page is11,211 rows held · newest sealed read 2026-08-29

• We caught 17 changes to Los Angeles County meeting records. We read Los Angeles County 68 times and its meeting list had meetings on it 47 of those times; these counts come from those 47 reads.
• We hold 11 meetings across 1 body, and 1,132 agenda items across 37 bodies, for Los Angeles County.
• The meeting list and the item list are not the same Los Angeles County file. The meeting list we hold is the Board of Supervisors calendar and nothing else. Of the 1,132 items we hold, 7 sit with a body on that meeting list and 1,125 sit with one of 36 other bodies. The biggest of those are Audit Committee (154), Los Angeles County Youth Commission (152) and LGBTQ+ Commission (100).
• 367 items moved from one stage to another, in the words Los Angeles County uses itself. We do not translate them.
• 137 items had the wording rewritten after already being on a published agenda. A further 9 were spacing or punctuation put right in a title, which we count but rank last.
• Nothing we compared has moved on a Los Angeles County meeting record since 9 Aug 2026. We keep reading it and saying so is the honest answer, not a bigger number. The items on those agendas do still move. We never compared 2 pairs of reads inside that stretch, because our own two reads were more than 3 days apart: 10 Aug 2026 to 18 Aug 2026 and 18 Aug 2026 to 27 Aug 2026. Anything that moved and moved back across one of those is not something we looked at, so read this as nothing we saw rather than nothing happened.

Real rows out of our sealed copies

These are rows we read out of dated copies we keep ourselves. The live source shows today only, so once a row moves, what it said before is gone from the place you would go to look.
Source: the meeting records of Los Angeles County, read through Legistar, the council-records system run by Granicus. The records are theirs; the dated copies and the comparison between them are ours.

What this page cannot tell you

• The meeting list and the item list come from two different Los Angeles County files and they do not line up. 1,125 of the 1,132 items we hold sit with a body that never appears on the meeting list we hold, so do not read the item count as the docket of any one body.
• On 21 of our 68 reads, Los Angeles County returned a meeting list with nothing on it. We ask for the meetings dated in the last 14 days and ahead, and on those days Los Angeles County had none. That is a short agenda, not a failed read: the read worked every time and the answer was an empty list, not an error. Its meeting list has come back with nothing in that window on every read since 29 Aug 2026. The last copy of it that had anything on it at all is ours from 28 Aug 2026, and the latest meeting on that copy is 1 Sep 2026. Its agenda items are current to 29 Aug 2026.
• We can only show you a change that happened between two of our reads. If a council put an agenda up and took it down again inside one day, we did not see it and we will not pretend we did. We missed 12 days: 19 Jun 2026, 4 Jul 2026, 8 Jul 2026, 15 Jul 2026 and 8 Aug 2026, plus a 7-day stretch from 11 Aug 2026 to 17 Aug 2026. Anything that moved and moved back inside one of those gaps is not in this feed, and we will not claim it is.
• We hold six governments and no others: Chicago, Seattle, Austin, Phoenix, Columbus, and Los Angeles County.
• We ask Los Angeles County for the meetings dated in the last 14 days and ahead, and for the items Los Angeles County edited in the last 7 days. That window is what we hold, not the whole docket. So a row leaving one of these lists means it left this file: it does not mean the meeting was cancelled, the item was killed, or that anyone named on it went away.
• A meeting dropping off the list is usually the list rolling forward past the meeting date, not a withdrawal. That happened 3 times here and is kept out of the table above on purpose.

More from this feed

• Up one level: City and county agenda changesThe whole feed, its price, and how the file arrives.
• What is and is not in this feedEvery source we read for it, how often, and the ones we refuse to collect.