When the Pattern Jury Charge Is Wrong


You know that feeling when you call the customer service line and an automated voice, says “press 1 if you’re calling about a new application, press 2 if you’re calling in response to a letter you received, press 3 if . . .”

“I’m not calling about any of those things,” you shout, to no one in particular. “I just want to talk to a real person!” You just want to explain your specific situation.

That’s what it feels like when you’re trying to explain to a judge why the Pattern Jury Charge (PJC) question doesn’t work for your particular case. You want to dial “0.”

And the result is often the same. More about that later.

Background on the PJC

First, let me explain what I’m talking about, especially for non-lawyers.

In Texas, where I defend non-compete and trade secret lawsuits, the Committee on Pattern Jury Charges of the State Bar of Texas publishes the Texas Pattern Jury Charges, affectionately known as the “PJC.” I’d guess most other states have something similar.

The PJC provides standard templates for the questions and instructions that a trial court judge submits to the jury for a verdict. Each template has a “Comment” section that cites to the statutes and/or case law that support it.

For example, the PJC question on breach of contract says “Did Don Davis fail to comply with the agreement?” The question is supported by case law that says a party breaches a contract when he fails to comply with the contract.

And now you know where I got Paula Payne and Dawn Davis, the characters in most of my hypotheticals. But I digress.

The PJC question on breach of contract works 90% of the time. But sometimes it doesn’t fit the particular facts of the case.

When the PJC is a Bad Fit

Suppose Dawn Davis sues Paula Payne for stealing Paula’s super-secret invoice template. Dawn claims this was misappropriation of trade secrets.

The PJC question asks, “Did Dawn Davis misappropriate Paula Payne’s trade secret?” It then provides a complicated definition of “misappropriation” taken straight out of the Texas trade secrets statute.

That sounds good in theory, but often that definition is a bad fit for the facts of the case. Under the statutory definition, there are six different ways a defendant can “misappropriate” a trade secret. We can condense those into essentially three ways: acquisition, use, or disclosure.

Suppose the case is only about acquisition. Dawn allegedly took the super-secret invoice template and kept it, but there’s no evidence she used it, or disclosed it to anybody.

In that case, the PJC question and definition is a bad fit, and should not be used. It would be better to simply ask “did Dawn Davis acquire Paula Payne’s trade secret?”

I covered this in Book Review: The New Texas Pattern Jury Charge on Trade Secrets.

In this case, the PJC instruction is not necessarily wrong, it’s just a bad fit. It is likely to cause confusion because it provides instructions about things that are not at issue.

Unfortunately, a lot of trial court judges are going to submit the PJC instruction anyway. It’s a warm fuzzy blanket. It provides a feeling of security, especially when the judge is not real strong on the area of law at issue.

This is wrong, and should not happen, but it could be worse.

It Gets Worse

In some cases, the PJC is not just a bad fit, it’s wrong under the facts of the case.

The best example is when an employer sues a former employee for breach of “fiduciary” duty. In that case, the PJC instruction on breach of fiduciary duty is simply wrong, and should not be used.

Recently, the Houston Court of Appeals expressly recognized this in Coe v. DNOW LP, __ S.W.3d __, No. 14-23-00410-CV, 2025 WL 1759382, at *22-23 (Tex. App.—Houston [14th Dist.] June 26, 2025, no pet. h.), holding that the PJC instruction “not an accurate statement of the law applicable to this case,” where a former employer alleged that its high-level managerial employees breached their fiduciary duties.

More about that case later. First some background.

A fiduciary duty is the highest kind of duty the law imposes. It includes a duty of care, a duty of loyalty, and a duty of full disclosure. Unlike any other legal duty, it requires the fiduciary to put the beneficiary’s interests ahead of his own.

Some classic examples of fiduciary duty would include:

  • An attorney’s duty to a client
  • A trustee’s duty to a trust beneficiary
  • A business partner’s duty to his partners
  • An officer or director’s duty to a corporation

For simplicity, let’s call the fiduciary duty owed by this kind of fiduciary an “absolute” fiduciary duty.

