Flock and Ding Dong Dash in Porterville

Leave a comment

Image by Gemini AI

“Knocking on people’s doors and leaving the area”.

That was the ‘reason’ Porterville Police Department entered into the Flock Automated License Plate Reader system for three searches in late July and early August, 2026. Each time, they searched over 700 networks.

On July 29, 2026, they checked the system twice, for a ‘487’ (grand theft). Both times, they checked 1 network.

On August 19, 2026, they checked 710 networks for “RED TOYOTA CAMRY”.

Ding dong dash, over 700 networks. (fast runners? Fast and Furious ready to pick them up and flee the state? The long way?)

Grand theft, 1 network. (Too much to carry out of town?)

How many Red Toyota Camrys do you suspect are in those 710 networks?

I wonder if Arte Johnson’s character Wolfgang would say “verrrry interesting… but shtupid!”?

Can I See Your Flock?

Leave a comment

Image by Gemini

On July 14, 2026 I filed a second public records act request for information about the Visalia Police Department‘s use of the Flock Automated License Plate Reader system. In that request, I asked for information regarding any agreements or other documentation that would allow VPD to access any Flock cameras operated by the Visalia Economic Development Corporation, Lowe’s, and Home Depot. The following is what I received today, August 20, 2026.

No documents were presented regarding Lowe’s and Home Depot, so, assuming the lawyers are giving me the all the information the city has, there are no agreements of any kind for the Visalia Police Department to access any data collected by cameras owned by those companies.

Does that mean if VPD wanted to check that data, they’d have to get a subpoena? Can they simply call over and ask? If granted permission (and why would they not be?), do they have to go to the location and get access using the store’s system, or can they log in and take the data directly from Flock’s servers? I don’t know.

As far as the Visalia Economic Development Corporation is concerned, I’m not certain they’ve ever actually installed any cameras. One camera is shown in the industrial park, but I have as yet been unable to determine if that is part of the VPD network, or is operated by VEDC. At approximately $3,000 each per year, VEDC may not have the money to maintain the subscription.

What’s more interesting is the letter from the VEDC to a rather extensive email list about Flock needing to preserve data due to a class-action lawsuit that is pending. Check out some of the people they sent it to:

A Visalia City Council member, the Visalia City Manager, the Visalia Assistant City Manager, someone at Southern California Edison, two or more construction companies, the Visalia Unified School District Superintendent, the Tulare County Office of Education Superintendent, and several others identified by name only. Why most of them need to be informed about a class action lawsuit against Flock is puzzling.

The City of Visalia has closed out this public records request, telling me “no other records matching your request exist or are in the possession of the City of Visalia”.

My previous Flock-related posts:

P.S. – Since Visalia is using grant money for the first four years of this contract, there has been no ongoing expense for the city. They will eventually have 22 cameras up, which could result in a $66,000 a year cost to maintain the system, once those grants expire. Your tax dollars are and will be paying to surveil you every time you drive by a Flock camera. Smile, won’t you?

Hidden in plain sight, but you are not allowed to see it

Leave a comment

Half A Million Flocks in May, 2026

Leave a comment

In April of 2026, I made a public records request of the Visalia Police Department. One of the things I asked for in that request was the logs of every outside agency that accessed the data collected by Visalia’s police department. I didn’t expect the sheer size of the results. I received audit logs for 18 months, running to tens of thousands of pages. I’m going to look at the latest (and biggest) of those files here.

From May 1, 2026 through June 1, 2026, there were 507,696 “hits” on the Flock data collected by Visalia PD. I’ve tallied the results to see who is searching license plate files (and other search terms) in Visalia. (Visalia accessed it’s own data 1,634 times in that month)

The biggest searcher was the California Highway Patrol, at 46,693 inquiries in just that one month’s time. Riverside County Sheriff’s Office was next, at 42,957.

There’s no way they thought vehicles they were “checking” for were in Visalia over 40,000 times each. It looks very much as if they simply have “all” selected for any search they do. Other agencies on down the list seem to be a bit more circumspect in their searches, but still cast wide nets when they do a Flock search.

Here’s a .txt file with the list, followed by an Excel list.

May 2026 audit

Beginning Search Time: May 1, 2026, 07:00:00 AM UTC
Ending Search Time: June 1, 2026, 06:59:59 AM UTC
Unique organizations: 309
Records tallied: 507,696

Org Name Tally

