At-Will Employment and the Exceptions That Actually Bite

Why this matters

Every owner has heard that they can let anyone go for any reason. It is broadly true and close to the least useful true thing in employment law, because nobody who brings a claim against you argues that you lacked the right to end the job. They argue about why you ended it, and at-will has nothing to say about that fight. The shops that get hurt are rarely the ones who fired someone unfairly. They are the ones who fired someone fairly, believed at-will covered it, and had spent four years quietly building a set of promises that took at-will off the table.

This card owns the doctrine and its exceptions for this library. None of it is legal advice about your own situation, and the state layer decides most of it, which is exactly why the doctrine is worth understanding before you need it.

The rule, and the only thing it defends

At-will employment means either side can end the relationship at any time, for any reason or for no reason, with no notice. It runs in both directions, which owners forget: the same doctrine that lets you release a tech on a Tuesday lets your best installer leave on a Wednesday without working a notice period. It is the default in every state except Montana, where it holds only through an initial probationary period and the section below owns the difference, and it is a default rather than a right, which means you can contract out of it and can also give it away by accident.

What at-will defends is the sufficiency of your reason. You do not have to prove the reason was good, fair, proportionate or even correct. You let a tech go because you did not like how he spoke to your wife at the Christmas party, and that is lawful. You let a dispatcher go on a hunch, and that is lawful too.

It defends nothing else. It does not defend a reason the law puts off limits, it does not defend a promise you made, and it does not defend you against the argument that the reason you gave is not the real one, which is what almost every claim is actually built on. Hold that distinction and the rest of this card follows from it.

The promises that convert the job without a decision being made

Nobody sits down and decides to give up at-will status. It goes in pieces, through ordinary shop behaviour.

A written promise of continued employment. An offer letter stating an annual salary can be read, in some states, as a promise of a year's work. The fix is one clause saying the figure describes the rate of pay rather than a term of employment, and that employment is at-will.

A spoken promise. "Stick with me through this winter and you have a job here as long as you want it" is the commonest way a small shop creates an implied contract, because it is said by the owner, in good faith, to keep someone who was about to leave. In states that recognise implied contracts from oral assurances, that sentence is evidence, and the person it was said to remembers it precisely.

A handbook that describes progressive discipline and then skips it. This is the big one. A handbook that says verbal warning, then written warning, then final warning, then termination has described a procedure. Where a state recognises an implied-contract exception, that sequence can become a term of the job. The exposure is not the handbook, it is the mismatch: having a procedure you then do not follow is worse than having none, because now the employee can point to your own document and say the shop broke its own rule. See related: Employee Handbook Essentials, Writing an Employee Handbook in Plain English.

A probationary period phrased as though something changes at the end of it. "Ninety days probationary, after which you become a permanent employee" invites the reading that permanent means something. Say instead that the introductory period is a review window and that employment is at-will before, during and after it.

The reasons a state will not let you use

Most states recognise a public-policy exception, built by their own courts rather than by Congress, and the categories are consistent enough to be worth knowing even where the scope is not. A firing generally cannot be for refusing to break the law, for reporting a violation to a regulator, for filing a workers compensation claim, for jury service, or for exercising a right a statute gives the employee.

Two of those hit a trade shop disproportionately. Refusing to break the law is the strongest version: a tech who will not sign off on work he says is not to code, or will not drive a vehicle he says is unsafe, sits inside the core of this exception, and a termination in the following weeks gets read against that refusal whatever else was going on. The workers compensation claim is the second, because the timing is usually terrible. An injured tech goes on restricted duty, is unproductive for two months, and the decision to let him go lands in the middle of an open claim. See related: Workers Comp Basics for Employer Reference.

Montana, the covenant, and why this is a state-by-state question

Two more exceptions exist and both are minority positions, which is itself the lesson.

A minority of states recognise an implied covenant of good faith and fair dealing in employment, and even there it is narrow rather than a general fairness requirement. The recurring fact pattern is a firing timed to take something already earned, usually a commission about to vest.

Montana is the one state that is not at-will after an initial period. Its Wrongful Discharge From Employment Act (Mont. Code Ann. 39-2-901 and following) makes a discharge actionable if it was not for good cause once the employee has completed a probationary period, the length of which the employer sets within the statute's limits. In Montana the default this card describes is not your default and you need the statute rather than this paragraph. Everywhere else, read Montana as proof that the question belongs to your state legislature and your state's courts rather than to a national rule you half-remember.

The two carve-outs every real claim is built on

Strictly these are not exceptions to at-will at all. They are separate statutory bans on particular reasons, sitting on top of the doctrine rather than inside it, and they are where nearly every claim a shop actually faces comes from.

