A small employer health care alliance is not an insurance company and it is not a plan. It is a status that an existing nonprofit organization qualifies for under Ohio Revised Code Chapter 1731, once the superintendent of insurance grants it a certificate of authority to sponsor a program for its small-employer members.
The thing a first-time buyer gets wrong here is assuming an alliance is a kind of carrier, or a kind of policy.
The statute defines a status, not a company
Ohio Revised Code 1731.01(A)(1), Small employer health care alliance definitions, is where the definition lives, and it reads as a test rather than a label:
“As used in this chapter: (A) ‘Alliance’ or ‘small employer health care alliance’ means an existing or newly created organization that has been granted a certificate of authority by the superintendent of insurance under section 1731.021 of the Revised Code and that is either of the following: (1) A chamber of commerce, trade association, professional organization, or any other organization that has all of the following characteristics: (a) Is a nonprofit corporation or association; (b) Has members that include or are exclusively small employers; (c) Sponsors or is part of a program to assist such small employer members to obtain coverage for their employees under one or more health benefit plans; (d) Except as provided in division (A)(1)(e) of this section, is not directly or indirectly controlled, through voting membership, representation on its governing board, or otherwise, by any insurance company, person, firm, or corporation that sells insurance, any provider, or by persons who are officers, trustees, or directors of such enterprises, or by any combination of such enterprises or persons.”
Four things have to be true at once. The organization is certificated by the superintendent. It is a nonprofit. Its members include or are exclusively small employers. And it is not controlled by anyone who sells insurance or provides care.
That last one is the requirement most descriptions leave out, and it is the most useful of the four, because it answers whose side is this thing on. The chapter carries one narrow exception to it in the same division: division (A)(1)(e) reaches an organization “comprised of members who are either insurance agents or providers, that is controlled by the organization’s members or by the organization itself”
— a group offering coverage to its own people. That is a scope clause, not a loophole.
Why the chapter exists, in the legislature’s own words
Ohio Revised Code 1731.02(A), Encouraging alliances of small employers to obtain health benefit plans, declares in terms that rising health care costs have made it difficult for small employers to provide benefits, and that alliances of small employers bargaining with insurers better assure adequate coverage at affordable cost — the larger the covered group, the more certain the result. Division (B) then instructs that the chapter “shall be liberally construed and applied toward the achievement of the public objectives set forth in division (A) of this section.”
A quieter sentence changes how you should picture the whole thing. Division (C) provides that the chapter is “in addition to and not in derogation of other authority under law”
, and that an existing arrangement that fits the definitions and otherwise conforms “is entitled to all applicable benefits under this chapter.”
Ohio is not creating a new species of entity. It is defining a status that an organization already in existence — a trade association, a chamber — can qualify for.
How an organization is authorized
The certificate is the hinge, and it lives in a section easy to miss in the numbering. Ohio Revised Code 1731.021, Obtaining certificate of authority from superintendent of insurance, opens with a prohibition:
“No organization, on or after July 1, 1996, shall sponsor an alliance health care program without first obtaining a certificate of authority from the superintendent of insurance.”
Division (C) sets the clock on the decision, and also sets out what happens when the answer is no:
“The superintendent shall, within ninety days after receipt of an application filed pursuant to division (B) of this section, do either of the following: (1) Grant a certificate of authority to the applicant if the superintendent determines that the applicant is in compliance with this chapter and any rules adopted thereunder. (2) Deny the application for a certificate of authority if the superintendent determines that the applicant is not in compliance with this chapter or any rules adopted thereunder. A notice of the denial shall be mailed to the applicant within thirty days after the superintendent makes the determination. The notice shall specify the reasons for the denial and shall state that the applicant may request a hearing within thirty days after the date the notice was mailed.”
A certificate is not permanent, and it does not run for a year from whenever it was issued. Division (D) provides that a certificate granted under the section “shall remain in effect through the thirtieth day of June following the date it was granted”
, so the program renews on a fixed annual cycle rather than on each organization’s own anniversary, and Ohio Revised Code 1731.021(E) requires the superintendent to give notice of the need to file a renewal at least sixty days before expiry.
“Alliance” is a protected term in Ohio
This is the part a buyer can actually use:
“No insurer or organization shall use the term ‘alliance,’ ‘small employer health care alliance,’ ‘alliance program,’ ‘alliance health care program,’ or any other similar term with respect to a health benefit program unless the organization that sponsors the program has been granted a certificate of authority under this section.”
In Ohio the word is not marketing language. If a program is described to you as an alliance, the statute says a certificate stands behind that word, and the Department of Insurance maintains the roster of certificated alliances. That is a verification step you can take before signing.
What an alliance is not
Ohio Revised Code 1731.03(B), Small employer health care alliance powers, is unusually blunt about what the structure is not:
“A small employer health care alliance is not and shall not be regarded for any purpose of law as an insurer, an offeror or seller of any insurance, a partner of or joint venturer with any insurer, an agent of, or solicitor for an agent of, or representative of, an insurer or an offeror or seller of any insurance, an adjuster of claims, or a third-party administrator, and will not be liable under or by reason of any insurance coverage or other health benefit plan provided or not provided by any insurer.”
Division (C) extends the same idea to promotion: promoting an alliance program, whether by the alliance or by an insurer, “is not and shall not be regarded for any purpose of law as the offer, solicitation, or sale of insurance.”
What it does do is in division (A)(1): negotiate and enter into agreements with one or more insurers for those insurers to offer health benefit plans to its small-employer members. An alliance bargains and administers; an insurer carries the risk and is liable on the coverage.
What an alliance may not do to its own members
The chapter also polices the alliance from the inside. Ohio Revised Code 1731.03(D) reads:
“(D)(1) No alliance shall adopt, impose, or enforce medical underwriting rules or underwriting rules requiring a small employer to have more than a minimum number of employees for the purpose of determining whether an alliance member is eligible to purchase a policy, contract, or plan of health insurance or health benefits from any insurer in connection with the alliance health care program. (2) No alliance shall reject any applicant for membership in the alliance based on the health status of the applicant’s employees or their dependents or because the small employer does not have more than a minimum number of employees. (3) A violation of division (D)(1) or (2) of this section is deemed to be an unfair and deceptive act or practice in the business of insurance under sections 3901.19 to 3901.26 of the Revised Code.”
That prohibition is addressed to the alliance — to who it may admit, and on what basis. What an insurer may use when it rates the group is a different question, worked through in the post on what an insurer can use to rate your group in Ohio.
What the agreement between an alliance and an insurer has to cover
An alliance program is not a handshake. Ohio Revised Code 1731.04(A), Provisions of agreement between alliance and insurer, prescribes a statutory minimum content for the agreement, beginning:
“An agreement between an alliance and an insurer referred to in division (B) of section 1731.01 of the Revised Code shall contain at least the following: (1) A provision requiring the insurer to offer and sell to small employers served or to be served by an alliance one or more health benefit plan options for coverage of their eligible employees.”
The remaining subjects the agreement must address, stated as subjects and not as promises about what any Ohio employer receives, run to a description of the plan options offered, the requirements an employee must meet to be eligible, the rates or the method by which rates will be set, continuation of coverage, and — at division (A)(6) — a provision prescribing the minimum employer contribution toward premiums or other charges required before a small employer may obtain coverage under a plan option offered through the program. The agreement must set one; the statute does not say what it is.
Chapter 1731 defines “small employer” for itself, and says so
The alliance chapter carries its own employer-size definition, and it expressly overrides every other chapter’s. Ohio Revised Code 1731.01(J) provides:
“‘Small employer,’ regardless of its definition in any other chapter of the Revised Code, in this chapter means an employer that employs no more than five hundred full-time employees, at least a majority of whom are employed at locations within this state.”
For the purposes of this chapter only, Ohio Revised Code 1731.01(J) calls an employer of up to five hundred full-time employees a small employer. The scope clause is what makes that sentence true, and lifting it out of the chapter is how it becomes false.
The chapter then supplies the test that decides who counts toward that ceiling. A ceiling handed over without its counting rules is worse than no ceiling at all. Ohio Revised Code 1731.01(J)(1) provides, for the purpose of that size test:
“(a) Each entity that is controlled by, controls, or is under common control with, one or more other entities shall, together with such other entities, be considered to be a single employer. (b) ‘Full-time employee’ means a person who normally works at least twenty-five hours per week and at least forty weeks per year for the employer.”
And Ohio Revised Code 1731.01(J)(2) keeps an employer that grows from falling out of the chapter the moment it crosses the line:
“An employer that qualifies as a small employer for purposes of becoming an enrolled small employer continues to be treated as a small employer for purposes of this chapter until such time as it fails to meet the conditions described in division (J)(1) of this section for any period of thirty-six consecutive months after first becoming an enrolled small employer, unless earlier disqualified under the terms of the alliance program.”
None of this contradicts Ohio’s small-group market definition. Both are chapter-scoped definitions doing different jobs — one decides who may join an alliance, the other which market rules a plan sits under. If what you need is the market band, the separate post on how many employees you need for a group plan in Ohio quotes that definition in full.
Membership runs on one definition; the plan still sits under the other
Ohio wrote the reconciliation into the statute. Ohio Revised Code 1731.03(E), as served today, provides:
“Except as otherwise specified in section 1731.09 of the Revised Code, health benefit plans offered and sold to alliance members that are small employers as defined in section 3924.01 of the Revised Code are subject to sections 3924.01 to 3924.06 of the Revised Code.”
Joining an alliance does not move your plan out of the small-employer chapter. That cross-reference was narrowed in April 2025: the prior version, effective March 23, 2007, Small employer health care alliance powers, ran the same sentence to a higher upper bound before House Bill 238 of the 135th General Assembly changed it. The sentence still does the same job — it is the statute that says the two definitions are not in conflict.
What this does not answer
This describes an authorized structure, not a measured market. It does not tell you whether any particular Ohio alliance is currently certificated, what its program offers, or whether joining one would serve you better than going to the small-group market directly — that last answer depends on your payroll, your ownership structure and what is actually on the table. For the state-level picture, start at small business health insurance in Ohio; if this is your first plan, the process is laid out under setting up a first group health plan.
The bottom line
A small employer health care alliance is a status an existing nonprofit organization earns, not a company Ohio creates. The superintendent of insurance grants the certificate, the certificate is what makes the word “alliance” lawful to use, and the statute says in terms that an alliance is not an insurer and is not liable on the coverage. It bargains; somebody else carries the risk.
Frequently asked questions
Is a small employer health care alliance an insurance company?
No, and Ohio says so in terms. Ohio Revised Code 1731.03(B) provides that an alliance is not and shall not be regarded for any purpose of law as an insurer, an offeror or seller of any insurance, a partner of or joint venturer with any insurer, an agent of an insurer, an adjuster of claims or a third-party administrator, and that it will not be liable under or by reason of any insurance coverage provided or not provided by any insurer.
Who decides whether an organization can be an alliance in Ohio?
The superintendent of insurance. Ohio Revised Code 1731.021(A) provides that no organization shall sponsor an alliance health care program without first obtaining a certificate of authority from the superintendent, and division (C) requires the superintendent to grant or deny an application within ninety days of receiving it.
Can any group call itself an alliance in Ohio?
No. Ohio Revised Code 1731.021(G) makes the word a protected term. No insurer or organization may use “alliance,” “small employer health care alliance,” “alliance program,” “alliance health care program,” or any similar term for a health benefit program unless the sponsoring organization holds a certificate of authority under that section.
Can an alliance turn down a small employer because its employees are unhealthy?
Ohio Revised Code 1731.03(D)(2) provides that no alliance shall reject any applicant for membership based on the health status of the applicant’s employees or their dependents, or because the small employer does not have more than a minimum number of employees. Division (D)(3) makes a violation an unfair and deceptive act or practice in the business of insurance.
Does Chapter 1731 use the same small-employer definition as the rest of Ohio insurance law?
No, and it says so on its face. Ohio Revised Code 1731.01(J) defines “small employer” for that chapter regardless of how any other chapter of the Revised Code defines the term, and sets the chapter’s ceiling at an employer that employs no more than five hundred full-time employees, at least a majority of whom work at Ohio locations. That is the alliance chapter’s own scope, not the market definition.
Does joining an alliance change which rules my plan sits under?
Ohio Revised Code 1731.03(E) is the provision that answers this. It provides that, except as otherwise specified in section 1731.09, health benefit plans offered and sold to alliance members that are small employers as defined in section 3924.01 remain subject to the small-employer chapter. Membership runs on one definition; the plan sold to a member still sits under the other.
About the author
Nate Jones, CPCU, is the founder of Wexford Insurance and Wexford Health Insurance, an independent agency placing small-business group benefits in 9 states. Nate reads Ohio’s alliance chapter against what a first-time buyer is actually being offered, so the difference between a certificated purchasing structure and the insurance itself is clear before anyone signs. Start with the Wexford Health Insurance quote form.