At-Will Employment Agreement: What the Termination Clause Can and Cannot Say

Saiba mais
Saiba mais
Saiba mais

Conteúdo da página

Maya S.
Paralegal

You've just hired your fifth employee this year. She signs the onboarding stack — offer letter, direct-deposit form, benefits enrollment, and a one-page at-will acknowledgment. Six months later, sales slip and you let her go. The next week, a demand letter lands on your desk. Her attorney's opening line: "Your employee handbook states that the company will follow a progressive discipline process before any termination." That single sentence, buried under "Vacation Accrual" on page fourteen, is now being used to argue that you breached an implied employment contract. Welcome to the at-will trap — and this guide is the way out.

The standard at-will employment relationship is the default rule in 49 of 50 U.S. states. It sounds simple: either party can end the relationship at any time, for any legal reason, or no reason at all. But "default" means it is easy to override, and employers override it constantly — through loose handbook language, casual oral promises, and termination clauses that inadvertently create the very job security they were meant to disclaim. This article walks through exactly what your termination clause must say, what it cannot say, and what happens in every exception state when you get it wrong. We will also help you draft language that has a real chance of holding up when challenged.

What "At-Will" Actually Means — and Why a Handshake Won't Save You

The at-will doctrine entered American employment law through a Tennessee Supreme Court case, Payne v. Western & Atlantic Railroad Co. (1884), which held that an employer "may dismiss their employees at will...for good cause, for no cause or even for cause morally wrong." Courts in other states gradually adopted the rule, and today it remains the default employment relationship in every U.S. state except Montana. The core concept is elegant: no fixed term, no promise of continued employment, no obligation to state a reason for termination. Both the employer and the employee are free to walk at any time.

What the doctrine does not mean, however, is "termination-proof." Four entirely separate bodies of law constrain at-will firing regardless of what your agreement says. Federal anti-discrimination statutes — Title VII of the Civil Rights Act of 1964, the Age Discrimination in Employment Act (ADEA), the Americans with Disabilities Act (ADA), and others — prohibit termination based on protected characteristics in every state. The National Labor Relations Act bars retaliation for union activity or concerted protected activity. The Fair Labor Standards Act (FLSA) prohibits firing an employee for complaining about wage violations. And state legislatures have piled on with their own protections for specific activities, ranging from medical marijuana use to off-duty tobacco smoking.

The at-will doctrine also has three common-law exceptions that courts have carved out over the past fifty years — implied contract, public policy, and implied covenant of good faith and fair dealing. These exceptions operate independently of anti-discrimination law and can be triggered by the wording of your own documents. The practical upshot: "at-will" is not a magic shield. It is a starting point that you can undermine — and many employers do — long before a termination decision is ever made.

Montana: The One State Where At-Will Ends After Probation

Montana is the lone outlier in U.S. employment law. Under the Montana Wrongful Discharge from Employment Act (WDEA), Mont. Code Ann. § 39-2-904, an employer must have "good cause" to terminate an employee once the probationary period ends. The default probationary period is six months, though employers may define a different period in a written personnel policy. During probation, Montana employees can be fired just like at-will employees everywhere else — for any legal reason or no reason. After probation, the rules change entirely.

"Good cause" under the Montana WDEA means a legitimate business reason — performance problems, misconduct, economic necessity — that is not a pretext. The statute also limits remedies: a successful claimant can recover lost wages and benefits for a maximum of four years, plus attorney fees, but no punitive damages unless actual fraud or malice is proven. Compared to the exposure in, say, a California wrongful termination lawsuit, Montana's damages cap is relatively contained. But the cause-requirement itself is a real constraint that catches employers off guard.

If you hire remote workers who are based in Montana, the WDEA applies to them regardless of where your company is incorporated or where your principal office sits. A choice-of-law clause in your employment agreement choosing, for example, Texas law does not override Montana's public policy statute. Before you use a create a one-size-fits-all termination clause for your remote workforce, check whether any employee is a Montana resident. If so, you need a state-specific addendum acknowledging the WDEA's requirements and defining the probationary period clearly.

Three Common-Law Exceptions to At-Will Employment

The Implied Contract Trap: How Handbooks Accidentally Create Job Security

