How does Indiana termination law and at-will exceptions work in 2026?

What this means for a US-or-international company hiring its first Indiana employee:

• You do not need cause to end an at-will hire. A reorganisation, a strategic pivot, a culture-fit decision: all sufficient on the baseline before the narrow exception bites.
• The judicial exception is anchored to two specific fact patterns. One: termination for filing a workers’ compensation claim. Two: termination for refusing to commit an unlawful act the employer has asked the employee to perform. Both come from a pair of Indiana Supreme Court rulings in the 1970s and 1980s and have not expanded materially since.
• An Indiana handbook generally cannot create an enforceable implied contract that overrides at-will status. The state courts have consistently refused to read employment manuals as binding agreements unless the employer separately and clearly contracted otherwise. That gives Indiana employers more drafting freedom than employers in implied-contract states.
• The federal stack still applies. Title VII, the Americans with Disabilities Act, the Age Discrimination in Employment Act, USERRA, and the Family and Medical Leave Act all bite on Indiana terminations as much as anywhere else.
• The cash trap is the final-pay rule. Indiana requires the final cheque within 10 business days of separation or by the next regular payday, whichever is earlier. A bi-weekly mainland payroll cycle defaults to the wrong answer.

Indiana sits opposite to California on judicial willingness to expand at-will exceptions. The Supreme Court took the workers’ compensation retaliation exception in 1973, took the refusal-to-violate-criminal-law exception in 1988, and stopped. It has explicitly declined to follow other states that recognise implied contracts from handbooks, or that recognise the implied covenant of good faith and fair dealing as a tort theory in the employment context. The narrowness is genuine. The federal anti-discrimination stack and the wage-payment statute are where most Indiana termination disputes actually live.

What the single judicial exception actually says

The Frampton case held that an at-will employee fired for filing a workers’ compensation claim has a tort action against the employer. The court reasoned that allowing termination would defeat the legislative purpose of the workers’ compensation statute. The McClanahan case extended the same logic to a truck driver fired for refusing to drive an overweight load that would have violated state criminal motor-carrier rules.

Both cases share a tight structure. The protected conduct has to be anchored to a specific statutory right (filing a comp claim) or a specific criminal-law prohibition (refusing to violate it). Indiana courts have repeatedly refused to expand the public-policy exception to softer fact patterns: refusing to violate company policy, reporting internally to management, or generic appeals to public morality.

Why the no-implied-contract rule matters for handbook drafting

In an implied-contract state like Michigan or California, a handbook that lists discharge grounds, promises progressive discipline, or hints at termination only for cause without a clear at-will disclaimer can be read as a binding agreement. Indiana courts have rejected that reading. The handbook is a policy document, not a contract, unless the employer separately and explicitly contracts otherwise.

That gives Indiana employers wider drafting freedom than employers in implied-contract states. You can include a progressive-discipline framework without that framework becoming an enforceable promise. You can list discipline categories without that list becoming an exhaustive set of grounds. The Indiana Supreme Court has been consistent on this point since the 1990s.

The discipline trap is the opposite one. An employer that wants to bind an employee to a fixed term, a non-compete, or a specific severance trigger has to do so in a separately negotiated written agreement. Burying those terms in the handbook will not work. A line that says “employees who complete 12 months of service receive eight weeks’ severance on termination without cause’’ tucked into a benefits handbook generally cannot be enforced against the employer in Indiana without a separate signed contract.

Owen’s Indianapolis SaaS hire

Owen is a senior software engineer at an Indianapolis SaaS company, three years in, with two written warnings about missed delivery commitments on file. His manager dismisses him for performance. The company’s handbook contains a clear at-will disclaimer on the front page, lists a four-step progressive-discipline framework as guidance, and is silent on severance. Owen signed an acknowledgement at hire and again at the last handbook update.

In an implied-contract state, Owen’s lawyer would point to the four-step framework and argue the employer skipped step four. In Indiana, that argument loses. The handbook is policy, not contract. The at-will disclaimer is the controlling text. Owen’s only viable theory would be a federal anti-discrimination claim or the narrow Frampton public-policy exception, neither of which fits the performance record.