RankAgency / OrganizationCount
1California Highway Patrol46,693
2Riverside County CA SO42,957
3San Francisco CA PD28,422
4Los Angeles CA PD19,367
5Orange County SO CA19,114
6Los Angeles County CA SD17,766
7San Jose CA PD15,670
8San Bernardino County CA SO12,167
9Oakland CA PD11,855
10San Diego County CA SD9,855
11Fremont CA PD7,241
12City of Riverside CA PD7,054
13Sonoma County CA SO7,054
14Ontario CA PD6,786
15NCRIC6,742
16Irvine CA PD6,585
17Fontana CA PD5,588
18Ventura County CA SO5,543
19Santa Clara CA PD5,472
20Contra Costa County CA SO5,191
21Elk Grove CA PD4,942
22Daly City CA PD4,939
23San Joaquin County CA SO4,724
24Kern County CA SO4,660
25Santa Rosa CA PD4,550
26Stockton CA PD4,516
27San Bernardino CA PD3,851
28Solano County CA SO3,792
29Chula Vista CA PD3,725
30Bakersfield CA PD3,560
31Vacaville CA PD3,402
32Sunnyvale CA PD3,218
33Corona CA PD3,185
34Placer County CA SO3,028
35Salinas CA PD3,014
36Hayward CA PD2,878
37Murrieta CA PD2,854
38Pasadena CA PD2,761
39Chino CA PD2,691
40Concord CA PD2,613
41Sacramento CA PD2,569
42Newport Beach PD CA2,510
43California Department of Corrections2,476
44Buena Park CA PD2,463
45Livermore CA PD2,434
46Napa County CA SO2,422
47Costa Mesa CA PD2,408
48Anaheim CA PD2,324
49San Mateo CA PD2,259
50Santa Maria CA PD2,245
51Marin County CA SO2,239
52Sacramento County CA SO2,142
53Orange CA PD2,139
54Fairfield CA PD2,120
55National City CA PD2,038
56Alhambra CA PD1,984
57Montclair CA PD1,956
58Petaluma CA PD1,939
59Santa Barbara County CA SO1,891
60Cypress CA PD1,805
61Morgan Hill CA PD1,787
62Garden Grove CA PD1,699
63Rialto PD CA1,693
64San Leandro CA PD1,665
65Fullerton CA PD1,646
66Visalia CA PD1,634
67Turlock CA PD1,608
68Santa Ana CA PD1,465
69Tracy CA PD1,440
70West Sacramento CA PD1,433
71Union City CA PD1,391
72Monterey County CA SO1,389
73Rocklin CA PD1,384
74Manteca CA PD1,367
75Simi Valley CA PD1,364
76Greenfield CA PD1,323
77Burbank CA PD1,289
78Butte County CA SO1,287
79Ventura CA PD1,275
80Citrus Heights CA PD1,242
81Gilroy CA PD1,237
82Upland CA PD1,227
83Redwood City CA PD1,191
84Downey PD CA1,166
85Hanford CA PD1,153
86El Cajon CA PD1,149
87Tulare County CA SO1,136
88Hercules CA PD1,136
89Riverside County CA District Attorney1,121
90Brentwood CA PD1,115
91Oceanside CA PD1,112
92Vallejo CA PD1,099
93Merced County CA SO1,079
94San Bruno CA PD1,054
95Desert Hot Springs CA PD1,049
96Cal Fire1,042
97Placentia CA PD1,028
98Marina CA PD990
99Glendora (CA) PD982
100Imperial City CA PD932

There are 209 additional unique organizations with counts ranging from 899 down to 1. You can see the entire list in the Excel file.

Here are my previous Flock-related posts:

The Flock Was Startled

Leave a comment

Pressure has been mounting on Flock Safety concerning it’s Automated License Plate Reader system. It’s widespread adoption across the United States has reached a level of public awareness and pushback that led the Georgia-based company to release an “update” to it’s policies, dated August 13, 2026. The cat of 24/7 surveillance and abuse by law enforcement officials is out of the bag, and it has startled the flock. Here are some highlights to it’s new policies, and some comments. (See the list at the end of this blog for all of the articles I’ve posted on the Flock system.)

Privacy

When we started Flock 9 years ago, we set the default ALPR retention period to 30 days, unless state or local policy decided on a shorter or longer period. We believed this struck a careful balance between safety and privacy. 

Today, we are updating our recommendation and default to a 7-day retention, and introducing “Evidence Mode.” Our analysis shows that over 90% of searches without a full plate are done within a week. Evidence Mode, which will roll out in the coming weeks, addresses the exceptional cases that take longer: detectives can preserve specific ALPR data as evidence for an active investigation in cold storage, consistent with existing laws and policies.