The implied contract exception is the most common way small business employers accidentally surrender their at-will rights. In the landmark case Pine River State Bank v. Mettille, 333 N.W.2d 622 (Minn. 1983), the Minnesota Supreme Court held that provisions in an employee handbook can create an enforceable implied contract between the employer and employee, provided that the handbook language is definite and clear, the employee received the handbook, and the employee provided consideration (by continuing to work). Since that decision, roughly 36 states have adopted some form of the implied contract exception — meaning that if your handbook promises more than at-will employment, a court in those states may hold you to that promise.

The dangerous phrases are depressingly ordinary. Courts have found implied contracts in handbooks that said the company "will investigate all allegations before taking action," that "employees will receive a written warning before any termination," that "disciplinary procedures include counseling, a written plan, and a final warning," or that employees may only be terminated for "just cause." You do not need to use the words "employment contract" anywhere. The question a court asks is whether a reasonable employee in those circumstances would believe that the employer had made a promise about termination procedures and had intended to be bound by it. Many courts say yes, and then hold the employer liable for breach when it deviates from the promised process.

The fix is a handbook disclaimer — not buried in fine print, but placed prominently, ideally at the very beginning of the handbook. A strong disclaimer must state three things: (1) employment is at-will, (2) nothing in the handbook creates a contract, and (3) only a written agreement signed by a named officer of the company can modify at-will status. New Jersey, for example, requires a "clear and prominent" disclaimer after its Supreme Court's 1985 decision in Woolley v. Hoffmann-La Roche, and courts have interpreted "prominent" to mean bolded, separated from surrounding text, and located at the front of the document. The disclaimer should also appear in the at-will agreement itself.

Sample handbook disclaimer language:

"Nothing contained in this Handbook, or in any other Company policy, practice, guideline, or communication, constitutes or is intended to create a contract of employment for any specified term or to alter the at-will nature of employment. Employment with [Company Name] is at will, meaning that either the employee or the Company may terminate the employment relationship at any time, with or without cause, and with or without notice, in each party's sole discretion. Only a written employment agreement signed by the President of [Company Name] may modify this at-will relationship."

You should also pair the handbook with a template acknowledgment form that the employee signs and dates on the first day. The acknowledgment confirms receipt of the handbook and separately restates the at-will relationship in plain language. This creates two independent pieces of evidence that the employee understood and agreed to at-will employment — evidence that becomes important if the case ever goes to discovery. You can find a reliable employment contract template to use as the foundation for your written agreement and acknowledgment form.

The Public Policy Exception: When Firing Becomes Unlawful Regardless of Your Clause

The public policy exception is a different animal from the implied contract exception — it cannot be contracted around, disclaimed away, or cured with better handbook language. About 42 states recognize it, and it prohibits employers from terminating employees for reasons that violate a clear, established public policy of the state. The underlying logic is that allowing employers to punish employees for doing things the law encourages — jury duty, filing a workers' compensation claim, reporting safety violations — would make those legal rights meaningless in practice.

Public policy claims typically fall into four categories: (1) the employee was fired for refusing to commit an illegal act; (2) the employee was fired for reporting a legal violation (whistleblowing); (3) the employee was fired for exercising a statutory right; and (4) the employee was fired for performing a statutory duty. Each category draws on specific statutes — OSHA for safety reports, state workers' comp statutes for comp claims, the Fair Labor Standards Act for wage complaints, and so on. Courts are not sympathetic when employers pretend they didn't know the reason was protected — the public policy exception includes a rebuttable presumption that when a protected act precedes a termination by a short time, causation is plausible.

  • Serving on jury duty or as a witness in legal proceedings
  • Filing or assisting with a workers' compensation claim
  • Reporting safety violations to OSHA or a state equivalent
  • Reporting illegal conduct by the employer (whistleblowing)
  • Refusing to falsify records, engage in fraud, or violate a professional code of ethics

The states that do not recognize the public policy exception include Alabama, Florida, Georgia, Louisiana, Maine, Nebraska, New York, and Rhode Island — though even in those states, federal anti-retaliation statutes such as the Sarbanes-Oxley Act, Section 11(c) of the Toxic Substances Control Act, or the Consumer Financial Protection Bureau's whistleblower rules may still apply. In every other state, the safest practice is to document the business reason for a termination decision before announcing it, and to ensure no protected activity occurred in the 90 days preceding the decision that could be misconstrued as the real motive.

The Good Faith Covenant: States Where Bad-Faith Firing Gets Expensive