The final-pay calculation is where Owen’s case becomes interesting. The company’s normal payroll cycle runs on the 15th and the last day of the month. Owen is dismissed on the 5th. The next regular payday is the 15th, which is within 10 business days, so the company is on the cycle. Push the dismissal to the 17th and the 10-business-day clock requires payment around 1 December rather than 15 December. The mainland payroll team that does not flag Indiana separations cuts the 15 December cheque and breaks the statute on its own cycle.

The claim menu a fired Indiana at-will employee can bring:

The Indiana Civil Rights Law and the 300-day federal window

Because the ICRC has a work-sharing agreement with the EEOC, an Indiana plaintiff can file with either agency and the charge is automatically cross-filed. The federal Title VII clock stretches from 180 days to 300 days because Indiana is a deferral state. The ICRC’s own state-law charge window is 180 days, which is shorter than the federal 300 but does not block the federal claim if the state window has closed.

The contrast is Alabama and Mississippi, both 180-day non-deferral states. A worker who waits 250 days in Indiana still has a live Title VII claim. The same worker in Alabama lost the federal claim on day 181.

The Indiana six-employee state-law threshold

Indiana’s state Civil Rights Law generally reaches employers with six or more employees, which is lower than the federal 15-employee Title VII floor. A startup with eight Indiana employees that thinks it is below the federal radar is still in scope for the state statute. The protected categories track Title VII closely but with a longer age band (the state law reaches 40 to under 75) and an explicit military-service category.

The Indianapolis and Marion County overlay

Indianapolis layers a city human-rights ordinance on top, enforced by the Indianapolis Office of Equal Opportunity, that adds sexual orientation and gender identity as protected categories at the city level (those are now federally protected post-Bostock, but the city ordinance has independent enforcement). Other Indiana cities run similar ordinances. House Enrolled Act 1393 (2023) reorganised the relationship between state law and local employment ordinances, so the city overlay sits within a narrower band than it did before. Confirm the current state-versus-local position with employment counsel before relying on a local ordinance as the primary route.

The ICRC administrative process

An Indiana Civil Rights Law plaintiff typically files with the ICRC first, the agency investigates, and either issues a notice of determination or refers the matter to an administrative law judge. Either side can elect to proceed in state court after the determination issues. The ICRC can award back pay, reinstatement, compensatory damages, and attorney’s fees. The agency has no statutory cap that mirrors the federal Title VII damages cap, though awards in administrative proceedings tend to track the federal pattern.

The deadlines on one page

Maya’s Fort Wayne separation, in arithmetic

Maya runs operations for a Fort Wayne manufacturing site. Her base is $95,000 a year, paid bi-weekly on Fridays. The company restructures and the role is eliminated effective Monday 4 May. The termination meeting is at 10 a.m. that Monday. The next regular payday under the bi-weekly cycle would be Friday 15 May.

The Indiana statute reads strictly. Friday 15 May is 12 calendar days after the Monday termination, which on the business-day count is around 9 business days. That lands inside the 10-business-day window, so the company is on the cycle by a single day. Push the termination to Wednesday 6 May and the 15 May payday is 9 calendar days later but only 7 business days, still inside the window. Push it to the following Monday 11 May, and 15 May is 4 business days later: comfortably compliant.

The trap is the central HR team running a multi-state cycle two weeks out. If that team puts Maya on the next-but-one payday (29 May) by mistake, the Indiana statute is breached. The Wage and Hour Division calls for records, finds the unpaid wages, and the liquidated-damages multiplier kicks in. On the 11 days of pay missed, the multiplier turns a roughly $4,000 wage exposure into roughly $8,000 plus the employee’s legal fees.

What “wages due’’ actually includes in Indiana

Indiana reads wages narrowly relative to California. The final payment must cover:

• Regular hourly or salary pay through the last moment worked, including the termination meeting itself.
• Earned and unpaid vacation only if your written policy treats it as a vested wage. Indiana does not impose a statutory rule that all accrued PTO is wages. A clearly drafted use-it-or-lose-it policy or a forfeiture-on-separation clause is generally enforceable, provided it is set out in the handbook and the employee acknowledged it.
• Commissions and bonuses already earned under the plan documents. The plan terms control whether a bonus is earned at the time of termination or forfeited because the employee was not employed on the pay date. Indiana courts generally enforce plan-document forfeiture clauses where the language is clear.
• Earned but unpaid overtime under the federal weekly threshold. Indiana does not impose a daily overtime rule.

