Minnesota Considered an AI Layoff Notice Law This Year. Here's What HR Teams Can Do Before the Next One.

Short answer: HF 4369, the Safeguarding Human Intelligence and Employment in Labor Displacement Act, was introduced in the Minnesota House on March 16, 2026. It would have required covered employers to give 90 days' notice before deploying technology that displaces workers, and to keep affected employees on regular pay during a 90-day transition with a chance to reskill. It is not law. The bill was heard without action, and the Legislature adjourned on May 18, 2026. Any future version would have to be introduced again. Connecticut already requires AI disclosure in layoff notices, and California's version takes effect January 1, 2027, so the habits this bill points toward are worth building whether Minnesota acts or not.

You don't need a Minnesota AI law on the books to start documenting how AI shapes your people decisions. Two states already ask for it.

HF 4369 would have put a 90-day clock on AI-driven job loss

The bill, sponsored by Rep. David Gottfried (DFL-Shoreview), took a different approach from most state AI laws. It did not regulate the technology. It regulated what happens to the people when the technology arrives. Gottfried described the goal as putting guardrails on how AI is used rather than on the technology itself.

As introduced, HF 4369 would have:

  • Applied to employers with 50 or more full-time employees in Minnesota
  • Required at least 90 days' written notice before a technological displacement, delivered to affected employees, their labor representatives, the Minnesota Department of Labor and Industry, local officials, and the regional workforce board
  • Required the notice to describe the functions being automated, the number and classification of affected workers, the expected displacement date, available retraining or reassignment, and the vendor supplying the AI system
  • Given affected employees a 90-day transitional employment period with continued pay and an opportunity to upskill or reskill
  • Made noncompliant employers liable for back pay and benefits to affected employees, enforced by the commissioner of labor and industry or the attorney general

The bill is a proposal, not a law

HF 4369 was introduced and heard, and no action was taken. The 2026 session, the second year of the two-year 94th Legislature, adjourned on May 18. A new Legislature convenes in January 2027, and if lawmakers want to revisit the idea, it starts over as a new bill.

So nothing in HF 4369 applies to any Minnesota employer today. What it does is show where state lawmakers are looking, and Minnesota is not looking alone.

Nearly one-third of Minnesota jobs are highly exposed to generative AI

The reason the bill got a hearing at all is a number. According to a report from North Star Policy Action and the University of St. Thomas, more than 31% of Minnesota jobs, about 813,000 workers, have high exposure to generative AI, meaning more than half of their work tasks could be automated. Gottfried cited that report when he presented the bill.

High exposure does not mean those jobs disappear. It does mean a large share of Minnesota employers will be making decisions about AI and their workforce in the next few years, and those decisions will be easier to defend if they are well documented.

California and Connecticut have already acted on AI layoff notice

Two states have moved from proposal to law.

Connecticut's SB 5, signed May 27, 2026, requires employers filing layoff notices under the state's WARN law to disclose to the Department of Labor whether the layoffs relate to the employer's use of AI or other technological change. That requirement took effect October 1, 2026.

California's SB 951, signed September 30, 2026 and operative January 1, 2027, amends the state's WARN law to require additional notice when a mass layoff, relocation, or termination is caused in whole or in substantial part by AI or other automated technology. The notice has to identify the displacement as technology-related and describe the affected positions and the technology involved.

Neither law bans AI-driven restructuring. Both ask employers to say when AI was part of the reason.

The habits that hold up under any of these laws

Minnesota HR teams do not need to wait for a statute to build the record these laws keep asking for. Four habits matter regardless of which state you operate in:

Know where AI touches people decisions. Keep a current list of tools that score, rank, flag, or schedule employees, and what decisions each one informs.

Keep the tool's output separate from the manager's judgment. When a decision is made, the record should show what the system said and what the person decided, and why.

Write it down when it happens. Performance context captured during the year is the record a human reviewer, an auditor, or a court will look for. Context reconstructed in December is weaker on every count.

Keep records long enough. California's FEHA regulations already require four years for employment records, including automated decision data. Colorado's new AI law, effective January 1, 2027, requires three years for compliance records. If you operate in more than one state, the longest rule sets your floor.