An employee owes an employer a kind of “fiduciary” duty. But does anybody seriously think an employee owes an employer an absolute fiduciary duty? No. This is not controversial.

I explained this in one of my oldest blog posts, labeling the employee’s duty Fiduciary Duty Lite.

For convenience let’s call the employee’s fiduciary duty a “limited” fiduciary duty.

Texas case law is pretty clear about what an employee can and cannot do under this limited fiduciary duty.

The employee cannot compete with the employer while still employed. But the employee can make plans to compete and can even conceal those plans from the employer. Abetter Trucking Co. v. Arizpe, 113 S.W.3d 503, 512 (Tex. App.—Houston [1st Dist.] 2003, no pet.).

This last point proves that the employee’s fiduciary duty is not an absolute fiduciary duty.

A true fiduciary would have a duty of full disclosure and a duty to put the employer’s interests ahead of his own. He wouldn’t be allowed to make secret plans to compete against his employer. He would have to tell his employer “I’m looking for another job and planning to join a competing company.”

No one thinks an employee has a duty to do that. An employee doesn’t have that kind of fiduciary duty.

And that’s why the PJC instructions on breach of fiduciary duty are wrong.

The PJC Instructions on Breach of Fiduciary Duty

The PJC instruction on breach of fiduciary duty doesn’t work for claims against former employees, because it is based on an absolute fiduciary duty, not an employee’s limited fiduciary duty.

Here’s what the PJC question and instruction on breach of fiduciary duty says. I’ve used “Employee” and “Employer” in place of “Don Davis” and “Paula Payne.”

Did Employee comply with his fiduciary duty to Employer?

As Employer’s agent, Employee owed Employer a fiduciary duty. To prove he complied with his duty, Employee must show—

1. The transaction in question was fair and equitable to Employer; and

2. Employee made reasonable use of the confidence that Employer placed in him; and

3. Employee acted in the utmost good faith and exercised the most scrupulous honesty toward Employer; and

4. Employee placed the interests of Employer before his own and did not use the advantage of his position to gain any benefit for himself at the expense of Employer; and

5. Employee fully and fairly disclosed all important information to Employer concerning the transaction.

PJC 104.2.

Two critical features make these instructions inappropriate for an employer’s claim that an employee breached a fiduciary duty by competing or making plans to compete:

First, the instructions in PJC 104.2 are intended for cases where the defendant is a fiduciary who engages in a transaction with the plaintiff, and the plaintiff claims that doing so was a breach of the defendant’s fiduciary duty.

This is apparent in Instruction 1, which refers to “the transaction[s] in question,” and Instruction 5, which refers to disclosure of information “concerning the transaction[s].” On their face, these instructions are intended for a situation where the defendant-fiduciary is involved in a transaction with the plaintiff-beneficiary.

For example, in Kinzbach Tool Co. v. Corbett-Wallace Corp., 160 S.W.2d 509, 510-11 (Tex. 1942), an employee negotiated a contract between his employer and a third party, secretly knowing what the third party was willing to pay, and secretly receiving a commission, without disclosing these facts to the employer.

In such a case, “when the fiduciary has profited or benefited from a transaction with the beneficiary,” the burden is on the fiduciary to show he fully disclosed information concerning the transaction. Comment to PJC 104.2.

Second, the instructions in PJC 104.2 are intended for absolute fiduciaries, not limited fiduciaries such as employees. Most of the instructions are derived from cases that did not involve mere employees.

Instruction 1, for example, says “the transaction[s] in question [was/were] fair and equitable to Paul Payne.” Instruction 2 says “Don Davis made reasonable use of the confidence that Paul Payne placed in him.” This instruction is derived from Stephens County Museum, Inc. v. Swenson, 517 S.W.2d 257, 261 (Tex. 1974), where a brother operating under a power of attorney advised his two sisters about management of their property. But Stephens did not say that a mere employee owes such a duty.