Why the cash mechanic matters

Other US states use simpler frameworks. Hawaii requires the cheque immediately at involuntary discharge. California requires it in the room at the termination meeting itself. Alabama and Florida default to the next regular payday with no specific outer cap. Indiana’s 10-business-day rule sits in the middle and is unusually short for a state with no statutory cap-and-trigger framework around it.

A central HR team running a multi-state payroll cycle two weeks out cannot rely on its normal cadence for an Indiana separation. It has to cut a manual cheque against the 10-business-day clock if the next regular payday falls outside that window. Teamed’s payroll engine flags Indiana separations at the point of decision and produces a cheque dated against the earlier of the two deadlines, alongside the wage statement that itemises any vacation pay-out and bonus calculation.

The handbook disclaimer

Indiana’s no-implied-contract rule does most of the work here, but the disclaimer still matters for two reasons. First, a clear at-will statement avoids confusion at the front line where managers, employees, and counsel read the handbook. Second, the disclaimer reinforces the at-will status if a separately negotiated agreement or oral assurance ever surfaces as a counter-claim.

Put a one-paragraph at-will disclaimer on the front page of the handbook, repeat it on the signature page, repeat it in the offer letter, and obtain a signed acknowledgement at hire and on every handbook update. The disclaimer should make clear that nothing in the handbook is an express or implied contract, that the employer reserves the right to modify any policy unilaterally, and that no manager other than a specified senior executive has authority to bind the company to a fixed-term agreement.

Contemporaneous performance documentation

Federal anti-discrimination law and the Indiana Civil Rights Law both turn on the question of pretext. Pretext is when a stated reason for termination is a cover for an unlawful motive: protected class, whistleblowing, leave request, workers’ compensation claim. The defence is contemporaneous documentation: performance reviews with dated entries, written warnings, performance improvement plans with signed acknowledgements, customer complaints, attendance records.

Documents created the day of the event carry far more weight in an Indiana jury and in an ICRC investigation than reconstructed narratives written after the right-to-sue letter arrives. The discipline is calendaring documentation at the point each issue is identified, not after the fact.

The termination letter

State the reason clearly and precisely. “Position eliminated as part of the May 2026 manufacturing-operations consolidation’’ works. “Continued failure to meet the documented delivery quota despite the 30-day performance improvement plan that ended on 14 April 2026’’ works.

Vague reasons (business needs, not the right fit) invite the plaintiff to fill in the blank with a protected-class motive. Indiana and federal courts both apply the McDonnell Douglas burden-shifting framework, and the test turns on whether the stated reason was the actual reason and whether the employer believed it at the time.

For terminations close in time to a workers’ compensation claim, the Frampton line of cases applies a stringent causation test. If the employee filed a comp claim in the prior six months and the stated reason is performance, the employer has to be able to point to a documented performance issue that pre-dates the comp claim. A reasonable Indiana employer treats any termination within six months of a comp claim as a high-risk file and brings counsel in early.

Same-day or 10-business-day final pay

The final pay must hit the earlier of the 10-business-day window or the next regular payday. The wage statement that accompanies it must itemise gross wages, hours worked, deductions, net wages, the pay-period dates, and a separate line for any vacation pay-out, bonus, or commission accrual. The Indiana Wage Payment Statute does not impose the same nine-item paystub rule California uses, but the Wage and Hour Division will look at the wage statement when adjudicating any wage claim. An incomplete statement that obscures the calculation invites a finding for the employee.

Independent grounds for protected-activity terminations

For terminations close in time to a workers’ compensation claim (Frampton), a refusal to perform an unlawful act (McClanahan), an ICRC charge, a wage-and-hour complaint, or an EEOC charge, Indiana courts apply a stringent causation test. If you have an independently sufficient ground for the termination, document it before the protected activity is on the table, and rely on it as the stated reason. That cuts off the retaliation theory at the root.