The record an auditor wants is the one your managers write during the year, not the one they rebuild in December.

Where Upward365 fits

Upward365 is performance management built around year-round context. Managers capture Notes, Uplifts, and Flight Checks as the year happens, Briefings keep 1:1s on a shared agenda, and the History Hub overlay puts the full year in front of the manager when the review opens. Reviews and peer feedback live in the same place.

We keep the judgment with people. Upward365's AI does not write reviews or comments. See our perspective on why we built one platform instead of two and how we approach AI guardrails in performance reviews.

That does not make anyone compliant with a law that does not exist yet. It does mean that if Minnesota, or your next state, asks you to show how a people decision was made, the record is already there. And when you need help, a real person who knows your account answers, often the same day.

Minnesota's bill focused on notice before AI displaces workers. California went a step further this year and now requires a human to check an AI system's output before it is used to discipline or fire anyone. Read what California's SB 947 means for your performance records.

See how Upward365 keeps a year of context behind every people decision. Book a Demo


Sources

Last checked 10/07/2026

This article is general information, not legal advice. It was accurate as of 10/29/2026. Legislation and effective dates change, and bills like HF 4369 can be reintroduced in a new session, so check the current status before acting on anything here. How any law applies depends on your situation. Talk to employment counsel before changing your policies.

Frequently Asked Questions

Is Minnesota's AI layoff notice bill law?
No. HF 4369 was introduced on March 16, 2026 and heard in committee without action. The 2026 legislative session adjourned on May 18, 2026. Any future version would need to be reintroduced.
Does HF 4369 apply to my company?
No. The bill did not pass, so it applies to no Minnesota employer today. If a similar bill is reintroduced in 2027, it would likely target employers with 50 or more full-time Minnesota employees, as HF 4369 did.
What would HF 4369 have required?
Covered employers with 50 or more full-time employees in Minnesota would have had to give 90 days' written notice before AI-driven displacement, keep affected employees on pay during a 90-day transitional period with reskilling opportunities, and notify state and local officials.
Which states already require AI layoff disclosure?
Connecticut has required AI disclosure in state WARN notices since October 1, 2026. California's SB 951 adds AI-related content to Cal/WARN notices starting January 1, 2027.
What is a WARN notice for AI-related layoffs?

A WARN notice is the advance notice employers file before a mass layoff. Connecticut and California have amended their state WARN laws so employers must also disclose when AI or other technological change is part of the reason for the layoff.

Is AI causing layoffs?

Some states now require employers to say when it is. A North Star Policy Action and University of St. Thomas report found more than 31% of Minnesota jobs, about 813,000 workers, are highly exposed to generative AI, meaning more than half of their tasks could be automated. High exposure does not mean those jobs disappear.

What does California's WARN Act require for AI layoffs?

California's SB 951, operative January 1, 2027, requires additional Cal/WARN notice when a mass layoff, relocation, or termination is caused in whole or in substantial part by AI or other automated technology. The notice must identify the displacement as technology-related and describe the affected positions and the technology involved.

When is an AI layoff disclosure required?

Connecticut has required employers to disclose AI-related layoffs in state WARN filings since October 1, 2026. California's requirement starts January 1, 2027. Minnesota has no AI layoff notice requirement, because HF 4369 did not pass.

Will Minnesota pass an AI layoff notice law?

Not yet. HF 4369 was heard in committee without action, and the session adjourned May 18, 2026. A new Legislature convenes in January 2027, and any AI layoff notice proposal would have to be introduced as a new bill.

Dave Arringdale, Co-Founder at Upward365

Dave Arringdale, Co-Founder at Upward365

Dave Arringdale is the Co-Founder of Upward365, a performance management and employee engagement platform built specifically for the underserved small to mid-sized business (SMB) market. His expertise is built on over 15 years in the performance management industry, during which he served over 1,500 companies through his previous venture, ReviewSnap, which he successfully co-founded and led as CEO. Connect on LinkedIn →

Get Email Notifications