“Recommendation and default” to 7-day retention. That doesn’t indicate that the customer agency can’t choose the 30-day and ignore the 7-day option. I suspect many agencies will opt for the 30-day setting. The “evidence mode” will probably be useful in ongoing cases.

Existing customers will keep their current, democratically approved retention periods. Customers who adopt the 7-day recommendation will receive Evidence Mode at no cost. Every community will continue to choose the retention period that fits its public safety strategy.

So this means every agency already using the Flock Automated License Plate Reader system (currently at more than 5,000 agencies, according to Flock) will continue with the 30-day data retention plan. Only new customers will have operate under the new “option” to only keep data for 7 days. Shall we take a wild guess at how many will opt for something other than the “default” suggestion?

And that “democratically approved” line is an attempt to mask that most agencies received approval from their city councils or county board of supervisors in the “consent calendar” agenda. That usually means no public discussion by the body, and the only members of the public that knew about it were those who bother to read the consent calendar and it’s agenda packets. Most communities never realized their leaders had bought (leased, actually) the system until problems started hitting the press. That’s how the Visalia, Porterville, and Farmersville city councils approved the contracts. The police departments asked, the cities put the items on the consent agendas, and they were approved with no discussion.

We are also introducing Offense filtering for sharing. Now, cities can choose which type of offenses are permissible for other agencies to access their cameras. For example, City A could allow City B to search its cameras only for a stolen vehicle, missing person, or violent crime while blocking searches related to immigration enforcement. This gives communities more control over data sharing while preserving collaboration where policies align.

This will require agencies to use the exact same codes for access to data from another agency. Computers are notoriously literal-minded, and see ‘INVESTIGATION’ as a different code than ‘investigation’. The California code for stolen vehicle is ‘10851’. If it’s entered as ‘stolen vehicle’, that’s a different offense as far as the computer is concerned. Most agencies will likely not activate ‘Offense filtering’, and just let other agencies have access. I suspect few will institute this option.

Accountability

Abuse of Flock technology, at any level, is unacceptable. We have strengthened safeguards over the past nine years, from basic audit logs to proactive monitoring. 16 weeks ago, we introduced Audit Assistance, which detects abnormal activity and flags it for Administrator review. In recent weeks, those reviews have been associated with arrests of several law enforcement officers who allegedly abused the system. More than one-third of our customers have voluntarily adopted Audit Assistance

Just now they’re instituting more robust methods of detecting unauthorized abuse. Most past abuses have been brought to light by news media or citizen auditing of access logs, not by the departments involved themselves.

We will now require all law enforcement customers to adopt this feature by the end of this year. In addition, we will institute proactive lockout. When a user’s activity meets defined criteria for abnormal behavior, Flock will automatically suspend access pending administrator review. The goal is to intervene before misuse becomes recurring or widespread.

They’re going to take three months to institute these procedures, while current abuse goes unchecked.

In July 2025, we introduced an optional case code requirement for searches. Results from participating agencies have been promising, so we will now require case codes for all law enforcement searches by the end of the year. Agencies may bypass the requirement in emergencies, but every exigent search will be flagged for administrator review.

Only a year ago did they introduce an “optional” requirement that searches be tied to a specific case number. This allowed agencies to ‘opt out’ (or just never ‘opt in’) to this, resulting in searches listed as “investigation”, “stolen”, or “theft”. A case number should always have been required.

Data Ownership

From the beginning, we have been clear that our customers own the data captured by their ALPR cameras. This has always been the case, but some of our contractual language has confused the public on this crucial point. To make that commitment easier to understand, next week we will publish an easy to read / plain English explanation of our contract on our website, organized section by section. The principle is simple: customers own the data, decide who can access it, and choose who they share it with

