11/3/26 City Council Meeting
Council tightens homeless camping ordinance
The council's main decision was a second round of changes to Chico's ordinance on camping on public property: after a motion to delay the vote until the city's broader homelessness plan is finished failed 3-4, the council passed an amended version of the ordinance 5-2, adding provisions that cleared areas must stay clear and that a camper's required 48-hour warning and shelter assessment need only be given once. The consent agenda — routine items bundled into a single vote — passed 7-0, with two members registering no votes on the related ordinance restricting camping in parks. The Finance Committee reported that the city's unfunded pension liability sits at about $167 million, down from the prior year but still a concern. Public comment ranged from a proposed low-cost shelter model to unrelated complaints about local media and public health. The council also voted to direct staff to bring back a redrafted shopping cart ordinance.
What happened, item by item
The council was scheduled to proclaim November as Homeless Youth Awareness Month, presented by representatives of the Butte County Office of Education. The recording does not capture this portion of the meeting clearly enough to report further detail.
The consent agenda bundles routine items into a single vote. This batch included final adoption of an ordinance updating park rules, a related ordinance restricting camping in parks, a year-end budget adjustment, a budget change to fund new Police Department staffing and $15,500 in redaction software for public records requests, two utility easement purchases tied to the North Esplanade reconstruction project, final maps for two housing subdivisions (Autumn Leaf Estates Phase 2 and a Habitat for Humanity project on Wisconsin Street), and approval of prior meeting minutes. One speaker addressed the consent agenda, urging the council to consider a "tiny home" shelter model as a lower-cost alternative to repeated encampment sweeps, saying "let's save some money and clean up our parks and downtowns, too," and arguing such programs cost roughly $4,000 per resident per year compared to an estimated $80,000 per year for someone who remains unsheltered. The consent agenda passed 7-0, with Councilmembers Goldstein and Hawley recorded as no votes on item 2.2, the camping-in-parks ordinance.
This item returned for further changes to an ordinance governing homeless camping on city property, part of an ongoing revision process shaped by the Warren Settlement Agreement — a legal settlement that requires the city to give notice and a shelter assessment before clearing an encampment. At the prior meeting the council had already changed how many days someone may sleep overnight in a recreational vehicle, moving it from the original seven days to three and then, as a compromise, to five; it had also extended the city's notice requirement from 24 to 48 hours.
Before voting on the ordinance itself, the council considered a motion to table the item until the city's five-year Unhoused Strategic Plan — then gathering public input and headed to the council on November 17 — could provide more data to guide any changes. That motion failed 3-4.
The council then voted on the ordinance as amended from the dais by Councilmember O'Brien, who said the version in front of the council had "a significant omission." His amendment added two things: that once an area such as a playground, bike path, or creek is cleared of camping, it must stay clear, and that once a person receives the 48-hour warning and a shelter assessment, the city does not have to repeat that same warning to the same person every time. Supporters argued this closes a loophole in which someone could move a short distance away, restart the 48-hour clock, and create a repeating cycle the city has dealt with for years; Chico Police Department leadership confirmed the department already has a dispatch system that can flag whether a person has previously received a warning, making a one-time notice workable without extra burden on officers.
Opponents raised several concerns. One member argued that lowering the recreational-vehicle camping allowance to five days instead of the original seven was a last-minute, arbitrary change made at the prior meeting, when every public speaker and several council members had argued against shortening it. Others said the new "stays clear" language left basic questions unanswered, such as how close a camper could move before being considered back in a cleared area, and suggested the city instead adopt a model ordinance circulated by the governor's office, which defines a 200-foot buffer around a cleared site and specific "exigent circumstances" for sensitive areas like waterways. Several members also said amending the ordinance clause-by-clause from the dais, while the city was simultaneously developing its broader Unhoused Strategic Plan, risked locking in details without enough data or community input, and preferred to handle any changes as part of that larger plan.
Two residents spoke on the item. One, Lynn Oberholzer, thanked the council for its handling of encampments near her neighborhood, saying "that side of Chico is so much better than it used to be after the alternative site was cleaned up," and added, "I understand very well what the Warren Settlement Agreement was. I've read it," pushing back on criticism that the council hadn't done enough. The second speaker argued the city's broader approach prioritizes enforcement over housing, saying "housing is the issue, homelessness is the outcome," and cited city data showing Chico has met only a small fraction of its state low-income housing targets over the past two decades while exceeding its higher-income targets.
The motion to table failed 3-4 (yes: Goldstein, Hawley, Winslow; no: O'Brien, van Overbeek, Bennett, Reynolds). The amended ordinance then passed 5-2 (yes: O'Brien, van Overbeek, Winslow, Bennett, Reynolds; no: Goldstein, Hawley). Because the ordinance was amended from the floor, staff said it will need to come back for at least one more reading before taking effect.
The Finance Committee chair presented an update on CalPERS, the state pension system, reporting the city's combined unfunded pension liability is about $167 million, funded at 71% — an improvement from roughly $180 million a year earlier, driven by stronger investment returns. The city's required annual payment toward that shortfall is about $17.5 million for the coming fiscal year, projected to rise to about $18.5 million the year after. No council vote was required; the committee also plans to review the city's insurance and risk-management strategy, its cash investment policy, and to start receiving quarterly budget-versus-actual updates.
City Manager Gillian Haen gave a verbal update: a public town hall on the draft Unhoused Strategic Plan was scheduled for the following evening, with the plan itself headed to the council on November 17; she described attending a national city managers' conference, a Fire Academy live burn exercise, Cal Water's 100th anniversary event, and the Treat Street Halloween event with the police chief and fire marshal. She also announced that Community Development Director Brendan Vieg is departing and that the city has engaged a search firm, Bob Marine Associates, to begin recruiting a replacement. No vote was taken.
A councilmember asked staff to redraft the city's shopping cart ordinance so that responsibility for retrieving stray carts falls more clearly on retailers, arguing that someone in possession of an abandoned cart is effectively holding stolen property. The request to put this on a future agenda passed 7-0.
“That side of Chico is so much better than it used to be after the alternative site was cleaned up.”
Votes & roll calls
Votes on individual items
- Goldstein and Hawley voted no on item 2.2. 2.2 · ORDINANCE OF THE CITY OF CHICO AMENDING TITLE 12R OF THE CITY OF CHICO MUNICIPAL CODE TO REGULATE CERTAIN ACTS OF CAMPING IN PARKS
The consent agenda is approved as one motion, so the roll call above is the vote on the whole bundle, recorded as the clerk called it. Before that vote, these members said they were voting differently on the items listed.
After the substitute motion to table failed 3-4, the council returned to Councilmember O'Brien's original motion seconded by Councilmember van Overbeek.
How they got there (1)
↳ Substitute motion to table the item; after it failed 3-4 the council fell back to the original motion by Councilmember O'Brien.
Notable moments
- The meeting opened with an audio problem — strings of "test" and silent "you" cues in the recording — before staff confirmed the stream was fixed on all platforms and thanked a remote service provider for troubleshooting it.
- In her report, the city manager noted she was the first Chico city manager to suit up and go through a live fire exercise with Fire Academy recruits, and that the city held its first-ever candidate orientation session for people running for local office.
- Explaining his vote in favor of the amended camping ordinance, one member said he feared that without the changes, the city would otherwise face "a repetitious procedure" similar to what it has experienced over the past five years under the settlement.
Public comment
Two people spoke during the general public comment period, and both raised subjects unrelated to items on the agenda.
- One speaker, Bo Powell, criticized Action News Now's management for not returning his calls and alleged a cover-up related to agricultural pesticide spraying (naming methyl bromide), along with claims about a past overpayment from Butte County to the city and allegations involving police and fire department raises; these claims were not substantiated by other sources in the meeting.
- A second speaker, Kevin Walters, raised concerns about COVID-19 vaccines, calling for them to be stopped, and also referenced unrelated topics including chemtrails and abortion.
- A public town hall on the draft Unhoused Strategic Plan is scheduled for the evening after this meeting (6–8 p.m., Council Chamber).
- The Unhoused Strategic Plan itself is scheduled for council consideration on November 17.
- The camping-on-public-property ordinance (item 5.1) will return for at least one more reading to formalize the amendments adopted at this meeting.
- A redraft of the shopping cart ordinance will come back to the council for discussion at a future meeting.
- The next council meeting is November 17, with the regular meeting at 6:00 p.m. (closed session beforehand, starting at 5:00 or 5:30 p.m.)
Every item as published on the official agenda. Timestamps play the moment that item came up. The recap tab covers what actually happened.
- 1. CALL TO ORDER - November 3, 2026, City Council Meeting
- 1.1. Invocation - Carol Raner, Christian Science Church Not in the recording
- 1.2. Pledge of Allegiance to the Flag Not in the recording
- 1.3. Roll Call Not in the recording
- 1.4. November 3, 2026, Closed Session Announcements - City Attorney Ryan R. Jones Not in the recording
- 1.5. Proclamation: Homeless Youth Awareness Month - Cambria Picket and Eileen Gonzalez of Butte County Office of Education Not in the recording
- 2. CONSENT AGENDA - All matters listed under the Consent Agenda are to be considered routine in nature.
- 2.1. ORDINANCE OF THE CITY OF CHICO AMENDING TITLE 12, CHAPTER 12.18 OF THE CITY OF CHICO MUNICIPAL CODE TO REGULATE CERTAIN PARK RULES AND REGULATIONS - final reading and adoption by reading of title only staff report ↗
- 2.2. ORDINANCE OF THE CITY OF CHICO AMENDING TITLE 12R OF THE CITY OF CHICO MUNICIPAL CODE TO REGULATE CERTAIN ACTS OF CAMPING IN PARKS - final reading and adoption by reading of title only staff report ↗
- 2.3. FY2025-26 SUPPLEMENTAL APPROPRIATION/BUDGET MODIFICATION NO. 2026-ASD-008 FY2025-26 Supplemental Appropriation/Budget Modification addresses year-end budget adjustments necessary to align appropriations with actual revenues, expenditures, and operational activity. These adjustments primarily consist of reallocations within existing budget authority, recognition of additional revenues and corresponding expenditures, interfund transfers, and capital project adjustments. (Barbara Martin, Administrative Services Director) staff report ↗
- 2.4. POLICE DEPARTMENT STAFFING MODIFICATIONS AND SUPPLEMENTAL APPROPRIATION At its October 20, 2026, meeting, the City Council authorized staffing modifications within the Police Department to address increasing Public Records Act requests. Staff is requesting approval of an amendment to FY 2026-27 Budget Appendix B-3 to reflect the authorized staffing changes and a supplemental appropriation of $15,500 for Veritone redaction software. These actions will formalize the City Council’s prior direction and support more efficient processing of public records requests. (Barbara Martin, Administrative Services Director) staff report ↗
- 2.5. ACQUISITION OF PUBLIC UTILITY EASEMENTS RESOLUTION OF THE CITY COUNCIL AUTHORIZING THE CITY MANAGER TO EXECUTE THE PURCHASE AGREEMENT AND ANY RELATED DOCUMENTS IN CONNECTION WITH THE ACQUISITION OF A PUBLIC UTILITY EASEMENT LOCATED ALONG THE ESPLANADE (PORTION OF APN 006-220-013) - SUSANA RAMIREZ GUZMAN, A MARRIED WOMAN AS HER SOLE AND SEPARATE PROPERTY RESOLUTION OF THE CITY COUNCIL AUTHORIZING THE CITY MANAGER TO EXECUTE THE PURCHASE AGREEMENT AND ANY RELATED DOCUMENTS IN CONNECTION WITH THE ACQUISITION OF PUBLIC UTILITY EASEMENTS LOCATED ALONG THE ESPLANADE (PORTION OF APN 006-550-015) - PREMIER SOLANO LLC, A CALIFORNIA LIMITED LIABILITY COMPANY Adopt - resolutions authorizing the City Manager to execute the Agreements for Acquisition of Public Utility Easements and any related documents necessary to acquire easements in association with the North Esplanade Reconstruction Project. (Brendan Ottoboni, Public Works Director - Engineering) staff report ↗
- 2.6. FINAL MAP PENDING COMMUNITY DEVELOPMENT DIRECTOR’S APPROVAL: SUB24-01, Autumn Leaf Estates Phase 2 Final Map (Epick Homes) Pursuant to CMC 18.05.010.A, final maps shall be noticed on the City Council agenda within 10 days of action by the Community Development Director. Final maps are administrative actions that confirm compliance with an approved tentative map. Once approved, the final map is recorded with Butte County, completing the legal recording process. The subject final map subdivides an approximately 9.95-acre parcel located west of Henshaw Avenue and north of Nord Avenue into 34 single-family residential lots, constituting Phase 2 of the Autumn Leaf Estates Subdivision. (Brendan Vieg, Community Development Director)
- 2.7. FINAL MAP PENDING COMMUNITY DEVELOPMENT DIRECTOR’S APPROVAL: PM22-01, Wisconsin Street Parcel Map (Habitat for Humanity) Pursuant to CMC 18.05.010.A, final maps shall be noticed on the City Council agenda within 10 days of action by the Community Development Director. Final maps are administrative actions that confirm compliance with an approved tentative map. Once approved, the final map is recorded with Butte County, completing the legal recording process. The subject final map subdivides an approximately 1.3-acre parcel into four residential lots. The property is located north of Wisconsin Street, east of Boucher Street, west of Everett Street, and south of Little Chico Creek. (Brendan Vieg, Community Development Director)
- 2.8. APPROVAL OF COUNCIL MEETING MINUTES OF 10/6/26 & 10/21/26 staff report ↗ staff report ↗
- 2.9. ITEMS REMOVED FROM THE CONSENT AGENDA
- 3. PUBLIC COMMENTS - Members of the public may address the Council at this time on any matter not already listed on the agenda and within the jurisdiction’s authority. Comments will be limited to three minutes or as determined by the Mayor based on the number of speakers. The Council cannot take any action at this meeting on requests made under this section of the agenda.
- 4. PUBLIC HEARINGS - None
- 5. REGULAR AGENDA
- 5.1. ORDINANCE OF THE CITY OF CHICO AMENDING TITLE 9, OF THE CITY OF CHICO MUNICIPAL CODE TO REGULATE CERTAIN ACTS OF CAMPING ON PUBLIC PROPERTY - final reading and adoption by reading of title only staff report ↗
- 5.2. ACCEPTANCE OF OCTOBER 21, 2026 FINANCE COMMITTEE MEETING REPORT - included three additional items At the 10/21/26 Finance Committee meeting, the committee was presented with an update on the CalPERS Actuarial. In addition, several items were requested to be added to the next Finance Committee Agenda. (Report - Councilmember van Overbeek, Chair, Finance Committee) staff report ↗
- 5.3. ITEMS ADDED AFTER THE POSTING OF THE AGENDA
- 6. REPORTS AND COMMUNICATIONS - The following reports and communication items are provided for the Council’s information. No action can be taken on items under this section unless the Council agrees to include it on a subsequent agenda.
- 6.1. CITY MANAGER’S REPORT - Verbal Report, City Manager Gillian Haen
- 6.2. COUNCILMEMBER REQUESTS - Pursuant to AP&P 10-10, Councilmembers may verbally request an item to be agendized at a future meeting. After stating what the item would be, a majority vote of Council is needed in order for staff to agendize.
- 7. ADJOURNMENT - Adjourn to November 17, 2026, Closed Session meeting at 5:00 p.m. or 5:30 p.m. followed by the Adjourned Regular meeting at 6:00 p.m. in the Council Chamber, 421 Main Street, Chico. staff report ↗
- 1. CALL TO ORDER IN THE COUNCIL CHAMBER AT 421 MAIN STREET, CHICO, CA.
- 1.1. ROLL CALL
- 2. CLOSED SESSION AGENDA - Members of the public may address the Council at this time on any item on the Closed Session agenda, with comments being limited to three minutes or as determined by the Mayor based on the number of speakers.
- 2.1. CONFERENCE WITH LEGAL COUNSEL - ANTICIPATED LITIGATION: Pursuant to Cal. Gov. Code Sec. 54956.9(d)(4): Two (2) cases.
- 2.2. CONFERENCE WITH LABOR NEGOTIATOR: Pursuant to Cal. Gov. Code Sec. 54957.6 Negotiator: Laura Izon (Atkinson, Andelson, Loya, Ruud and Romo Law Firm (AALRR)) & Barbara Martin, Administrative Services Director Employee Organizations: Chico Fire Management Employees, Chico Management Employees, Chico Police Management, Chico Police Officers Association, Chico Public Safety Association, Confidentials, International Association of Fire Fighters, Service Employees International Union - Trades & Crafts, Stationary Engineers Local 39, United Public Employees of California - Local 792
- 2.3. PUBLIC EMPLOYEE PERFORMANCE EVALUATION: Pursuant to Cal. Gov. Code Sec. 54957(b). Title: City Clerk
- 2.4. CLOSED SESSION ITEMS THAT AROSE AFTER THE POSTING OF THE AGENDA
- 3. ADJOURNMENT - Adjourn to the City Council Meeting on Tuesday, November 3, 2026, at 6:00 p.m.
Machine transcript (local Whisper transcription), lightly cleaned — expect imperfections. Timestamps play that moment right here; the official video is one click away too.
Nothing was recorded here.
test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test
Yeah. It's fixed. And we have it on all platforms, streaming, channel 11, as well as Zoom. So thank you, Council, for letting us take that quick break and for our service provider who remoted in. Thank you, Angie. All right. Consent agenda. All matters listed under the consent agenda are considered routine in nature and can therefore be enacted with one motion. Are there any no votes? Oh, I'm sorry. I didn't look to my left. I looked to my right.
All right. Consent agenda. All matters listed under the consent agenda are considered routine in nature and can therefore can be enacted with one motion. Are there any no votes or Council disqualifications? I'd like to register a no vote for item 2.2. All right. Same registering no on 2.2. All right. Do we have any speakers for consent? We do. We have one speaker on consent.
Wow. That makes it a lot easier. Thank you. Council, staff, thank you. Let's save some money and clean up our parks and downtowns, too. Our state shelter team is 25 people with letters of support from several other nonprofits who are moved by our deadly yet preventable shelter crisis. What does a shelter crisis mean in Chico? Spending millions on sweeps and who knows how much on fences and the unrecovered debt in the millions and rising annually at Enloe Hospital. By some estimates, it can cost Chico taxpayers $80,000 per person per year to leave someone unsheltered. Compared to $4,000 a year, a residence pays for a tiny home in a tiny home village like Opportunity Village in Woodland, California.
After visiting several homeless programs and getting their documents, NIST found a few features common to successful shelter programs like a common building for meetings, food prep, building relationships and protection from extreme weather, co‑management from a local nonprofit that will listen to input from the participants, limit program size to effective group size. Effective programs are between 4 and 30 people in size. Mandatory weekly meetings so participants get to know each other, build trust, develop peer group pressure to be a good citizen. North State Shelter Team includes a licensed clinical social worker, experienced case managers, two nurses, many trained volunteers who, after years of the operation of our award‑winning mobile showers program, have developed a unique level of trust with our unhoused community.
That gives us the confidence and the skills to ensure the success of our tiny home program, a program that will save our community money and help clean up downtown. In fact, we offer to cover the costs of this program. Thank you. Thank you. He's our only speaker. All right. Consider a motion. Move to approve. Second. Okay. There's a motion and a second to approve the consent agenda as noted with Councilmember Hawley and Councilmember Goldstein voting no on item 2.2, and I'll read those ordinance titles. Ordinance of the City of Chico amending Title 12, Chapter 12.18 of the City of Chico Municipal Code to regulate certain park rules and regulations, final reading and adoption. And then item 2.2, Ordinance of the City of Chico amending Title 12.R of the City of Chico Municipal Code to regulate certain acts of camping and parks, final reading and adoption.
Councilmember Goldstein? Yes. Councilmember Hawley? Yes. Councilmember O'Brien? Yes. Councilmember Van Overbeek? I'm sorry, Debbie, are we voting on the entire agenda except 2.2? No, we're doing all of them because it wasn't removed. They just registered a no vote. Yes. Okay. Councilmember Winslow? Yes. Vice Mayor Bennett? Yes. Mayor Reynolds? Aye. Carries 7-0. All right. Public comment. Members of the public may address the Council at this time on any matter not already listed on the agenda and within the jurisdictional authority. Comments will be limited to three minutes as determined by the Mayor. How many speakers do we have? We only have two and checking to see if we have any on Zoom, but Bo Powell followed by Kevin Walters.
And while you're coming up, I missed the last sentence. Council cannot take action at this meeting on these requests made under this section of the agenda. Okay. Two. Yes. Hello. Last time I was here, last meeting, I kind of got scolded. I was in the back talking to Bella Barbosa of Action News. I was giving her my name because when I called, I tried to talk to the new boss, Hayley Watts. She never returns calls. So trying to be decent, I gave her an opportunity. She still didn't return my phone calls. I guess being the boss at Action News is a lot like being the chief of police or a fire chief here in town, because if you admit that the company you work for has been covering up the illegal crime, the ag spray, well, that affects everybody that used to work there.
On Monday, on Action News, they announced that Chico State is going to have a farm advisory thing on the internet now. So that farm advisory obviously knows the chemicals that have been used, the methyl bromide that I've been telling you about, that caused me to have seizures for years. Now, I have been exposed to it prior, so I'm probably a little more sensitive. But I went to the doctors for 18 years now. They act like I'm just talking about a bunch of nothing. Well, you know who knows I'm not talking about a bunch of nothing? I came here and I told you about the overpayment that Butte County paid the city of Chico. Right at the same time when they were legalizing the methyl bromide and during the next 10 years.
And Chico PD got a big, big raises during that time. Wednesday after the county supervisor meeting on Action News, you know, they had the thing about the solar panels. Well, you know who knows about how Butte County and Chico works? That company. They offered to pay off the sheriff and the firemen. If you want to go around what the citizens want, you pay off the cops and the fire department. Thank you. Thank you, Kevin Walters. So COVID is still being offered at the hospitals and the VA and the COVID shot. It's murdered 17 million people now. And it's still being offered. Not sure really why it's always been labeled a weapon of mass destruction. It's got the highest warning label from the FDA.
So that's Fauci's wife, by the way. And it's a I think it's black box warning. So wondering why it's still being offered. It's a weapon of mass destruction. It doesn't stop the spread or keep you from getting it. And it's nanotechnology, self-assembling, blood clots, people planking, dying from it. And we have the chemtrails, too, still. It's been stopped in one state, Florida. It's $100,000 fine for chemtrails. Don't know why we can't stop it. It's the COVID shots been stopped in seven states labeled as a weapon of mass destruction. So just wondering when you guys are going to stop the murdering, if you ever are. Doesn't seem like it. Would you have to be arrested for murder charges? We put murder charges against you guys.
And then maybe you'll do something about the managers of the hospitals that are still offering it. Abortion was created on a lie, too. That's murder, too. Jane Roe was never raped. She's a Christian now, pro-life. But abortion's still happening. That's murder. So I just kind of want to end the idiocracies and stuff. And the murdering, you know, you can look at other states. This is the United States. There's a state that doesn't have homelessness, Idaho or Ohio, you know. Like Florida is charging $100,000 for chemtrail pilots. There's some money for you all, you know. Gives the cops something to do. Geotrack the planes, get them with a $100,000 fine. Then you can house the homeless and stuff.
So a detox for the shot has been collodial gold and collodial silver and collodial copper. And a lady at the health food store said that there's a, it's like a counter-spike protein thing. It was about $60 for that, though. So it'd be nice if those COVID shots could stop and stop murdering people, I think. I mean, sounds pretty intelligent to me, but oh well. Thank you. All right. Item 5.1, Ordinance of the City Council Amending Title IX of the City Municipal Code. We have a report from our City Attorney, Ryan Jones. Yes. Thank you, Council. This is returning, we've discussed it a couple of meetings. In the last meeting, there was a motion on this particular ordinance, the other two were already passed earlier in this evening, related to the vehicle time.
And so it was three days, and the ordinance has been extended to five days. I'll show that on the slide where that is. That would be under 9.20-040, letter B. That was one change as part of the first reading. The other change was to, in light of the concerns about funding and the 24-hour notice being too short related to guidelines, I think the Council's motion was to change that to 48 hours. So that's in about six different spots. I'm just kind of highlighting it there, in 050C and D, letters E and F. So anywhere where it was a 24-hour notice has been modified to a 48-hour notice. Those are the only modifications that were made from the last discussion that the Council had. If there's any questions, this could count as the second reading.
Those changes were made subsequent, as the first reading, two weeks ago. Happy to answer any questions you may have. That's my presentation tonight. Any questions before we go to speakers? No? All right. How many speakers do we have? We have two. Lynn Oberholzer and Scotty Franzische. So Lynn is first. »» Well, good evening everybody. For a change, I don't think I'm going to run the timer down to zero. I've been here many times in the last year and a half. And really, I just wanted to say thank you to every single one of you who is up here. This was a pretty good learning experience for me, being here and watching you all vote. I've been here in the past, but it's been a while about other issues.
I just really appreciate, and so does everyone on my end of town and probably all over town, but I guess I was focusing in on the alternative site. It seems to me like it doesn't really matter. Some of you have different beliefs and I don't know, political parties or whatever. I'm not really too big on that. But I just really appreciate that every one of you listened and there were a few 7-0 votes on some issues that I brought up. That side of Chico is so much better than it used to be after the alternative site was cleaned up. Everybody out there, we are very grateful for the things that we have read in here. We're really hoping that you, you know, stick to it and enforce. Actually out on my end of town, it hasn't been five years we've been living with this.
It's been since the campfire because camping started out there after the campfire and then COVID allowed it because there were rules about that. And I don't like hearing people bad mouth what you guys have done over the last five years because I think you've done a lot. But with your hands partially tied behind your back. I understand very well what the Warren Settlement Agreement was. I've read it. And it seems like a lot of people just bad mouth all of you for not doing more. And I think you've done a really good job given the situation. And there's some new things that have happened in the last few years. I'm glad to see different shelters that are here. Many homes over near behavioral health, the new senior disabled homeless units going up out on 32.
The pallet shelter. I'm glad to hear it's saying. Anyway, I just want to say thank you very much. I appreciate what you've done. And I hope you can do even more to make this a nicer place for some of us. And I kind of want to say also, I know this is election day, and I kind of like the combination up there. It's election day. But anyway, thank you very much. Thank you. Scotty Francis shed. Good evening, council members. My name is Scotty transition. I want to talk to you about something that seems to be getting lost in these discussions about camping ordinances, enforcement and homelessness, housing. Housing is the issue. Homelessness is the outcome. And no matter how many ordinances you write, how many citations you issue and how many encampments you clear, you cannot ordinance your way out of a housing crisis.
Let's talk about the numbers for decades. Chico has known exactly how many houses we need, including houses for low income residents. And from 27 to 2014, Chico achieved just 17.6% of its low housing income targets. In 2014 to 2022, we achieved only 30%. During that same second period, we achieved 213% higher income housing targets. Think about that. We exceeded our higher income housing targets by more than double while failing to reach even a third of our low income targets. That wasn't because we didn't know what kind of housing we needed. We had the numbers. We even considered policies, including inclusionary zones that could have helped address the shortage. Then we abandoned them. And now, after all these years, we're spending our time debating whether people experiencing homelessness can sleep.
How did we become, or how did that become a solution to a housing shortage? We invested millions of dollars into shelters, services, facilities and enforcement. And I'm not saying those services don't help people. They do. And I do know we need them. But I want to know something. How many people have actually helped get out in permanent housing? Because filling shelter beds isn't the same as ending homelessness. Moving someone from tent to temporary shelter isn't the same as housing them. And moving someone from one sidewalk to another certainly isn't solving anything. Now let's look at the city's proposal, five-year strategic plan. The city identifies over 1,065 people experiencing homelessness, including 360 living unsheltered.
And the plan's main numerical reduction goal, just 90 fewer people, 90, 90 people. That's the goal in five years. And that's not even 90 people permanently housed. Nowhere in the 27-page plan. That's time. Thank you. That's time. Thank you. Thank you. He was our last speaker. All right. All right. Council Member O'Brien. Thank you, Mayor. So I read through this because details matter and I think there is a significant omission in the ordinance as currently written. So one, I'm going to suggest we need a provision that states that once we clear an area, say children's playground, a bike path, one mile, or vulnerable creeks, it stays clear. No more tents or camping allowed. Second, when we provide a 48-hour warning to an individual about illegal camping and provide an assessment to that individual about available services, we should not have to repeat that over and over and over.
That is the biggest flaw in the Warren settlement. And that, unfortunately, was due to a judge's ruling that has harmed our community, including the homeless, for five years. If we leave the ordinance as written, this will be the likely scenario. A 48-hour warning and assessment will be provided to a camper with an encampment. Within that 48-hour window, the camper could simply move 100 feet down a creek, bike path, or park and start the 48-hour clock process again. This would truly create the whack-a-mole situation we want to avoid. We have learned hard lessons that these legal details matter, that we should not leave legal interpretation to others. Without an ordinance, with these clear and specific details, as I articulated, that is exactly what we will be doing as a city, leaving a void for someone else to fill.
All right, Councilmember Hawley? This isn't originally why I pressed the button to speak. I'm a little confused now. Your proposal is to add to this ordinance. Can you repeat that? So one, we need a provision that states that once we clear an area, say a park, a creek, or whatever, it stays clear, no more tents or camping allowed. That's number one. Number two, when we provide a 48-hour warning to an individual that includes an assessment about available services, we do not have to repeat that over and over and over. That warning and assessment is done one time, one individual, period. That's what I'm suggesting. I don't even understand how that can be tracked. And a lot of these people aren't easily identifiable by the same officer.
Like how is an officer expected to know exactly? We identify them all the time. That's actually quite easy for our officers to do. But also pair up, has this person in the past for however much time has been given shelter options before? It's one assessment, one warning for one person. That's actually pretty easy to track. Okay. And a year later, if they get cleared from the same area, all of a sudden, whatever law enforcement officer talks to them no longer has to give them shelter options? I feel that No, we can always provide shelter options. We can always provide those additional details. We do not have to have that encapsulated in our ordinance. That's unnecessary. I thought the proposal was to include it in the ordinance.
It is. What I'm saying is if an officer, and we do this all the time, if they want to do something that goes beyond the ordinance, they can do that. They can provide all the shelter options they want. We do that all the time. Very appropriate. I think there's more to digest here. But my original reason for asking to speak, thank you, Mayor Reynolds, is just to comment that is that, you know, banning overnight camping in a recreational vehicle for five instead of seven days, as the ordinance originally was laid out, was a last-minute arbitrary amendment that killed what might have been a 7-0 vote, which was unfortunate. At the last meeting, every single speaker and three council members made compelling arguments against the change, and not a single speaker or a council member attempted to create an argument in favor of lowering the legal time someone could spend the night in a recreational vehicle.
The amendment was not a compromise, but a display of authority. I believe that good policy is not made based on party lines or optics, but it's made in a collaborative way, in a process designed to incorporate public input. So I would really appreciate any council or even staff input to justify lowering the legal allowability of days in 9.20 of recreational vehicle camping. But, yeah, Councilmember O'Brien's proposal is very interesting to me. I'm happy to consider further curation of this ordinance change, but I'm not sure I truly understand your proposal enough to give staff direction on that yet. Councilmember van Overbeek? Yeah, let me start with a question for the City Clerk. So it sounds like, well, Councilmember O'Brien has some proposed amendments to the code, and Councilwoman Hawley has a different one, I think, a proposed amendment.
Did you propose an amendment, or? I think keeping 9.20 at seven days instead of lowering it to five days is appropriate. All right. So don't we need to vote on these separately? Well, I think right now you're just having discussion. There hasn't been a formal motion. So I would think you can take them separately, or you can, well, if you, I would probably take them separately. Okay. Just because there are two items, need a provision if once the city clears an area it stays cleared, no more tents or camping allowed. The second one for Councilmember O'Brien was a 48-hour warning and assessment once given. The city shouldn't have to repeat that over and over again. And then he clarified that the warning assessment is done for only once per person.
And then, of course, target team can always provide shelter options. That's what they do. Okay. So I. So there's that one, but, and Councilmember Hawley did not actually make that as a motion, her item. She just asked for more discussion and consideration. Okay. I'd like to make a comment on Councilmember O'Brien's proposed amendment. So after five years of dealing with attorneys in the war and settlement agreement, I think what I believe that what Councilman O'Brien proposed is very important, a very important amendment because it really makes the whole thing crystal clear. And so thank you for bringing that to our attention. I support that. If we're ready for a motion, I'll make a motion to support it.
We've still got people in the queue that want to speak. Okay. And Vice Mayor Bennett, you're next. Peña, you heard what Councilmember O'Brien has suggested and actually proposed. Do you see, and another Councilmember has problems with it because of the reasons you stated, do you see a problem with the officers being able to identify a particular person on a repeat basis so that they could, in fact, advise the person that they've been warned before and not need to repeat that 48-hour notice over and over and over again, which I think would probably happen. I do appreciate Councilmember O'Brien's suggestion. I think that could make it easier for the enforcement side of this particular situation.
So you see a problem with that? I don't see a problem. We do have a mechanism in our computer-aided dispatch system where we keep, where we can create like a flag when we've spoken with someone or given them an advisement, and regardless of which officer interacts with them on a subsequent contact, the officer would query the dispatch if this person has been given an advisement. They would search because that would be logged under the person, and we could identify if that person had been given an advisement when they were given that advisement. So it would definitely streamline the process, and it wouldn't be a hardship or an obstacle to limit it to a single occurrence and having recorded. We could also put a cap on that or a specific timestamp if that's what you wanted and can go back to that and identify it.
Thank you. Councilmember Winslow? Thanks. Yeah, so I do agree with Councilmember Hawley as far as the recreational vehicle thing, but that's kind of been a conversation we've had. Councilmember O'Brien, it's a good point that we don't want that to happen, and I think it's clear that it hasn't been super well thought through and like how this will apply in practice, you know, and even if we were to take your direction, and I mean if we put it in the ordinance right now, I think that would be crazy because you should think a little bit more about the text of your law and not do it ad hoc on the dais. But even then, to say that somebody can't move close by, it's like how close is close by is a question.
And I will return to something that I've said every time we talk about this for a while, that this model ordinance put forward by Governor Newsom makes a lot more sense than our ordinances we're trying to like patch up in weird ways, especially in this rushed process we've been under in the last few months. And for that, I would say that for one, they call out exigent circumstances where you don't need to notice because there's some kind of threat to infrastructure, life, health, safety, or something which we could define ourselves and we could define to mean something that matters in our community, like waterways are an unacceptable place to camp, like hands down, or bike paths, just not a good place to camp at all, and don't have to worry about the standard process we would have for other places where people tend to camp and maybe go unnoticed for a long time.
And then they also do mention 200 feet is what they, is in the model ordinance for that you can't post, you can't recamp within 200 feet of a posted notice to vacant vacate. So that's like what you're calling out right there. I mean, it was thought about in that, and that's why I suggested that we would be better off, I think, looking at an ordinance like that than trying to work up our own. In general, we have this unhoused strategic plan and process. We are collecting public input on this as we speak. And this conversation would be much more intelligently handled if we were to postpone changing the ordinances until it's part of a broader plan. So my suggestion would be, whenever we're ready for a motion, would be to just table this conversation.
And we can take that input, like confirm that your, what you're calling out, Councilmember Ryan, is a good thing for us to account for in our laws. But the appropriate way for us to handle that is to table it until we've had more conversations and have a more comprehensive plan. Councilmember Goldstein. Thank you, Mayor. I have one question for staff first. So this is supposed to be our second reading of the ordinance. But to be clear, if we were to make amendments tonight, we would have to do another second reading. Right. Okay. Well, actually, this was a first reading. It could have been the second reading, but because there were changes last meeting, this is a first reading. No, it definitely has to come back at least one more time for a second reading if there's consensus on what the language is tonight.
It could be that I'm being asked to come back again for another first reading in two weeks, which is fine. And we can make some more amendments at that point, but it is not a second reading. Okay. Just thank you for clarifying that. I tend to agree with my colleagues that we're continuing to make changes on the fly. And while I'm glad that we're having these discussions, I share in the concern that some of these changes we're making aren't backed up. And we are concurrently developing an unhoused strategic plan where I feel like these discussions could be had with more depth with community stakeholders and with more data to back them up. So I would support the idea of tabling this until we can work further on developing the plan.
Okay. Okay. And the only thing I had just to address Councilmember Hawley, it actually was an attempt to compromise and work across the aisle, and it was to increase the time. and I made that motion. So we went from three days to five days. We're not just decreasing. You said we went from a week down to three days, so. The original CMC says seven days. You made a motion for three, and there was a friendly amendment from. I made a motion to seven. Oh, there was a friendly amendment from O'Brien, I thought, for five. But it's printed three. So we were at three, and I was trying to get bipartisan support, and I made it seven, and there was a friendly amendment to go to five. But anyways, we have increased the days to five.
That's the only thing I just wanted to clarify. But we are where we are. Do we have an actual motion on the floor? I know you said what you would like to do, but is there a motion? So I will make a motion. As I articulated, the city clerk seemed to capture that really well, and she always does. Could you repeat that back? Debbie and I can repeat it myself if that's helpful. It would be to probably reintroduce the ordinance of the city of Chico, amending Title IX of the Chico City Municipal Code to regulate certain acts of camping on public property as amended. One, need a provision if once the city clears an area, it stays clear, no more tents or camping allowed. Number two, 48-hour warning and assessment.
Once given, the city wouldn't have to repeat that over and over again. Warning assessment is done only once for each person, and that the target team and staff always provides shelter options when communicating with them. Thank you, perfect. You're welcome. I'll second that. Sir, I thought your direction was that the target team does not provide shelter options to people, you know, more than once. That was not my motion. Could you clarify it one more time, then, that what exactly, sorry, I don't mean to make you reread the whole thing, but I had the same question. So, on the 48-hour warning and assessment, once given to one individual, then the city wouldn't have to continue to repeat that same warning and assessment every single time.
However, it was duly noted that the target team always provides shelter options. So, one warning, one assessment, one person, one time. Say it in a very concise way. Okay. See, that time you said assessment, that includes assessment for shelter options. Yep. But we can always do more regarding the assessment if we want, and staff can always do that. They always have that discretion. I'll just back up my previous point that this is being done without thinking about a larger whole plan and the fact that we're having this whole conversation and haven't even mentioned the outreach and engagement team that we have that actually this whole council at a seven-zero vote approved keeping post-war in, and that being the front lines of engaging people in waterways.
So, my substitute motion would be that we table this discussion, taking the input from Council Member Bryan's comments and re-discuss it in the context of a broader unhoused strategic plan. Second. City Manager, okay. We've got a motion and a second on a substitute. City Manager Haen, I see you. I just wanted to make a clarification. So, currently, the notice requirements do not require assessment in the ordinance. So, I just want to point that out. If we are moving forward, I just want the council to understand that the motion is to require the 48-hour notice and require assessment in the ordinance. The assessment currently is just in our operational plan, not our ordinance. So, I just wanted to clarify if that's the intention here to add assessment to the ordinance when it didn't exist there prior.
So, since we are doing it, if we pass this, one time, one person, one warning, I would include an assessment in that warning. Okay, thank you.
Do we have a second on the substitute motion to table this item? Yes, Council Member Hawley. Yeah, Council Member Hawley. All right, thank you. Okay, and that was to table it in order for this item to be further discussed. Is that correct? Yeah, in the context of the unhoused strategic plan that's under development. Okay, let me just throw that in there. All right, Council Member Goldstein? Yes. Council Member Hawley? Yes. Council Member O'Brien? No. Council Member van Overbeek? No. Council Member Winslow? Yes. Vice Mayor Bennett? No. Mayor Reynolds? No. It fails three, four. And then we go back to the original motion and find it made by Council Member O'Brien and seconded by Council Member van Overbeek.
And do the vote. Council Member Goldstein? No. Council Member Hawley? No. Council Member O'Brien? Yes. Council Member van Overbeek? Yes. Council Member Winslow? Yes. Vice Mayor Bennett? I'm going to vote yes because I have a great fear that this is gonna be a repetitious procedure, just like we've been experiencing for the past five years. So I'm gonna vote yes. Okay, thank you. Mayor Reynolds? Aye. It carries five, two. All right, we will, 5.2, acceptance of the finance committee report. Council Member van Overbeek? Okay, I am gonna need the clicker. All right. Thank you.
Okay, everybody's favorite subject, the CalPERS unfunded pension liability, which is basically what this is about. So there's two sources of, two components to the pension cost. One is it's a percentage of payroll, there's actually three. It's a percentage of payroll, it's a return on investment that CalPERS makes. And then the third piece, because they've had a shortfall, is that the city's required to make a fixed annual payment. So this is a report on what those numbers are. So the bad news is the combined unfunded pension liability is almost $167 million, because the markets were really good in the last year or so, it's actually down $14 million from June of 24 on, it was $180 million. So right now the CalPERS pension for city employees is funded at 71%.
And although that's a concerning, only 71% of the money required to pay the pension obligations exists in the fund. The balance is made up by the one-time annual payment by the city. So the state mandates that for the safety employees, fire and police, that there be a 21.66% contribution. Everybody else is 12.25. The employees pay some portion of that. So the combined unfunded liability payment for this fiscal year will be 17, excuse me, Barbara, was this this year or last year? The 17.49. That'll be for 27-28. 27-28, okay. It's 17 and a half million dollars. So you can, this is what it's projected to be over the next roughly 20 years until 2043. And it's projected to go up a bit until 28 and then slowly come down.
There's a whole bunch of things that can impact this. For example, if we had a major reversal in the equity markets that would suppress CalPERS returns and would increase the amount of the unfunded liability payment the city would have to make. But this is their best guess at this point. Their returns, they used to have an 8% assumed return. They lowered it to 6.8. And over the last, you can see the last 10 or so for 30 years, they've done pretty well. Last year, they had a return of 11.6%. That sounds great until you remember that S&P 500 did 21%. So they have underperformed. And the reason that we have this situation is because CalPERS over the last 20 years has only done 2 3rds as well as the index funds, the major stock market indexes.
So the funding, the situation has improved. It's still alarming. Both plans are now 71% funded. This is better than it's been for some time. The 2728 UAL payment is $17.5 million. It's gonna increase to 18.52 million in the next fiscal year. And the city's done a really good job under the leadership of Director Martin in maintaining pension reserves. And I think we've done a good job of hitting our numbers. Any questions about this? I know it's a very stimulating topic, but it impacts all city employees. So it's important. Okay, if there's no questions, the other thing I wanna report is that I asked that we have a discussion about the city's risk management strategy. What do we self-insure? What do we buy insurance for?
What are the deductibles? That was a report, but I wanted to have a discussion with the committee. I also wanna revisit what our cash investment policy is. So the city has a fairly large amount of cash, and I wanna make sure that it's being invested safely. And then lastly, at every finance committee meeting, I'd like to get, or quarterly, like to get an update on where we are with actual numbers versus the budgets and apply this red, yellow, green code so that we can focus on areas that are problematic. And that was the finance committee report. Perfect. Council Member Hawley, did you have a question? Yeah, just one. Thanks, Mayor Reynolds. Council Member van Overbeek, can you clarify the quarterly reports?
Did you mean specifically CalPERS quarterly updates? No, budget versus actuals. Okay. So we do a budget, and I wanna know what we actually spent compared to what we budgeted, just to make sure we're not going off track somewhere. And that would be both from a revenue and an expense. Thank you. All right, how many speakers do we have? We don't have any. Nobody wants to talk about CalPERS. I'm shocked. All right, so we're accepting the report. Are those actions that you, we need to make a motion that you want us to give permission, or is that just giving direction to Barbara to have her bring those things? I don't think there needs to be an action by the council. No, okay. No, okay. Just making sure we're not stepping.
All right, no speakers. Reports and communications. The following reports and communications items are provided for council's information. No action can be taken on items under this section of the agenda unless the council agrees to include it on a subsequent agenda. City manager's report. City manager, Ms. Haen, do you have a report for us? Yes, I'll fly through this real quick. I know everyone's antsy to get moving. Draft unhoused strategic plan. We had a service provider meeting last week, tomorrow night here in the council chambers from six to 8 p.m. We'll be doing a town hall meeting to gather public input on that plan. So please bring your comments forward tomorrow. We've been getting a lot of great input on the plan.
The unhoused strategic plan is scheduled for council consideration on November 17th. Last week, I attended the ICMA conference, 1017 to 1021 in Long Beach. It was a great conference of city managers all over the nation, including I met a city manager from Portugal and Canada. So it was very interesting. There was a lot of talk about economic development and homelessness and housing, team building with staff, a lot of great topics and a lot of great courses. So thank you for allowing me to go and represent the city. I've met with a lot of people since the last meeting I was at, Chamber of Commerce, Smart Growth Advocates, Lupine Legacy. Worked with Debbie and Ryan and we gave a candidate orientation for the first time here in the city of Chico, which was great.
So we took the candidates that were running for election and had all of our department directors and our expert staff explain to them who they were and what their departments each did in the role here in the city for service provision. It was, I think, really successful. I attended the Fire Academy live burn. I suited up and went into the fire with the recruits. First city manager to ever do that here in Chico, so I'm very proud of that. It was amazing. And I'm excited to go this Friday to the academy graduation. So we're looking forward to that. Very proud of the men working hard. Attended the Cal Water 100th anniversary celebration, which was also very wonderful with the vice mayor. I did an NSPR interview and Action News Now podcast just talking about the different priorities and the input that I've gained in the first 12 weeks here on the job.
So that's been really great communication-wise. Also went to the Bidwell Park and Playground Commission. I plan to attend every commission and meet them all and understand what their roles are and move forward with that. Also met with 3Corps, took a tour of the airport and met with the Butte College president. So very busy few weeks. We've kicked off the recruitment for the community development director. We've selected Bob Marine Associates, and that is underway soon. The position will be on the website. Sadly, we will miss Director Vieg, but we're excited to get moving on that recruitment ahead of time. And just did last week the Treat Street costume judging with the police chief Aldridge and fire marshal and Action News Now, Mr. Emilio.
It was a great event, as I stated earlier, it was amazing to see how many kids and family were out there. And my daughter helped in the fire booth and the police booth and went around. And it just, it was a really great community event and it really seemed to be super successful. Many people were eating in the restaurants and going into the shops that were open at the time. So I really liked that, to see that happening. So with that, that ends my report for this week. Thank you. All right, thank you very much. Pursuant to APMP 1010, council members may verbally request an item be agendized at a future meeting after stating what the item would be a majority of council is needed to vote in order to agendize.
Do we have any council member requests? I have one. All right. I would like us to redraft the shopping cart ordinance the way it's currently written. The onus on controlling the shopping carts falls on the owner of the shopping cart. So if it gets picked up, I believe that the way it works is we find the retailer the shopping cart comes from. A shopping cart is four or $500. Anybody in possession of a shopping cart has received stolen property. And I wanna see us redraft that measure so that the carts are confiscated. Okay, so you wanna talk about shopping carts? I do. Okay, perfect, that'd be great. Thank you. I'll second that request, Mayor. All right, we have a motion and a second. Madam Clerk.
All right, and that's to agendize the discussion about redrafting the shopping cart ordinance. Let's see, Council Member Goldstein. Sure, yeah. Council Member Holly. Yes. Council Member O'Brien. Yes. Council Member Van Overbeck. Yes. Council Member Winslow. Yes. Vice Mayor Bennett. Mayor Reynolds. Aye. Carries seven, zero. Anybody else? No, all right. We will adjourn to November 17th, closed session meeting at five or 530 followed by our regularly scheduled meeting at 6 p.m. here at 421 Main Street. Happy election night and see you in two weeks. Thank you.
Every recap on this site is produced by the same pipeline: official city sources in, a machine transcript, a logged cleanup pass, and AI steps that read the votes and draft the recap. This page shows exactly what each step did for this meeting — including the full instructions we give the AI — so you can judge the process, not just trust the output. (For the pipeline in general, see How it's made.)
This summary was generated using prompt version 13. → See version history
The weakest link is turning the meeting's audio into text. Council chambers have distant microphones, cross-talk, and names the transcription model has never heard — so names, dollar figures, and mumbled stretches are where errors creep in. Everything downstream inherits those errors, which is why the later steps exist mostly to catch them: a name-correction pass with a public log (step 3), instructions that tell the AI to omit or flag anything shaky (step 4), and a cross-check of every vote against the clerk's record (step 5). If you spot something wrong, tell us.
- 1
Start from the official record
We pull the agenda and the full meeting video straight from the city's own publishing system (Granicus) — fetched November 6, 2026. Along with the city's published member roster (step 3) and the clerk's official minutes once posted (step 5), these are the recap's only sources — all of them city records, and you can check the two main ones yourself:
- 2
Turn the audio into text
Biggest source of errorsWe transcribe the meeting audio locally with an open-source speech-recognition model (
whisper-1), producing 979 timestamped segments. Machine transcription mishears things — especially proper names and numbers — and it doesn't know who is speaking. - 3
Clean up the transcript — with receipts
A rule-based pass (no AI) merges the raw segments into readable paragraphs and checks name-like words against the official member roster. It only corrects a name when the context makes the match near-certain — after a title like “Councilmember” or an exact first name — and every correction is logged below. Anything it can't confirm is flagged for a human instead of silently guessed.
All 10 name corrections made in this meeting
Transcript said Corrected to Times Hayne Haen 2 Van Herbeck van Overbeek 2 Haley Watts Hayley Watts 1 Van Obrek van Overbeek 1 Pena Peña 1 Captain Peña Peña 1 Van Iverbeck van Overbeek 1 Veague Vieg 1 4 name spellings we could not confirm
These looked like member names but didn't clear our confidence bar, so they were left as heard and passed to the next step as “treat with suspicion.”
- “mr. emilio” (closest roster match: Emilio Del Carpio, heard 1× — listen at 1:08:25)
- “debbie” (closest roster match: Deborah Presson, heard 3× — listen at 25:16)
- “bob marine associates” (closest roster match: , heard 1× — listen at 1:08:25)
- “angie” (closest roster match: , heard 1× — listen at 18:00)
- 4
Draft the recap with AI
The cleaned transcript, the official agenda, and the list of unconfirmed names go to a language model (
claude-sonnet-5) , run November 6, 2026. The instructions below are the complete, verbatim prompt — nothing is hidden. Note what it demands: accuracy over completeness, no editorializing, omit shaky details rather than guess, and mark anything it can't verify — those become the dotted-underline flags you see in the recap.Read the full recap prompt
The {{PLACEHOLDER}} markers are where this meeting's title, date, agenda, transcript, and unconfirmed-name list are inserted.
You are writing a plain-language recap of a Chico, California {{MEETING_BODY}} meeting for residents who don't usually follow local government. Your job is accuracy first, accessibility second — this recap must be trustworthy enough to publish with light human review. You are given three sources: 1. The official meeting agenda (structured, reliable). 2. A ROLL-CALL VOTES record (structured, authoritative for tallies and outcomes — extracted deterministically from the clerk's roll calls, and corrected against the clerk's official minutes when so noted). 3. A transcript of the meeting audio produced by automatic speech recognition (unreliable in places: garbled or misheard words, and no speaker labels — you cannot tell from the transcript alone who is speaking). Rules: - Only report things supported by the sources. If the transcript is too garbled to tell what happened on an item, say "unclear from the transcript" rather than guessing. - Use direct quotes wherever the actual words spoken carry the moment better than a paraphrase would. This is especially true for ceremonial items — honors, farewells, proclamations, tributes — where what was said IS the story, and for public comment, where a resident's own words carry something a paraphrase flattens. Do NOT quote {{BODY_MEMBERS}} debating or discussing any item, contested or not: paraphrase their positions instead (see the item-by-item rules below). And never set a quote apart in bold as a pull-quote — a quote sits in the sentence like any other words. Quote verbatim from the transcript, keep each quote to a sentence or two, and only quote passages that read cleanly. The transcript will contain garbled or fragmentary stretches — never quote those, and never stitch fragments together with ellipses to salvage a broken passage. Instead, trim the quote down to just the portion that reads as a clean, complete thought (even if that's a single clause) and paraphrase the rest, or pick a different quote entirely. Watch for transcription errors *inside* a quote too: if a proper noun in the quoted passage is spelled differently from how the roster, agenda, or the rest of the transcript renders it (e.g. a hospital or person's name garbled in one cue), use the established spelling — the speaker said the real name; the transcriber misheard it. A quote should read as smoothly as if it appeared in a newspaper. A well-chosen quote makes the recap feel human; aim to include several across the recap when the transcript supports them. - Never attribute a quote or statement to a named person unless the transcript itself makes the speaker unambiguous (e.g. they introduce themselves by name, the mayor is running the meeting procedure, or the honoree of an item is responding). Speakers who introduce themselves may be quoted by name; otherwise attribute by role ("a member of the public", "the general manager of the parks district"). For speakers who are not {{BODY_MEMBERS}}, don't let this rule stop you from quoting — a role-based attribution is fine. - The seated {{BODY_MEMBERS}} are the exception: there are only a handful of them and the roster names every one, so "a {{BODY_MEMBER_TITLE}} said" reads as "we couldn't tell which one" and weakens trust in the direct quote. A dais remark may be quoted only on a ceremonial item (a member's tribute, farewell or proclamation remarks), and only when you can pin it to a specific member (the roll-call structure often makes this possible — the clerk says a name right before the member speaks). If you can't, paraphrase the point without quotation marks and without a name ("one member argued the cost wasn't justified") or choose a different quote. - Vote outcomes matter most. The ROLL-CALL VOTES record below is the authoritative source for who voted how and whether each motion passed or failed — report every outcome from it, and never contradict it based on your own reading of the transcript. The clerk sometimes skips a member during a roll call and abstentions are often silent, so a roll call that *sounds* incomplete in the transcript can still have a definitive recorded outcome — trust the record, and when it notes a vote came from the official minutes, you may state that vote as fact (e.g. an abstention the audio never captured). Use the transcript for everything around a vote: who made the motion, the debate, what members said. Only if a vote appears in neither the record nor clearly in the transcript should you say the outcome isn't clear. - Consent-agenda convention: before the consent motion, members often "register a no vote" on one specific item, or recuse themselves from one item, while the bundled consent motion still passes with every member voting yes in the roll call. This is normal procedure, not a discrepancy — the roll call approves the bundle, and the clerk records the stated exception against that single item. Report it that way ("the consent agenda passed 7-0, with {{BODY_MEMBER_TITLE}} X recorded as a no vote on item 2.4 and {{BODY_MEMBER_TITLE}} Y recused from item 2.3"). Never describe a registered exception as a conflict between what a member said and the recorded vote, and never present it as something the transcript leaves unresolved. - Plain language: define jargon inline the first time it appears (e.g. "consent agenda — routine items approved in one vote"). Write for a smart neighbor, not a policy wonk. - The MEMBER ROSTER below is ground truth for member names, roles, and pronouns. Its second list, of staff and other officials, is ground truth for those people's spellings and roles: the transcript routinely mishears them (it notes how), so when the transcript names or describes one of them — "the police chief", "Deputy Director Keene" — use the list's spelling, and name them by role or by name as the item needs. Use the listed pronouns when referring to a listed person, and never infer anyone's gender from their first name — several members have ambiguous first names. For anyone listed without pronouns, and for people on neither list (other staff, public commenters), use pronouns only when the transcript itself makes them clear (e.g. someone is introduced as "Mr./Ms. X"); otherwise repeat the name or role instead of guessing a pronoun. - Keep neutral tone. No editorializing about whether decisions were good or bad. - Don't inflate scale. The transcript has no timestamps, so you cannot tell how long anything took: never write "hours of testimony", "a marathon debate", "a lengthy discussion" or similar. Convey weight with what you can count or quote instead — "after eight speakers", "most of the commenters". The same goes for crowd size, emotion and consensus: "the room was packed" or "residents were furious" only if the transcript says so. Marking uncertainty — this recap is published with light or no human review, so the writing itself must carry the honesty: - Prefer to OMIT a shaky detail when the recap works without it. A recap that says less but is all true beats one that says more and needs checking. - When a detail is worth including but you can't fully verify it against the sources — a name spelling the transcript renders inconsistently, a dollar figure heard once in a garbled stretch, an outcome you're inferring from context — wrap just that span in an uncertainty tag with a short plain-language reason: `<unsure reason="the transcript spells this name several ways">Gillian Haen</unsure>` `<unsure reason="figure heard once in a garbled stretch of audio">$1.2 million</unsure>` The reason should say why it's uncertain in words a reader understands ("the audio is unclear here", "the transcript is inconsistent"), not pipeline jargon. Use this tag sparingly — a handful of times at most; if you're reaching for it constantly, omit more instead. - Never mark vote outcomes as unsure — take them from the ROLL-CALL VOTES record. Only when a vote appears in neither the record nor clearly in the transcript, say so in plain text ("the recording doesn't make the final tally clear") rather than reporting a tally you're guessing at. - The KNOWN UNCERTAIN NAME SPELLINGS list below (if present) comes from an automated pass that compares the transcript against the official member roster. Treat those spellings as unreliable: use the roster's spelling when you're confident who is meant, wrap the name in `<unsure>` when you're not, and avoid building any factual claim on a name from that list. Produce the recap in exactly this structure, in Markdown: # {{MEETING_TITLE}} — Recap ## TL;DR One paragraph, 3-5 sentences: the meeting in a nutshell. Lead with the most consequential decision. ## What happened, item by item For each substantive agenda item (skip pure procedure like pledge of allegiance and roll call unless something notable happened): a short heading with the item number, then what it was and what happened, including the outcome. How much you write depends on whether the {{BODY_MEMBERS}} disagreed. Use the ROLL-CALL VOTES record to tell which of the three cases below you are in. **Unanimous vote, or no vote at all.** 1-3 sentences: what the item was in plain language, and that it passed or failed unanimously. The agenda is usually the better source for what was actually proposed; use the transcript for what the agenda doesn't cover. Nothing more is needed — a unanimous vote means there was nothing to settle. If the item was a presentation or study session with no vote and no disagreement, describe what was presented and leave it there. **Split vote with no real discussion.** The same 1-3 sentences, plus the split and who was on which side, taken from the votes record. Do not manufacture a disagreement the transcript doesn't contain: if members voted differently without saying why, report the split and stop. **Split vote with discussion — the case that needs care.** Members usually explain a no vote, or signal their concern in the questions they ask beforehand. Whenever they do, this recap must represent the disagreement fairly, and that takes more room than three sentences. Cover, in this order: 1. What was actually proposed, and what the {{MEETING_BODY}} was being asked to decide. 2. **The case for it**, as its supporters would state it. Often nobody on the dais argues for a proposal, because the proposal *is* the case — staff presented it and a majority agreed. When that is what happened, the supporting rationale is the reasoning in the staff presentation plus whatever members said in support. 3. **The case against it**, as its opponents would state it: the specific concern, objection, or question behind the opposition. 4. **Any legal or factual point a reader needs in order to follow the disagreement at all** — a settlement or law that constrains what the city may do, a deadline, a cost figure the two sides read differently. State it plainly where it belongs in the item, not as an aside. 5. The outcome and the split. Then check your own work on that item: would someone who argued each side read this and recognize their actual reason in it? If one side's reasoning is thin because the transcript doesn't capture it, say so ("the recording doesn't capture why the three no votes landed that way") rather than leaving the imbalance unexplained. Two hard rules for split-vote items: - **Never let length guidance push out one side's rationale.** A longer item is correct here. An item that gives one side's reasoning and not the other's is not, however short and accurate it reads. - **Write the two sides as positions, not as rosters of names.** "The case for" and "the case against" are arguments, and this recap presents them as arguments. Do NOT list which members held which position, and never infer that a member made an argument from the way they voted: a yes vote is not evidence that the member advanced the reasoning behind it, and grouping names by tally invents a record of who said what. Name a member only where the transcript itself pins that specific statement to that specific person beyond any doubt, which is the same bar the quoting rules use. When in doubt, leave the argument unattributed. The argument is the thing a reader needs; who made it is optional, and the outcome line already tells them who voted which way. - **Represent, don't adjudicate.** Give each position its strongest honest form, in the terms its own holders used. Never signal which side had the better of it, which argument answered the other, or that the outcome settled who was right. **Paraphrase dais positions on these items; do not quote them** (the same rule holds on every non-ceremonial item, split or unanimous). A single quoted line frames a whole debate around whoever happened to be most quotable, and that is the exact distortion this section exists to prevent. Default to describing the position without a name ("opponents argued the cost wasn't justified"); attach a member's name only where the transcript leaves no doubt that this person made this point. Ceremonial items and public comment still carry quotes under the quoting rules above. ## Notable moments 2-4 bullets: exchanges between members, announcements, procedural surprises, or anything else a resident might want to know happened. Public comment gets its own section below — don't duplicate it here unless a {{BODY_MEMBER_TITLE}}'s *response* to a comment is itself the notable part. A colourful aside from a member can go here, paraphrased rather than quoted; from a split-vote item, only once that item above already states both sides' reasoning, because a member's joke must never be the only thing the recap records about a member who also argued a position on the merits. ## Public comment What residents actually came to say. This is often the most interesting part of a meeting and the part least visible in the official record, so give it real attention — but report only what the transcript supports. Lead with a sentence or two on the shape of it: roughly how many people spoke, and whether the comment was dominated by one subject or spread across many. Then 2-5 bullets covering: - **Recurring themes.** When several speakers raise the same subject, say so and give a sense of the volume ("a dozen speakers", "most of the roughly twenty commenters") and of where they came down. If speakers were divided, say that rather than flattening them into one position. - **Specific and unusual subjects.** A single speaker raising something concrete, local, or surprising is worth a bullet even if nobody else mentioned it — a specific intersection, a business, a personal experience of a city service. - **Comment on items not on the agenda.** Chico takes general public comment; those subjects often signal what's coming and rarely appear anywhere else. Weave in a short direct quote where one captures a point better than paraphrase. Prefer the vivid and specific over the generic. Naming speakers: - Use a speaker's name only when the transcript clearly gives it (they usually state it, or the clerk calls it). Otherwise "one speaker", "a resident", "several neighbours" — never guess at a name. - **Check every speaker name you are about to write against the KNOWN UNCERTAIN NAME SPELLINGS list.** If it appears there, do NOT print it as fact. These are private residents, not {{BODY_MEMBERS}}: there is no roster to correct the spelling against, so a flagged name is simply unreliable. Describe them instead ("a local business owner", "a downtown resident") — that carries the same meaning and cannot misname anyone. Only if the identification genuinely matters to the point, wrap it: `<unsure reason="name spelling unverified">Kelly Lesser</unsure>`. Attributing a direct quote to a misspelled private person is the specific harm this prevents. - Public commenters are private residents, not public figures. Report what they said about city business; don't repeat incidental personal details (health, finances, addresses, family circumstances) that aren't the point of their comment, and don't characterize them beyond what they said. - Never infer gender or pronouns from a name — the roster rule applies here too, and commenters are not on the roster. Use the name, "the speaker", or "they". Skip this section entirely if nobody spoke during public comment. ## Coming up Bullets for any future dates, deadlines, or follow-up actions mentioned (next meeting date, items continued to a later date, etc.). --- MEETING METADATA: Title: {{MEETING_TITLE}} Date: {{MEETING_DATE}} MEMBER ROSTER (ground truth for names, roles, and pronouns): {{ROSTER}} KNOWN UNCERTAIN NAME SPELLINGS (from automated roster comparison; may be empty): {{UNCERTAIN_NAMES}} ROLL-CALL VOTES (authoritative record of every motion's tally and outcome; notes mark votes corrected from the clerk's official minutes): {{VOTES}} AGENDA: {{AGENDA}} TRANSCRIPT (automatic speech recognition of the meeting audio — imperfect, no speaker labels): {{TRANSCRIPT}}Read the social-media post prompt
Our Instagram cards are written by a second AI pass whose only source is the already-reviewed recap — it is forbidden from adding any new facts.
You are writing copy for a social media carousel post (Instagram-style, multiple swipeable cards) recapping a Chico, California {{MEETING_BODY}} meeting, aimed at residents who don't usually follow local government. You are given an already fact-checked recap of the meeting. It is your ONLY source. Rules: - Every fact must come from the recap. Do not add, infer, or embellish anything — no new numbers, names, dates, or outcomes. If the recap says an outcome was unclear, either skip that item or say it plainly. - Hedged claims are not stories. Where the recap hedges or flags uncertainty ("the transcript doesn't make clear…", "the recording doesn't capture…", `<unsure>` tags), that material may not appear on a card at all — never build a card, or even one line of card copy, around what ISN'T known. Never pair a body describing confusion or an open question with a definitive badge (a card saying a vote was murky next to "Passed 7-0" contradicts itself and destroys trust). Strip the hedged part and keep only what the recap states as fact; if what's left wouldn't interest an average resident, drop the card entirely. - Quotes must appear word-for-word in the recap. You may shorten a quote, but never alter or paraphrase inside quotation marks. - Neutral tone — no editorializing, no cheerleading, no snark. Being punchy is fine; having an opinion is not. - Never infer anyone's gender from their name. Use a gendered pronoun for a person only if the recap itself uses that pronoun for them; otherwise write around it (repeat the name, use "their", or use the role). - Write for someone mid-scroll: concrete, plain language, zero jargon. If a term like "consent agenda" is unavoidable, gloss it in a few words. - No hashtags or emojis in card text. Produce 5 to 8 cards following this template: 1. First card — type "hook". The single most consequential decision of the meeting as a short headline (max 8 words), e.g. "Chico has a new **city manager**". Wrap the single most important word or short phrase (1-3 contiguous words) in double asterisks exactly as shown — the card design visually highlights that phrase. Exactly one marked phrase, in the hook headline only; never use asterisks anywhere else. The eyebrow and cue fields are fixed template text (see schema below); you only write the headline. 2. Middle cards — type "item", one card per newsworthy *story*. A headline (max 8 words), a body of 1-2 sentences (max 40 words) saying what it was and what happened, and — whenever there was a vote — a badge with the outcome ("Passed 5-2", "Unanimous", "Failed 3-4", "No vote taken"). Only include items an average resident would care about; skip routine business unless the dollar amount or subject makes it interesting. - Each card must cover a distinct story. When several agenda actions are chapters of the same storyline (two procedural votes about the same rate increase, two related motions on the same topic the same night), combine them into ONE card — never write two cards a reader would experience as near-duplicates. - Never write a card whose subject is just "the consent agenda passed" or "minutes were approved" — that is routine business, not news. If one consent item is genuinely notable (an unusual dollar amount, a hire), make the card about that specific item and mention in the body that it passed as part of the consent agenda. 3. Optionally one card — type "quote" — when the recap contains a quote strong enough to stand alone (ceremonial moments, memorable public comment). The quote is the whole card: quote text (max 30 words), attribution as given in the recap, and a context line (max 12 words) saying what it was about. - The quote must read as a complete thought to someone seeing only this card: at least one full sentence, never a sentence fragment or a two-word phrase, and no ellipses. If the recap only quotes a short fragment, or the line only makes sense alongside the surrounding paraphrase, skip the quote card — a carousel with no quote card beats one with a confusing quote. - Never attribute a quote card to one of the {{BODY_MEMBERS}}, named or not. A single line from the dais turns a decision into one member's soundbite, so their debate and discussion stay paraphrased in the item cards. The only exception is a member's own words on a ceremonial item (a tribute, a farewell, a proclamation). Attribution is otherwise a named or role-described speaker who is NOT one of the {{BODY_MEMBERS}} ("A member of the public", "A PBID board member", "Enloe Health's representative"). If the recap's best quote is from the dais, pick a different quote or skip the quote card. - The context line must say concretely what the quote is about and where the speaker stood (e.g. "Speaking against the rate increase during public comment"), not just name the topic. 4. Last card — type "coming_up". Body listing the next meeting date/time and any upcoming deadlines from the recap (max 40 words). The cta field is fixed template text. Also write a "caption" for the post itself: 3-5 sentences adapted from the recap's TL;DR, plain language, ending with a pointer to the full recap at the link in bio. Output STRICT JSON only — no markdown fences, no commentary before or after. Schema: { "caption": "...", "cards": [ {"type": "hook", "eyebrow": "{{MEETING_BODY_UPPER}} RECAP · {{MEETING_DATE_DISPLAY}}", "headline": "... with the key phrase **marked**", "cue": "Swipe for what happened"}, {"type": "item", "headline": "...", "body": "...", "badge": "Passed 5-2"}, {"type": "quote", "quote": "...", "attribution": "...", "context": "..."}, {"type": "coming_up", "headline": "Coming up", "body": "...", "cta": "Full recap at the link in bio"} ] } The "badge" field is omitted when there was no vote. Card order: hook first, coming_up last, items in the order that best tells the story of the meeting (most consequential first), quote card placed next to the item it relates to. The first item card must be the same story the hook headline promises — don't tease one decision on the cover and lead with a different one. --- MEETING METADATA: Title: {{MEETING_TITLE}} Date: {{MEETING_DATE}} APPROVED RECAP (your only source): {{RECAP}} - 5
Read the votes — then check them
A separate AI pass reads the clerk's roll calls from the transcript (“Councilmember Goldstein? Yes…”) and records how each member voted. Because a vote record is too important to take on the model's word, rule-based code then checks it: every name must match the official roster, the count can't exceed the size of the body, and the result is squared against the tally the clerk states out loud. Any vote that can't be reconciled with the clerk's count is flagged, not guessed. Mismatches are shown, not hidden:
Read the full vote-extraction prompt
The complete, verbatim instructions the vote-reading AI is given — the {{PLACEHOLDER}} markers are where this meeting's roster and transcript are inserted. It is told to record only what it hears and never to invent a voter or a tally.
You are extracting the roll-call votes from a Chico, CA city council or commission (e.g. Bidwell Park & Playground Commission) meeting transcript. Your output is consumed by software, not read by a person — return only the structured data requested, grounded strictly in the transcript. ## How Chico runs a vote The person calling the vote may be a **clerk** or the **chair** (mayor / vice mayor / commission chair). Members carry titles — Mayor / Vice Mayor / Council Member / Chair / Vice Chair / Commissioner — but they are all just voting members of the body. **Roll-call votes.** On most substantive motions the clerk (or chair) calls the roll: they speak each member's name and the member answers right after — "Council Member Goldstein? — Yes. Council Member Hawley? — No. ..." When the roll is done the clerk or chair usually reads the outcome into the record: "Motion carries, 6 to 1." There is no speaker labeling in the transcript — you infer who is speaking from the name called immediately before the answer. **Voice votes.** Not every motion gets a roll call. Routine items — especially the consent agenda — are often approved by unanimous voice vote: the chair asks "any no votes or disqualifications?", hears none, takes a "motion / second," and declares it carried. No members are named individually. This is a real, passed vote and must be captured — but you did not hear anyone vote by name. Record it as a vote with `vote_method: "voice"` and an empty `votes` list (see the schema). The transcript is an imperfect machine transcription. Names are often garbled (the same member may appear as "Haen", "Hain", "Hahn"). Read through the noise; use the roster below as the ground truth for who is on the body. ## The voting body (roster — ground truth) Only these people cast votes. Resolve every name you attribute to exactly one roster member. {{ROSTER}} ## Your sources You may be given up to **two** transcripts of the same meeting: 1. **Primary — the Whisper transcript** (the "## Transcript" section below). This is your main source. Prefer it for who said what: it has the best flow and the most reliable attribution of a spoken vote to the member who cast it. 2. **Secondary — closed captions** (the "## Closed captions" section at the very end, when present). These are the meeting's official Granicus captions — noisier, with no speaker flow — but an *independent* record that sometimes contains a roll call the Whisper transcript lost. The Whisper transcript occasionally **degenerates**: its decoder gets stuck repeating one phrase (most often "Thank you." over and over, or a short loop) for a stretch — typically after a recess — and the real speech in that window is simply missing from it. A repetitive run like that is a **gap**: a vote may have happened there that the Whisper transcript does not contain. How to use the two sources together: - **Read the Whisper transcript as the spine.** Extract every roll call you find in it, as usual. - **Use the captions to fill gaps.** Where the Whisper transcript is degenerate (a "thank you" loop or similar) or silent over a stretch, look in the captions for a roll call in that same window and extract it from them. - **Reconcile — never double-count.** The two sources overlap heavily. A single real roll call must produce exactly **one** entry in your output, even when it appears in both transcripts. Match by what the vote was on, its tally, and its approximate timestamp; do not emit the same vote twice just because you read it in both places. In particular, do NOT emit both a `voice` entry and a `roll_call` entry for the same motion: if you heard members answer by name (a roll call), emit only the roll-call entry — the voice-vote form is for motions where nobody was named. When the same motion shows up at nearly the same timestamp in both sources, that is one vote, not two. - **When a vote is found only in the captions**, extract it from them and set `source_note` to a short note saying so (e.g. "recovered from captions; the Whisper transcript degenerated into a repeated 'thank you' loop over this stretch"). Its timestamps come from the captions. - **If no captions section is provided**, the Whisper transcript is your only source — proceed with it alone. ## What to extract Return a list of **roll calls**, in the order they occur. There are two kinds: - `attendance` — the opening roll call where members answer "here"/"present". Capture it, kind = `attendance`. - `vote` — a vote on a motion, whether taken by roll call (members answer yes/no/abstain individually) or by voice (see above). **Capture EVERY motion that gets a vote — completeness matters as much as accuracy.** Missing a whole vote is the most common and most damaging error. The votes easiest to miss, and which you must NOT skip: - The **consent agenda** vote near the start ("Approve the Consent Agenda as read"). It nearly always happens, and is frequently a **voice vote** — capture it as one (`vote_method: "voice"`). - **Quick unanimous votes.** A routine item can pass in seconds with little discussion — still a real vote, by roll call or voice, and must be captured. - **Procedural / housekeeping motions** — these are real votes: "add an item to the agenda" (often needs a 2/3 vote), "suspend the 30-day rule", "set aside the rule about starting items after 10 p.m.", "continue this item to the next meeting", "refer this to the Internal Affairs Committee", and "agendize a discussion on X" for a future meeting. Councilmember requests at the end of the meeting frequently get voted on this way — scan the late portion of the transcript for them. - **A second vote on the same item.** One agenda item can produce two roll calls: a substitute motion (voted first) and then the main motion, or a re-vote to restate the record. Capture both, in the order they occur. Do not, however, invent a roll call that isn't there — completeness never means guessing (see the rules below). For each roll call provide: - `kind`: `vote` or `attendance`. - `vote_method`: `roll_call` or `voice`. Use `roll_call` when members answer individually by name (and for `attendance`); use `voice` for a voice vote where no members were named. For a voice vote: return an empty `votes` list, leave `stated_yes`/`stated_no` null unless an actual count was spoken, and set `stated_result` from what was declared ("carried"/"failed"). - `start_seconds` / `end_seconds`: the timestamps (from the transcript markers) where this roll call begins and ends. - `motion_text`: a short plain description of what was moved, if the transcript makes it clear (else null). - `agenda_item_hint`: the number of the item on THIS meeting's agenda that the vote is taken under, if stated near the vote (e.g. "4.3"), else null. An item number that refers to some other meeting (a reconsideration or follow-up of an item "heard March 17") is not this vote's item — use the item the council is on now (often Councilmember Requests), or null. - `stated_yes` / `stated_no`: the tally the clerk/chair SPOKE, as two integers — `stated_yes` is the ayes, `stated_no` is the noes ("motion carries 6 to 1" → `stated_yes: 6, stated_no: 1`). ONLY if a count was actually spoken. Do NOT compute it yourself from the votes. Use null for both if no tally was spoken. - `stated_result`: `carried` or `failed` if the outcome was spoken ("motion carries" / "motion fails"), else null. - `source_note`: null for a normal roll call read from the Whisper transcript. Set it to a short string ONLY when this roll call was recovered from the closed captions because the Whisper transcript was degenerate or silent over its window (see "Your sources"). - `sequence_role`: how this roll call relates to the others on the same question — one of `standalone`, `substitute`, `main`, `amended`, `restated`, `reconsideration`, `revote` (see "Relating successive votes"). Default `standalone`. - `sequence_group`: a small integer (starting at 1) shared by every roll call that is part of one deliberation on the same question; `null` for a standalone vote. - `sequence_note`: one plain-language sentence saying what changed versus the prior related vote; `null` when standalone. - `item_dissents`: for a BUNDLED motion (almost always the consent agenda), the exceptions members registered against individual sub-items. See "Consent-agenda exceptions" below. `null` or omitted when there are none. - `votes`: one entry per member you heard vote (empty for a voice vote), each with: - `member`: the exact roster name, or null if you cannot confidently tell who it was. - `vote`: `yes`, `no`, `abstain`, or `absent` (for attendance use `present` / `absent`). - `evidence_quote`: the short transcript snippet this vote is based on (the name + answer). - `evidence_seconds`: the timestamp of that snippet. ## Rules (accuracy over completeness) 1. **One roll call per motion.** Some agenda items get two separate votes — a substitute motion then the main motion, or a re-vote "to make it clean." These are SEPARATE roll calls, each with its own tally. Never merge two motions into one roll call, and never split a single roll call into two. When two or more roll calls are part of one deliberation on the same question, keep them separate here but link them with the `sequence_*` fields (see "Relating successive votes") — linking is not merging. 2. **Never guess a name; never drop a bare answer.** In a garbled roll a member's answer often appears as a bare "Yes" / "Aye" / "I vote aye" with no name attached. Record EACH such answer as a vote with `member: null` — never drop it. A vote you can't name still counts toward the tally. If a spoken name doesn't clearly match a roster member, still record the vote with `member: null`. Do not assign a vote to a roster member you aren't confident you heard. 3. **A mover or seconder has not thereby voted.** A member who moves or seconds a motion has not cast a recorded vote by doing so. Never record the mover or seconder as a `yes` vote unless you also hear them answer in the roll call. 4. **The spoken tally is ground truth for the count — transcribe it, don't compute it.** If the clerk says "6 to 1", `stated_yes` is 6 and `stated_no` is 1, even if you only clearly heard 5 yes votes. Leave both null when no count was spoken. 5. **The count can never exceed the body.** There are only as many voting members as the roster lists. If you seem to have heard more yes+no votes than that, you misread something — re-read before returning. 6. **Not everyone votes on every motion.** A member may **recuse** themselves (step aside for a conflict of interest — often stated: "I'll be recusing myself on this item") or be absent for part of the meeting, so a motion can carry with fewer voters than the full body (a 6-0 where one seat sat out). Record only the votes you actually heard on each roll call — do not carry a member's vote over from another motion, and do not pad a roll call up to full body. If someone was announced as recused or stepped away, mark them `absent` for that roll call. 7. **Carry absences forward.** If the opening attendance roll shows a member absent (or a seat vacant), mark that member `absent` on every later roll call unless the transcript shows them arriving and voting. 8. **Every heard vote needs evidence.** Populate `evidence_quote` and `evidence_seconds` for each vote so a human can verify it. 9. **Never infer gender or pronouns from a name.** 10. **A dissent on a consent sub-item is not a no on the bundle.** Before the consent motion the chair asks for "no votes or disqualifications" and members answer for individual items ("put me down for a no on 2.6"). Record those in `item_dissents` — NOT by changing anyone's vote in `votes` and NOT by adjusting the tally. The bundled roll call is usually still unanimous, and both facts are real. Scan the minutes of transcript BEFORE the consent motion for these declarations, and the clerk's read-back of the motion, which usually lists them. See "Consent-agenda exceptions". 11. **Only real votes.** Ordinary discussion that happens to name a member ("thank you, Mayor") is not a vote. A roll call is a dense run of name→answer pairs; a voice vote is a "motion / second / any objections / carried" exchange. ## Read each roll call as a conversation Real roll calls are messy. People interrupt, ask which motion is up, explain themselves, and change their minds before the result is announced. The rules above describe the usual shape; they are not a script the transcript has to match. What you are recording is **each member's vote as it finally stood when the result was announced** — read the whole exchange, then decide. Situations you will meet, none of which should trip you up: - **A changed answer.** A member answers, then — often after asking or being told which motion this is — gives a different answer: "No. — Wait, is this the substitute? — It is. — Then yes." Their vote is the final answer, not the first word. Quote the exchange that shows the change. - **Discussion in the middle of the roll.** A member uses their turn to explain their reasoning, someone answers a question, and the roll resumes. The vote is the answer they eventually give, which may come after several sentences. - **An explanation before the answer.** "I'm going to vote no because…" is a no; "I can't support this one" is a no; "I'll support it" is a yes. Read what they meant, not just a keyword. - **A re-called name.** The clerk calls someone again ("I'm sorry, Council Member Hawley?") or asks them to repeat. One member, one vote: the clarified answer. - **Out-of-order or batched answers.** A member who stepped away answers at the end; the chair votes last; two people answer at once. Place each answer with the member who gave it. - **Recusals announced inside the roll** ("Council Member van Overbeek is recused") — record `absent` for that roll call. If an exchange is genuinely ambiguous even after reading it as a whole, say so honestly: record the vote you can support with `member: null` or leave the member off, rather than forcing a reading. ## Consent-agenda exceptions Chico approves the consent agenda as ONE motion, but before taking it the chair asks "are there any no votes or council disqualifications?" and members register dissent against individual sub-items — "put me down for a no on 2.6", "I'll be registering a no vote on item 2.6", "I'm recusing myself from 2.3". The clerk usually reads it back when stating the motion: "approve the consent agenda as read, with it noted on item 2.6 — three nos: Council Member Hawley, Council Member Winslow, and Council Member Goldstein." The roll call that follows is still on the WHOLE bundle, and it is routinely unanimous — a member who registered a no on one sub-item still votes yes on the consent motion. Both facts are true and both must be recorded: - `votes` and the tally describe the bundled motion exactly as called. If the roll was 7-0, every member is `yes` and the tally is 7-0. Do NOT mark someone `no` in `votes` because they dissented on a sub-item, and do NOT adjust the tally. - `item_dissents` records the exceptions, one entry per (item, kind): ```json "item_dissents": [ { "item": "2.6", "kind": "no", "members": ["Hawley", "Winslow", "Goldstein"], "evidence_quote": "with it noted on item 2.6. Three nos. That was Council Member Hawley, Council Member Winslow, and Council Member Goldstein.", "evidence_seconds": 1004.0 } ] ``` `kind` is `no`, `abstain`, or `recused`. `item` is the agenda number as spoken ("2.6"), or null if the member never names one. Use exact roster spellings in `members`, same as `votes`. Ground every entry in something actually said. If a member declares a no vote but never names an item, still record it with `item: null` rather than guessing which item they meant. If nobody registers an exception, omit the field — an empty consent motion is the normal case. ## Relating successive votes One agenda item often produces more than one roll call, because the body works a single question through several motions before settling it. A substitute motion is voted first; when it fails the body falls back to the original ("main") motion. A motion is amended and re-voted. The clerk asks to "restate" a motion to clean up the record. A member "moves to reconsider" an item decided earlier. These are all **separate roll calls with their own tallies** (rule #1 stands) — but they belong to one deliberation, and downstream we group them so a reader sees the whole arc and which outcome is operative. When a roll call is a substitute / amendment / restatement / reconsideration / re-vote of another motion **in this same meeting**, set all three `sequence_*` fields on every roll call in that arc: - Give each roll call in the arc the same `sequence_group` integer (the first arc you find is `1`, the next distinct arc `2`, and so on). - Set `sequence_role` on each: `main` for the underlying/original motion, `substitute` for a substitute motion, `amended` for a re-vote after an amendment, `restated` for a "restated motion," `reconsideration` for a motion to reconsider a prior decision, `revote` for a plain re-vote to clean up the record. - Set `sequence_note` to one sentence explaining what changed relative to the prior related vote — e.g. "After the substitute motion failed 3–4, the council fell back to Vice Mayor Bennett's original motion." Ground every link **strictly in spoken cues** — "substitute motion," "we'll vote on that one first," "restate the motion," "move to reconsider," "let's re-vote." If the transcript does not actually say the roll calls are related, leave them `standalone` / `null` / `null`. Two votes on the same agenda item are NOT automatically an arc — a meeting can approve item 5.2's staff report and later, separately, refer 5.2 to committee; only link them when the transcript ties them to the same question. Never invent a relationship to tidy up the output. ## When no tally was spoken Commissions (and some council votes) frequently do NOT speak a numeric tally. When no tally is spoken there is no backstop for the count downstream, so be **exhaustive** in capturing every answer on that roll call — every bare affirmation, every named vote. A missed answer on a no-tally roll call is uncorrectable later. ## Self-check before returning **When a tally was spoken, check your votes against it.** If the yes and no votes you recorded don't add up to the clerk's count, you have almost certainly misread part of the exchange — most often a member who changed their answer, an answer you attached to the wrong member, or one you missed. Re-read that roll call as a whole conversation and correct the votes the transcript actually supports. Never change a vote just to make the numbers fit: if the transcript doesn't support a different reading, leave it as you heard it and let the mismatch stand — it will be reviewed by a person. Also: for any vote with **no spoken tally**, re-read its surrounding transcript lines once more — specifically hunting for (a) bare affirmations ("yes"/"aye" with no name) you may have skipped, and (b) any present member you haven't yet placed on that roll call. Add anything you find. ## Output format Return **only** a JSON object — no prose, no markdown fences — in exactly this shape: ```json { "roll_calls": [ { "kind": "vote", "vote_method": "roll_call", "start_seconds": 3996.1, "end_seconds": 4012.1, "motion_text": "Adopt the resolution amending the fee schedule", "agenda_item_hint": "4.3", "stated_yes": 6, "stated_no": 1, "stated_result": "carried", "source_note": null, "sequence_role": "main", "sequence_group": 1, "sequence_note": "After the substitute motion failed 3–4, the council fell back to the original motion to adopt the fee schedule.", "votes": [ {"member": "Goldstein", "vote": "yes", "evidence_quote": "Council Member Goldstein? Yes.", "evidence_seconds": 3996.1}, {"member": "Hawley", "vote": "no", "evidence_quote": "Council Member Hawley? No.", "evidence_seconds": 3998.4} ] }, { "kind": "vote", "vote_method": "voice", "start_seconds": 380.0, "end_seconds": 392.0, "motion_text": "Approve the Consent Agenda as read", "agenda_item_hint": "2", "stated_yes": null, "stated_no": null, "stated_result": "carried", "source_note": null, "sequence_role": "standalone", "sequence_group": null, "sequence_note": null, "votes": [], "item_dissents": [ { "item": "2.6", "kind": "no", "members": ["Hawley", "Winslow", "Goldstein"], "evidence_quote": "with it noted on item 2.6. Three nos. That was Council Member Hawley, Council Member Winslow, and Council Member Goldstein.", "evidence_seconds": 388.0 } ] } ] } ``` Use the exact roster spelling for `member` (or `null`). Use `null` (not the string "null") for absent fields, including `stated_yes`/`stated_no` when no tally was spoken, and `sequence_group`/`sequence_note` for a standalone vote. `vote` is one of `yes`, `no`, `abstain`, `absent`, `present`. `sequence_role` defaults to `standalone`. If there are no roll calls, return `{"roll_calls": []}`. ## Transcript Each line is `[start–end]` seconds followed by the text. {{TRANSCRIPT}} ## Closed captions (secondary source) The meeting's official Granicus closed captions, if available — same `[start–end] text` line format. Use these ONLY to fill gaps where the Whisper transcript above is degenerate or silent, and reconcile against it so no roll call is counted twice (see "Your sources"). Attribute every recovered name to a roster member the same way. {{CAPTIONS}}Vote Clerk said We counted Check Item 2 7-0 7-0 ✓ match Item 5.1 3-4 3-4 ✓ match Item 5.1 5-2 5-2 ✓ match Item 6.2 7-0 7-0 ✓ match - 6
A quick check, then it's published — and you're part of this step
Honesty about our own process: this pipeline is mostly automated. Before publishing, a person skims the draft for major problems — a wrong vote outcome, a garbled item — but it's a quick check, not a line-by-line fact-check against the video (this recap was published November 18, 2026). That's why reader corrections genuinely matter here: if you spot an inaccuracy, tell us and we'll check it against the recording and fix it. Corrections are noted on the page, not silently edited.