Ticking the AI Box on a WARN Notice: New York Portals, California SB 617, and SB 951

The Executive Messaging Split: Investor Hype vs. Sworn Agency Filings

Boards reward executives who frame cost cuts as AI-driven margin expansion. State labor agencies and discrimination plaintiffs read that exact same transcript against your signed WARN filing.

Sit in the chair between the CHRO, the CFO, and Investor Relations forty-eight hours before a 180-person restructuring. In the draft Q3 earnings script, the CEO tells analysts that generative customer-routing and automated QA agents permanently retired 30% of support seats. Meanwhile, outside counsel sends over a draft New York WARN portal submission and an OWBPA Exhibit A selection statement. Those legal drafts attribute the exact same layoff solely to "macroeconomic demand normalization," leaving the technological innovation box unchecked.

Both documents cannot be true at once. Since March 2025, the New York State Department of Labor (NYSDOL) online WARN portal enforces a strict technology question under N.Y. Lab. Law § 860-b and 12 NYCRR Part 921. Every filing employer must check a mandatory box stating whether "technological innovation or automation" contributed in whole or in part to the layoff. If checked, the employer must name the exact technologies involved. Early state reviews showed almost zero employers checking the box despite constant corporate announcements crediting AI for leaner headcount.

California went further by statute. First, Senate Bill 617 took effect on January 1, 2026, amending Cal. Lab. Code § 1401. That law invalidates every pre-2026 Cal-WARN template that omits Local Workforce Development Board (LWDB) coordination elections, standardized America's Job Center text, and CalFresh food-assistance details. Second, on September 30, 2026, California enacted Senate Bill 951, taking effect January 1, 2027. Covered Cal-WARN notices driven in whole or substantial part by artificial intelligence or automation must carry a top-line banner: "This notice is for a technology displacement."

New York's 90-Day Portal Checkbox and California's 2026–2027 Two-Step

New York tests "in whole or in part" causation at 90 days' advance notice, whereas California's 2027 SB 951 rule tests "in whole or in substantial part" at 60 days. Missing California's live 2026 SB 617 boilerplate already breaks your notice today.

Compare the statutory mechanics across both states before your people operations lead uploads a single PDF or mails an employee packet:

