TL;DR: Minnesota has no signed AI employment law yet, but the Minnesota Human Rights Act already applies to AI hiring decisions. Proposed legislation HF 4757 would add notice, documentation, and appeal rights. Build your compliance infrastructure now.
Minnesota occupies an interesting position in the US state AI regulation map. The state has been one of the more active legislatures on AI policy, with multiple employment-related AI bills advancing in the 2025-2026 session. But as of mid-2026, none have been signed into law. Note: HF 4757, which passed in the prior session, is the Minnesota Consumer Data Privacy Act (MCDPA), a consumer privacy law, not an AI employment act. The AI employment proposals in the current session carry different bill numbers (HF 4369, HF 4131, and others). That does not mean Minnesota employers are operating in a vacuum. Existing state civil rights law already creates real obligations for employers using AI in employment decisions, and proposed legislation sets a clear direction for where those obligations are heading.
This guide covers what applies today, what the proposed legislation would add, and how to structure a compliance program that satisfies current requirements and positions your organization for whatever comes next.
What applies right now: the Minnesota Human Rights Act
The Minnesota Human Rights Act (MHRA) is one of the broadest state anti-discrimination laws in the country. It prohibits discriminatory practices in employment based on race, color, creed, religion, national origin, sex, disability, age, marital status, familial status, and several other protected characteristics.
The MHRA applies to employment decisions whether made by a human or an automated system. If a resume screening tool trained on historical hiring data disproportionately rejects candidates of a particular race or national origin, that is a discriminatory employment practice under the MHRA, even if no individual at the company intended to discriminate. Disparate impact claims do not require proof of intent.
What this means practically:
- If you use an AI tool that scores or ranks candidates in Minnesota, you need to know whether that tool produces disparate impact across protected classes.
- If you cannot get demographic impact data from your vendor, you are flying blind on MHRA risk.
- "The algorithm did it" is not a defense to a discrimination claim. The employer is responsible for the outcome.
The MHRA is enforced by the Minnesota Department of Human Rights (MDHR). Complaints can result in investigations, conciliation, administrative hearings, and civil court proceedings. Remedies include back pay, reinstatement, compensatory damages, and attorney's fees.
Current state of Minnesota AI employment legislation
HF 4757: the Minnesota Consumer Data Privacy Act (already signed)
Minnesota HF 4757 was signed into law on May 24, 2024 as the Minnesota Consumer Data Privacy Act (MCDPA), effective July 31, 2025. It is a comprehensive consumer data privacy act, not an AI employment act. The MCDPA includes provisions on automated decision-making and profiling in consumer contexts. A general employment exemption limits its reach for data collected in a traditional employment relationship, though the boundary can blur for AI tools that gather data from external sources (such as social media) about applicants. If your hiring process involves AI tools that scrape external applicant data, have counsel review whether MCDPA provisions apply.
Active proposals in the 2025-2026 session (94th legislature)
The 94th Minnesota legislature has several AI employment-related bills under consideration as of mid-2026:
HF 4369 / SF 4576, AI job displacement notice: Would require employers planning to deploy technology that could displace workers to give 90 days' written notice before implementation. During that 90-day period, affected employees would continue receiving pay and benefits while being offered reskilling opportunities. Employers who violate the law could face fines of up to $10,000 per affected employee and lose eligibility for state contracts.
HF 4131 / HF 3794, Surveillance-based wage discrimination: Would prohibit using automated decision systems to set individualized wages based on worker surveillance data, and require employers to disclose what data informs automated wage-setting decisions.
None of these bills have been signed into law as of mid-2026. Employers should monitor the Minnesota legislature's session calendar. Building documentation infrastructure now, for disclosure notices, human review pathways, and AI tool inventories, positions organizations well regardless of which bills ultimately pass.
Who would be covered under proposed legislation
The active 2025-2026 AI employment proposals have varying scope. HF 4369 (AI job displacement notice) would cover employers planning to deploy technology that displaces workers in Minnesota, regardless of where the employer is headquartered. The surveillance wage discrimination bills (HF 4131, HF 3794) would cover employers using automated systems to set individualized wages based on worker monitoring data.
Coverage under these proposals applies to decisions affecting Minnesota employees and applicants. A California-based company using AI to eliminate Minneapolis positions, or to set wages for its Minnesota workforce based on monitoring data, would likely be a covered deployer under the relevant bills.
None of these proposals have been enacted. For current obligations, the MHRA coverage section above governs.
How proposed MN requirements compare to other state laws
| Requirement | MN proposed (HF 4369 + others) | NYC Local Law 144 | Colorado SB 26-189 | Illinois HB 3773 |
|---|---|---|---|---|
| AI job displacement notice (90 days) | Yes (HF 4369) | No | No | No |
| Prior notice to applicants/employees | Partial (HF 4369 covers displacement) | Partial | Yes | Yes (video interviews) |
| Opt-out / human review right | Not in current proposals | No | Yes | Yes |
| Independent bias audit | No | Yes (annual) | No | No |
| AI as sole determinant prohibited | Not in current proposals | No explicit rule | Yes | No |
| Surveillance wage discrimination ban | Yes (HF 4131) | No | No | No |
| Status | Proposed, not signed | Enacted | Enacted | Enacted |
Minnesota's proposed framework would be among the more protective in the country, particularly if private right of action provisions survive into the final version.
Minnesota Consumer Data Privacy Act considerations
Separate from AI-specific employment legislation, the Minnesota Consumer Data Privacy Act (MCDPA) includes provisions on automated decision-making and profiling. As enacted, the MCDPA applies to consumers in their personal capacity, and there is a general employment exemption for data collected in an employment context.
However, employers should be aware that the boundary between consumer data and employment data can blur. If an employer uses a platform that gathers data from an applicant's social media or online presence in ways that go beyond traditional employment data collection, MCDPA protections may apply to portions of that data. Have counsel review any AI tool that scrapes or analyzes applicant data from external sources.
Practical compliance checklist for Minnesota employers
This checklist addresses both current MHRA obligations and preparation for likely legislative requirements.
Immediate actions (based on existing MHRA)
- Inventory every AI tool used in hiring, screening, promotion, and performance management decisions affecting Minnesota employees or applicants
- For each tool, request demographic impact data from your vendor showing pass/fail or scoring rates by race, sex, and other protected classes
- Review results against the four-fifths rule (80% rule) commonly used in employment discrimination analysis: a selection rate for a protected group that is less than 80% of the rate for the highest-scoring group signals potential adverse impact
- Document your review and any remediation steps taken
- Ensure human reviewers are actually reviewing AI outputs and have authority to override them, not just rubber-stamping scores
Preparation for proposed legislative requirements (HF 4369 and others)
- If your organization uses AI tools that could affect job count or working conditions in Minnesota, draft a notice protocol, HF 4369 requires 90 days' written notice before technology-driven job displacement
- Create an AI tool inventory document: tool name, vendor, decision type, deployment date, potential workforce impact, and last review date
- Identify which employment decision workflows currently rely on AI outputs without a documented human review step, and redesign those workflows
- If your organization uses automated tools to set individual wages, review those tools against the surveillance wage discrimination bills' proposed requirements
- Assign ownership of AI tool compliance monitoring to a named HR or legal team member
Vendor management
- Request documentation from each AI vendor describing the tool's methodology, training data, and any internal bias testing results
- Add contractual provisions requiring vendors to notify you of material changes to AI model behavior
- Confirm vendors can provide demographic impact data on request
Legislative monitoring
- Set a quarterly calendar reminder to check HF 4757 session status
- Subscribe to updates from the Minnesota Department of Human Rights and the Attorney General's office
- Brief HR leadership on the direction of proposed legislation so budget and staffing decisions account for implementation costs
What good documentation looks like
If HF 4757 passes, documentation requirements will likely ask employers to maintain records of:
- Which AI systems are used in which employment decision contexts
- The basis for concluding the AI output was reviewed by a human
- Any appeals or opt-out requests received and how they were handled
- Vendor representations about bias testing and model accuracy
Start building that record now. A simple spreadsheet tracking tool name, decision type, date of last human review protocol review, and any demographic impact assessments on file is a reasonable starting point. For organizations with more than a handful of AI tools in use, a lightweight AI register (see the AI tool register template as a starting format for employment-specific documentation) provides better structure.
What Minnesota employers should do today
The legislative situation is uncertain, but the risk is not. Under existing MHRA obligations, Minnesota employers using AI in employment decisions have real exposure to discrimination claims today. The most important steps are assessing your current AI tool stack for disparate impact risk and ensuring human review of AI outputs is genuine and documented.
For the legislative piece, build the infrastructure that proposed legislation would require, treat it as a planning exercise that will be validated when law passes. Employers who wait for a signature to start building disclosure notices and opt-out processes will have less time and will be making decisions under pressure.
Related reading
See AI hiring tool compliance US state laws for the full state-by-state regulatory map. For a jurisdiction with an enacted law that shares some of the same elements as HF 4757, see Colorado AI Act SB 26-189 employer compliance guide 2027. The EEOC AI hiring guidance 2026 employer checklist covers federal anti-discrimination overlay that applies in every state. For comparison with the strongest enacted employment AI disclosure requirement, see NYC Local Law 144 AI bias audit employer guide. Illinois has a narrower enacted law covering video interviews: Illinois AI employment disclosure law 2026. Check the AI regulation deadline calendar 2026 for the latest effective dates and the AI governance checklist 2026 for a broader governance program.