Maya’s Fort Wayne plant consolidation, in arithmetic

Maya runs operations at a Fort Wayne manufacturing site with 140 employees. The parent company decides to consolidate production to a Mexico facility, and the plan is to lay off 80 Fort Wayne staff effective 1 March 2027.

Federal WARN bites: the site clears the 100-employee threshold and the layoff exceeds 50 employees and meets the 33 percent test. Maya has to file a 60-day notice to affected employees, the Indiana Department of Workforce Development, and the chief elected local official (in Allen County, the County Commissioners). The notice has to land on or before 1 January 2027 for a 1 March layoff date.

That is the entire state-law obligation. Indiana has no chapter 394B equivalent (Hawaii) or CDLE Rapid Response statute (Colorado) that adds a parallel state notice clock or a state-funded dislocated-worker allowance. The Indiana Department of Workforce Development coordinates Rapid Response on-site briefings and unemployment-insurance pre-registration on a voluntary basis once the federal WARN notice lands, but there is no separate state-statute requirement for those services.

Federal WARN at a glance

Why federal-only is the Indiana story

Indiana ranks among the minority of US states without a state mini-WARN statute. Hawaii’s chapter 394B, Illinois’s Worker Adjustment and Retraining Notification Act, California’s WARN Act, and New York’s WARN Act all stack on top of the federal statute with shorter notice clocks, lower employee thresholds, or additional dislocated-worker allowances. Indiana does not. The state policy posture is closer to Florida, Alabama, and most of the South: federal WARN is the floor and there is no further state overlay.

For an employer running multi-state mass-layoff workflows, the simplification matters. The Indiana piece is the federal-WARN piece with no additional state-side calendar. The trap is the opposite assumption: an employer with a small Indiana satellite within a larger US footprint that automatically applies the Illinois WARN 75-day clock or the California WARN reduced-threshold rules to its Indiana site is over-noticing. There is no benefit and the early notice can complicate the federal WARN single-trigger calculation.

What shows up in case dockets and in client matters:

• Frampton workers’ comp retaliation tort. An employer terminates an employee within months of a workers’ compensation claim filing. The plaintiff frames the termination as retaliation under Frampton with punitive-damages exposure. The defence is documenting the independent business reason before the comp claim was on the table, with dated performance entries that pre-date the claim.
• Federal anti-discrimination claim through the ICRC and EEOC. An employee files a charge with the ICRC within 180 days or the EEOC within 300 days alleging a Title VII, ADA, or ADEA motive. The ICRC investigates, issues a determination, and either party can elect court. The Indiana Civil Rights Law tracks the federal protected classes closely, plus a longer age band and an explicit military-service category. The fix is calibrating the handbook, background-check policy, and discipline criteria to both the federal and state lists.
• Reid’s Bloomington research-analyst dismissal. Reid is a research analyst at a Bloomington life-sciences company. His supervisor asks him to misrepresent test data in a federal grant filing. Reid refuses. He is dismissed two weeks later for “poor culture fit.’’ Reid sues under the McClanahan branch of the public-policy exception, arguing he was fired for refusing to violate federal false-statement criminal law. The fact pattern fits squarely within McClanahan: a specific statutory criminal prohibition (the false-statements statute), an employer demand, an employee refusal, a termination, and a tight causation timeline. The employer’s defence has to point to an independently documented basis for the dismissal that pre-dates the data-misrepresentation request. Without that paper trail, the case settles or loses on summary judgment. The lesson: Indiana’s public-policy exception is narrow, but where it bites, it bites hard.
• Final-pay wage claim with the Indiana Department of Labor. A discharged employee’s final cheque arrives outside the 10-business-day window, omits an accrued vacation balance that the handbook treats as earned, or omits a commission that vested before termination. The employee files a complaint, the Wage and Hour Division calls for records, and the statutory liquidated-damages multiplier kicks in. The exposure on a single late cheque is small. Repeated across a team of ten Indiana separations in a year, the pattern becomes its own line item with mandatory attorney’s-fee shifting.
• Handbook-as-contract overreach. An employer drafts a handbook that includes a severance schedule (“employees who complete 12 months of service receive eight weeks’ severance on termination without cause’’), a non-compete reference, or a fixed-term promise. Indiana courts will generally refuse to enforce those terms against the employer unless separately negotiated as a contract. The reverse failure mode is the employer believing the handbook binds the employee to a non-compete or a severance trigger that has not been separately signed. The fix is moving any term that needs contractual force out of the handbook into a separate signed employment agreement.