More recent Texas case law has made it clear that the duties referenced in these instructions do not apply to a defendant who is a mere employee.

In Johnson v. Brewer & Pritchard, P.C., 73 S.W.3d 193 (Tex. 2002), the court approved decisions holding that “an employee does not owe an absolute duty of loyalty to his or her employer” and accordingly held that an associate does not owe a law firm an “absolute fiduciary duty.” Id. at 201. The Comment to PJC 104.2 expressly acknowledges this. “Not every fiduciary relationship creates a general fiduciary duty,” the Comment states, citing cases including Johnson.

Applying Johnson to Claims Against Employees

Applying this principle from Johnson, Texas courts of appeals have repeatedly made it clear that a mere employee does not have an absolute fiduciary duty to his employer:

“An at-will employee may properly plan to compete with his employer, and may take active steps to do so while employed. . . . The employee has no general duty to disclose his plans and may secretly join with other employees in the endeavor without violating any duty to the employer.” Abetter Trucking, 113 S.W.3d at 512; accord PAS, Inc. v. Engel, 350 S.W.3d 602, 613-14 (Tex. App.—Houston [14th Dist.] 2011, no pet.).

Evidence that an employee formed a competing business without telling his employer does not conclusively establish a breach of fiduciary duty. Ameristar Jet Charter, Inc. v. Cobbs, 184 S.W.3d 369, 373-74 (Tex. App.—Dallas 2006, no pet.).

“An employee may prepare to go into competition with his employer, and can actively take steps to do so while still employed. The employee does not have a general duty to disclose his plans and can secretly join with other employees to compete without violating a duty to his employer.” Cuidado Casero Home Health of El Paso, Inc., 404 S.W.3d 737, 752 (Tex. App.—El Paso 2013, no pet.).

“[A] fiduciary may make plans to compete with its employer and make some preparations to compete without breaching its fiduciary duty.” Shufood LLC v. Liu, No. 01-21-00463-CV, 2024 WL 4628402, at *15 (Tex. App.—Houston [1st Dist.] Oct. 31, 2024, no pet. h.) (mem. op.).

As these cases illustrate, an employee does not have a general duty of full disclosure to an employer or a duty to put the employer’s interests before his own.

This is apparent in the rule that it is not a breach of fiduciary duty for an employee to make plans to compete with his employer and to conceal those plans from the employer. Abetter Trucking, 113 S.W.3d at 512. That rule would make no sense if an employee had an absolute fiduciary duty of full disclosure and to put the employer’s interests before his own.

Considering the limited scope of an employee’s fiduciary duty established by the case law cited above, the instructions in PJC 104.2 are simply incorrect when applied to a claim for breach of fiduciary duty against a mere employee.

The Comment to the PJC instruction gives a slight nod to this problem. Tucked away in the Comment is this nugget: “The instruction may require modification based on the specific facts involved. Not every fiduciary relationship creates a general fiduciary duty . . . In such cases, it may be appropriate to modify the list of duties in PJC 104.2 to define the scope of the fiduciary duty.”

Strangely, though, the Comment to the PJC instructions doesn’t specifically talk about the need to modify the instructions for claims against employees, and it doesn’t cite any of the cases above that specifically apply Johnson to claims against employees. No Abetter. No Ameristar. No Cuidado.

The result is a PJC instruction that is almost destined to be misapplied.

The DNOW Case

I can confirm from personal experience that Texas trial courts are prone to mistakenly using the PJC instructions for breach of fiduciary duty for claims against mere employees.

It would be so nice to have a case that specifically says the PJC instruction is wrong when applied to a defendant who was merely an employee of the plaintiff.

Enter DNOW.

Coe v. DNOW involved competition in the oilfield equipment industry. After DNOW bought Odessa Pumps, a group of Odessa Pumps employees left to work for Permian Pump & Valve. 2025 WL 1759382 at *1. You can already tell this is the most Texas trade secrets case imaginable.

