When a renewal arrives higher than expected, Washington employers often ask whether fully insured coverage is still the right way to fund their health plan. Fully insured plan alternatives can give an employer more visibility, flexibility, or control, but each approach changes the balance among claims risk, cash flow, administration, and the employee experience. The right answer depends on your workforce, claims history, budget goals, and appetite for responsibility, not on a single employee-count rule.
What are fully insured plan alternatives?
In a fully insured group health plan, the employer pays a carrier a set premium. The carrier pays covered claims under the policy, manages the provider network, and takes the direct claims risk during the plan year. The employer still faces renewal changes and must manage contributions, enrollment, compliance, and employee questions, but it does not generally pay claims as they occur.
Fully insured plan alternatives change one or more parts of that arrangement. An employer may accept more claims responsibility in exchange for additional claims information or potential financial upside. It may use a pooled structure to share risk with other employers. Or it may change the employer contribution model so employees choose individual coverage within an employer-defined allowance.
These approaches are not interchangeable. A level-funded plan is not simply a cheaper fully insured plan. A self-funded plan is not a fully insured plan with different paperwork. An HRA is a reimbursement and contribution structure, not automatically a replacement for every group medical plan. Comparing the funding model separately from the network and plan design helps leadership see what is actually changing.
How do the main funding paths compare?
The table below is a starting point for a Washington employer conversation. Actual terms vary by carrier, administrator, stop-loss contract, group profile, and plan design. A quote should be evaluated on the full structure, not on the label alone.
| Approach | Who carries claims risk? | Cash-flow pattern | What changes for the employer? |
|---|---|---|---|
| Fully insured | The carrier | Generally fixed monthly premium | More predictable budgeting and simpler claims risk, with less direct claims visibility and less control over the funding economics. |
| Level-funded | Shared or limited through a bundled structure and stop-loss | Usually a fixed monthly payment, subject to contract terms | More reporting and potential surplus participation, with additional underwriting and administration to review. |
| Self-funded with stop-loss | The employer for claims below the applicable attachment points; stop-loss protects against defined high claims | Claims cash flow can vary | More claims data and plan-design control, plus greater responsibility for funding, administration, contracts, and risk management. |
| Captive | The employer retains a defined layer while sharing selected risk through a captive pool | Structured contributions with pooled-risk considerations | Can combine self-funded economics with shared protection, but requires careful review of participation rules, governance, pool performance, and exit terms. |
| HRA-supported approach | Depends on the underlying arrangement and reimbursement design | Employer defines an allowance or contribution approach | Can support individual coverage or a broader benefits strategy, but requires distinct compliance, employee education, and administration decisions. |
The most important question is not which row sounds least expensive. It is which responsibilities your organization can manage consistently while preserving a useful benefit for employees.
When does a level-funded plan deserve a closer look?
Level-funded plans are often considered by employers that want a more structured alternative to traditional fully insured coverage without moving immediately to the most direct form of self-funding. The employer typically makes a predictable payment that combines several components, which may include expected claims, administration, and stop-loss protection. The details differ substantially among products, so the contract must be read carefully.
Potential advantages may include more regular claims reporting, a clearer view of plan performance, and a defined process for handling a favorable claims year. Potential trade-offs may include medical underwriting, participation requirements, exclusions or limitations in the risk protection, and a different renewal conversation if claims run higher than expected.
Washington employers should also compare the provider network and employee cost-sharing, not just the monthly funding number. A lower employer cost is not a successful change if employees lose access to important doctors or face a benefit structure they cannot understand. WHIA's existing level-funded versus fully insured comparison provides a deeper look at that focused decision.
What should employers know before considering self-funding?
Self-funding can give an employer more direct access to claims information and greater influence over plan design. The employer pays covered claims from plan assets or operating cash flow, usually with a third-party administrator handling claims operations and stop-loss coverage addressing defined high-cost exposures.
Stop-loss is important, but it does not make every self-funded plan equivalent to fully insured coverage. Specific and aggregate protections have attachment points, contract language, exclusions, renewal terms, and timing requirements. A decision also has to account for claims-payment timing, reserves, reporting, administrative capacity, fiduciary responsibilities, and the possibility that an adverse claims year affects cash flow.
For that reason, a Washington employer should not move to self-funding because a spreadsheet shows a favorable expected result in one year. Review multiple years of claims information where available, stress-test high-cost scenarios, and ask how the structure would operate if the group's claims experience changes. WHIA's guide to self-funding for small employers in Washington covers those mechanics in more detail. This article's purpose is to show where self-funding fits among the alternatives, not to replace that deeper analysis.
How can a captive change the risk conversation?
A health benefits captive is a pooled arrangement in which participating employers share a defined layer of risk under a structured program. Each employer still has its own plan and responsibilities, while the captive can provide another layer of risk sharing and reporting. The details are program-specific, and the presence of a captive does not remove the need to understand claims funding or stop-loss protection.
Captives may appeal to leadership teams that want more transparency and potential control than a traditional fully insured arrangement offers, but that do not want to carry every layer of claims volatility alone. The trade-off is added complexity. Employers should ask how the pool is governed, how contributions are calculated, what happens after a poor claims year, how members enter and exit, and whether the organization has the time and discipline to use the available data.
A captive also needs to fit the workforce. A group with limited claims history, changing participation, or little internal capacity may need a simpler structure. A group with a stable operating plan and leadership willing to review claims trends may be better positioned to evaluate pooled-risk options. There is no universal threshold that makes a captive right for every Washington employer.
Where does an HRA-supported approach fit?
An HRA-supported approach starts with a different question: instead of choosing one group medical plan for everyone, should the employer define a reimbursement allowance that supports eligible individual coverage? The answer depends on the HRA design, employee needs, affordability requirements, administration, and the employer's broader benefits strategy.
This distinction matters because an HRA is not just another name for a level-funded or self-funded plan. It can be part of a benefits strategy, but it changes how employees shop for coverage, how the employer communicates the benefit, and how ongoing administration works. Employees may value choice, while others may prefer the familiarity and guidance of a group plan. The employer must evaluate both sides of that experience.
Washington employers considering this route should model employee participation and education needs before treating an allowance as a simple cost-control switch. Review the reimbursement rules, documentation, notices, vendor capabilities, and support employees will receive. WHIA's HRA insurance plan guide can provide background on how HRA structures work.
Which alternative fits a Washington employer's goals?
Start with the decision criteria rather than a preferred product. A leadership team should be able to answer these questions before comparing proposals:
- How much claims risk can the organization absorb? Consider cash reserves, claims-payment timing, financial reporting, and how a high-cost year would affect operations.
- How much visibility is useful? Claims data can support better decisions, but only if someone has the time, skills, and authority to review it and act on the findings.
- What does predictable budgeting mean for this employer? A fixed premium, a fixed funding payment, a claims-based payment pattern, and an allowance each create different planning obligations.
- How much administration can HR and finance support? The employer may need to coordinate a third-party administrator, stop-loss carrier, captive program, reimbursement platform, or employee education.
- What must employees be able to keep? Review provider access, prescription coverage, specialist relationships, plan contributions, deductibles, and the clarity of the enrollment experience.
- What does Washington-specific fit require? Compare available networks, state requirements, group size, workforce locations, carrier participation, and the practical support employees receive during the transition.
Group size is relevant, but it is not a decision by itself. A Washington employer with 25 employees and favorable claims may have a different opportunity from a 25-employee group with unstable claims. A 150-employee organization may have more ways to structure risk, but it also has more employees, locations, provider relationships, and administrative expectations to protect.
Cost should be modeled instead of promised. WHIA may identify an opportunity for savings, including its approved 29% average savings figure where appropriate, but no savings figure is a guarantee for an individual employer. The analysis should show what assumptions drive the result, what happens if claims differ, and how the employee contribution and network would change.
How should you compare proposals before changing funding?
Ask each proposal to show the same categories in the same order. Separate the plan design from the funding structure so a lower premium does not hide a higher deductible, narrower network, or greater employee contribution. Then review:
- Funding mechanics: what is paid each month, what is paid when claims occur, and what protection applies?
- Risk terms: what are the specific and aggregate attachment points, exclusions, contract periods, and renewal conditions?
- Claims reporting: what data is available, when is it available, and who will help interpret it?
- Administration: who handles enrollment, claims questions, compliance support, eligibility changes, and employee advocacy?
- Employee impact: which providers, prescriptions, deductibles, copays, coinsurance, and contribution levels change?
- Exit and renewal: what happens if the arrangement no longer fits, and what information will the employer have before the next renewal?
A disciplined comparison can also keep renewal decisions grounded. WHIA's health plan retention guidance explains why employers should assess costs, claims, networks, contributions, and service together rather than reacting to the renewal rate alone. The same discipline applies when the employer is considering a new funding model.
What questions should Washington employers ask?
Is a level-funded plan the same as a fully insured plan?
No. Level-funded plans often use a fixed payment and may include claims funding and stop-loss components, but the contract, underwriting, reporting, and risk structure must be evaluated on its own terms.
Is self-funding appropriate for a small Washington employer?
It can be appropriate in some situations, but size alone does not decide the issue. Claims history, cash flow, stop-loss terms, administrative capacity, employee needs, and leadership risk tolerance all matter.
Does an HRA replace a group health plan?
Not automatically. An HRA-supported approach has its own design, compliance, communication, and administration requirements. It should be compared as a distinct benefits strategy rather than treated as another label for group plan funding.
Will an alternative funding model guarantee savings?
No. An alternative may create an opportunity, but results depend on the group's claims, plan design, network, contract terms, employee participation, and market conditions. Ask for assumptions and downside scenarios, not only the best-case illustration.
What is the first step for a Washington employer?
Gather the current renewal, plan summaries, employee contribution structure, claims information available to the employer, provider concerns, and service issues. Then compare alternatives against the goals the leadership team has agreed to protect.
Ready to compare your fully insured plan alternatives?
Changing funding is a significant benefits decision. The best next step is a clear, employer-specific conversation about what you are paying for, what risk you are prepared to take, and what employees need from the plan. Washington Health Insurance Agency (WHIA) helps Washington employers review those trade-offs with expert, unbiased guidance and practical support.
Book a conversation with WHIA about your health plan alternatives.