The lesson, repeated in every Indiana employment-defence briefing: the at-will headline is genuine and strict, the handbook is policy not contract (which gives drafting freedom and removes accidental enforceability), the contemporaneous performance file is your federal-discrimination and Frampton defence, the 10-business-day cheque is your wage-claim defence, and federal WARN is the only mass-layoff layer.

What an Indiana termination through Teamed looks like operationally:

• Pre-termination review. Your named country specialist for the United States and an in-house US employment specialist run the file. We check the contemporaneous performance documentation, the handbook for the at-will disclaimer, the offer-letter at-will language, the protected-activity timeline (workers’ compensation claim, federal whistleblower disclosure, FMLA leave, EEOC or ICRC charge, USERRA), and the stated reason against the Title VII, ADA, ADEA, and Indiana Civil Rights Law lists plus the Frampton and McClanahan public-policy categories. A real US-licensed employment specialist as a named contact, not chatbot triage.
• Termination letter and 10-business-day final pay. We draft the letter with a specific, independent stated reason that meets the federal pretext-defence standard. Final pay is calculated against your written vacation and commission policy, dated against the earlier of the 10-business-day clock or the next regular payday, and accompanied by a compliant wage statement. Statutory employer cost (FICA, FUTA, Indiana SUI, Indiana state withholding, county withholding, workers’ comp accrual on the final period) passes through at cost, itemised on every invoice, with no markup. No setup fee, no exit fee, no hidden fees: every line is auditable.
• State and federal notices. If federal WARN is triggered, we file the 60-day notice to affected employees, the Indiana Department of Workforce Development as the state dislocated-worker unit, and the chief elected local official for the county where the site sits. Indiana has no state mini-WARN to layer on top, so the workflow is the federal piece in full, with voluntary Rapid Response coordination through DWD if you want the on-site briefings.
• Documentation handover. Every termination file is mirrored to your tenant in the Teamed platform: the letter, the performance documentation, the PIP timeline, the protected-activity audit, the final wage calculation against the 10-business-day clock, the wage statement, the vacation accrual at separation, and the receipt of payment timestamp from the meeting. If an ICRC complaint arrives on the 180-day clock, an EEOC charge on the 300-day clock, or a Frampton tort suit on the 2-year clock, the file is ready.

Pricing is one number per employee per month with no FX mark-up between the currency you pay us in and the US dollars Teamed remits in Indiana. The Indiana-specific work, the letter draft, the 10-business-day cheque calculation, the handbook audit, the federal WARN coordination with the Department of Workforce Development if a mass layoff is on the table, all sits inside the single fixed rate.

Behind the platform sits a named country specialist for the United States and an in-house US employment specialist who knows the Frampton retaliation framework, the McClanahan refusal-to-violate-law line, the Indiana no-implied-contract rule, the Indiana Civil Rights Law six-employee threshold, the 10-business-day final-pay clock, and the federal-WARN-only mass-layoff floor. Contractor onboarding, EOR payroll, and entity graduation live on one platform. An Indiana contractor who converts to W-2 keeps their record. That same employee can later graduate from EOR to your own Indiana-registered entity without changing system. Contractor through EOR to entity, one timeline, one platform.

When EOR is the right call (and when it isn’t)

EOR works while you are testing the Indiana market, running a small remote team, or sitting on one or two Indiana hires inside a wider US footprint. Indiana’s county-tax overlay, the WH-4 county-of-residence rule, and the 10-business-day final-pay clock all add per-state overhead that bites harder than in lighter-touch states.

Once you have six to eight Indiana employees and a predictable hiring run-rate, the maths of running your own Indiana-registered entity starts to win. Teamed’s EOR vs Entity Crossover Calculator shows you the month it flips, and we tell you when. The conversation is built into the relationship; the model graduates when it should.