The implied covenant of good faith and fair dealing applies in roughly eleven states. In its strongest form — adopted by California in Foley v. Interactive Data Corp., 47 Cal.3d 654 (1988) — the covenant prevents employers from firing employees in bad faith or for motives that are dishonest or malicious, even if the technical at-will relationship is otherwise intact. The classic scenario is a long-tenured employee fired two weeks before a retirement benefit vests, or a commissioned salesperson fired the day before a large commission payment comes due, so the employer can pocket the money.

Courts in good-faith states do not require employers to have an objectively compelling reason for every termination — they simply look for evidence of malice or dishonesty in the employer's motivation. Kmart Corporation v. Ponsock, 732 P.2d 1364 (Nev. 1987) is an instructive case: the Nevada Supreme Court found that Kmart terminated a long-term employee specifically to avoid paying retirement benefits and held that this constituted a breach of the covenant. The plaintiff recovered as if the covenant were a tort — a result that can include compensatory and, in some jurisdictions, punitive damages.

If your company operates in California, Alaska, Arizona, Montana, Nevada, Wyoming, Idaho, Massachusetts, Delaware, Utah, or Connecticut, keep the timing of any termination decision under review. Firing an employee who is three weeks from vesting in a 401(k) match, a stock option tranche, or a deferred bonus creates significant litigation risk even if your at-will clause is letter-perfect. Document independent business reasons for the termination well in advance, and when in doubt, consult an employment attorney before acting. Start with a solid at-will employment agreement template as your baseline, then add state-specific provisions as needed.

Why You Still Need a Written At-Will Agreement Even Though It's the Default

Some employers skip the written at-will agreement because at-will employment is already the legal default. This is like skipping a smoke alarm because fires are rare. The default rule only gets you so far — once a lawsuit is filed, you need evidence, not theory. A written at-will agreement signed by the employee on the first day of employment creates three evidentiary advantages that the default rule alone cannot provide. First, it defeats the implied contract exception by establishing an express, written statement of at-will status that is inconsistent with any implied promise of job security. Second, it gives you a signed document to show a jury — "here is exactly what the employee agreed to" — rather than relying on the legal presumption. Third, it records the date, so any oral promise made after signing that conflicts with at-will status can be addressed: the modification clause in your agreement should require a signed writing to change anything.

Written at-will agreements also serve a communication function that experienced HR professionals appreciate: they set clear expectations. Employees who understand from day one that employment is at-will are less likely to be surprised by a termination and more likely to have made realistic plans. This is particulary true for employees who previously worked in Europe, Canada, or other jurisdictions where "at-will" has no equivalent and termination always requires cause and notice. A clear, readable at-will agreement reduces the shock that triggers lawsuits even when the termination itself was entirely legal.

If you don't already have a well-organized library of employment documents, the template catalog is a good place to standardize what you're using. You'll find agreements covering everything from offer letters to non-compete clauses — all of which should be consistent with and cross-reference the at-will status you establish in your core agreement.

Anatomy of an At-Will Termination Clause — five required components

The Core Termination Clause: Language That Actually Holds Up

Courts across the country have reviewed thousands of at-will termination clauses. The language that survives — consistently — shares several features: it names the at-will relationship explicitly, it uses both the "without cause" and "without notice" formulations, it expressly prevents modification by anything other than a signed writing, and it disclaims the effect of the employee handbook. The clause should stand alone in the agreement rather than being embedded in a paragraph about something else, and it should appear prominently — ideally both in the offer letter and as a separate acknowledgment form.

The "without cause" and "without notice" language matters because courts have split them. An agreement that says "employment may be terminated without cause" but is silent on notice can be read to require at least reasonable notice before termination. An agreement that says "employment may be terminated without notice" but is silent on cause can be read to require a legitimate reason. Using both phrases explicitly removes the ambiguity. The modification clause matters because without it, a supervisor's oral assurance that "you'll be here as long as you do your job" can — in some states — create an implied modification that overrides the written agreement.

Sample at-will termination clause:

"Employment under this Agreement is at will. Either party may terminate this Agreement and the employment relationship at any time, with or without cause, with or without advance notice, in each party's sole and absolute discretion. Nothing in this Agreement, in the Company's employee handbook, or in any other Company policy, oral statement, or course of conduct shall be construed to create a contract of employment for any specific term or to alter the at-will nature of the employment relationship. No modification of this at-will status shall be valid or enforceable unless set forth in a written instrument specifically identifying this Section and signed by an authorized officer of the Company and by the Employee."