The contract signed by the City of Visalia states, in three places, that data generated by the Flock cameras utilized by the Visalia Police Department is owned by the city, and will not be sold to other parties. The same contract also says:

  1. DATA USE AND LICENSING
    4.1 Customer Data. As between Flock and Customer, all right, title and interest in the Customer Data, belong to and are retained solely by Customer. Customer hereby grants to Flock a limited, non-exclusive, royalty-free, irrevocable, worldwide license to use the Customer Data and perform all acts as may be necessary for Flock to provide the Flock Services to Customer. Flock does not own and shall not sell Customer Data
    .
  • 4.2 Customer grants Flock a non-exclusive, irrevocable, worldwide, royalty-free, license to use the Customer Generated Data for the purpose of providing Flock Services. Flock does not own and shall not sell Customer Generated Data.
  • 4.3 Anonymized Data. Flock shall have the right to collect, analyze, and anonymize Customer Data and Customer Generated Data to the extent such anonymization renders the data nonidentifiable to create Anonymized Data to use and perform the Services and related systems and technologies, including the training of machine learning algorithms. Customer hereby grants Flock a non-exclusive, worldwide, perpetual, royalty-free right to use and distribute such Anonymized Data to improve and enhance the Services and for other development, diagnostic and corrective purposes, and other Flock offerings. Parties understand that the aforementioned license is required for continuity of Services. Flock does not own and shall not sell Anonymized Data.

They claim “some of their contractual language has confused the public”, and they’re going to release a “plain English” explanation of their contracts. There contracts also say this:

  1. MISCELLANEOUS
    11.1 Compliance With Laws. Parties shall comply with all applicable local, state and federal laws, regulations, policies and ordinances and their associated record retention schedules, including responding to any subpoena request(s).

Maybe I’m “confused”, but that reads to me that they’ll give up those data files to anyone with a subpoena. I’m not confident Flock will stand up to an “administrative subpoena” issued by ICE or DHS. We’ll see what the “plain English” notice says. I’m also wondering about their 3-times repeated comment that Flock does not own and will not sell customer data. They won’t sell it, but does saying the agency owns it’s data mean that Flock, while it won’t ‘sell’ it, can give it away? Like to AI training? (That is a term in the contract. They’ll use “anonymized” data to train “machine learning algorithms”. Who else?)

There’s been a growing pushback against Flock for several years, and it’s reached a tipping point. They’re now adjusting their contracts and attempting to make “options” look like the operating standards. The 7-day retention is a choice, not a requirement, as some media sources are reporting. New contracts can still opt for the 30-day retention, and existing users don’t have to change, either.

This action by Flock is much like that line from Macbeth, “Told by an idiot, full of sound and fury, signifying nothing”. It is doubtful most agencies will lock themselves into 7-day time frames unless their controlling governments force it upon them. On their own, they’ll opt for the 30-day, and possibly longer, if that option is afforded to them. I don’t mean that as a slam, but it would be organizationally logical to take advantage of the abilities presented.

The real problem is the warrantless dragnet collection of data on citizens in every community with these cameras (of whatever brand, it’s not just Flock). Courts are finding similar mass data-gathering to be in violation of the 4th Amendment, and eventually one will make it to the Supreme Court of the United States dealing with license plate readers. While Flock and others insist there is no facial recognition capability, it’s only a matter of time and software development. The cameras are already technologically advanced to provide that data, it just has to be programmed. It’s just a matter of time.

Here are my previous Flock-related posts:

Flock Me – Round 2

Leave a comment

In my post, “The Final Flock – and the answer is “NO”, the City of Visalia closed out my Public Records Request without providing all of the information I requested, citing privacy laws, and police department policy.

Sorry, that’s not good enough. I’m trying again. Today, August 7, 2026, I’ve filed the following supplemental Public Records Request:

RE: Formal Public Records Request & Demand for Disclosure — Personal ALPR Data (Plate: JJRJR)

Supplemental to PRAR Dated April 24, 2026 / Response Dated August 3, 2026

Dear Custodian of Records and Ms. Berglund:

I am writing to formally request—and respectfully demand—the release of public records pursuant to the California Public Records Act (CPRA), California Government Code § 7920.000 et seq. This letter serves as a specific, narrow request following the supplemental response issued by Herr Pedersen & Berglund LLP on August 3, 2026 regarding my initial April 24, 2026 request.

1. Scope of Request

Pursuant to the CPRA, I request copies of all Automated License Plate Reader (ALPR) records, data files, metadata logs, and associated digital images captured or maintained by the Visalia Police Department (including fixed cameras and mobile units) that reference or identify the following California license plate registered to me:

  • License Plate: JJRJR
  • Time Period: The 30-day period immediately preceding and ending on the date this written demand is received by the City/Department.

2. Legal Basis and Response to Department Denials

The City’s August 3, 2026 response asserts that raw ALPR data is exempt under the CPRA balancing test (Gov. Code § 7922.000), cites Department Policy 428.2 stating ALPR data is “not open to public review,” and references Civil Code § 1798.90.55 regarding transfers to non-public agencies. Respectfully, these assertions misapply established California case law and statutory rules regarding individual requests for personal records.

