Say you’ve got people in three states. One hire in Virginia, a couple in Connecticut, the rest back at headquarters somewhere else. Until recently you ran one handbook, one hiring workflow, and one non-compete across all of them, and it worked fine.
In the back half of 2026, it stopped working.
Every state went its own way this year, and the gaps between them got wide enough to fall through. A job posting that’s perfectly legal in one state is a violation in another. A non-compete that holds up in one state is dead paper in the next. An AI hiring tool that’s invisible in most of the country suddenly triggers testing and disclosure duties the moment your candidate happens to sit in the wrong place.
The biggest mistake owners make is assuming HQ location dictates the rules. Employment law follows where your employee physically sits, not where you’re headquartered. Hire one person remote in a state with rules, and you’ve stepped onto that state’s legal ground whether you meant to or not.
So you’re not running one workforce anymore. You’re running one per state.
This isn’t a horizon problem you can push off to 2028. Some of it is live right now. Some of it lands in January.
AI Is Making Hiring and Firing Calls, and a Few States Are Now Watching
Plenty of businesses already run software to screen resumes, rank applicants, and flag who gets cut in a layoff. Most owners don’t think of that software as making the decision. The law is starting to think it does.
Connecticut is the sharpest example of where this is headed. Two pieces of its new AI accountability law went live October 1. First, if somebody hits you with a discrimination claim involving an automated tool, a court can now weigh whether you tested that tool for bias, and how good, recent, and thorough the testing was. Second, when you file a federal mass-layoff notice, you have to tell the state labor department whether the layoffs relate to your use of AI or other technology.
Neither one makes you send anyone a form yet. They change what happens when something goes wrong. Run an automated screener, get challenged, produce zero bias testing, and that silence becomes the other side’s best evidence.
A separate piece of the Connecticut law, telling applicants and employees in advance when an automated system is a substantial factor in a decision about them, doesn’t kick in until systems deployed on or after October 1, 2027. Handle it on next year’s calendar.
Only the state attorney general can enforce this law. There’s no private right of action, meaning an applicant can’t personally sue you under it. The risk shows up as an AG inquiry and as evidence in a discrimination case, not as a wave of individual lawsuits.
Colorado is the other anchor, and it’s a 2027 item. Under its reworked AI law, when an automated system drives a decision that lands badly for someone, you have to give a plain-language explanation of the tool’s role, and the person can ask you to correct wrong data and request a human to review and reconsider. A Colorado job applicant or employee counts as a covered person. That takes effect January 1, 2027. The earlier version of this law let smaller employers off the hook, and this reworked one dropped that carve-out, so if an automated tool materially drives a hiring or pay decision in Colorado, you’re covered no matter your size.
Here’s the objection I hear constantly: “our software vendor handles all the AI compliance.” No. The testing, documentation, and notice obligations land on you, the employer. You can’t contract your own violation away, and Colorado’s law specifically voids the clause that tries to shove liability back onto the vendor.
Protecting yourself is two things.
First, documented bias testing. Not a vendor’s marketing line, a written record that the tool was tested for adverse impact across race, sex, and age, showing when, on what data, and what the results were. If your candidate pool skews one way and the tool’s selection rate skews the same way, you want that on paper, with the fix you made, before anyone asks.
Second, make the vendor put it in writing. Before you sign or renew, demand their actual bias-testing results and methodology, not a one-line assurance that the tool is “fair.” Ask how it was validated and on whose data. Get contract terms that put the testing obligation on the vendor and require them to hand over documentation if you’re challenged. A vendor who won’t give you any of that has told you something about the tool. That’s the AI-in-hiring governance piece.
Start with an inventory: find every place AI touches a hiring or firing call, find out which states your applicants and employees sit in, and get the testing documented before the tool makes its next decision.
Every State Went Its Own Way, and You’re on the Hook Wherever Your People Sit
Pay transparency is where the split gets concrete. Virginia’s new pay transparency law took effect July 1. You now have to put the wage or salary range in every posting, public and internal, and you can’t ask for or lean on an applicant’s salary history. Same in a growing list of other states.
A compliant posting is a real, good-faith pay range, not “competitive” and not a placeholder $1 to $500,000 spread that names a range while telling nobody anything. Note the benefits that come with the role. And kill the salary history question everywhere, including the “what are you making now?” a hiring manager asks by reflex in the phone screen. Write the posting to the strictest state you hire in, and it clears the rest.
Here’s the trap with one national posting. Some states now require the range. Meanwhile, if you hold government contracts or do public-sector work, the pressure runs the other way, with diversity, equity, and inclusion (DEI) programs and pay-related mandates getting pulled back. A national handbook, written once for the whole company, doesn’t split the difference. It guarantees you’re wrong in at least one place.
Employer speech is fracturing too. Maryland’s Worker Freedom Act took effect October 1 and bars you from disciplining an employee who declines to attend a meeting where you’re pushing your opinion on political or religious matters. And “political” expressly includes whether to support a union. If you run mandatory all-hands meetings with a political or union-tinged message, that’s a real constraint in Maryland now, and other states are looking at the same idea.
So what do you do with a map that no longer agrees with itself? You stop maintaining one handbook. You build one base policy plus a per-state layer on top, and you reconcile the head-on conflicts on purpose instead of finding them in a complaint.
If Your Retention Plan Is a Non-Compete, Check Which Half of Your Team It Still Covers
The ground under non-competes kept moving in 2026, and it moved on a dollar threshold.
Tennessee’s new non-compete rule took effect July 1 and voids non-competes for any worker earning under $70,000 a year, for agreements signed, renewed, or amended after that date. This is a $70,000 line, not a ban. Below it, the agreement is void. Above it, non-competes still operate where the state otherwise allows them.
The people you most want to lock down, the VP of sales, the key engineer, usually earn above these lines and often stay enforceable in states that still permit non-competes. What’s broken is the apply-to-everyone template you had every new hire sign regardless of role. Enforceability turns on the employee’s earnings and state, and that varies desk to desk.
Virginia tightened things further. Its expanded non-compete standard, effective July 1, bars enforcing a non-compete against an employee you fired without cause unless you paid severance you disclosed at signing. And it gives all employees the right to sue over a violation, not the narrow low-wage slice that could before. More of your Virginia workforce can now take you to court over a bad covenant.
Washington is one to plan for, not act on yet. Its ban on non-competes for Washington-based workers, including stay-or-pay clauses that make someone repay or forfeit pay for taking lawful work, doesn’t take effect until June 30, 2027.
Stop leaning on a uniform non-compete to protect your business across state lines. It no longer travels. A well-drafted confidentiality and trade-secret agreement does.
A non-compete tries to stop a person from working for a competitor at all, which is exactly the part states keep voiding. A confidentiality and trade-secret agreement protects something narrower and sturdier: your client lists, your pricing, your margins, your product roadmap, the process you built that nobody else has. Your former employee can take the next job, but they can’t walk out with the information that makes your business yours and hand it to whoever hired them. Courts enforce that, and it doesn’t hinge on the employee’s salary or state. It holds whether your person makes $50,000 in Tennessee or $200,000 in Virginia, because it’s grounded in law every state recognizes.
And the honest retention play was never the covenant anyway. It’s paying and treating people well enough that they don’t want to leave.
Quick Hits: The Smaller Changes That Still Carry a Fine
A few smaller items are cheap to comply with and expensive to miss, and they follow the same per-state logic.
- Employee monitoring notice. Connecticut’s electronic surveillance rules, live October 1, now require your written monitoring notice to name the specific workplace locations where monitoring may happen, to post notice there, and to give new hires a plain-language statement of what’s off-limits. If you monitor email, devices, or activity in Connecticut, update the notice. It’s the same logic that gives AI meeting notetakers wiretap exposure when nobody in the room got told they were recording.
- Warehouse quotas. Connecticut also now regulates production quotas at larger distribution centers. If you run a covered warehouse, you owe each affected employee a written description of every quota, and the quotas can’t cut into meal or restroom breaks. Descriptions to current employees were due August 1, 2026. If you missed it, fix it now.
- Earned wage access. If you offer employees pay advances through an earned-wage-access benefit, Maryland’s new provider rules, effective October 1, subject those providers to consumer-loan requirements and bar them from soliciting or accepting tips from your employees. Check what your vendor is doing before it becomes your problem.
Plan for 2027
- Colorado AI regime (January 1)
- Washington non-compete and stay-or-pay ban (June 30)
- Connecticut applicant-notice duty for AI (October 1)
This Is a Coordination Problem Now
Compliance stopped being a document you write once. It’s something you keep straight across every state you employ people in, and it shifts underneath you every few months.
That’s the work I do. If you’re running one handbook, one hiring process, and one set of covenants across states that no longer agree, I can help you keep the state layer straight and take keeping up with multistate changes off your plate: a multistate handbook and policy review, AI-in-hiring governance and notice setup, and a non-compete and pay transparency check state by state. Not a teardown, a per-state layer that fits your actual footprint.
Learn More About Multi-state Compliance Services
If that’s where you are, let’s talk.
FAQ
I only have a handful of remote people in other states. Does this really apply to me? Yes. Employment obligations generally follow where the employee physically works, not where your company is based. One remote hire in a state with pay transparency, notice, or non-compete rules pulls you into that state’s requirements. You don’t get to apply your home-state handbook to someone working in Virginia or Connecticut.
Our HR software vendor says they handle AI compliance. Aren’t we covered? No. The notice, documentation, and bias-testing obligations land on the employer, and “the vendor handles it” isn’t a defense when a candidate or ex-employee challenges the decision. Colorado’s law even voids the clause where a vendor promises to eat your liability. Use the tool as documented and get the vendor’s bias-testing in writing, but the responsibility stays with you.
We have non-competes signed by everyone. Why would they suddenly not hold? Because enforceability depends on the employee’s state and earnings, and several states moved this year. Tennessee voids them below $70,000. Virginia expanded who can sue over a bad one. Washington bans them for its workers starting in 2027. A uniform agreement is now enforceable for some people and void for others, and the signature doesn’t change that.
This sounds like a lot. What do I actually do first? Map where your people physically work. Then pressure-test the three things most likely to be wrong across those states: your handbook, your automated hiring process, and your restrictive covenants. Handle what’s live now before Q4, and scope the 2027 items after.
