Requirements and Law

Do You Have to Offer Health Insurance in Tennessee

A person in scrubs writes on a clipboard while a seated person holding a glass of water looks on, in a room with a sofa and daylight.

The honest answer has two halves, and only one of them resolves.

Whether Tennessee’s own law imposes a duty on a private employer to offer health insurance could not be affirmed either way. We went to the route the Department of Commerce and Insurance itself publishes for reading Tennessee insurance statutes, and what came back contained no statutory text at all. So this page does not tell you Tennessee requires an offer, and it does not tell you Tennessee requires none. Those are different claims from “we don’t know,” and only the third one is supported.

What does resolve is the federal overlay — and it resolves in a way that surprises most employers. The section everyone calls the employer mandate is not written as a mandate. 26 U.S.C. § 4980H(a) imposes an assessable payment when two separate conditions are both satisfied. It commands nothing.

What we looked for, where we looked, and what came back

The Department of Commerce and Insurance publishes a Rules and Laws page, and that page tells a reader in its own words: “To review Tennessee insurance statutes, use the Laws link and search under Tenn. Code Ann. Title 56, Insurance.”

We used the Laws link. It redirects to a commercial legal-research container. The response is HTTP 200, content-type text/html, and 3,702 bytes long. The body is a cookie test plus a browser-fingerprinting routine that assembles an identifier from screen and user-agent properties and then calls a redirect to the real container. Searching that document for “56-7” returns nothing. So does “Tenn. Code.” So does “Chapter,” so does “coverage,” so does “insurance.” There is no statutory text in the document at any point, and a reader without a subscription cannot get past it.

That is a specific finding, not a shrug. It is also not a claim that Tennessee’s law is unavailable in general — two other Tennessee primary sources are wide open, and this site relies on both. The Tennessee Secretary of State publishes the Official Compilation of Rules and Regulations as ordinary PDFs with real text layers, which is where the Insurance Division’s rate filing rules come from. The Secretary of State also publishes enacted public chapters as readable documents. It is the codified compilation — the consolidated, currently-in-force text of Tenn. Code Ann. Title 56 — that a plain reader cannot open.

We also declined to fill the gap with a third-party summary. Compilations of state insurance law carry their own vintage, and at least one widely used compilation is demonstrably behind Tennessee’s own recent enactments. Substituting one would have converted an honest gap into a confident sentence with worse provenance.

The federal section people call a mandate is not written as a command

Here is 26 U.S.C. § 4980H(a) in its own words:

If— (1) any applicable large employer fails to offer to its full-time employees (and their dependents) the opportunity to enroll in minimum essential coverage under an eligible employer-sponsored plan (as defined in section 5000A(f)(2)) for any month, and (2) at least one full-time employee of the applicable large employer has been certified to the employer under section 1411 of the Patient Protection and Affordable Care Act as having enrolled for such month in a qualified health plan with respect to which an applicable premium tax credit or cost-sharing reduction is allowed or paid with respect to the employee, then there is hereby imposed on the employer an assessable payment equal to the product of the applicable payment amount and the number of individuals employed by the employer as full-time employees during such month.

Read the grammar rather than the reputation. It is an if-and-then. The first limb is paragraph (1), the employer not offering. The second is paragraph (2), a separate fact about an employee — that someone has actually been certified as having enrolled in exchange coverage with a credit or a cost-sharing reduction attached. Both limbs have to be true in the same month before anything is imposed, and what is then imposed is a payment, not an obligation to have offered.

The practical consequence is that “you must offer coverage” is a paraphrase that loses the structure. An employer that is not an applicable large employer is outside the section entirely. An applicable large employer that offers nothing but has no employee so certified is inside the section and still triggers no payment.

The amount figures attached to that payment are deliberately not on this page. They were available and are withheld, because a dollar figure printed beside a conditional section reads as a price tag on a decision, and it is not a decision an amount clarifies.

The currency of the section is worth stating, since the topic attracts stale commentary: the amendment history in the 2024 edition of the U.S. Code ends with Pub. L. 118-168, § 4(a), December 23, 2024, which added a different subsection. Subsection (a) itself is untouched since the original enactments.

Which employers that section even reaches

Everything above turns on the term “applicable large employer,” and the statute and the regulation do not define it in identical words. The regulation is the one to read, and the divergence is the reason.

26 CFR § 54.4980H-1(a)(4) provides:

The term applicable large employer means, with respect to a calendar year, an employer that employed an average of at least 50 full-time employees (including full-time equivalent employees) on business days during the preceding calendar year. For rules relating to the determination of applicable large employer status, see § 54.4980H-2.