And get this: some of the former DNOW employees transferred DNOW documents to flash drives or personal email accounts and took the documents to Permian. Id. at *2. The documents filled at least 32 boxes. Id. And one former employee admitted lying under oath when he denied copying DNOW’s information and using it after he joined Permian. Id.

In many cases like this, the employees take a bunch of documents and don’t really do anything with them. But in DNOW, there was actually evidence the former employees used DNOW’s documents at Permian.

For example, one former employee provided Permian the rates DNOW’s San Angelo and Odessa branches were charging Pioneer, a big customer. He even texted “I think if we match price and can deliver our mechanics and parts [at] a slightly lower rate we can choke the market in 6 months with them.” Id. at *12.

In trade secrets litigation, we call this a “bad fact.”

Armed with plenty of bad facts, DNOW sued a big group of the former employees, alleging a conspiracy to misappropriate DNOW’s trade secrets. DNOW also claimed that four of its former employees breached their fiduciary duties to DNOW. DNOW described them as “executive, managerial, and high-level employees,” although it appears they were not directors or officers. Id. at *19.

DNOW asked for a jury instruction on breach of fiduciary duty that tracked the Pattern Jury Charge instruction. See id. at *22. The former employees cried foul, objecting that the instruction did not accurately describe the limited fiduciary duty of an employee. They proposed an alternative instruction clarifying that an “employee does not owe an absolute duty of loyalty to the company,” “can properly plan to compete with his employer,” “can take active steps to do so while still employed by that employer,” and “has no general duty to disclose his plans to the employer.” Id. at *22-23.

The trial court sided with DNOW, submitting the PJC-based instruction. Id. at *22.

The court of appeals said the trial court got it wrong. The PJC-based instruction “is not an accurate statement of law applicable to this case,” the court reasoned, “because even a fiduciary employee ‘may plan to compete with his employer and take certain steps toward that goal without disclosing his plans to the employer.’” Id. (citing PAS, Inc. v. Engel, 350 S.W.3d at 613-14).

The court of appeals held that the former employees’ requested instruction was “substantially correct and was necessary to avoid misleading the jury about the duties the fiduciary appellants owed to DNOW.” Id. at *23. Therefore, the trial court “abused its discretion in refusing the instruction.” Id.

This error was harmful. “The charge permitted the jury to find breach of fiduciary duty on legally invalid bases,” the court said. Id. at *25. Thus, the court could not be “reasonably certain that the jury was not significantly influenced by the error.” Id. Accordingly, the court of appeals reversed the portion of the judgment addressing DNOW’s breach of fiduciary duty claims and send those claims back to the trial court for a new trial. Id.

Of course, the trouble of a new trial could have been avoided if the trial court had not made the mistake of submitting a PJC-based instruction that did not follow the law on fiduciary duties of employees. Hopefully the DNOW case will be a warning to other trial courts not to make the same mistake.

Should Plaintiffs Be Careful What They Wish For?

The trial court’s mistake in DNOW was not unusual. I know from my own practice, and from talking with lawyers who practice in this field, that the siren song of the PJC instruction can be hard for trial court judges to resist.

Keep in mind, typically the lawyer for the plaintiff is actively urging the trial court down the wrong road. “Your Honor, the instruction we’re asking for is routine, it’s verbatim out of the PJC!” You can imagine the rhetoric.

That same kind of argument was made in Bestway Oilfield, Inc. v. Cox, another recent Texas case involving oilfield equipment. In that case, Cox was not even a managerial employee. He worked in the purchasing department of Bestway Oilfield, a company that sells valves to the oil and gas industry. While employed by Bestway, Cox formed a side business called ServicePlus, focusing on selling small parts like seals, without telling Bestway.

After Cox left, Bestway sued him for various claims including breach of fiduciary duty. Citing the PJC, Bestway’s counsel requested a jury instruction almost identical to the instruction submitted in DNOW.

Of course, Cox’s lawyer protested vigorously. The PJC instruction is based on an absolute fiduciary duty, not the limited fiduciary duty of an employee, he said. Cox wasn’t an officer or director. Heck, he wasn’t even a manager.

