Non-Compete and Non-Solicitation Agreements: Enforceability and Limits

Restrictive covenants sit at the intersection of employment law, competition policy, trade secrets, and contract enforcement. Employers want to protect customers, confidential information, workforce stability, and investment in training. Employees and regulators focus on mobility, wages, bargaining power, and overbroad restraints.

This guide supports the Employment Law pillar by explaining non-compete and non-solicitation enforceability in practical terms.

What is a non-compete agreement?

A non-compete agreement restricts a worker from working for competitors, starting a competing business, or engaging in certain competitive activities after employment. The restriction may be part of an employment contract, equity agreement, severance agreement, acquisition agreement, or standalone covenant.

Enforceability varies widely. Some jurisdictions ban or heavily restrict employee non-competes. Others enforce reasonable restrictions tied to legitimate business interests. Sale-of-business covenants may receive different treatment from ordinary employment covenants.

What is a non-solicitation agreement?

A customer non-solicitation clause restricts efforts to solicit certain customers or prospects. An employee non-solicitation clause restricts recruiting or inducing employees to leave. These clauses are often narrower than non-competes, but they still require careful drafting.

A non-solicit should define covered customers, lookback period, restricted conduct, duration, and exceptions. Overbroad clauses that prevent ordinary competition or cover unknown customers may face challenge.

What business interests can be protected?

Common protectable interests include trade secrets, confidential information, customer relationships, goodwill, specialized training, and sale-of-business value. The employer should be able to explain why the restriction is needed for the specific role.

A junior employee with no strategic information should not receive the same restriction as a senior executive with customer relationships and confidential strategy. Role-based tailoring improves enforceability and employee relations.

What is the FTC noncompete issue?

The FTC finalized a broad noncompete rule in 2024, but its status has been heavily litigated and the agency later moved away from defending the rule. Employers should check current federal and state status before relying on any national summary.

Because the landscape changes, companies should maintain a covenant review calendar. Existing forms should be reviewed when law changes, when hiring in new states or countries, and when employees move to remote locations.

How should employers enforce covenants?

Enforcement should be evidence-based and proportionate. The employer should identify the covenant, protected interest, breach evidence, harm, urgency, and desired remedy. Aggressive letters without a factual basis can create counterclaims and reputational risk.

Exit interviews should remind employees of continuing obligations, collect devices, confirm return or deletion of data, review customer transition, and preserve access logs where appropriate.

Employer compliance checklist

An employment law program should translate legal obligations into repeatable HR and management workflows. The checklist should cover hiring, classification, contracts, wage and hour, leave, accommodations, discrimination, harassment, workplace safety, privacy, discipline, termination, restrictive covenants, remote work, records, and manager training. The practical question is not whether the company has a policy. The question is whether managers know what to do when a real issue appears.

For this topic, the core control areas are Overbroad non-compete, Wrong worker group, Vague customer non-solicit, No protectable interest, Poor exit controls. Each area needs a named owner, decision trigger, evidence standard, escalation path, and document location. Employment issues move quickly because they involve people, deadlines, pay, emotions, health information, and workplace relationships. A slow or inconsistent response can turn a manageable issue into a claim.

The workflow should follow this path: Role review -> Law check -> Draft narrow -> Onboard -> Exit. HR should not operate separately from legal, payroll, finance, security, IT, and line managers. Payroll needs classification data. Legal needs documents and facts. IT may need access logs. Managers need scripts and boundaries. Privacy teams may need to review employee monitoring, background checks, or cross-border HR data.

Common mistakes employers make

The first mistake is relying on labels instead of facts. Calling someone salaried does not automatically make them exempt. Calling someone a contractor does not automatically remove wage and hour obligations. Calling a separation mutual does not eliminate termination risk. Employment law usually looks at what actually happened, not only what the document says.

The second mistake is inconsistent treatment. Employees in similar roles should be managed under consistent standards unless a documented reason supports a difference. Inconsistent pay, discipline, leave approval, investigation quality, accommodation handling, or severance practice can become evidence in disputes.

The third mistake is poor documentation. Employers often document too little before discipline and too much in emotional language after conflict begins. Good records are factual, dated, specific, respectful, and connected to policy or performance expectations. They avoid speculation, blame language, jokes, and unnecessary medical or personal details.

Records, training, and review cadence

Employers should keep current offer letters, employment agreements, job descriptions, wage records, time records, leave records, accommodation files, policy acknowledgments, training logs, investigation files, disciplinary notices, performance reviews, payroll classifications, contractor files, and termination documents. Sensitive files should be access-controlled, especially medical, accommodation, investigation, and complaint records.