The statute, at 26 U.S.C. § 4980H(c)(2)(A), describes “an employer who employed an average of at least 50 full-time employees on business days during the preceding calendar year.” The parenthetical is absent there and present in the regulation — and that parenthetical is the part that changes who is actually inside the definition. An employer that reads only the statute will count itself out of a definition the regulation counts it into.

Note also what the test is made of: an average across the preceding calendar year, not a headcount on any particular day. A business that grows across a year and a business that is that size all year are not in the same position under it.

The seasonal-staffing exception that can change the count

Where an employer’s staffing swells and then recedes across a year, the counting rules carry an exception built for exactly that shape, and it is quotable in full.

26 CFR § 54.4980H-2(b)(2) provides:

If the sum of an employer’s full-time employees and FTEs exceeds 50 for 120 days or less during the preceding calendar year, and the employees in excess of 50 who were employed during that period of no more than 120 days are seasonal workers, the employer is not considered to employ more than 50 full-time employees (including FTEs) and the employer is not an applicable large employer for the current calendar year… For purposes of this paragraph (b)(2) only, four calendar months may be treated as the equivalent of 120 days. The four calendar months and the 120 days are not required to be consecutive.

The last sentence is the practical one, and it is the sentence most often missed. A seasonal pattern that runs in two separate stretches — a summer and a holiday peak, say — is not disqualified from the exception by being split. The exception turns on the total length of the period and on the excess workers being seasonal, not on the calendar being tidy.

Where Tennessee’s small-employer line comes from, and where it does not

A related question arrives with this one, because employers conflate the two: which market am I buying in? That is a different rule, and Tennessee has answered it explicitly.

Federal rule sets the definition and then expressly permits a state to raise the ceiling. 45 CFR § 144.103 provides, within its definition of small employer, that “A State may elect to define small employer by substituting ‘100 employees’ for ‘50 employees.’”

Tennessee was offered that election and declined it in writing. TDCI Bulletin No. 15-01, dated October 22, 2015 and issued in response to the Protecting Affordable Coverage for Employees Act, states: “The Department takes the position that it is in the best interest of Tennessee consumers and the insurance industry to adhere to the Federal definition of small employer and large employer, as cited above, and will not apply the State option.”

CMS records the same result from the other side. Its published state-by-state rating table carries a column for states that have notified CMS they are expanding the small-employer definition, with the footnote “State has notified CMS that it will expand the definition of small employer from 1-50 employees to 1-100 employees.” The states enumerated in that column are California, Colorado, New York and Vermont. Tennessee is not among them, and the table’s own legend resolves a blank cell as the federal default applying.

Two independent sources, one state and one federal, pointing the same way. That is as solid as this kind of finding gets.

A rule that says one thing in its heading and another in its scope

There is a trap in Tennessee’s own rules here, and it is the reason to read whole sections rather than headings.

One of the rules in the health filing chapter still carries a 2012-vintage description of the small group market worded around a wider employee band than the market definition above. Read on its own, that wording looks like Tennessee defining its market more broadly than Bulletin 15-01 says it does. It is not. The rule scopes that wording expressly — “For the purposes of this Rule” — to the medical loss ratio calculation. It is an accounting boundary inside one rule, not the definition of who buys in the small group market.

This is worth internalizing beyond this one instance. A heading is not a scope, and a definition inside a rule can be narrowed by the rule to that rule alone. Tennessee’s filing chapter does exactly that. If a sentence about Tennessee’s market definition is sourced to a rule rather than to Bulletin 15-01 or to CMS, check which paragraph it came out of.

Tennessee has not adopted the Medicaid expansion, and it does not move the duty

The record here is verified and narrow, and it is worth stating precisely because it is frequently stretched.

KFF’s state-by-state tracker records Tennessee as “Not Adopted,” and its own notes state that states’ decisions about adopting the Medicaid expansion are as of August 2026. The state-side corroboration is TennCare’s own page on major Medicaid eligibility categories in Tennessee, which enumerates children by age band, pregnant women, parents or caretaker relatives, institutionalized individuals and the Medicare cost-sharing programs, and contains no Affordable Care Act low-income adult expansion group. We also went to the federal primary source, medicaid.gov, which returned a bot-block response on three attempts including a full browser header set — we record that as a block on our request, not as a statement by the source.

What that status does not do is change anything about an employer’s duty. It is a rule about who is eligible for a state program, addressed to individuals. It neither creates an obligation to offer coverage nor removes one. The figures usually attached to that sentence — income thresholds, poverty-level percentages, coverage-gap estimates — are not in the verified record, so they are not on this page.

What to do with an answer that is honestly incomplete

Three things are actionable even with half the question unresolved.

First, treat the federal section as a test with two limbs rather than as a rule you either follow or break. Whether it reaches you at all is settled by the regulation’s definition, on a preceding-calendar-year average, with full-time equivalents folded in and the seasonal exception available where the staffing pattern fits.

