Red Flags in Non-Competes: Geographic Scope and Time Restrictions

Introduction

Non-compete agreements are among the most common—and controversial—clauses found in employment and freelance contracts. Designed to protect a company’s legitimate business interests, such as trade secrets, client relationships, and proprietary processes, non-competes can also become tools of excessive control when poorly drafted or misapplied. While not enforceable in every jurisdiction (notably banned in California for most employees), they remain widely used across the U.S. and globally.

One of the primary red flags in a non-compete clause lies in its geographic scope and duration, both of which must be reasonable to stand up in court. Overly broad restrictions can effectively block skilled professionals from working in their field for years or across entire regions, even if they pose no real threat to their former employer.

For freelancers, consultants, engineers, developers, creatives, and corporate employees alike, understanding how to identify unreasonable geographic reach and excessive time limits is essential before signing on the dotted line. This article breaks down what constitutes a red flag in these two critical dimensions of non-compete clauses—and what you can do about it.

What Is a Non-Compete Agreement?

A non-compete agreement (or covenant not to compete) restricts an individual from engaging in similar professional work for a competitor—or starting a competing business—within a specific time frame and geographic area after leaving a job or contract engagement.

These agreements typically apply during employment and extend into the post-employment period. While employers argue they’re necessary to protect sensitive information and customer relationships, courts scrutinize them closely because they limit an individual’s ability to earn a livelihood.

To be enforceable in most jurisdictions that allow non-competes (such as New York, Texas, or Florida), three conditions generally must hold:

1. The restriction protects a legitimate business interest.
2. It is no broader than necessary in scope, duration, and geography.
3. It does not impose undue hardship on the employee.

When any of these factors fail—especially geographic reach or time limits—the clause may be voided entirely or reformed by a court.

Red Flag #1: Overly Broad Geographic Scope

The geographic scope defines where you are prohibited from working in competition with your former employer. A reasonable range depends on the nature of the business and the role, but red flags arise when employers demand restrictions that far exceed their actual market footprint.

Examples of Unreasonable Geographic Clauses

• “You shall not work for any competing firm within 50 miles of our headquarters in Chicago.”
• “This restriction applies nationwide across all U.S. states.”
• “The employee agrees not to engage in competitive services anywhere the company currently operates or may operate in the future.”

These examples illustrate common overreaches:

1. National bans for local businesses: A dental practice restricting a hygienist from working at any dental office in the country is disproportionate unless that hygienist had access to national patient databases or franchise plans—which they likely didn’t.

1. Blanket regional coverage without justification: Requiring a software developer who worked remotely for a Denver-based startup to avoid all tech jobs across the Mountain West makes little sense if the company serves only local clients.

1. Future expansion zones: Phrases like “wherever the company may operate” give employers unchecked power over undefined future territories—making enforcement unpredictable and unfair.

How Courts Evaluate Geographic Reasonableness

Courts assess whether the geographic restriction aligns with where the employer actually does business or has protectable relationships. For instance:

• If a logistics company operates only in Texas, restricting an operations manager from working for competitors across all 50 states is likely unenforceable.
• A national sales executive who managed accounts coast-to-coast might reasonably be restricted within certain key markets—but not necessarily every zip code.

Judges often apply the “blue pencil rule,” allowing them to strike down or narrow overbroad regions while preserving enforceable portions. In some cases, courts may refuse to modify the clause and invalidate it entirely if it’s too sweeping.

Red Flag #2: Excessive Time Restrictions

The duration of a non-compete—the length of time you're barred from competitive work—is another major factor in determining enforceability. While short-term restrictions are more likely to be upheld, excessively long periods raise red flags.

Common Problematic Durations

• 3–5 year bans for mid-level engineers or marketing staff
• 2-year no-work clauses for freelance designers with no access to source code
• Lifetime prohibitions disguised as “indefinite confidentiality” terms

In general:

• 6 months is often considered presumptively reasonable.
• 1 year may be acceptable in high-stakes roles involving deep client relationships or trade secrets (e.g., senior executives, R&D leads).
• More than 2 years is rarely upheld unless justified by extraordinary circumstances.

Even then, the burden falls on the employer to prove why such a long restriction is necessary—not merely convenient.

Industry-Specific Considerations

Certain fields see tighter scrutiny due to rapid innovation or mobility:

• Tech & Software Development: Given fast product cycles and skill obsolescence, courts are reluctant to enforce multi-year bans. A three-year non-compete on a mobile app developer may prevent them from using skills that become outdated in 18 months.

• Healthcare Professionals: Some states limit or prohibit non-competes for doctors and nurses due to public health concerns. Even where allowed, restrictions beyond one year are often challenged successfully.