Training should be role-specific. Executives need escalation and retaliation awareness. Managers need documentation, harassment, discrimination, wage-hour, accommodation, leave, and termination basics. HR needs investigation discipline and deadline tracking. Payroll needs classification and timekeeping controls. Remote teams need rules for time capture, equipment, security, expenses, and cross-border work.

A useful review standard is simple: someone outside the matter should be able to open the file six months later and understand the issue, facts, decision-maker, policy basis, employee communication, legal review, and follow-up owner. If that cannot be done, the file is not ready for an agency inquiry, litigation hold, audit, settlement discussion, or executive review.

Decision questions before action

Before hiring, disciplining, terminating, reclassifying, denying leave, refusing accommodation, enforcing a covenant, or approving remote work, ask whether the decision affects protected rights, pay, benefits, immigration, privacy, safety, data, retaliation risk, or contractual obligations. Also ask who has authority, which documents apply, what facts are verified, what alternatives were considered, and what communication should be given to the employee.

The strongest employment decisions are boring in the best way: clear role expectations, consistent standards, timely communication, documented facts, respectful tone, and visible follow-through. They do not require perfect outcomes. They require a process that a neutral reviewer can understand.

This discipline protects speed. When managers know the escalation path and HR has usable templates, routine employment matters do not stall. Legal attention can then focus on high-risk issues: protected complaints, medical leave, discrimination allegations, executive exits, mass layoffs, cross-border work, worker classification, and restrictive covenants.

Manager playbook and escalation rules

Managers are the first line of employment law compliance, but they should not be expected to become lawyers. They need practical playbooks that say what to do, what not to say, when to pause, and who to call. The playbook should cover attendance issues, overtime requests, performance concerns, medical information, complaints, harassment observations, pay questions, remote-work requests, resignation notices, and suspected misconduct.

A good manager playbook includes approved phrases and escalation triggers. For example, a manager who hears that an employee has a medical restriction should not ask for diagnosis details; the manager should route the issue to HR. A manager who receives a harassment concern should not promise secrecy or conduct a private investigation; the manager should escalate promptly. A manager considering termination after a complaint should pause for HR and legal review.

Escalation rules should be visible and simple. Protected complaints, wage concerns, safety reports, leave requests, pregnancy-related issues, disability accommodation, union or collective activity, immigration concerns, data incidents, threats, violence, harassment allegations, and executive separations should all move out of ordinary manager discretion. This prevents well-intentioned but inconsistent decisions.

Audit readiness and evidence quality

Employment files should be built as if a neutral reviewer may read them later. That reviewer might be an agency investigator, judge, mediator, auditor, buyer, insurer, executive, or new HR leader. The file should show the timeline, applicable policy, facts reviewed, people involved, decision-maker, employee response, and final action. It should avoid emotional commentary, speculation, sarcasm, and unnecessary personal detail.

Payroll and time records deserve special discipline. Wage-hour claims often turn on records rather than memory. Employers should retain time entries, edits, approvals, overtime records, pay changes, deductions, commission calculations, bonus plans, exempt status analysis, and contractor classification reviews. If a manager edits time, the reason should be documented. If an employee works remotely, the timekeeping system should still capture actual work time where required.

Investigation files should be separated from general personnel files where appropriate. They may contain witness statements, sensitive allegations, credibility assessments, legal advice, medical references, or security evidence. Access should be limited. The file should still be usable: allegations, scope, evidence, findings, corrective action, and follow-up should be clear.

Metrics that reveal employment risk

Employers should track more than headcount and turnover. Useful legal-risk metrics include overtime spikes, missed meal or rest periods where applicable, contractor tenure, repeated role reclassification, complaint volume, complaint closure time, investigation outcomes, leave duration, accommodation requests, performance-improvement plan results, termination reasons, severance exceptions, and manager-specific employee relations patterns.

Metrics should be used carefully. A low complaint rate may mean a healthy workplace, or it may mean employees do not trust the reporting system. A high complaint rate may mean a troubled workplace, or it may mean employees trust the process enough to report early. The value is in patterns, not raw numbers.

Leadership should receive a concise employment risk dashboard. It should identify open high-risk matters, overdue investigations, wage-hour concerns, recurring manager issues, policy gaps, training completion, and jurisdictions requiring legal updates. This gives executives visibility without exposing unnecessary employee detail.

The dashboard should lead to action, not just reporting. If the same manager, location, role, or policy creates repeated issues, the employer should update training, supervision, staffing, documentation, or policy language before the pattern becomes a formal claim.

Restrictive covenant risk table

FAQ