At-Will Employment in Texas: The Doctrine, the Exceptions, and the Termination Mistakes That Create Exposure

Texas recognizes one of the strongest at-will employment presumptions in the country. An employer can terminate an employee for a good reason, a bad reason, or no reason at all — and that is an accurate statement of Texas common law. Most founders hear this and conclude they're bulletproof. They're not.

What at-will actually protects is narrow: the right to make employment decisions without owing an explanation. It does not protect terminations made for unlawful reasons. Firing someone because of race, sex, national origin, disability, religion, or age is still discrimination regardless of the at-will default. Terminating an employee in retaliation for filing a workers' compensation claim, reporting harassment, or engaging in other protected activity is still retaliation. The at-will doctrine doesn't touch any of that — those claims arise under federal and state statutes that operate on top of the common-law baseline.

The second blind spot is contractual. At-will is a default, not an inviolable rule. Parties can modify it — and founders do so accidentally all the time. An offer letter that promises employment "as long as performance remains strong" or specifies that termination requires cause has created a contractual limitation. To overcome the at-will presumption, an employee must show — through the written terms of an offer letter, contract, or handbook — that the parties clearly and specifically agreed to restrict termination to defined circumstances. Poorly drafted offer letters, employee handbooks with progressive-discipline language, and verbal assurances can all supply that evidence.

The Five Texas Statutory Exceptions

Texas at-will employment doesn't disappear — it coexists with a set of statutory and common-law carve-outs that create real exposure when founders ignore them. Each exception has its own trigger, its own causation standard, and its own remedies. Getting one of these wrong is not a technicality; it's a jury question.

Sabine Pilot: Refusing to Commit a Crime

The Sabine Pilot doctrine — drawn from Sabine Pilot Service, Inc. v. Hauck, 687 S.W.2d 733 (Tex. 1985) — carves out a narrow public-policy exception: an employee cannot be terminated if the sole reason for termination was the employee's refusal to perform an illegal act that would subject the employee to criminal liability. The word "sole" is doing the heavy lifting. The plaintiff must prove that no other reason drove the discharge — the moment the employer can point to a mixed motive, the claim collapses. A founder who fires an employee partly because of poor performance and partly because the employee refused to falsify a report will likely defeat the claim. That said, "partly" is a fact question, and juries decide it.

Workers' Compensation Retaliation (Tex. Lab. Code §451.001)

If you terminate — or in any way discriminate against — an employee because they filed a workers' compensation claim, hired a lawyer for one, testified in a workers' comp proceeding, or even took steps to initiate such a claim, you've violated Texas Labor Code §451.001. The causation standard here is "but for" — the employee must show that the termination would not have occurred when it did but for the claim. That is a lower bar than Sabine Pilot's sole-cause requirement. Remedies include reinstatement, lost wages, mental anguish damages, and punitive damages. For a startup, punitive exposure on a retaliation claim can dwarf any savings from the termination itself.

The practical trigger for founders: an injured employee mentions they may file a claim on Monday, and you move to terminate by Friday. The timing alone generates a causation inference. Wage and hour concerns, documented performance issues, or a legitimate restructuring can all rebut that inference — but only if the documentation existed before the claim appeared.

Jury Duty (Tex. Civ. Prac. & Rem. Code §122.001)

Texas law prohibits discharging, threatening, intimidating, or coercing any permanent employee because they serve as a juror. Remedies under Tex. Civ. Prac. & Rem. Code §122.003 include lost wages and compensation of not less than one year and not more than five years. A startup that replaces an employee during a two-week trial and calls it a coincidence will have a difficult time convincing a jury — particularly one empaneled under the same statute. Note the "permanent employee" qualifier: classification of the worker matters before you act.

TCHRA Discrimination (Tex. Lab. Code §21.001 et seq.)

The Texas Commission on Human Rights Act mirrors Title VII and prohibits employment discrimination on the basis of race, color, sex, disability, religion, national origin, age (40 and older), and genetic information. It applies to employers with 15 or more employees for at least 20 calendar weeks in the current or preceding calendar year. Courts interpret TCHRA in parity with Title VII, which means federal precedent on burden-shifting, pretext, and mixed-motive analysis applies directly. Founders at the 10-to-15-employee threshold should know that the headcount calculation includes part-time workers. Crossing 15 employees mid-year does not delay coverage — the 20-week test looks at any point in the year.