I recall the argument well because I was the lawyer doing the protesting.

Anyway, the trial court rejected my argument and submitted the PJC-based instruction on breach of fiduciary duty. In closing argument, I did my best to argue the jury should answer “no,” but it was tough sledding, considering how much the instruction favors the plaintiff. So I was disappointed, but not really surprised, when the jury answered “yes.”

But in a way, Bestway did us a favor. By asking for an incorrect instruction on breach of fiduciary duty, Bestway gave us a compelling issue for appeal. If Bestway had submitted an instruction that correctly stated the applicable law, and if the jury had answered yes, we would be in a tougher spot. As in DNOW, perhaps it’s a case of “be careful what you wish for.”

I can hear it now. “Hello, this is the Houston Court of Appeals. Press 1 for charge error. Press 2 for harmful error. Press 3 for . . .”

________________________

Zach Wolfe (zach@zachwolfelaw.com) is a Texas trial lawyer who handles non-compete and trade secret litigation at Zach Wolfe Law Firm (zachwolfelaw.com). Thomson Reuters has named him a Texas “Super Lawyer”® for Business Litigation every year since 2020.

These are his opinions, not the opinions of his firm or clients. Reasonable people can disagree. Every case is different, so don’t rely on this post as legal advice for your case.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


On April 23, 2024, the FTC voted 3-2 to approve its final rule banning non-competes for U.S. workers. Unless the federal courts block the rule (more about that later), it will go into effect on September 4, 2024.

(Update: The federal courts did block the rule. Sort of. See Texas Federal Court Enters Limited Preliminary Injunction Staying FTC’s Noncompete Clause Ban from my friends at Morgan Lewis.)

My law practice focuses on defending non-compete and trade secret claims, so as you might imagine, that was a busy week for me.

You can imagine the text messages from clients. “Hey, did you see this news about the FTC?”

I tried not to be too sarcastic. “Uh, yeah. I heard about it.”

I had two main things to tell my clients who have non-compete agreements:

First, don’t get too excited.

Second, it’s complicated.

Yes, it’s complicated, for several reasons. But in this blog post I will make it simple. You can determine if the FTC’s ban applies to your non-compete in five easy steps.

1. Did the company’s cause of action accrue before 9/4/24?

Sorry, if you’re already a defendant in a non-compete lawsuit, the FTC rule won’t do much for you.

Section 910.3(b) says:

Existing causes of action. The requirements of this part do not apply where a cause of action related to a non-compete accrued prior to the effective date.

Generally, a claim “accrues” when all the facts necessary to support it exist. So, if you’ve already violated a non-compete—allegedly—then the cause of action has already accrued.

There may be some borderline cases where there’s a dispute about whether the non-compete was breached before or after 9/4/24. But if there’s already a pending lawsuit, it’s safe to say the cause of action already accrued, and the new rule does not apply.

2. Is the non-compete clause part of an agreement to sell a business?

Generally, courts are more willing to enforce a non-compete that is part of the sale of a business, versus a non-compete in an ordinary employment agreement. I cover this at Non-Competes in the Sale of a Texas Business.

The FTC rule recognizes this with an important exception in Section 910.3(a):

Bona fide sale of business. The requirements of this part shall not apply to a non-compete clause that is entered into by a person pursuant to a bona fide sale of a business entity, of the person’s ownership interest in a business entity, or of all or substantially all of a business entity’s operating assets.

Of course, there will be litigation over borderline cases, but if you’re non-compete is part of an agreement to sell a business, the FTC ban likely will not apply.

3. Is the non-compete ban retroactive?

But let’s say your non-compete is part of an employment agreement, and you haven’t violated it yet. Does the new rule retroactively ban your non-compete?

It depends on whether you’re a “senior executive.” If you were in a “policy-making position” and made more than $151,164 annually, then you’re a “senior executive.”

In that case, the rule does not prohibit the employer from seeking to enforce a non-compete you entered into before 9/4/24, the effective date of the rule. See Rule 910.2(a)(2).