Notice what the clause above does not include: it does not define "cause," does not list grounds for termination, does not promise a specific notice period, and does not reference any disciplinary procedure. Each of those additions would weaken the clause. The moment you define cause, you have created an implied obligation to follow that definition. The moment you promise 30 days' notice, you have created a contractual right that the employee can enforce even if your intent was merely to be polite. The cleaner and more absolute the clause, the harder it is to challenge.

Wording Courts Have Struck Down — and What to Write Instead

If you draft the termination clause yourself — or inherit one written by a manager who took a business law course in 1998 — certain phrases should trigger immediate concern. "Permanent employment" is the granddaddy of bad language: courts in multiple jurisdictions have held that describing someone as a "permanent employee" (as opposed to a "temporary" or "contract" employee) creates a reasonable expectation of continued employment. The word has appeared in job postings, offer letters, internal memos, and even job titles ("Permanent Marketing Manager"), and each instance can be evidence in an implied contract claim.

The phrase "termination for cause" without the qualifier "or without cause" is nearly as dangerous. If your agreement says the company "reserves the right to terminate for cause," a court can read that as limiting the company's right to cause situations only. The word "cause" doing all the work here: you've implied that without cause, you can't fire. Similarly, "the company will provide 30 days written notice before any termination" — even if intended as a courtesy policy — can become a contractual right. One California appellate court held that an employer's established practice of providing two weeks' severance to all departing employees created a legitimate expectation of that severance in a wrongfully terminated employee, though the employee handbook said nothing about it. Practice creates precedent.

Phrases suggesting a review or investigation process are equally risky. "We will conduct a fair and thorough investigation before making any termination decision" and "disciplinary decisions will follow a progressive discipline policy" have both been held to create implied procedures that the employer must actually follow. If you then fire someone without investigation or progressive discipline, you've breached the implied term — even if the underlying reason for termination was entirely valid. The irony is that employers who write these phrases intend to be fair; what they actually do is create legal obligations they then fail to fulfill in the heat of a termination decision.

Red-Flag Language vs. Safe Language in At-Will Termination Clauses

"For Cause" Definitions: The Clause That Accidentally Locks You Into Just-Cause Termination

A subtler version of the language problem arises when employers try to be helpful by defining what "cause" means. The goal is transparency: you want employees to know what behaviors will get them fired. The problem is the exclusive-list doctrine. When a contract (including an employment agreement) lists specific grounds for termination, courts may infer that the list is exclusive — that is, termination is only permitted for the listed reasons. If your at-will clause says "the company may terminate for cause, including but not limited to dishonesty, serious misconduct, or repeated policy violations," the phrase "including but not limited to" offers only partial protection.

Some courts treat "including but not limited to" as genuinely non-exhaustive, in which case the list is illustrative and not limiting. Others, particularly in implied contract states, look at the overall context and hold that a long, specific list signals an intention to identify the permissible grounds for termination. The more detailed and specific the list, the greater the risk. An employer who fires someone for poor performance — a plainly legitimate business reason — after an agreement that listed only "dishonesty," "theft," "harassment," and "insubordination" as grounds for termination may find itself defending a breach-of-contract claim.

The cleanest solution is to remove any cause definitions from the at-will termination clause entirely. If your company uses a separate progressive discipline policy — as many do — keep that policy entirely out of the employment agreement and include it only in the handbook, with a clear statement that the handbook is not a contract. For documents like a non-compete agreement that is signed alongside the employment agreement, include a cross-reference making clear that the at-will clause in the primary agreement governs the employment relationship, while the non-compete governs only post-employment restrictions. Mixing causes, conditions, and prohibitions across multiple related documents is a drafting minefield.

  • Never list termination grounds in the at-will clause itself — it converts a disclaimer into a promise
  • If a discipline policy exists, keep it in the handbook, not the agreement
  • Add "including but not limited to" if a list is unavoidable, but understand it provides only partial protection
  • Have an employment attorney review any clause where the word "cause" appears more than once

Severance Language in Termination Clauses: Helpful Tool or Binding Promise?

