By Cortni Lawson, Founder & CEO, InfraNet HR
Navigating multi-state employment laws in 2026 means knowing which states actually bite HR teams — not just which statutes exist on paper.
HR rarely discovers multi-state compliance during strategic planning meetings.
They discover it when something goes wrong.
An employee gets hurt.
A leave request lands in the inbox.
A supervisor calls asking whether a termination can move forward.
A workers' compensation claim changes status.
A complaint gets filed.
An employee asks for an accommodation.
Suddenly someone is trying to determine which state's rules apply, what notices are required, who owns the next step, and whether a deadline is already approaching.
Nobody in that moment is thinking about employment law theory.
They're trying to figure out what happens next.
That's why I think most conversations about multi-state compliance start in the wrong place.
Most articles start with regulations.
HR doesn't experience regulations.
HR experiences events.
The injury.
The leave request.
The complaint.
The accommodation.
The termination.
The law matters. The event is what creates the work.
And as employers continue hiring remotely, expanding into new states, and managing employees across multiple jurisdictions, the number of obligations connected to a single event keeps growing.
This guide covers the states that create the most friction for employers, the mistakes I see HR teams make repeatedly, and the operational realities of managing employment events across state lines.
Because in my experience, compliance problems rarely happen because someone intentionally ignored the law.
They happen because nobody realized what an event triggered until after something important was missed.
The Real Problem Isn't State Laws. It's Employment Events.
Most compliance discussions focus on regulations.
I think that's backwards.
HR teams don't wake up thinking about regulations.
They wake up thinking about situations.
An employee tears a rotator cuff.
A supervisor reports harassment concerns.
A leave certification arrives.
A workers' compensation adjuster requests documentation.
An employee asks for an accommodation.
A manager wants to terminate someone.
Those situations trigger obligations that vary by state, location, employee classification, industry, and company policy.
The challenge isn't memorizing every law.
The challenge is recognizing everything an event triggers and making sure nothing falls through the cracks.
Take a workplace injury.
Most organizations immediately think:
Workers' compensation claim.
Fair enough.
But that same injury may also trigger:
- OSHA recordability review
- OSHA reporting obligations
- Leave eligibility review
- ADA accommodation considerations
- Return-to-work planning
- Carrier communications
- Supervisor follow-up
- Documentation retention requirements
- State-specific reporting obligations
One event.
Multiple workflows.
Multiple deadlines.
Multiple stakeholders.
Potentially multiple states.
That's where employers get into trouble.
Not because they don't care.
Not because they're trying to cut corners.
Because life doesn't happen one regulation at a time.
It happens all at once.
The same thing happens with leave.
What starts as a straightforward medical leave request can quickly become an FMLA question, a state leave question, a benefits issue, an accommodation discussion, a payroll issue, and a return-to-work planning exercise.
Most HR professionals can figure out the law.
The harder part is making sure the right thing happens every time, regardless of who is working the case, who is out of the office, or which state is involved.
Why Multi-State Compliance Keeps Getting Harder
Twenty years ago, many employers operated primarily in one state with one handbook and a relatively consistent workforce.
Today's reality looks different.
Organizations hire remote employees.
Employees relocate.
Companies acquire facilities in other states.
Managers supervise teams spread across multiple jurisdictions.
An employee may live in New York, report to a manager in Texas, and travel periodically to California.
A warehouse employee may be injured in Kansas while assigned to a Missouri location.
A supervisor in Colorado may manage employees in Arizona, Oklahoma, and Illinois.
Each situation creates different obligations.
Each obligation creates different timelines.
Each timeline creates another opportunity for something to be missed.
The issue isn't simply legal complexity.
The issue is execution.
The spreadsheet lives with HR.
The deadline lives with HR.
The carrier relationship lives with HR.
The accommodation history lives with HR.
The institutional knowledge lives with HR.
Which means HR becomes the backup system for the entire organization.
Vacations get interrupted.
Inboxes get checked after hours.
Coverage becomes difficult because nobody else has the full picture.
And every year there are more opportunities for something to fall through the cracks.
More leave programs.
More pay transparency laws.
More privacy regulations.
More local ordinances.
More reporting obligations.
More remote employees working in places they didn't live when they were hired.
The laws matter.
The real risk is that nobody realizes something was triggered until after a deadline passes.
The Top 10 Most Complex States for Employment Compliance
| State | Key Risk Areas | HR Complexity Level | Notes for Multi-State Employers |
|---|---|---|---|
| California | Wage & Hour, Leave, Pay Transparency, PAGA | Very High | Meal and rest break requirements, pay transparency, local ordinances, aggressive enforcement, and a near-total non-compete ban |
| New York | Leave, Pay Transparency, Wage Theft | Very High | State requirements layered with New York City obligations create significant administrative complexity |
| Illinois | BIPA, Predictive Scheduling, Non-Competes | High | Chicago-specific requirements and biometric privacy laws create unique exposure |
| Massachusetts | Paid Family Leave, Non-Competes | High | Strong employee protections and active enforcement environment |
| New Jersey | Paid Leave, Wage Payment | High | Extensive leave protections and wage-and-hour requirements |
| Washington | PFML, Minimum Wage, Non-Competes | High | State leave requirements combined with local variations and worker protections |
| Connecticut | Paid Leave, Wage & Hour | High | Detailed compliance requirements that often surface during audits and disputes |
| Maryland | Paid Family Leave, Wage Recovery | High | State obligations plus local requirements in certain jurisdictions |
| Oregon | Paid Sick Time, Predictive Scheduling | High | Frequent legislative updates and scheduling requirements |
| Colorado | Paid Family Leave, Pay Transparency | High | Strong transparency requirements and evolving employment protections |
Honorable Mentions
Several states continue increasing in complexity and are worth watching closely:
- Virginia
- Minnesota
- Nevada
- Maine
- Rhode Island
Each has seen meaningful movement in leave laws, worker protections, pay transparency requirements, or enforcement activity.
Common Multi-State Compliance Mistakes That Create Exposure
Using One Handbook Nationwide
This is probably the most common mistake I see.
The logic sounds reasonable.
Create one handbook.
Apply it everywhere.
Stay consistent.
The problem is that consistency doesn't automatically create compliance.
A policy that works perfectly in Missouri may be incomplete in California.
A leave process that works in Kansas may miss requirements in New York.
Trying to force every location into one universal policy often creates confusion for managers and gaps for employees.
Applying the Strictest Rule Everywhere
The opposite mistake is treating California as the default standard for every location.
Sometimes that approach makes sense.
Often it doesn't.
Over-compliance creates administrative burden, unnecessary costs, and policies that managers don't understand.
The goal isn't to apply every rule everywhere.
The goal is to apply the right rules in the right places consistently.
Missing Local Ordinances
State law is only part of the picture.
Cities and counties increasingly have their own requirements.
Chicago.
New York City.
Seattle.
Denver.
Los Angeles.
San Francisco.
A company may have a compliant state-level process while still missing local obligations.
That's where a lot of surprises happen.
Leaving Managers to Figure It Out
Many compliance failures don't start in HR.
They start with a manager trying to help.
A supervisor says the wrong thing during a leave conversation.
A manager mishandles an accommodation request.
Someone promises something they shouldn't promise.
Someone disciplines an employee without understanding protected activity concerns.
Most managers aren't employment law experts.
They shouldn't be expected to be.
But they do need training and support.
Relying on Tribal Knowledge
Every HR team has that person.
The one who knows everything.
The one who remembers how a situation was handled three years ago.
The one everyone calls when something unusual happens.
The problem is that eventually people leave, retire, get promoted, or take vacations.
When knowledge lives inside people instead of systems, risk follows them out the door.
What One Employment Event Can Trigger
| Event | Potential Downstream Impacts |
|---|---|
| Workplace Injury | Workers' compensation, OSHA review, OSHA reporting, leave eligibility, ADA accommodations, return-to-work planning, carrier communications |
| Leave Request | FMLA, state leave programs, benefits coordination, accommodations, job protection obligations |
| Employee Complaint | Investigation, retaliation concerns, documentation requirements, corrective action, employee relations follow-up |
| Termination | Final pay obligations, unemployment claims, COBRA, record retention requirements, restrictive covenant questions |
| Accommodation Request | Interactive process, medical documentation, leave considerations, job modifications, return-to-work coordination |
Most systems track the initial event.
Very few help employers manage everything that comes next.
What HR Teams Are Actually Tracking
On paper, HR tracks workers' compensation claims, OSHA recordability, leave certifications, accommodations, unemployment claims, investigations, and compliance deadlines.
In reality, HR tracks people.
They're tracking whether an employee sent updated restrictions.
Whether the adjuster returned a phone call.
Whether the supervisor completed the investigation.
Whether someone updated the OSHA log.
Whether the leave paperwork came back.
Whether the employee is returning Monday or next month.
Systems call them cases.
HR experiences them as unfinished conversations.
And every unfinished conversation creates another opportunity for something important to be missed.
That's why so many HR professionals feel like they're constantly carrying the organization in their heads.
Because in many organizations, they are.
Practical Strategies That Actually Work
Maintain a Living State Matrix
If you operate in multiple states, create a living reference document that tracks:
- Leave requirements
- Wage and hour obligations
- Pay transparency laws
- Non-compete restrictions
- State reporting requirements
- Required notices
Review it quarterly.
Employment law changes too quickly to treat compliance as a one-time project.
Build Core Policies With State Overlays
Instead of creating completely separate handbooks, establish core policies and layer state-specific requirements where necessary.
This approach creates consistency while still recognizing jurisdictional differences.
Capture Institutional Knowledge
Document decisions.
Document outcomes.
Document lessons learned.
Every investigation, leave case, workers' compensation claim, and accommodation process creates knowledge that can help the organization next time.
Too many companies solve the same problem repeatedly because nobody documented what happened the first time.
Train Managers Early
Managers don't need to become HR experts.
They do need to recognize when something should be escalated.
The earlier HR becomes involved, the easier most situations are to manage.
Focus on Handoffs
Many compliance failures happen between people.
The supervisor thought HR was handling it.
HR thought the carrier was handling it.
The carrier thought the manager was handling it.
Nobody owned the next step.
Clear ownership prevents more problems than almost any policy ever will.
Final Thoughts
Multi-state compliance isn't getting simpler.
States continue adding leave programs, pay transparency requirements, accommodation obligations, privacy protections, and reporting expectations.
Local ordinances add another layer.
Remote work adds another layer.
Multi-state operations add another layer.
The organizations that succeed won't be the ones that memorize every regulation.
They'll be the organizations that build reliable systems around employment events, documentation, visibility, and handoffs.
Because when an injury, leave request, complaint, accommodation request, or termination occurs, the question isn't whether obligations exist.
The question is whether your organization consistently recognizes them and follows through.
And in my experience, that's where the real compliance work begins.