If your company offers equity and employment terms to early employees and you hit that threshold without revisiting your HR infrastructure, a termination that looked clean under at-will doctrine may now sit squarely inside TCHRA's coverage window.

Military Leave (USERRA + Tex. Gov't Code §437.204)

The federal Uniformed Services Employment and Reemployment Rights Act (USERRA) prohibits adverse employment action where military service is a motivating factor — a standard that is intentionally broad. What USERRA does not fully cover is National Guard service under state orders. Texas fills that gap through Government Code §437.204, which provides the same basic protections for members of the state military forces ordered to authorized training or duty by state authority: an employer may not terminate such an employee because of that service. Founders with remote or distributed teams should assume the combined federal-state framework applies. The gap between "USERRA doesn't cover this" and "no law covers this" closed in Texas long ago.

Federal Exceptions That Apply in Texas

Texas at-will employment exists within a larger federal framework that most startup founders dramatically underestimate. State law sets the baseline; federal statutes carve out mandatory exceptions that apply regardless of what Texas law says, what your offer letters say, or whether you have five employees or five hundred. Three federal regimes deserve particular attention because their reach is wider than founders typically assume.

The NLRA — No Headcount Floor

The National Labor Relations Act is the federal exception that surprises Texas founders most. Unlike Title VII or the ADA, the NLRA has no employee-count threshold. The NLRB's jurisdictional reach covers the great majority of private-sector employers — including non-union businesses, startups, and businesses in right-to-work states like Texas — based on interstate commerce activity, not headcount. For tech and service companies — the category nearly all startups fall into — NLRB jurisdiction attaches at just $50,000 in indirect interstate commerce activity. A startup clearing $500,000 in total revenue is covered under any standard the NLRB applies.

What the NLRA protects is equally misunderstood. Section 7 shields "protected concerted activity" — which does not require a union or an organizing campaign. When two or more employees discuss wages, complain about working conditions in a Slack channel, or collectively push back on a policy, that is protected activity. A single employee acting on behalf of coworkers or attempting to initiate group action can also be protected. Firing an employee for telling a colleague what they earn, or for posting workplace grievances where coworkers can see them, is an unfair labor practice regardless of whether a union is anywhere in the picture.

FMLA — Two Theories of Liability, Not One

The Family and Medical Leave Act applies once you reach 50 employees in 20 or more workweeks during the current or prior calendar year. Individual eligibility requires 12 months of employment and at least 1,250 hours of service in the 12 months before leave begins, at a location where the employer has 50 or more employees within a 75-mile radius. Founders who hit the 50-employee mark and don't immediately update their leave policies are already exposed.

The more operationally dangerous aspect of FMLA is that it creates two distinct causes of action. Under 29 U.S.C. §2615(a)(1), it is unlawful to interfere with, restrain, or deny any FMLA right — meaning a manager who discourages an employee from taking leave, or who conditions a promotion on not taking leave, has potentially violated federal law before any termination occurs. Under §2615(a)(2), terminating or otherwise discriminating against an employee for asserting FMLA rights is a separate violation. Founders often focus on the retaliation theory and miss that the interference theory can be triggered by pressure, scheduling practices, or informal statements made well before a termination decision.

Title VII, ADA, ADEA, and FLSA Anti-Retaliation

Title VII, the ADA, and the ADEA — already discussed in the context of Texas TCHRA parity — apply in Texas with the same force as federal law. Because the Texas Commission on Human Rights Act tracks these federal analogs, compliance with one framework largely satisfies the other, though procedural differences exist. The FLSA's anti-retaliation provision (29 U.S.C. §215) adds a separate layer: employees who complain about wage and hour violations, or who cooperate with a Department of Labor investigation, are protected from adverse employment action regardless of the at-will rule. For reference on coverage: Title VII and the ADA apply at 15 or more employees; the ADEA (age discrimination) applies at 20 or more.

What an Employment Agreement Does to At-Will Status

Texas starts every employment relationship as at-will — but founders modify that default constantly, often without realizing it. A contract that restricts termination to "for cause" only changes the legal standard the employer must meet before letting someone go. That language doesn't have to appear in a formal employment agreement to be enforceable; an offer letter with the same words carries the same legal weight. If your last five offer letters included "for cause" termination language, you may have already signed away at-will status for those employees.

Not all written language rises to that level, though. Texas courts require clear mutual intent to alter the at-will default. Handbook provisions stating that the company "only terminates for cause" or manager comments like "you'll have a job here as long as you perform" generally won't overcome the presumption in litigation. The line is meaningful: vague handbook language, informal assurances, and aspirational policy statements fail. An explicit, signed written agreement with defined cause standards does not. Founders who use offer letter templates that mix these registers — formal headers, informal promises — are in the most exposed position.

Equity vesting creates a separate termination timing risk that deserves direct attention. Some courts have found that terminating an employee immediately before a vesting cliff, specifically to prevent shares from vesting, frustrates the employee's right to benefits earned through past service. The high-profile California example is Shah v. Skillz, which produced an $11.5 million verdict on that theory — but Texas does not generally recognize the implied covenant of good faith and fair dealing in employment contracts, so that specific theory has limited traction in Texas courts. The stronger argument in a Texas proceeding would be breach of the explicit cause definition in the agreement itself, not the implied covenant. Texas employees may also plead breach of contract or promissory estoppel — arguing the equity grant agreement or offer letter created an enforceable promise to allow cliff vesting — which can survive even without a California-style implied covenant theory. Founders should be careful about timing: a termination that coincides suspiciously with a vesting date invites litigation regardless of which theory ultimately wins.

The Termination Documentation That Limits Exposure

At-will status gives you the legal right to terminate without cause — but it does not insulate you from a discrimination or retaliation claim that arises from that termination. The distinction matters because those claims are litigated on the record you built before the termination, not on the at-will doctrine itself. Progressive discipline, performance improvement plans, and written warnings serve a legal function that goes beyond HR formality: they create a consistent, documented history that shows the termination was based on performance, not a protected characteristic.

Inconsistent discipline is one of the most reliable ways to convert a clean termination into a viable lawsuit. If a founder disciplines or terminates an employee in a protected class for conduct that a similarly-situated employee outside that class was allowed to commit without consequence, courts and juries treat the inconsistency as evidence of discriminatory motive. Startups with informal cultures are particularly vulnerable here — unwritten norms applied differently across a small team generate exactly the comparator evidence plaintiff's counsel needs. The fix is simple in principle: document the standard, apply it uniformly, and record every deviation.

The separation agreement is a second documentation layer with its own legal requirements. The threshold question is whether the termination is being characterized as for cause or without cause — that distinction controls more than the narrative. A for-cause termination may trigger forfeiture of unvested equity under the company's option plan, affects the employee's unemployment insurance eligibility with the Texas Workforce Commission, and can complicate COBRA continuation coverage. Without-cause terminations generally preserve those entitlements. Whatever characterization is accurate, it should appear consistently in the separation agreement, any internal records, and any communications with equity plan administrators.

For employees who are 40 or older, the Older Workers Benefit Protection Act (OWBPA) imposes specific validity requirements on any waiver of federal age discrimination claims. A noncompliant waiver is unenforceable — meaning the company releases the employee from claims, but the employee retains the right to sue under the Age Discrimination in Employment Act anyway.

One threshold that trips up founders planning larger workforce reductions: the federal WARN Act (29 U.S.C. § 2101) requires 60 days advance written notice before a plant closing or mass layoff, but it only applies to employers with 100 or more employees conducting layoffs of 50 or more workers. Texas has no state mini-WARN Act of its own, so for most startups running individual terminations or small-scale reductions, the WARN Act will not be triggered. The relevant threshold to track is headcount — once you approach 100 employees, WARN Act compliance should be in the planning checklist for any sizable reduction.

Actionable next steps for Texas founders:

• Before any termination, pull the employee's file and confirm you have documented performance or conduct issues with dates, specifics, and whether prior warnings were issued.
• Review how you disciplined other employees in comparable situations — if the record shows inconsistency, consult employment counsel before proceeding.
• Decide whether the termination is for cause or without cause and ensure that characterization is consistent across the separation agreement, equity plan records, and any internal communications.
• For any employee 40 or older receiving a separation agreement with a release of claims, run through the OWBPA checklist: ADEA reference, plain language, attorney advisement, 21-day (or 45-day) consideration period, 7-day revocation window.
• Track your headcount — if you are conducting a reduction in force approaching 50 employees at a single location, evaluate federal WARN Act obligations before issuing notices.
• Have a Texas employment attorney review your separation agreement template at least once a year; statutory requirements and case law on waiver enforceability shift, and a defective template compounds risk across every termination that uses it.