But if you’re not a senior executive, then the rule applies, even if you entered into the non-compete before the effective date of the rule.

4. Are you in the Fifth Circuit?

So far, we’re assuming the rule actually goes into effect on September 4, 2024. That is not a certainty.

There are at least three federal lawsuits seeking to block the rule as unconstitutional and exceeding the FTC’s authority. For a good summary of these, see Analysis of FTC Non-Compete Ban Legal Challenges: Does the Ban Pass Constitutional Muster?

Two of these lawsuits are in Texas: Ryan, LLC v. FTC, Case No. 3:24-cv-00986, in the Northern District of Texas and Chamber of Commerce v. FTC, Case No. 6:24-cv-00148, in the Eastern District of Texas.

And let’s just say it’s no accident where they were filed.

I’ll save my opinion on the merits of those suits for another post. (Short version: I think a major weakness is that the arguments against the FTC rule tend to ignore the extent to which state law already imposed similar limits.)

But I will repeat the prediction I made when the rule was first proposed. I expect both the conservative Fifth Circuit and the 6-3 conservative majority on the Supreme Court will be hostile to what they will see as a partisan vote by a federal agency to sweep aside state non-compete law with the stroke of an administrative law pen.

My short-term prediction is that the rule will be blocked before its effective date of 9/4/24, and my long-term prediction is that SCOTUS will strike down the rule.

This is, admittedly, based on more on “vibes” than any detailed analysis of the merits. You can usually trust vibes when it comes to the Supreme Court.

But let’s suppose I’m wrong, and the rule goes into effect as planned. That brings us to the final and possibly most important question.

5. Is the restriction in your agreement a “non-compete clause”?

The FTC’s new Rule 910 generally declares it an “unfair method of competition” to enter into or enforce a “non-compete clause.”

But as with many things in the law, so much rides on definitions. How exactly does Rule 910 define a “non-compete clause”?

The rule defines a non-compete clause as:

(1) A term or condition of employment that prohibits a worker from, penalizes a worker for, or functions to prevent a worker from:

(i) Seeking or accepting work in the United States with a different person where such work would begin after the conclusion of the employment that includes the term or condition; or

(ii) Operating a business in the United States after the conclusion of the employment that includes the term or condition.

Thus, in simplified terms, a “non-compete clause” prohibits, penalizes, or functions to prevent a worker from seeking or accepting work or operating a business.

That’s a pretty abstract definition. Let’s make it more concrete by applying it to two typical non-compete clauses.

Non-Compete 1 says:

Employee may not work for or operate any Competing Business in the Restricted Area during the Restricted Period in the same or similar capacity that Employee served for Company.

Assume that “Competing Business” is defined essentially as the business that Company does.

Non-Compete 2 is a little more complicated. It says:

After termination of employment, Employee is free to seek or accept work or operate a business in competition with Employer.

However, Employee may not solicit or accept business from any Restricted Customer in the Restricted Area during the Restriced Period.

“Restricted Customer” means any customer Employee dealt with or received confidential information about during Employee’s last year of employment with Company.

If you know anything about non-compete law, you know that generally a non-compete must have a reasonable time limitation and a reasonable geographic limitation. So to keep our hypotheticals simple, let’s assume the “Restricted Time Period” and “Restricted Area” are reasonable.

That leaves the scope of activity restrained. Let’s look at the scope of activity of both sample non-competes.

Non-Compete 1: Generally prohibited by both current Texas law and the FTC rule

Is the scope of activity restrained by Non-Compete 1 reasonable, under current Texas law?

The short answer is no. Of course, we’re talking reasonableness, a fuzzy concept, so it is almost always open to debate. And believe me, I have this debate often in my cases, with both opposing counsel and judges. But as a general rule, the scope of activity restrained by Non-Compete 1 is too broad. It’s what Texas courts have called an impermissible “industry-wide exclusion.” I cover this in detail in The Industry-Wide Exclusion Rule in Texas Non-Compete Litigation.

