By Andy Stein, Founder & President, The Worksite Group
You closed the ICHRA deal. Medical is set. Your client has a predictable defined contribution, the renewal math works, and the relationship feels solid.
Then HR calls. What about dental? What about vision? Where do employees enroll for life insurance?
This is the moment most ICHRA implementations get complicated — not because the strategy was wrong, but because ICHRA was never designed to manage the full benefits package. It handles medical, but everything else still needs a home.
After working through more than 250 ICHRA administration projects for employers across a wide range of industries and sizes, this is one of the most consistent friction points we see. Brokers who placed a clean, well-designed ICHRA implementation find themselves fielding HR complaints six months later. Not about the health plan, but about the ancillary benefits that got left without a real administrative solution.
The good news: it’s a solved problem. The key is knowing where the gap opens and what a complete setup actually looks like before your client ever sees an enrollment screen.
Why ICHRA Doesn’t Solve the Ancillary Benefits Problem
ICHRA is built for one thing: putting medical coverage on a defined contribution model. Dental, vision, life, disability, and voluntary benefits are outside its scope entirely. Employers moving to ICHRA usually need a separate platform, carrier connections, and an administrator to manage every non-medical benefit line. That gap is where implementations quietly break down.
Most brokers understand this in theory. The problem is that in the push to implement ICHRA correctly, getting the class structure right, hitting the implementation timeline, setting up the marketplace, the ancillary question gets deferred. It becomes something to sort out after the medical piece is live.
By the time HR’s managing two separate systems, employees are getting enrollment reminders from two different portals, and dental deductions aren’t matching payroll records, the deferred problem has become an active one.
|
What Breaks When Ancillary Benefits Are on a Separate Platform
When the ICHRA platform handles medical and a separate platform handles everything else, the failure points are predictable. They’re not dramatic at first. They build.
- Employees face two enrollment experiences. Medical is streamlined, and everything else is a headache. Different logins, different deadlines, different support contacts. Many disengage from the second one entirely. Voluntary benefits enrollment is the first casualty.
- HR manages two vendor timelines during open enrollment. Double the configuration, double the troubleshooting, double the escalations when something doesn’t sync correctly.
- Carrier data goes out of sync. A life event change in the ICHRA portal doesn’t automatically update the dental or vision carrier. Someone on the HR side ends up owning that reconciliation manually.
- New hire onboarding breaks. The ICHRA effective date and the ancillary enrollment window are set up separately, with different deadlines. New employees get their health coverage sorted and miss their dental window because the timelines never matched.
- Year-round support fragments. Employees calling about a vision claim in March reach a different contact than the one who helped them with their health plan in October. Nothing’s connected because the administration isn’t connected.
None of this is a catastrophic failure. It’s the slow erosion of the client relationship — HR spending time on administration instead of people, employees confused about benefits they can’t fully use, and the broker who designed the solution getting blamed for a system problem.
The Employee Experience Problem That Shows Up at Renewal
Benefits professionals spend most of their time on plan design and cost modeling. Less time gets spent on what the employee actually experiences when they try to use what was built. That gap tends to surface at renewal, when satisfaction numbers are lower than expected and HR is asking why voluntary benefits enrollment hasn’t moved.
The MetLife Employee Benefit Trends Study found that 74 percent of employees say it matters to them that their benefits feel connected. Only 64 percent say that’s actually the case at their employer. That 10-point gap is an administration problem, not a plan design problem.
| What a connected ancillary benefits experience looks like | What fragmented administration actually delivers |
| One enrollment experience for every benefit line | Separate portals with different logins and timelines |
| One support contact who knows the full benefits picture | Different contacts per benefit line, none with the full picture |
| Life event changes that update all carriers automatically | Manual reconciliation every time something changes mid-year |
| New hire onboarding on one synchronized timeline | ICHRA and ancillary on separate clocks — gaps are common |
What a Solved Ancillary Benefits Setup Actually Looks Like
The cleanest ICHRA implementations we’ve seen run through a platform that can host medical and ancillary lines of coverage in the same system. One enrollment experience for the employee. One system for HR to manage. One set of carrier connections feeding real-time eligibility data. One support contact for the broker.
The SYNC Service is how that integration works in practice. It connects the ICHRA medical enrollment and the ancillary benefits enrollment so they run on the same timeline — same open enrollment window, same new hire onboarding trigger, same year-round support infrastructure. Benefits administration outsourcing done this way isn’t a workaround. It’s how the full package was meant to operate.
The practical difference shows up in the moments that matter:
- A new hire completes ICHRA enrollment and their dental, vision, and voluntary benefits in a single session, not two separate ones with a gap in between.
- An open enrollment runs as one coordinated process with one vendor timeline. HR isn’t managing two configuration deadlines with two different platforms.
- A life event in March updates eligibility across all carriers from one change. Nobody owns a manual reconciliation spreadsheet.
- An employee calls about a vision claim in July and reaches support that has their full benefits picture, not just their medical enrollment.
Questions to Ask Before You Recommend an Ancillary Administration Solution
Not every benefits administration platform handles the full package. Some specialize in ICHRA and hand ancillary off to a separate system — which recreates the problem you were trying to solve. Before recommending an outsourced benefits administration partner to a client, these are the questions worth asking directly:
Does the platform manage the full benefits package in a single system?
Ask specifically whether dental, vision, life, disability, and voluntary benefits enroll in the same platform as medical. If ancillary feeds into a separate portal or vendor, you’re looking at the two-system problem from a different angle.
How are carrier connections built and maintained?
Direct API or EDI carrier connections keep eligibility data synchronized in real time. Manual file transfers create lag, introduce errors, and require someone on the HR side to catch discrepancies that shouldn’t exist. Ask who builds those connections, who owns them when something breaks, and how long setup takes for a new carrier.
Is payroll integration bidirectional and tested?
A payroll integration that pushes deductions automatically isn’t the same as an export file HR uploads manually. Confirm how mid-year changes are handled, ie. when someone has a baby and adds a dependent, how does that deduction update, and who owns the reconciliation if it doesn’t?
How does new hire onboarding work across all benefit lines?
ICHRA effective dates and ancillary enrollment windows need to run on the same timeline. If new hire onboarding is configured separately for each platform, you’ll end up with gaps. Ask specifically how the timing is coordinated when an employee starts mid-month.
Does the administrator protect the AOR relationship?
Some benefits administration vendors create channel conflict by going direct to employers. It’s worth confirming explicitly before you make a recommendation. A broker-first administrator works behind the scenes and keeps the client relationship yours. That should be a non-negotiable criterion, not an afterthought.
When employees are navigating two systems, they often stop fully engaging with one. Voluntary benefits — the ones with the clearest ROI for employees — are exactly the ones that get skipped when enrollment is confusing. That shows up in utilization data at renewal, and it becomes a harder conversation than it needs to be.
|
The Ancillary Question Has Become Part of the ICHRA Pitch
A few years ago, brokers could place ICHRA and defer the ancillary conversation. Clients were new to the model, expectations were being set, and the medical piece was enough to demonstrate value.
That window has closed. Employers who’ve been on ICHRA for a year or two are comparing their experience to what they expected. The ones who are happiest have a unified benefits setup. The ones who are frustrated are managing two systems and wondering why their broker didn’t anticipate the problem.
Answering the ancillary question up front, as part of the ICHRA administration conversation, not after it, is now part of what separates brokers who retain ICHRA clients from brokers who place them and lose them at year two.
It’s also the natural place to demonstrate the kind of implementation depth that a tech-only ICHRA vendor can’t offer. Handing a client a marketplace link and a separate enrollment portal isn’t a solution. Building a complete setup where everything connects is.
|
Frequently Asked Questions
Can dental and vision benefits be enrolled on the same platform as ICHRA?
Sometimes yes, usually no. Most ICHRA software systems cannot host ancillary lines. A benefits administration platform like Employee Navigator or other solution can run ancillary enrollment alongside ICHRA on a single system, so employees complete all elections in one place. The SYNC Service specifically integrates the ICHRA medical enrollment and the ancillary enrollment so they operate on the same timeline and through the same support infrastructure.
How do brokers protect their AOR when recommending a benefits administration partner?
Look for a benefits administration outsourcing partner that works exclusively through the broker channel and has an explicit policy against going direct to employers. AOR protection should be standard, not something you have to negotiate. Confirm it in writing before recommending the platform to a client.
What benefit lines should be included in a complete ICHRA implementation?
A complete setup covers dental, vision, life, short- and long-term disability, accident insurance, identity theft protection, and any voluntary benefits the employer offers — all enrolled through the same platform as the ICHRA administration, on the same timeline, with the same employee support. If any of those lines are handled separately, that’s an administration gap worth closing before open enrollment.
When should the ancillary benefits conversation happen in an ICHRA implementation?
Before the ICHRA is placed, not after. The enrollment platform, carrier connections, and payroll integration for ancillary benefits take time to configure. Starting that conversation after medical is live means ancillary either launches late or gets rushed. Brokers who include it in the initial implementation plan avoid the two-system problem entirely.
Get the ICHRA Ancillary Checklist
If you’re in the middle of an ICHRA implementation, or about to start one, the ICHRA Ancillary Checklist covers every item that should be confirmed before your client sees an enrollment screen.
Twelve items across four areas: enrollment setup, employee experience, HR and administration workflow, and open enrollment coordination across all benefit lines. One page. Built for benefits consultants who need to move fast without leaving the ancillary question for someone else to discover.
Ready to talk through ICHRA opportunities for your book of business? Let’s connect.
— Andy Stein, Founder & President, The Worksite Group