Many small business owners include severance language in their employment agreements because it feels fair and because they believe it will discourage lawsuits. Both instincts are reasonable. The problem arises when severance language is written as an unconditional promise rather than a conditional benefit. "Upon termination without cause, Employee shall receive a severance payment equal to [X] weeks of base salary" reads as a binding contractual obligation. You have now guaranteed severance in every non-cause termination, including the ones where the employee spent six months underperforming before you finally let them go.

The alternative — and the approach courts are most comfortable with — is discretionary severance language that preserves employer flexibility while signaling goodwill. Discretionary language avoids creating a right the employee can enforce independently of the rest of the agreement. It also avoids triggering ERISA's severance plan requirements, which kick in when severance is paid as part of an ongoing, ongoing plan rather than a case-by-case decision. If your company pays severance to five or more employees in a rolling 12-month period, even under "discretionary" policies, consult an ERISA attorney — you may have inadvertently created a welfare benefit plan with its own disclosure and claims-procedure requirements.

Sample discretionary severance language:

"The Company may, in its sole and absolute discretion, offer a severance payment upon termination of employment. Any such offer, if made, will be conditioned upon the Employee's execution and non-revocation of a written separation and general release agreement in a form acceptable to the Company. The Company is under no obligation to offer severance, and no prior offer of severance to any other employee shall create any entitlement on the part of this Employee to receive severance in any amount."

The release requirement in the severance clause is also worth emphasizing. A general release signed in exchange for severance can resolve ADEA claims (with a 21-day review period and 7-day revocation window under the Older Workers Benefit Protection Act), Title VII claims, state discrimination claims, and even implied contract claims. If your company offers any meaningful severance, conditioning it on a signed release is almost always worth it. Just make sure the release complies with the OWBPA requirements if the employee is 40 or older.

Final Paycheck Laws That Must Run Alongside Your Termination Clause

Your termination clause governs the contractual relationship, but state law governs when the final paycheck must be issued. These two bodies of law operate independently, and violating state final paycheck timing rules can result in waiting-time penalties that dwarf the underlying wage amount. California is the most aggressive: an employee who is involuntarily terminated must receive their final paycheck, including all accrued and unused vacation pay, at the time of termination. An employee who quits with at least 72 hours' notice must also receive payment at the time of resignation. California waiting-time penalties under Labor Code § 203 can equal up to 30 days of the employee's daily wages, plus attorneys' fees.

Other states have different timing rules, but virtually all of them are faster than the next regular payroll cycle. New York requires final payment no later than the next scheduled pay date. Texas requires final payment within six days of the discharge date. Oregon requires immediate payment upon involuntary termination. Massachusetts, like California, also includes accrued vacation in the final paycheck and requires payment on the date of termination. None of these rules can be altered by your employment agreement — they are mandatory state labor standards that override any contractual provision to the contrary.

  • California: final pay at time of termination; vacation pay included; 30-day penalty per day late
  • Texas: final pay within 6 days of discharge date
  • New York: final pay by next scheduled pay date
  • Massachusetts: final pay at time of termination including accrued vacation
  • Oregon: immediate final pay on involuntary termination

If your business operates across multiple states, build a simple state-by-state final paycheck matrix into your HR procedures and make sure your payroll administrator has access to it before every separation. For businesses that use independent contractors alongside employees, note that contractor final payment timing is governed by the contract terms, not state wage payment statutes — one more reason to keep a well-drafted independent contractor agreement with clear payment terms in every contractor engagement.

Remote Employees Across Multiple States: One Agreement Is Not Enough

Before 2020, the question of which state's employment law governed a remote worker was largely theoretical — most remote workers lived near the company's office. The explosion of fully remote hiring since then has turned multi-state employment law into a daily operational reality for small businesses. A single employment agreement, drafted under Delaware or Texas law, can leave you badly exposed when the employee works from California, New Jersey, or Illinois — all of which have employment laws significantly more protective than the national baseline.

Choice-of-law clauses in employment agreements are a useful starting point, but they do not override mandatory state statutes. California courts, in particular, have consistently held that California's Labor Code protections apply to employees who work in California, regardless of what the employment agreement says about choice of law. That means a California-based remote employee working for a New York company under a New York–law agreement is still entitled to California's final paycheck rules, California's meal and rest break requirements, California's non-compete prohibition (California Business and Professions Code § 16600 renders virtually all non-compete agreements void for California employees), and California's implied covenant of good faith and fair dealing. The agreement's choice-of-law clause simply does not change this.