Furthermore, on its face Non-Compete 1 is a “non-compete clause” as defined by the FTC. I mean, it’s pretty clear: It prohibits the employee from working for a competing business.

So, we can say two things about Non-Compete 1.

First, the FTC rule prohibits it. Second, Texas law already prohibited it (generally).

Non-Compete 2: Generally allowed by both Texas law and the FTC rule

Non-Compete 2 is more difficult. As a lawyer who represents defendants in non-compete cases, I can certainly come up with an argument that Non-Compete 2 is unenforceable under Texas law.

But honestly, it’s not likely to be a winning argument. Most judges are going to see the scope of Non-Compete 2 as reasonably limited the proper purpose of protecting the company’s goodwill and confidential information.

I cover this topic in more detail in Wolfe’s First Law of Texas Non-Compete Litigation. The short version: you can’t take your customers with you.

So, as a general rule, Non-Compete 2 is probably enforceable under current Texas law.

But is it a prohibited “non-compete clause” under the FTC rule?

Answering this question requires two steps.

Step 5a: Does the clause expressly prohibit working for or operating a competing business?

On its face, Non-Compete 2 does not expressly prohibit working for or operating a competing business.

In fact, it says the opposite: “Employee is free to seek or accept work or operate a business in competition with Employer.”

So the answer is no. But that’s not the end of the story.

Step 5b: Does the clause function to prevent working for or operating a competing business?

Remember, the definition of “non-compete clause” includes a provision that “functions to prevent” a worker from seeking or accepting work for a competing business or operating a competing business.

Enter the functional test: Regardless of how the restriction is worded, does it function to prevent Employee from going to work for a competitor?

In other words, is it a “de facto” non-compete? This was the term the FTC used in its comments when the rule was originally proposed. I explained at What Everybody’s Missing About the FTC’s Proposed Non-Compete Rule.

On this question we must consult the FTC’s comments to the final rule, in particular the comments at page 38364 of the Federal Register, Volume 89, May 7, 2024. You can also find those comments at page 23 of this PDF.

Some key FTC comments:

  • Pursuant to the term “functions to prevent,” the definition of non-compete clause also applies to terms and conditions that restrain such a large scope of activity that they function to prevent a worker from seeking or accepting other work or starting a new business after their employment ends, although they are not expressly triggered by these specific undertakings.”
  • This prong of the definition does not categorically prohibit other types of restrictive employment agreements, for example, NDAs, TRAPs, and non-solicitation agreements.
  • [T]he term “functions to prevent” clarifies that, if an employer adopts a term or condition that is so broad or onerous that it has the same functional effect as a term or condition prohibiting or penalizing a worker from seeking or accepting other work or starting a business after their employment ends, such a term is a non-compete clause under the final rule.
  • [T]he definitions three prongs—“prohibit,” “penalize,” and “function to prevent”—are consistent with the current legal landscape governing whether a particular agreement is a non-compete.

As these comments indicate, a non-solicitation agreement does not necessarily function as a non-compete, but it could.

Suppose, for example, that the Company in Non-Compete 2 sells equipment to oilfield services companies. Suppose further that Employee’s customers include the five largest oilfield services companies in the geographic area at issue, and that they account for 90% of the market there.

In that case, Non-Compete 2 would arguably function to prevent Employee from accepting employment with a competing company, because as a practical matter all the customers he would want to sell to would be Restricted Customers.

That would arguably be a “de facto” non-compete clause, generally prohibited by the FTC rule.

Or is it? The lawyer for the company seeking to enforce the non-compete will argue otherwise.

That’s where the argument is going to be.

_________

Zach Wolfe (zach@zachwolfelaw.com) is a Texas trial lawyer who handles non-compete and trade secret litigation at Zach Wolfe Law Firm (zachwolfelaw.com). Thomson Reuters has named him a Texas Super Lawyer® for Business Litigation every year since 2020.

These are his opinions, not the opinions of his firm or clients, so don’t cite part of this post against him in an actual case. Every case is different, so don’t rely on this post as legal advice for your case.



Source link