Second, do not accept a confident statement about Tennessee statutory duty without asking where it was read. The codified compilation is behind a subscription wall. Anyone quoting the codified text of Tenn. Code Ann. Title 56 to you either has that subscription or is repeating a compilation — and at least one widely used compilation demonstrably lags Tennessee’s own enactments.

Third, remember that “must you offer” and “what happens if you do” are separate questions with separate law behind them. Coverage sold to a Tennessee small employer sits inside the federal market rules regardless of what the duty question turns out to be, and those rules are readable, current and much more likely to affect a decision you are actually making this year.

The bottom line

We cannot tell you Tennessee imposes a duty on a private employer to offer coverage, and we will not tell you it imposes none — the Department’s own Laws link resolves to a subscription container with no statutory text in it. What is readable is the federal overlay, and 26 U.S.C. § 4980H(a) is not written as a command at all: it imposes an assessable payment only when two separate conditions are both met.

Frequently asked questions

So does Tennessee law require a private employer to offer health insurance?

We could not affirm an answer in either direction, and saying so is the honest result rather than a dodge. The route we took is the one the Department of Commerce and Insurance publishes: its own “Laws” link, which the Department’s Rules and Laws page describes as the way to “review Tennessee insurance statutes.” That link redirects to a subscription legal-research container. What comes back to an ordinary reader is 3,702 bytes of browser-check and redirect JavaScript, with zero occurrences of “Tenn. Code,” “56-7,” “coverage” or “insurance” anywhere in the document. There is no statutory text in it at any point. We therefore do not write that Tennessee imposes a duty, and we do not write that it imposes none.

Doesn’t federal law require employers to offer coverage?

Not in the way the phrase “employer mandate” suggests. 26 U.S.C. § 4980H(a) is written as a conditional: “If— (1) any applicable large employer fails to offer to its full-time employees (and their dependents) the opportunity to enroll in minimum essential coverage… and (2) at least one full-time employee of the applicable large employer has been certified to the employer… as having enrolled for such month in a qualified health plan with respect to which an applicable premium tax credit or cost-sharing reduction is allowed or paid… then there is hereby imposed on the employer an assessable payment.” Both limbs have to be met. The section imposes a payment; it does not command an offer.

How does an employer know whether it is an applicable large employer?

The definition to read is the regulation rather than the statute, because the two are not worded identically. 26 CFR § 54.4980H-1(a)(4) provides: “The term applicable large employer means, with respect to a calendar year, an employer that employed an average of at least 50 full-time employees (including full-time equivalent employees) on business days during the preceding calendar year.” The statute at 26 U.S.C. § 4980H(c)(2)(A) describes “an employer who employed an average of at least 50 full-time employees on business days during the preceding calendar year” — with no parenthetical. That parenthetical is the part that changes who is actually covered, which is why the regulation is the one to cite.

Does Tennessee use a wider small-employer definition than the federal one?

No, and Tennessee said so in writing. Federal rule permits a state to raise the ceiling: 45 CFR § 144.103 provides that “A State may elect to define small employer by substituting ‘100 employees’ for ‘50 employees.’” Tennessee declined. TDCI Bulletin No. 15-01, dated October 22, 2015, states that “The Department takes the position that it is in the best interest of Tennessee consumers and the insurance industry to adhere to the Federal definition of small employer and large employer, as cited above, and will not apply the State option.” CMS’s published state-by-state table enumerates the states that notified it they were expanding the definition — California, Colorado, New York and Vermont — and Tennessee is not among them.

Tennessee has not adopted the Medicaid expansion. Does that create any obligation for my business?

No. The expansion status is a coverage-eligibility fact about individuals, not a rule addressed to employers, and nothing about it adds to or subtracts from what an employer must do. The status itself is verified: KFF’s state tracker records Tennessee as “Not Adopted,” with its own notes stating that state decisions are as of August 2026, and TennCare’s own page on major Medicaid eligibility categories in Tennessee enumerates children by age band, pregnant women, parents or caretaker relatives, institutionalized individuals and the Medicare cost-sharing programs — and contains no Affordable Care Act low-income adult expansion group. We attempted the federal primary source as well; medicaid.gov returned a bot-block response on three attempts, which we record as a block rather than as a finding.

About the author

Nate Jones, CPCU

Nate Jones, CPCU, is the founder of Wexford Insurance and Wexford Health Insurance, an independent agency placing small-business group benefits in 9 states. He works the employer-duty question the way it actually resolves in Tennessee — a federal section that is conditional rather than commanding, sitting over a state code that a plain reader cannot open. Start with the Wexford Health Insurance quote form.