The protected-characteristic reason. Federal coverage starts at a headcount: Title VII at fifteen employees for twenty or more calendar weeks in the current or preceding year (42 U.S.C. 2000e(b)), the ADA at the same fifteen (42 U.S.C. 12111(5)), the ADEA at twenty, for age forty and over (29 U.S.C. 630(b)). Two things about those numbers surprise owners. State fair-employment laws reach much smaller employers, in several states down to one, so being under fifteen buys less than it sounds like. And race discrimination can be brought under 42 U.S.C. 1981, which carries no employee threshold at all, so a three-person shop is not exempt from that one.

The protected-activity reason. Complaining about discrimination, filing a charge, taking part in someone else's investigation, raising a wage complaint (29 U.S.C. 215(a)(3) under the FLSA), or two employees discussing their pay with each other, which is protected concerted activity under Section 7 of the National Labor Relations Act (29 U.S.C. 157) at private employers whether or not anyone is in a union. A sibling card owns this one in full. See related: Retaliation, the Claim That Outlives the Original Complaint.

Why at-will loses to a pretext argument

The federal burden-shifting framework (McDonnell Douglas Corp. v. Green, 1973) runs in three moves. The employee shows enough to raise an inference. The employer states a legitimate, non-discriminatory reason, which is the easy move, because at-will means almost any honest business reason qualifies. Then the employee argues the stated reason is a cover for a banned one.

At-will wins you the second move and does nothing in the third. The third is not decided on evidence of what was in your head, because nobody has that. It is decided on inconsistency: a reason that changed between the meeting and the unemployment hearing, a rule enforced against one person and not another, a performance problem nobody wrote down until the week of the firing, a glowing review dated a month before. Every one of those is a record problem rather than a legal one, which is why the record card, not this one, is what changes your Monday. See related: Documenting Performance Before You Ever Need To.

A worked case: eleven late arrivals and a dismissed dispatcher

A shop with nineteen employees lets a dispatcher go for chronic lateness. The lateness is real: over fourteen weeks she arrived after her start time eleven times, and the owner can prove every one from the phone system's login stamps. He thinks this is the easiest firing he has ever done. Three facts make it the hardest.

The handbook describes four steps: verbal warning, written warning, final written warning, termination. She got the first and the last. Two of the four happened, the two in the middle did not, and the missing pair are precisely the steps that would have created a dated record of her being told this was serious.

A second dispatcher was late nine times in the same fourteen weeks and was never written up. Eleven against nine is a difference of two arrivals over fourteen weeks, roughly one extra late every seven weeks, and nobody reads that gap as the difference between keeping a job and losing one. The owner's honest answer is that he found the second dispatcher easier to work with. That is a lawful reason, and said out loud it also demonstrates that lateness was not the deciding factor.

Three weeks before the termination the dispatcher asked in a team meeting why the techs' drive time between jobs was not on their time cards. That is a wage complaint, and raising it in good faith is protected activity whether or not she was right about the drive time.

At-will is not in dispute anywhere in this case. Nobody argues the owner lacked authority to end the job. The argument is that lateness was available as a reason and was not the reason, and the shop's own documents make that argument for the other side: a procedure written down and not followed, a comparator treated differently and not papered, and a protected complaint three weeks upstream.

What would have changed the answer. Write the second dispatcher up for her nine lates on the same form and the comparator argument disappears, leaving an ordinary performance case. Run the four handbook steps and the record shows notice, a chance to correct, and a decision made against a standard rather than against a person. Move the termination to before the wage complaint rather than three weeks after it and the timing inference never forms. None of those three is legal work. All three are shop habits, and all three had to exist before anyone needed them.

Where this article stops

Two forks sit past the edge of anything you should act on from a page. The first is a firing where the person has recently done something protected, because that analysis is about timing and evidence rather than about the doctrine, and it is worth an hour of an employment lawyer's time before the meeting rather than a year of it after. Walk in with the personnel file, every dated write-up, the comparator's file, and the names of everyone who was in the room for the complaint. The second is Montana, and any state whose fair-employment statute reaches your headcount when the federal one does not, because there the default this card describes is not yours.

References

• Title VII of the Civil Rights Act of 1964, 42 U.S.C. 2000e(b) (fifteen-employee coverage threshold)
• Americans with Disabilities Act, 42 U.S.C. 12111(5); Age Discrimination in Employment Act, 29 U.S.C. 630(b); Civil Rights Act of 1866, 42 U.S.C. 1981
• National Labor Relations Act Section 7, 29 U.S.C. 157 (protected concerted activity at private employers)
• Montana Wrongful Discharge From Employment Act, Mont. Code Ann. 39-2-901 and following
• See related: Documenting Performance Before You Ever Need To, Firing an Employee Without Handing Them a Claim, Employee Handbook Essentials