Every year, benefits leaders make the same bet. They pick a new carrier, negotiate a better rate, and assume the transition will be smooth. Then January 1st hits. Employees call, frantic, because their prescriptions are rejected. Infusion appointments get canceled. HR spends weeks on the phone sorting out claim denials.
The common explanation is bad communication or poor plan design. But I've spent enough time inside these systems to know the truth. The problem isn't the plan. It's the switch itself. And nobody talks about it because it's invisible-happening inside servers and data feeds that never touch a human hand.
What Actually Happens When You Change Carriers
Here's a scenario you've probably never considered. Your HCM system-Workday, ADP, UKG, whatever you use-sends a file to the new carrier. That file contains employee names, dates of birth, and enrollment choices. It's called an 834 transaction, and it's the standard way carriers get their member lists.
But that file contains zero clinical history. Zero prior authorizations. Zero ongoing treatment records. Zero pharmacy claims history. Every employee arrives at the new carrier as a blank slate. A newborn, from a data perspective.
So when someone shows up for their weekly dialysis session on January 2nd, the new carrier's system says, "I've never seen this person before. No pre-approval on file. Denied."
The Four Invisible Failures
Through years of watching these transitions, I've identified four specific breakdowns that almost always happen. They're technical, but the impact is deeply human.
1. The Prior Authorization Blackout
Imagine an employee battling rheumatoid arthritis. They've had a prior authorization for a biologic infusion that was approved through March under the old plan. When the new carrier takes over, that authorization disappears. It's not in their system because no one sent it over.
The clinic submits a claim for the January infusion. Denied. The employee calls the carrier, who says, "That authorization was with your previous plan. You need to submit a new one." That process takes 5 to 14 business days. Meanwhile, the patient either goes without treatment or pays out of pocket.
This isn't malice. It's a data handshake failure between two systems that don't want to talk to each other.
2. The Pharmacy Washout
Specialty drugs are where this hurts most. Your PBM changes with the carrier. The old PBM immediately deactivates all member IDs. The new PBM has zero history on the employee's existing medications.
On January 1st, someone with diabetes walks into their pharmacy to refill a GLP-1 agonist. The system rejects it. Reason: "New member, no prior therapy documented." The pharmacist can't override it without a manual authorization. The employee is told to call the insurance company, waits on hold for 45 minutes, and gets told to "ask your doctor to send a continuity of care request."
That medication costs $1,200 per month. The employee goes without for a week. Their blood sugar spikes. This is not a plan design issue. It's an infrastructure failure.
3. The COBRA Continuity Trap
Here's a detail even seasoned HR leaders miss: COBRA participants do not move with the group. Former employees on COBRA must stay on the old plan. Active employees go to the new plan. This creates two separate enrollment streams flowing from the same HCM.
Your benefits administration platform-bswift, Ease, Benefitfocus-has to split the 834 file: one feed to the old carrier for COBRA, another to the new carrier for active employees. If one record misroutes, a COBRA participant accidentally gets enrolled in the new plan. That's a compliance violation because the COBRA qualifying event didn't include that plan. And if claims get paid under the wrong plan, untangling that takes months.
Most employers don't catch this until an audit or a COBRA participant calls about an ID card for a plan they never elected.
4. The File Date Paradox
Carriers load new members into their systems 10 to 30 days before the effective date. They need time to print ID cards and set up portals. But what happens when an employee has a baby on December 28th?
They update their dependent in the HCM on December 29th. That update gets bundled into the 834 file sent on December 30th. The new carrier loads the baby on December 31st. On January 1st, the employee tries to file a claim for the birth. The new carrier denies it because the date of birth is before the effective date. The old carrier denies it because the dependent was never loaded in their system.
The family is in a no-man's-land. Neither carrier will pay. The employee is stuck, and HR has no easy way to fix it because both systems claim the dependent isn't theirs.
Why This Keeps Happening
The root cause is simple: carriers and benefits platforms have no incentive to build a bridge. They assume employees will call customer service and eventually get things sorted. That call center costs them money, but not as much as building a new data transfer protocol would.
Meanwhile, employers bear the cost in lost productivity, damaged trust, and employees going without critical care. We've normalized this chaos. We shouldn't.
What You Can Actually Do About It
I've seen a few organizations break this cycle. It takes work, but it's possible. Here's what works:
- Demand a continuity of care file from your old carrier. Most can export a CSV of all active prior authorizations. Ask for it during contract termination. You have leverage; use it.
- Create a blackout window for enrollment changes. No new hires, no dependent updates between December 20 and January 5. This eliminates the file date paradox.
- Require your new carrier to accept a pre-enrollment clinical dependency file. This is non-standard but possible. Push your broker to make it a contract term. If the carrier resists, ask them to explain how they'll handle day-one claims for ongoing treatments.
- Test your COBRA split before go-live. Ask your benefits administration platform to run a simulation. Confirm that no COBRA records leak into the new carrier feed.
The Takeaway
Switching health plans isn't a transaction. It's a data migration project with life-altering consequences. Every year, we treat it as routine because the failures are invisible-until they land in an employee's inbox or at their pharmacy counter.
Stop accepting that chaos is normal. Demand a bridge between the old system and the new one. Your employees don't care about the cost savings. They care about whether their medication is ready on January 2nd.
That's the only metric that matters.