• New York WARN (90 days' notice; 50+ FT employer threshold): Triggered at a single site by 25+ full-time losses representing at least 33% of the site workforce, or 250+ full-time losses regardless of percentage, or a plant closing affecting 25+ workers. The online portal asks whether technological innovation or automation contributed in whole or in part, prompting the filer to name the specific AI models, RPA tools, or automated software systems replacing the roles.
• California Cal-WARN Today — SB 617 (Effective January 1, 2026; 60 days' notice): Applies to any "covered establishment" that employed 75 or more full-time and part-time persons within the preceding 12 months when ordering a mass layoff of 50+ employees in a 30-day period, a relocation, or a termination. Under Lab. Code § 1401 as amended by SB 617, every notice to employees, the EDD, the LWDB, and local elected officials must include: (1) whether the employer plans to coordinate rapid-response services through the LWDB, another entity, or not at all; (2) a functioning phone number and email address for the LWDB plus exact statutory language describing America's Job Center of California services regardless of coordination; (3) CalFresh program description, helpline phone number, and website URL; and (4) a functioning employer contact phone number and email address.
• California Cal-WARN Starting January 1, 2027 — SB 951: Note the calendar trap! Because Cal-WARN requires 60 days' advance notice, any California reduction scheduled to take effect in early March 2027 has notices going out right after New Year's Day 2027. When a covered Cal-WARN event is caused "in whole or in substantial part" by AI or automated technology replacing or automating positions, SB 951 requires the top-of-notice statement "This notice is for a technology displacement," plus the headcount, job classifications, and work locations displaced by automation, the exact job functions automated, and the category of AI or automated system responsible. EDD will publish notice summaries online and issue quarterly statewide automation-displacement reports.

How to Audit Actual AI Causation Before Answering the Question

Do not guess whether AI caused a layoff based on press-release adjectives. Test whether deployed software actually absorbed the eliminated tasks before the seats were cut.

In AI and changing work restructurings, corporate reality falls into three distinct operational buckets. Only two of them belong inside a technology-displacement disclosure:

1. Category A — Deployed task substitution (Tick Yes): An AI coding assistant, automated invoice-matching pipeline, or LLM tier-1 support agent is live in production, handling a documented share of ticket or transaction volume, and management eliminates 55 seats because those exact workflows are now automated. Both NY's "in whole or in part" standard and CA SB 951's "substantial part" standard are triggered.
2. Category B — Capital reallocation without task automation (Tick No, and fix the CEO's script): The company cuts 80 legacy marketing and recruiting roles to free up $14 million in OPEX to buy GPU compute or hire machine-learning engineers. AI did not automate the eliminated recruiting or field-marketing duties; budget priority shifted. Ticking "AI displacement" is factually inaccurate—and Investor Relations must stop describing the cut as "AI replacing legacy workflows."
3. Category C — Aspirational "AI-first" mandate before deployment (High pretext danger): Leadership cuts 60 roles claiming future AI tools will absorb the work next quarter, while redistributing the workload onto surviving human staff today. If automated scoring or telemetry simultaneously picked who stayed and who left, review our AI productivity-metric layoff selection audit immediately—because claiming "automation replaced the seat" when surviving younger or non-leave peers absorbed the work invites pretext findings under McDonnell Douglas.

Remember the OWBPA mirror check under 29 U.S.C. § 626(f)(1)(H)(i). Your 45-day group release packet must state "any eligibility factors" for the termination program. If your NY or CA WARN filing certifies that Tier-1 billing reconciliation was automated by an optical-invoice LLM, your OWBPA eligibility description cannot vaguely recite "individual skill alignment for 2027."

Copy-Ready AI Causation Governance Memo & Cal-WARN Rider

Complete and sign this internal causation memo before locking WARN filings, OWBPA packets, and external communications. Attach the SB 617 / SB 951 rider checklist to every California reduction review.

INTERNAL PRIVILEGED & WORK-PRODUCT GOVERNANCE RECORD
Subject: Workforce Reduction Causation Alignment — WARN, OWBPA & External Disclosures
Event ID: [RIF-2026-Q4] | Target Notice Date: [Date] | Target Separation Date: [Date + 60/90 Days]

PART A — EMPIRICAL AUTOMATION CAUSATION TEST
1. Were specific job tasks of affected roles absorbed by live software, AI models, or robotics prior to or concurrent with role elimination?
   [ ] YES — Deployed Task Automation (Complete Item 2)
   [ ] NO  — Budget reallocation / volume decline / org delayering without task automation (Skip Item 2; prohibit "AI replaced these roles" claims in IR/PR scripts)

2. If YES, document verified deployment facts:
   - Affected Job Classifications & Locations: [List exact titles & sites]
   - Specific Job Functions Automated: [e.g., Automated outbound invoice reconciliation & tier-1 chat triage]
   - Category & Name of Technology System: [e.g., Generative LLM support routing & ERP OCR workflow]
   - Share of Role Capacity Displaced: [e.g., ~65% of weekly ticket volume per FTE]

PART B — CROSS-DOCUMENT CONSISTENCY SIGN-OFF
[ ] NY WARN Portal (if NY triggered): Checkbox matches Part A; system names match Item 2 verbatim.
[ ] CA Cal-WARN Notice (SB 617 Mandatory 2026 Check): Includes LWDB coordination statement, LWDB phone/email, verbatim AJCC services paragraph, CalFresh description/helpline/URL, and active HR phone/email.
[ ] CA Cal-WARN Notice (SB 951 Mandatory from Jan 1, 2027): If Part A = YES ("in whole or substantial part"), top line states verbatim: "This notice is for a technology displacement" and lists counts, roles, sites, automated duties, and AI category.
[ ] OWBPA Exhibit A: Stated eligibility factors align with Part A (task elimination vs. comparative skill scoring).
[ ] Earnings Call / Town Hall / Press Copy: Reviewed by Legal & CHRO so external phrasing matches Part A.

Signed: ______________________ (CHRO)  ______________________ (General Counsel)  Date: __________