A. Rejection of Blanket Exemptions (ACLU v. Superior Court)

In ACLU Found. v. Superior Court of Los Angeles County (2017) 3 Cal.5th 1032, the California Supreme Court explicitly held that routine ALPR data collection is not automatically exempt as an investigative record (Gov. Code § 7923.600) because the scans are indiscriminately gathered rather than generated for a targeted inquiry. Furthermore, the Court established that agencies cannot issue blanket denials or rely on generalized privacy claims to withhold all ALPR records.

B. Absence of Privacy Exemption for the Subject Citizen

The primary justification for withholding raw ALPR data under the CPRA balancing test (Gov. Code § 7922.000) is protecting the privacy of individual vehicle owners. However, when an individual requests their own vehicle’s records, the privacy interest belongs entirely to the requester. Releasing location records of license plate JJRJR to the registered owner of plate JJRJR poses zero invasion of personal privacy. The privacy protections of the CPRA exist to safeguard citizens from government intrusion, not to shield public agencies from disclosing non-sensitive records to the data subject.

C. Statutory Duty to Segregate and Disclose (Gov. Code § 7922.525)

California Government Code § 7922.525 mandates that “any reasonably segregable portion of a record shall be available for inspection by any person requesting the record after the deletion of the portions that are exempted by law.”

To the extent the Department contends that releasing raw database files might expose third-party details or systemic operational configurations, the law requires the Department to redact or segregate those exempt elements and release the non-exempt data points (i.e., timestamps, coordinates/locations, and images matching plate JJRJR).

D. Misapplication of Civil Code § 1798.90.55 and Internal Policy

Civil Code § 1798.90.55 prohibits ALPR operators from selling, sharing, or transferring ALPR information to commercial entities or non-public agency third parties for private commercial use. It does not override an agency’s statutory obligations under the CPRA to release records to a requesting citizen. Furthermore, local agency policy (such as VPD Policy 428.2) cannot supersede state statutory law or Supreme Court precedent.

3. Requested Action & Timelines

Because this request is narrow, limited strictly to a single license plate over a 30-day window, and involves an individual seeking their own vehicle data, it presents minimal administrative burden to locate and process.

Pursuant to California Government Code § 7922.535, please provide a determination within 10 calendar days of receipt of this letter as to whether the City will comply with this request. If the Department asserts that any portion of the requested 30-day dataset or images remains exempt, please cite the specific statutory exemption for each redacted or withheld portion and demonstrate how the public interest in withholding clearly outweighs the public interest in disclosure under Government Code § 7922.000.

Thank you for your prompt attention to this matter and your continued service to our community. I look forward to receiving your response and the responsive data files.”

We’ll see if that shakes loose my data stored on the Flock Automated License Plate Reader system employed by the Visalia Police Department. I’m crossing my fingers, but not holding my breath.

As in my previous posts, here are my blogs about the Flock adventure I’ve been on:

  1. What the Flock?
  2. Well, Flock Me!
  3. More Flock, more fun
  4. Flock you later
  5. Flock the Lawyers
  6. Flock Me A Little Bit
  7. Tick tock tick Flock
  8. The Final Flock – and the answer is “NO”
  9. Hidden in the Flock
  10. Reason me this, Flock

“Reason” me this, Flock

Leave a comment

Cartoon image by Gemini AI

In June of 2026, Visalia Police Department decided they no longer wanted the public to know why they were accessing the Flock Automated License Plate Reader system.

Let’s look at Visalia PD’s “Transparency Page” .CSV file for two different 30 day periods this year. Here’s the one starting on May 5, 2026, which contains the “reason” field in the log.

From the left to the right, we see the following ; an ID number, apparently coded. The “user ID” is merely asterisks. No public idea who is accessing the data. Next is the date and time, in “Zulu” time, which is UTC, which is Greenwich Mean Time. (London, England) Next is the number of “networks” being searched. I don’t know if this means number of cameras, or number of agencies, businesses, and organizations. The final field is “reason”. Each search of the database requires a reason for the search. They’ve told us each access requires a case number, but it’s never been listed on the public facing page. As it is, some of the “reason” entries are simply meaningless. More on that in a bit.

Now, starting sometime in June of 2026, VPD has removed the “reason” field from the file. I’m going to assume it’s visible on their side of the site (all of this stuff sits on Flock servers, requiring users to log in and access the information remotely), but we can no longer see it. Our “transparency” is becoming more opaque.

More