• Freelancers & Consultants: Since these workers typically serve multiple clients under short engagements, blanket bans risk chilling entire career paths. A graphic designer should not be barred from designing logos for five years just because one client made them sign a broad non-compete.

Real Cases: Where Courts Drew the Line

Several court rulings highlight how unreasonable geographic and time limits lead to invalidated clauses:

Ohio Valley Environmental Services v. Freeman (2018)

An environmental consultant was restricted from working in West Virginia, Kentucky, Ohio, Pennsylvania, Maryland, or Virginia for two years after termination. The court struck down the restriction as overly broad given that his actual work covered only three counties in West Virginia.

“The geographic scope must be tied to where the employee actually worked or had influence—not an arbitrary list of neighboring states.”

AMN Healthcare v. Pysher (2016)

A travel nurse signed a non-compete barring her from working for competitors within 50 miles of any facility using AMN’s services—even ones she’d never heard of. The Ninth Circuit ruled this “constructive territory” concept unenforceable due to lack of notice and proportionality.

This case underscores that vague or constructive geographic definitions fail legal muster when they exceed actual business operations.

EarthWear Clothiers, Inc. v. Holcomb (2019)

A one-year restriction on a senior employee was upheld—but only after the court narrowed it from covering 34 states to just those where the company had verifiable customers during his tenure.

The takeaway: breadth kills enforceability.

How Employers Justify Overreach—and Why It Often Fails

Employers sometimes argue that broad non-competes are needed to:

• Prevent poaching of clients or team members
• Stop dissemination of trade secrets
• Maintain competitive advantage in growing markets

While these concerns aren’t unfounded, courts require proportionality. Simply claiming “we want maximum protection” isn't enough.

For example:

• If your job didn’t involve client interaction (e.g., backend development), the risk of poaching is low.
• If all proprietary data was stored behind secure access controls and you signed an NDA, a separate non-compete may be redundant.
• Remote work further complicates geography-based limits—how do you define “50 miles” when your office is virtual?

In fact, the Federal Trade Commission (FTC) issued a proposed rule in 2023 that would ban most non-competes nationwide, citing anticompetitive effects and wage suppression. Though not yet final, it signals growing regulatory skepticism toward overbroad covenants.

How to Spot Red Flags Before Signing

Before accepting any contract with a non-compete clause, ask:

1. Does the geographic scope match my actual work area?

• Did I travel regionally or nationally?
• Does the company operate in all locations listed?

1. Is the time restriction proportional to my role and access?

• Am I in R&D with critical IP knowledge—or in a standard contributor role?
• Would six months be sufficient to transition clients or declassify data?

1. Are there carve-outs for freelance, volunteer, or unrelated work?

• Can I still consult in adjacent industries (e.g., writing about tech without coding)?
• Is passive income (blogs, courses) included in the ban?

1. Can it be negotiated?

• Many companies will accept narrower terms if asked upfront.

Negotiating Smarter Non-Competes

You’re not powerless. Even standard form contracts can often be modified with polite negotiation:

Sample Language for Revision Requests

“I’m comfortable agreeing to a non-compete, provided the geographic scope is limited to counties or markets where I had direct client responsibility and the duration does not exceed 12 months.”

Or:

“Given my role focused solely on internal tooling with no customer contact, I request removal of the non-compete or substitution with a non-solicitation clause.”

Non-solicitation clauses—which bar contacting former clients or hiring away teammates—are often acceptable substitutes and less restrictive than full non-competes.

What to Do If You’ve Already Signed

If you signed an agreement with overly broad terms:

1. Document everything: Keep records of your responsibilities, travel history, and access permissions.
2. Consult legal counsel before taking a new role that might trigger conflict.
3. Request clarification or amendment from the former employer if possible.
4. Do not ignore it, even if you think it's unenforceable—some companies still sue to intimidate.

Conclusion

Non-compete agreements can serve valid business purposes—but only when they're narrowly tailored. Geographic scope and time restrictions are two of the most common flashpoints where employers overreach, creating clauses that may be legally invalid or practically suffocating for workers.

Red flags include nationwide bans for local roles, multi-year prohibitions without justification, and vague territories based on hypothetical expansion plans rather than real operations. Courts consistently rule against such extremes in favor of fairness and employee mobility.

Whether you're signing your first freelance contract or joining a growing startup as an early engineer, take the time to understand—and push back on—unreasonable non-compete terms. Your future career options depend on it. And remember: just because something is written into a contract doesn't mean it's enforceable. Knowledge is power when navigating the fine print of modern work agreements.