tldr;
California signed three workplace AI bills on September 30. One of them got effectively all the coverage.
That one, SB 947, is also the furthest out: July 1, 2027.
Two others go operative January 1. And a fourth bill, from last year, turns into a hard filing deadline on May 12.
All four ask your tenant the same question: can you prove which system produced this output, what data fed it, and who looked at it before you acted.
This is a lineage problem, and you either have the log or you don’t.
Newsom signed the No Robo Bosses Act on September 30, and by Wednesday I had seen the same headline about eleven times.
AI can’t fire you in California anymore. Humans required. Landmark, first in the nation, etc.
All true. Also effective July 1, 2027, which means the most-covered workplace AI law in the country is the one you have the most time to think about. The news cycle has excellent instincts for drama and none whatsoever for your project calendar.
It is also, and I say this with affection, called the No Robo Bosses Act. A real statute, with a real penalty schedule, named like a Saturday morning cartoon. I’ve spent two years arguing that vendor branding has a shelf life of about nine months while the architecture is permanent. Legislative branding works the same way, and it is just as good at deciding which of your problems gets read about.
He signed three bills touching workplace AI that day. Two of the others go operative January 1, which is three months out. And there is a fourth, from last year, that never entered this news cycle at all, and it comes due on May 12.
That one first, because it is the one that will actually eat your year.
SB 464 is a job catalog project wearing a compliance costume
California pay data reporting currently buckets your workforce into ten EEO-1 job categories. SB 464 replaces that with twenty-three categories built on the SOC system.
Read that again with your “I own the job catalog” hat on.
That is a remap of every job profile you have against a classification scheme you probably don’t currently store. It’s being told to sort the laundry into lights and darks for eight years, and then being told this year it goes by fabric weight. Ten to twenty-three isn’t a longer list of the same thing. It’s a different taxonomy, and nothing in your tenant is going to volunteer the crosswalk for you.
Here’s the part that may beruin your Monday.
SB 464 was signed in October 2025, and employment firms covered it properly at the time. It just got filed under pay transparency rather than AI, so it surfaced in exactly zero of last week’s roundups.
The twenty-three categories attach on January 1, 2027. The first report filed under them is due May 12, 2027, and it covers the 2026 calendar year.
Count the months. The report is seven months out. The year it covers is the one you are ten months into right now.
You are not classifying going forward. You are crosswalking a year of history you already finished generating, under a taxonomy you weren’t using at the time. Nobody is going to re-interview 2026 for you.
And the enforcement half is already live. Since January 2026 the penalties are mandatory rather than discretionary: a hundred dollars per employee for the first violation, two hundred for the next. For a 500-person California headcount that is fifty thousand dollars, then a hundred. Mandatory, as in the court no longer gets to be charmed by your explanation.
SB 951 asks a question you cannot answer retroactively
SB 951 amends Cal-WARN, effective January 1. If a mass layoff or relocation is caused “in whole or in substantial part” by an AI system or other automated technology replacing positions, your notice now has to include four new things.
The count of affected positions attributable to the automation. The specific job functions being automated. The category or type of AI system responsible. And a line at the top of the notice that reads, in plain language, “This notice is for a technology displacement.”
The legislature wrote that sentence out for you. Verbatim. In the statute. That is roughly how much faith they had that anyone would volunteer it.
But sit with the third requirement, because that’s the one with teeth.
Somebody has to name which system automated which roles. Not in the abstract. On a legal notice, with a date on it. Which means the attribution was tracked while the automation was happening, by someone, in a form you can retrieve.
Nobody tracks that today. Automation arrives as four initiatives with four business cases and zero shared ledger, and eighteen months later a VP says the word “efficiency” and the headcount moves.
The attribution is knowable. It’s just only knowable while it’s happening. You cannot write the receipt after the meal.
The statute also doesn’t define “in substantial part,” or “other automated technology,” or what to do about a reduction with mixed causes. So you get to make that call. Which is a polite way of saying someone will make it for you at two in the afternoon on the day the notice is due.
AB 1883 is an inventory question
AB 1883, also January 1, bars employers from using AI-based surveillance tools to recognize, infer, or predict an employee’s emotional state, or to collect neural data.
Five hundred dollars a violation. Which reads like a parking ticket right up until you notice the statute is not counting incidents.
The neural data half is science fiction for most of us. The emotional state half is not.
Go look at what in your stack scores sentiment. Engagement survey free text. Anything doing tone analysis on written feedback. Anything a vendor sold you by using the word “pulse.” I’m not telling you any of that is illegal, because the answer depends on specifics well above my pay grade and well outside my license.
I’m telling you that in three months somebody is going to ask you for the list, and the list does not currently exist.
And now the famous one
Which brings us back to SB 947, where the actual practitioner payload is buried in a clause nobody quoted.
You can’t rely solely on an automated decision system for discipline or termination. Fine, obvious, nobody was going to admit to doing that anyway.
But when an ADS is the primary basis, a human has to review and corroborate the decision “using the information that produced the output.” And if that corroboration turns up anything inaccurate, incomplete, or misleading, you can’t use the output at all.
Not glance at the score. Review the inputs that made the score.
That is a lineage requirement with a human attached. You need to hand a reviewer the underlying data, keep a record that they looked at it, and have that record survive a Labor Commissioner asking about it two years later.
Nine months to build that, document it, and train the people who execute it. If you have ever changed a business process that touches discipline, you know nine months is one release cycle and a prayer.
Which, sure. Except I already wrote the piece about how that goes.
Back in August I wrote about twenty people approving something by not questioning it. The approval chain existed. Every signature was real. Nobody read anything. The governance was architecturally perfect and functionally decorative.
California is about to legally require exactly that mechanism, and I have very little confidence it will work better because a statute asked nicely.
Where the other side has a point
I don’t want cynicism to read as an argument against the law, because it isn’t one.
A human in the loop, even a bored one, beats no human. The notice requirement is genuinely good: telling someone an automated system helped end their job is the bare minimum of treating them like a person. And the lineage work is work you should be doing anyway. The state didn’t invent the obligation. It put a date on one you’d been deferring.
That’s usually how this goes. The regulation isn’t the burden. The regulation is the invoice for eight years of nobody asking.
Monday
Three things, none of which require a lawyer.
Find out who owns the SOC crosswalk. Not eventually. This week. It’s a reconstruction project with a seven-month clock, and those always run long. At most places it is currently nobody’s job.
Inventory every system in your stack that produces a score, a classification, or a recommendation about a person. Not AI systems. Scoring systems. The statutory definition is broader than your mental model of it, and this one inventory feeds three of the four bills.
Map the data and the human for each one. What feeds it, who reviews the output today. Where the answer is “nobody,” that’s your January gap list.
In eight days I’ll be in Vegas watching Workday spend four days selling agentic HR to forty thousand people. California just spent one afternoon writing rules about agents. As far as I can tell, nobody on either stage is talking to the other one.
The vendors will sell you the agent. The state will ask you who approved its output.
Only one of those conversations happens inside your tenant.
– Mike.
P.S. SB 947 got the coverage because it had the best name. SB 464 got filed under the wrong category for a year and is going to cost you more hours than the other three combined. There is a lesson in there about taxonomies.
Sources
Dates and penalty figures in this piece are drawn from the following. Nothing here is legal advice. If any of this touches your tenant, your employment counsel is the person to call. And don't let them tell you I sent them to you. I didn't.
SB 947, the No Robo Bosses Act. Signed September 30, 2026. Effective July 1, 2027.
Ogletree Deakins, California Governor Signs 3 Bills Targeting AI and Workplace Surveillance
Crowell & Moring, New Guardrails on Automated Decision Systems in Discipline and Termination
Legal 500, California Passes No Robo Bosses Act
CNBC, Newsom bans AI “robo bosses,” reversing his earlier veto
Office of Sen. McNerney, signing announcement
SB 464, pay data reporting. Signed October 13, 2025. SOC categories attach January 1, 2027. First report due May 12, 2027, covering calendar year 2026.
Atkinson, Andelson, Loya, Ruud & Romo, California Revamps Pay Data Reporting Obligations
Seyfarth Shaw, Preparing Now for California’s Updated Pay Data Reporting Requirements
Seyfarth Shaw, California Amends Its Pay Data Reporting Requirements
Nilan Johnson Lewis, What Employers Need to Know Before 2027
Payne & Fears, California Expands Pay Data Reporting Obligations Under SB 464
Liebert Cassidy Whitmore, SB 464 Expands Pay Data Reporting Requirements
SB 951, Cal-WARN technology displacement notice. Effective January 1, 2027.
California Legislature, SB-951 bill text
AB 1883, workplace surveillance and emotional-state inference. Effective January 1, 2027.
Mondaq, California Passes AB-1883 Targeting AI Workplace Surveillance of Emotional State and Neural Data
California Assembly, committee analysis of AB 1883
Effective-date validation
CalChamber HRWatchdog, New 2027 Employment Laws