The practical solution for small businesses with remote employees in multiple states is a base at-will employment agreement plus state-specific addenda. The base agreement covers the core terms — compensation, duties, at-will status, intellectual property assignment, confidentiality. Each addendum then modifies or supplements those terms to comply with the specific state's mandatory employment laws. For businesses with more than a handful of remote workers, a remote work policy that formally establishes the employee's work location, the governing state law for wage and hour purposes, and the process for reviewing and updating the addendum when an employee moves to a new state is well worth the investment to create.

The "Seperate Document" Problem: Why Your At-Will Clause Can Get Lost in the Stack

One underappreciated drafting risk is structural rather than linguistic: the at-will clause gets buried. A small business owner hands a new hire a fifteen-page offer letter, a separate NDA, a direct-deposit authorization, a benefits enrollment form, and maybe a non-compete. The new hire signs everything at once, often without reading any of it carefully, and the at-will clause is on page eleven of the offer letter in a font slightly smaller than everything else around it. Six months later, the employee argues they never meaningfully agreed to at-will employment because they didn't know the clause was there.

Courts have been receptive to this argument under the doctrine of reasonable notice — particularly for clauses that waive significant rights. The New Jersey Supreme Court, in Witkowski v. Thomas J. Lipton, Inc. (1993), evaluated whether employees received adequate notice of handbook provisions and found that notice is insufficient if the relevant language is buried in a long document without adequate signaling. The practical lesson: your at-will clause should appear as a seperate, one-page acknowledgment form that the employee signs independently, in addition to whatever at-will language appears in the body of the agreement. This creates a standalone piece of evidence — a document about which neither party can later claim confusion.

Consider bolding the at-will statement, using a slightly larger font for the heading, and placing it at the very top of the acknowledgment form rather than at the bottom where signature fatigue sets in. If your onboarding is electronic, use a workflow tool that requires a separate signature or initials on the at-will acknowledgment before the employee can proceed to the next form. These procedural steps cost nothing but create a record that is difficult to challenge in litigation.

At-Will Agreement Pre-Signing Checklist

Pre-Signing Checklist: Twelve Things to Verify Before Anyone Signs

Use the checklist below as a final quality review for every at-will employment agreement your business uses. If any item is missing or unclear, fix it before the agreement is signed — retrofitting employment documents after a dispute arises is expensive, and courts are skeptical of "clarifying amendments" made after the fact. A clean, comprehensive agreement signed on day one is worth ten carefully-worded explanations made under deposition pressure three years later.

  • The words "at will" appear explicitly in the termination clause — not just implied by context
  • Both "with or without cause" and "with or without notice" appear in the same clause
  • A modification lock clause requires a signed writing from a named officer to change at-will status
  • The handbook is disclaimed as a non-binding policy document in both the agreement and the handbook itself
  • No cause definitions, lists of terminable offenses, or progressive discipline commitments appear in the agreement
  • Severance, if mentioned, uses discretionary language conditioned on a release
  • State final paycheck timing obligations are noted in the HR procedure checklist, not the agreement
  • Remote workers in Montana or other exception states have state-specific addenda
  • Non-compete and NDA are signed as separate documents with their own headings and signature lines
  • The at-will acknowledgment form is signed independently, not buried in a multi-page document
  • For California-based employees, the non-compete is omitted entirely (Bus. & Prof. Code § 16600)
  • A final review by an employment attorney has been scheduled at least annually to catch statutory changes

No checklist substitutes for professional legal review, but these twelve points catch the most common and costly errors before they turn into litigation. Employment law changes frequently — California, New York, and Illinois in particular have enacted significant new employee protections in each of the last several years — so an agreement that was perfectly drafted in 2022 may need updating by 2025. Build the annual review into your business calendar the same way you build in your business license renewals and tax filing deadlines. For a solid foundation, start with a current at-will employment agreement template and customize from there rather than drafting from a blank page.

The at-will doctrine is one of the most powerful tools in U.S. employment law — giving businesses real flexibility to manage their workforce without the cumbersome just-cause requirements common in other countries. But that flexibility is conditional on your willingness to draft carefully, document consistently, and review periodically. Get the termination clause right, keep your handbook aligned, and train your managers to avoid casual oral promises about job security. Do those three things and the at-will doctrine will work the way it was designed to.

Article reviewed by: Maya S. (Attorney)

By continuing to use the site you agree to the use of cookies. Read more in the privacy policy.