Hidden in the Flock

Leave a comment

Gemini AI image

Flock Automated License Plate readers have been increasingly in the news recently, as problems with the surveillance system have come to light. Many communities have begun to re-think their use of Flock. Los Angeles PD is one large agency that has decided to revisit their use, and has put renewing their subscription on hold for now. Here are my thoughts on Flock and other similar license plate reader operations.

In a perfect world, computer-based information systems like Flock would be a powerful tool for law enforcement. Put in a license plate number, or a vehicle description, and given enough cameras in the system, pinpoint where a stolen car went (or is), find a missing elderly person who drove off and has become confused on how to get home, or a myriad of other scenarios that might benefit from accessing such a database.

The problem is, we don’t live in a perfect world.

More

Tick tock tick Flock

1 Comment

Visalia Police Department Public Records Request – update

On April 19, 2026, I posted “What the Flock?“, my first entry about the proliferation of Flock Automated License Plate Readers in Visalia, California.

On April 24, 2026, I posted “Well, Flock Me!“, about a nearby community (Merced, California) disabling their Flock ALPR system after problems with unauthorized access were discovered. On that same day, I filed a Public Records Request with the Visalia Police Department, about Visalia’s recent installation of Flock cameras. The City had ten days to respond.

On May 5, 2026, I posted “Flock you later“, where the City of Visalia takes advantage of a 14 day extension to provide the requested documents.

On May 11, 2026, I posted “Flock the Lawyers“, wherein the City informs me they have to run it past the lawyers first, and they were targeting June 1, 2026 for release of the documents.

On May 27, 2026, “Flock Me A Little Bit” is the next chapter, in which the City is initially refusing to provide some of the requested documentation, since I was requesting the images in the system of a particular license plate. My license plate. I sent them a copy of my vehicle registration. The next target date for complying with my request was June 20, 2026.

On June 29, 2026, I posted to Facebook, tagging both the City of Visalia and the Visalia Police Department, that they were nine days past their own due date for information. That was at 1pm. By 3pm, I received a “supplemental response to your public records request”, via email. This response stated “The attached document shows the result of a Department audit searching for any monitoring and investigating activity for JJRJR. No data exists.” Except that wasn’t what I asked them to provide. I had no reason to suspect the Police Department deliberately did a search for my license plate, for whatever reason. What I asked for was every instance of my plate being recorded by the system. Those are two different things. They are not going to convince me that my plate has never been recorded by their system.

In that response, they also moved the date again. More information was supposed to be available July 20, 2026.

On July 10, 2026, I received this letter, and a link to a DropBox file with audit logs.

There are tens of thousands of pages (PDF file pages) in response to this part of my request. In case the link in the letter doesn’t work, you can see them at my Dropbox, at this link: https://www.dropbox.com/scl/fo/6u6l4w0jwe54w6y1fvllu/AAZ4mAaSF8XPUJfqUpd2lwo?rlkey=iuqasfx1t6r8hhwgz02h36us1&st=qkgkdqht&dl=0

They state “The Department’s staff is continuing its diligent search and review of requested records. The Department’s staff members estimate they will be able to supplement this response on or about August 20, 2026, earlier if able.”

Tick tock tick Flock

Tulare County Board of Supervisors Public Records Request – final update (Proposition 50)

Leave a comment

On October 14, 2025, the Tulare County Board of Supervisors passed a resolution expressing Tulare County’s stand against Proposition 50, the ballot measure before California voters to redraw Congressional district boundaries. (The proposition passed in the November, 2025 election at 64.42% in favor.)

On June 5, 2026, I became interested in who requested this item be brought forth before the Board of Supervisors, and filed a Public Records Act request. To it’s credit, Tulare County responded quickly and thoroughly.

In that request, I asked who directed the item be placed on the agenda, and who wrote the suggested resolutions (one supporting the proposition, and one opposing it). After wading through a bunch of emails, and numerous copies of the same documents providing background (everyone seems to forward responses with the attachments), it became relatively clear.

Supervisor Vander Poel, in an email to the Board of Supervisors Chief of Staff, Israel Sotelo, on September 29, 2025, said, “I was approached this weekend regarding Tulare County’s position on Proр 50. I noticed Kern County took a position recently. Can we get an agenda item set for mid October to consider the same?”

On October 14, the item was on the Board agenda, with two drafts presented. One in support of the proposition, and one opposed.

Staff researched the issue, with emails flying fast and furious from hither and yon as they worked on Vander Poel’s request.

More

Older Entries