Biden Executive Order Takes Aim at Noncompete Agreements – IA Magazine

If you’ve ever signed a stack of onboarding paperwork so thick it could double as a doorstop, you’ve probably met the
noncompete agreement. It’s the clause that says, “Congrats on the jobalso, please don’t do this job anywhere else for a while after you leave.”
For years, noncompetes quietly spread from corner offices into everyday roles, showing up in industries that run on talent, relationships,
and know-howincluding the insights and market research world that IA Magazine readers know well.

That’s why President Biden’s 2021 Executive Order on competition made headlines: it didn’t instantly erase noncompetes (sorry, no magic wand),
but it did put them on the federal government’s “we should probably do something about this” list. The order encouraged the Federal Trade Commission (FTC)
to consider curbing what it called the unfair use of noncompete clausessparking a chain reaction that reshaped the national conversation,
triggered a major FTC rulemaking effort, and pushed employers and workers to take a much closer look at what’s in those clauses.

This article breaks down what the executive order did (and didn’t) do, how the legal landscape shifted after it, why the FTC’s attempted nationwide
rule became a courtroom brawl, and what employers and workers can learn from the whole sagaespecially in relationship-driven fields like insights.

Noncompete Agreements: The Plain-English Version

A noncompete agreement is a contract term that restricts someone from working for a competitoror starting a competing business
for a certain time, within a certain geographic area, after leaving a job. In theory, it’s meant to protect an employer’s legitimate business interests,
like trade secrets or sensitive customer relationships.

In practice, noncompetes can range from “reasonable guardrails” to “this feels like a professional ankle monitor.” A typical noncompete might specify:

• Duration: 6 months, 1 year, 2 years (or longer)
• Geography: a city, a state, “within 50 miles,” or (occasionally) “the entire universe”
• Scope: what work is off-limits (e.g., direct competitors, similar job functions, specific product categories)

Noncompete vs. NDA vs. Nonsolicit

People often lump restrictive agreements together, but they’re different tools:

• Non-disclosure agreement (NDA): “Don’t share confidential information.” This is about secrecy, not job mobility.
• Non-solicitation agreement: “Don’t poach clients/customers (or employees) you met here.” This targets specific relationship-based conduct.
• Noncompete agreement: “Don’t work in this space at all for a while.” This is the broadest restraint.

In industries like insightswhere client trust, proprietary methodologies, panels, data management practices, and talent pipelines all mattercompanies may feel
a strong pull toward restrictive covenants. But the bigger the restriction, the more likely it is to become legally risky, harder to enforce, and a morale-killer
that makes recruiting harder than it needs to be.

What Biden’s Executive Order “Took Aim” At (and What It Didn’t)

The 2021 executive orderoften referred to by its number, Executive Order 14036was a sweeping “competition” directive covering many
parts of the economy. The noncompete piece was one slice of a much bigger pie.

What it did

The order encouraged the FTC to consider using its rulemaking authority to curtail what it described as the unfair use of noncompete clauses
and other employment terms that can limit worker mobility. That encouragement mattered because it signaled federal priority and gave momentum to regulators
already interested in labor-market competition.

What it didn’t do

The executive order did not itself ban noncompetes. It didn’t instantly invalidate existing contracts. It didn’t rewrite state law.
Instead, it set policy direction and nudged agenciesespecially the FTCtoward action.

That distinction is important. If you’re a worker, the EO didn’t automatically “free” you from a contract. If you’re an employer, the EO didn’t immediately
make your agreements unlawful. But it was a flashing yellow light: Prepare for change, and audit your practices.

From Executive Order to Courtroom Drama: A Quick Timeline

1) July 2021: The competition EO shines a spotlight

The Biden administration framed noncompetes as a widespread practice affecting tens of millions of workers, arguing that limiting them could make it easier
to change jobs and increase wages. The EO helped move noncompetes from “HR fine print” to “national policy conversation.”

2) January 2023: The FTC proposes a sweeping rule

The FTC proposed a nationwide rule that would largely ban noncompete clauses. Supporters saw it as overdue worker protection; critics saw it as regulatory
overreach. Either way, it was a huge swing: the federal government was attempting to standardize a topic traditionally governed by state law.

3) April/May 2024: The FTC finalizes its Non-Compete Clause Rule (then gets blocked)

The FTC announced a final rule in April 2024, later published in the Federal Register in May 2024. The rule would have prohibited most new noncompetes,
and it required employers to stop enforcing most existing noncompetes for workers who weren’t “senior executives,” plus give notice to affected workers.
It also included exceptions (for example, in the context of a bona fide sale of a business).

But here’s the key twist: the rule never took effect. Federal courts blocked enforcement, concludingat least in some decisionsthat the FTC
lacked authority for a regulation that broad.

4) 2025: The FTC drops its appeal, and the national “ban” effectively fizzles

After litigation and a change in federal executive-branch leadership, the FTC moved to dismiss its appeal in September 2025. The practical result:
the attempted nationwide rule didn’t become the new reality. Instead, noncompetes returned to the messy but familiar patchwork: state laws, individual contracts,
and case-by-case enforcement.

5) August 2025: EO 14036 is revoked

In August 2025, a new executive order revoked EO 14036. Revocation doesn’t erase historyagencies and courts don’t “unsee” what happenedbut it does change
the federal policy signal going forward.

Why State Law Still Runs the Show

Even during the FTC rule debate, the most important truth for everyday people remained: noncompete enforceability is primarily state law.
That means the answer to “Can my employer do this?” often depends on where you work, where the company is based, and sometimes where you’ll work next.

A few patterns you’ll see across states

• Broad bans in a small set of states: Some states generally prohibit employee noncompetes, with limited exceptions (often tied to sale of a business).
• Income thresholds: Several states allow noncompetes only for workers above certain earnings levels.
• Notice and consideration requirements: Some states require advance notice before employment begins, or additional compensation beyond “you have a job.”
• Special rules for certain professions: Healthcare (especially physicians), broadcast, and other regulated fields may get unique treatment.

The headline: even if you hear “noncompetes are banned,” you still have to ask, “Where?” and “For whom?” A clause that looks enforceable in one state could be
void in another. And remote work makes this even more confusing, because you can live in one state, work for a company in another, and serve clients nationwide.

Why Noncompetes Became a Federal Target

Noncompetes sit at the intersection of two big American values: freedom to work and freedom to compete. The debate gets spicy because both
sides can sound reasonableuntil you see how noncompetes are used in the real world.

The case against noncompetes

• They can suppress wages: If workers can’t credibly leave for better offers, employers feel less pressure to raise pay.
• They can block career growth: A restriction can force someone to switch fields or relocatesometimes for modest roles that don’t involve trade secrets.
• They can discourage entrepreneurship: Starting a competing business is hard enough without a contract saying “not until 2026.”
• They show up where they don’t make sense: Noncompetes have been reported in jobs far removed from proprietary R&D, which raises fairness concerns.

The case for noncompetes (and why employers like them)

• Protecting trade secrets and confidential strategy: Employers worry about competitors “hiring the playbook,” not just the person.
• Defending customer relationships: In relationship-based business (hello, insights!), client trust can be the whole ballgame.
• Protecting investment in training: Some companies argue they invest heavily in onboarding and specialized training and need a safeguard.

A key theme in modern policy discussions is proportionality. Many critics argue the real problem isn’t every restrictive covenantit’s the overuse of broad
noncompetes when narrower tools (NDAs, nonsolicits, data security, trade secret protections) can do the job without locking people out of their profession.

What IA-Minded Industries Should Watch Closely

If you work in insights, analytics, research operations, panel management, or consulting, you’ve probably seen how mobility and confidentiality collide.
Teams are built on specialized skills and client trust. At the same time, talent grows by moving, learning, and bringing better ideas across organizations.

Common noncompete flashpoints in the insights world

• Client-facing account leads who know pricing, renewals, and decision-maker preferences
• Methodology and product experts who can replicate a workflow or dashboard approach
• Panel and sample operations where vendor relationships and sourcing strategies can be sensitive
• Custom research strategists with industry-specific playbooks and proprietary templates

The practical challenge is building contracts that protect legitimate interests without overreaching. Overbroad restrictions can backfire:
they can deter top candidates, spark internal distrust, and create legal risk if your agreement conflicts with a state’s requirements.

A Practical Playbook (Not Legal Advice) for Employers and Workers

For employers: reduce risk without losing protection

1. Audit what you’re using and why.
   If your noncompete is the same for a senior strategist and an entry-level coordinator, it’s time for a reality check.
2. Use narrower tools first.
   NDAs, data access controls, and nonsolicits often protect what you truly care about without restricting employment options.
3. Pay attention to state rules and income thresholds.
   Multi-state workforces require multi-state compliance. “One template to rule them all” is a fantasy novelfun, but risky.
4. Define confidential information clearly and protect it operationally.
   Courts tend to take trade secret protection more seriously when companies treat it seriously: access limits, training, and security protocols matter.
5. Consider “garden leave” or compensation-based restrictions.
   If you truly need someone out of the market briefly, paying for that time can be fairer and more defensible than unpaid restraints.

For workers: know what you signed and what’s negotiable

1. Don’t assume it’s enforceableor unenforceable.
   State law and specific contract language matter. “My friend said…” is not a legal standard (sadly).
2. Ask for specifics.
   If the scope is vague (“any competitive business”), request clarity. Narrower language can protect everyone.
3. Negotiate reasonable boundaries.
   Shorter duration, smaller geography, defined competitors, and role-based limits can matter more than you’d think.
4. Keep your exit clean.
   Return devices, don’t download confidential files, and avoid messy gray areas. Even in states skeptical of noncompetes, trade secret claims can still bite.
5. Get advice when stakes are high.
   If a clause could derail your career move, consult a qualified attorney in your state. That cost can be far less than a prolonged dispute.

So… Did the Biden Executive Order “Win”?

It depends on how you define “win.” The executive order didn’t directly rewrite contract law, and the FTC’s attempted nationwide rule didn’t become enforceable.
But the EO did accomplish something powerful: it forced the country to argueout loudabout whether broad noncompetes are fair, effective, and compatible with
competitive labor markets.

Even after revocation of EO 14036 and the collapse of the FTC’s rule, the pressure didn’t vanish. States continue to update laws. Employers are increasingly shifting
toward confidentiality, trade secret protection, and narrower restrictions. Workers are more likely to ask questions before signing. In that sense, the target moved
and the conversation changed.

Real-World Experiences Related to Noncompetes (Extra Section)

Policies and court decisions can feel abstractuntil you’re the person trying to change jobs, hire a specialist, or protect a client relationship.
Here are some common, real-to-life experiences people report across industries (including insights), showing how noncompetes play out on the ground.
Think of these as “field notes” from the modern labor market.

1) The “Surprise Clause” moment

A candidate gets an offer, celebrates, then reads page 17 of the paperwork and discovers a noncompete that blocks working for “any competitor” for two years.
The candidate wasn’t negotiating at that levelthey assumed it was standard confidentiality language. Now the excitement turns into an awkward email:
“Hey, quick question… what exactly counts as a competitor?” Employers sometimes underestimate how often this creates distrust right at the moment they’re trying
to build commitment.

2) Recruiters learn to ask early (because they’ve been burned)

In tight talent markets, recruiters and hiring managers increasingly ask upfront: “Are you under a noncompete?”
Not because they want dramabecause they want to avoid spending six weeks courting someone only to realize the start date will be delayed by legal review.
In relationship-driven roles (client leads, sales, consulting), a restrictive covenant can become a hidden hiring tax: more time, more risk, more uncertainty.

3) The small business owner’s fear: “I trained them… now what?”

Some small and mid-sized businesses rely on noncompetes because they feel vulnerable. They don’t have massive legal teams, and a single key employee leaving can
feel existentialespecially if that person knows pricing, pipelines, or proprietary workflows. For these owners, the shift away from noncompetes can feel like
losing the locks on the front door. The healthier long-term answer, though, is often stronger operational protection: access controls, clearer NDAs, documented
processes, and building a team structure where knowledge isn’t trapped in one person’s head.

4) The “client relationship” gray zone

In insights and consulting, relationships are currency. A common scenario: a researcher leaves Firm A for Firm B, and former clientswho trust the personreach out.
The worker may feel like they’re simply continuing professional relationships, while the former employer sees it as solicitation. This is where narrowly written
nonsolicits (and clear client ownership policies) can prevent misunderstandings far better than a broad “you can’t work in this industry” noncompete.

5) The “I’m not trying to steal anything” reality check

Many workers aren’t trying to take trade secrets; they’re trying to take their skills. But companies don’t always distinguish between
“I learned how to do this kind of analysis” and “I downloaded the company’s proprietary models.” When disputes happen, they often revolve around data handling:
what was accessed, what was transferred, and what security practices existed. This is why clean offboarding processes and clear data policies matter.
They protect the company and the worker from messy accusations later.

6) Negotiation is becoming more normal

A quiet but meaningful change since the Biden EO spotlight: more people negotiate restrictive covenants like any other contract term.
Candidates ask for shorter timeframes, narrower scopes, or compensation-based restrictions. Some companies agreeespecially when they realize the alternative is
losing the candidate. This is a cultural shift: noncompetes are less likely to be treated as “non-negotiable boilerplate” and more like what they truly are:
a significant limitation on someone’s future work.

The big lesson from these experiences is simple: noncompetes aren’t just legal instrumentsthey’re trust instruments. Overuse can harm morale and recruiting.
Under-protection can create real business risk. The best outcomes tend to come from balance: protect truly confidential assets with strong operational controls,
use targeted agreements when needed, and avoid sweeping restraints that punish ordinary career growth.

Conclusion

“Biden Executive Order Takes Aim at Noncompete Agreements” is an accurate headlinebecause the EO put a spotlight on how noncompetes affect job mobility and wages,
and it spurred major federal action attempts through the FTC. Yet the story’s ending (so far) is less “nationwide ban” and more “national wake-up call.”
The FTC’s final rule was blocked, federal priorities shifted, and the EO itself was later revokedbut the debate it ignited continues to shape state laws,
employer practices, and worker expectations.

For IA Magazine readers and anyone working in talent-driven, relationship-heavy fields, the smartest move is to treat restrictive covenants as precision tools.
Keep what’s fair and defensible, drop what’s overbroad, and build real protection through operations, confidentiality, and good business practicesnot just
by telling people they can’t work.