First Time Open Enrollment HR: Your Plain-English Guide

This site contains affiliate links. View the disclosure for more information.

My first open enrollment was at a company with 60,000 employees. I was new to benefits, new to the job, new to the building. They handed me a binder, told me OE started in one month, and walked away. I didn’t know what a file feed was. I didn’t know who the carrier was versus the broker versus the vendor. I didn’t know how the rates got built. I didn’t know why I was being asked to come in on a Saturday. I just nodded and showed up and tried to look like I belonged.

If you’re reading this, you might be exactly where I was. Maybe you got promoted into benefits without training. Maybe you’re the HR generalist who picked up the OE binder because nobody else would. Maybe you’re three weeks into your first benefits job, and the senior person who handled this just gave their notice. Whatever brought you here, here’s what nobody is going to tell you out loud: open enrollment isn’t actually that hard to understand. It’s hard because nobody explains it.

So let’s fix that.

What Open Enrollment Actually Is

Open enrollment is the one window per year where employees can pick or change their benefits without needing a qualifying life event. That’s it. That’s the whole concept.

The reason it works that way comes from the IRS. When your company offers benefits on a pre-tax basis (which almost every employer does), the IRS requires that those elections be locked in for the plan year. You can’t just change your medical plan in July because you’re feeling differently about deductibles. The window to choose is the OE window. After it closes, your choices are locked unless something big happens. The technical term for those exceptions is qualifying life events, or QLEs.

So when someone says “open enrollment runs November 1 through November 15,” what they really mean is: this is the only window where the rules of the game allow you to change your elections without needing a qualifying reason. Miss it, and your options narrow to almost nothing until next year. You can read more about the legal basis in the IRS Employer’s Tax Guide to Fringe Benefits if you want the source material.

That’s what OE is. Now let’s talk about what’s actually happening behind the scenes.

The Cast of Characters

Six relationships that determine whether your OE actually works.

A lot of people are involved in your OE, and most of them don’t sit in your building. The first time someone says “talk to the carrier about that,” you need to know who they mean.

Your carrier is the insurance company: UHC, Aetna, Cigna, BCBS, Anthem, Kaiser, the big names. The carrier holds the risk on a fully insured plan. If claims go higher than premiums, the carrier loses money, not you. On a self-insured plan, the carrier just administers the claims, and your company pays the claims directly. Most small to midsize employers are fully insured. Most large employers are self-insured. You’ll want to know which yours is.

Your broker is your strategic advisor. They quote your renewal, negotiate with carriers, recommend plan design changes, and explain to leadership why premiums went up. They don’t work for the carrier. They work for you. (Technically, the broker may get paid commission by the carrier, but their job is to serve your company’s interests.) A good broker is one of the most valuable relationships you’ll have in this role.

Your benefits administration vendor is the software where employees actually log in to make their elections. PlanSource, BenefitFocus, Workday, ADP, BSwift, Empyrean, the list goes on. Sometimes this is built into your HRIS (Workday, UKG), and sometimes it’s a separate platform that feeds data over. The vendor isn’t the carrier. The vendor isn’t the broker. The vendor is the system.

Your payroll system processes the deductions. Sometimes it’s the same software as your ben admin (Workday does both). Sometimes it’s separate (UKG for payroll, PlanSource for benefits). When payroll and ben admin are separate, they connect through a data feed. When that connection breaks, paychecks go wrong. We’ll come back to that.

Your TPA (third-party administrator) handles claims on self-insured plans. If you’re fully insured, the carrier is both the underwriter and the claims processor, and you may never deal with a TPA. If you’re self-insured, the TPA is who employees call when their claim gets denied.

Inside your company: the CHRO who’ll ask you questions you can’t answer yet. The CFO who cares about the budget impact. The IT person who controls system access. The payroll manager who runs the actual deduction file. Communications who’ll help with the announcements. You’re the coordinator. You’re not doing all this alone.

How Plans Get Picked

Long before you ran your first OE, somebody decided what plans your company offers. Three medical options? One dental? Voluntary life? That was a decision somebody made, usually months before plan year start, in a series of meetings you weren’t invited to.

The renewal cycle starts about 90 to 180 days before your plan year begins. For a calendar year plan with a January 1 effective date, that means the renewal conversation usually starts in July or August. Your broker pulls together data on how your current plans performed, including claims trends, utilization, and demographics, then brings that to the carrier. The carrier comes back with a renewal offer. The broker negotiates. Plan options get added or removed. Cost-sharing percentages get adjusted (how much the company pays toward each plan versus how much the employee pays).

By the time OE arrives, those decisions are locked. Your job during OE isn’t to pick the plans. It’s to administer the ones leadership already chose.

Here’s the part that helps you in year two: you can sit in on the renewal strategy meetings. Ask your broker. Ask your manager. Even just listening teaches you how the decisions get made. By the time you’ve sat through one renewal cycle, you’ll understand why your CFO cares so much about a 3% versus 7% increase and why your CHRO is asking whether the HDHP participation hit a certain threshold.

How Rates Actually Get Built

How open enrollment rates get built: claims, demographics, network, plan design, market trends — Five inputs that determine why your premium went up.

This is the part employees ask about every fall: “Why did my premium go up?” If you don’t know the answer, you can’t explain it, and an employee with no explanation gets angry fast.

Rates get built from a few inputs.

For most small to midsize employers, your group is experience-rated. Your premium increase (or decrease) is based on your group’s actual claims over the past 12 to 24 months. High-claim year? Premiums go up. Big claim event in the prior year (a complex pregnancy, a transplant, a long hospitalization) drives the next year’s rate. Premiums go up.

A few other things move the number:

Demographics. If your workforce got older, average claims rise. If you added a lot of new hires in their twenties, average claims fall. Even small shifts move the rate.

Network changes. If a carrier renegotiated its hospital contracts, your premiums move. If a major health system left a network, your premiums move.

Plan design changes. If you raised deductibles, premiums go down. If you added a richer plan option, premiums on that plan go up.

Market trends. Pharmacy costs (especially specialty drugs and GLP-1 medications) have driven double-digit increases industry-wide for the past several years. That hits every employer, regardless of how good your group looks. According to KFF’s 2025 Employer Health Benefits Survey, the average family premium hit $26,993 last year, with employers citing prescription drug spending as the top contributor to rising costs.

When an employee says “why did my premium go up 8%?”, you don’t need to deliver a Harvard lecture. You need to know enough to say: “Our group’s claims came in higher than expected, and pharmacy costs across the industry are up significantly. The CFO and the broker worked hard to absorb as much of that as possible, but some of the increase had to pass through. Here’s what the company is contributing.” That’s a real answer. It’s the answer your broker would give you. Now you can give it to your employee.

The Technical Machinery (Including That File Feed You Don’t Understand Yet)

This is where most new admins drown. The machinery isn’t complicated once someone shows you. The problem is nobody shows you.

Your benefits administration system is the source of truth for elections. When an employee logs in and picks the HDHP with employee+spouse coverage and a $2,400 annual FSA, that election lives in the ben admin. Everything downstream is supposed to match the ben admin.

A file feed is exactly what it sounds like: a file of data that “feeds” out of one system and into another. After OE closes, your ben admin generates files for every carrier. One file for the medical carrier, one for dental, one for vision, one for life. Each file lists every enrolled employee, every dependent, every coverage tier, every effective date, every term date for people who dropped coverage. That file goes to the carrier, gets loaded into the carrier’s system, and now the carrier “knows” who has coverage starting January 1.

File feeds usually run on an EDI (Electronic Data Interchange) connection, which sounds technical but just means there’s a standard format for the file. Some carriers want a file every week. Some want it monthly. Some want a special “OE file” right after enrollment closes. Your ben admin vendor and your broker can tell you the cadence for each carrier.

Now the part nobody tells you: a file feed can run successfully and still drop records. The system reports “file transmitted.” The carrier reports “file received.” Everyone goes home. Then in February, somebody calls because their coverage shows as terminated when they’re still active. Or worse, they show as active when they should have terminated and the carrier is still paying claims for someone the company stopped covering months ago.

This is what almost burned me my first year. A coworker, already on Medicare in her late sixties, terminated during OE. The file fed out with null values in the term code field. The carrier read “null” as “still active.” Six months later she called crying because every claim her doctors submitted was getting denied. Medicare saw our employer plan still showing as active and refused to pay. Denied claims were already past $30,000 and growing. Three months of escalation calls and one lucky decision by a human at the carrier to grant a six-month retroactive termination on a 60-day contractual rule saved us from a six-figure problem. I didn’t know what a file feed was. I do now.

Then there’s your payroll integration. The ben admin tells payroll what to deduct from each paycheck. When somebody elects $2,400 in an FSA, payroll needs to deduct that across the 26 paychecks of the year (about $92 per pay period). When somebody changes from employee-only medical to family, payroll needs to update the per-paycheck premium. That handoff between ben admin and payroll is its own potential failure point. Sometimes the data file runs but the new deduction dates don’t update. Sometimes the prior plan year’s last paycheck pulls the new plan year’s rates because the payroll calendar inside the ben admin never rolled forward. Each of those failure modes is a different reconciliation nightmare in January.

The OE Timeline (And Why You Might Be Working a Saturday)

The full open enrollment year timeline from 120 days out through mid-year audit — OE is two to four weeks. The work around it spans nine months on either side.

If you’ve never seen the full timeline laid out, here it is.

90 to 120 days before plan year start: renewal strategy meetings. Plan decisions get made.

60 to 90 days before: vendor configuration. The ben admin gets built out with the new plan year, including plans, rates, eligibility rules, and employee contributions.

30 to 45 days before: communications start going out. Employees get their packets. The portal opens.

OE window (typically 2 to 4 weeks): employees make their elections. You handle the questions, the panic, the late enrollees.

The cutover weekend: this is your Saturday. The portal closes Friday night or Sunday night. Over that weekend, the ben admin finalizes the new plan year’s data. File feeds run to every carrier on an agreed-upon schedule. Payroll deductions get tested against a sample of employees. Manual touches happen, including corrections to weird edge cases, last-minute adds, and exceptions approved by leadership. By Monday morning, everyone is supposed to have valid coverage for the new plan year.

Some companies don’t need anyone in the office that Saturday. Some companies may allow a 1-week admin period to catch the stragglers. Bigger companies and companies with complex integrations need eyes on the cutover. The 60K-employee company I worked at? Yeah. Saturday. Bagels in the conference room and someone at every screen.

January 1: new plan year is live. Coverage active. Deductions adjust on the first paycheck of the year.

January and February: reconciliation. Every error from cutover gets discovered now. This is the busiest inbox month of the year.

March 15: for plans with a Healthcare FSA grace period, the prior plan year truly closes here.

April 1: for employees who moved from PPO plus FSA to HDHP, HSA eligibility opens.

June: mid-year audit. The checkpoint that catches what OE missed. (More on this in Post Open Enrollment Audit: The 5-Phase System That Saves January.)

That’s the year. OE itself is two to four weeks. The work around OE spans nine months on either side.

If you want a printable version of the timeline you can keep on your desk, the free OE Survival Guide has one built in. Same timeline. Take it.

What Usually Goes Wrong (For First-Timers)

What Usually Goes Wrong

• The file feed runs “successfully” but drops records silently.
• People who termed show as active, or active people, show as termed.
• The payroll calendar inside the Ben Admin doesn’t roll forward to the new plan year.
• The first paycheck pulls the wrong rates.
• Employees who didn’t enroll miss the window and then demand exceptions in January.
• Required notices (Medicare Part D Creditable Coverage, CHIP, HIPAA Special Enrollment) get missed because they have different distribution rules than the OE guide.”What doesn’t roll” categories like FSA elections, HSA contributions, and voluntary benefits go uncommunicated.
• Employees assume things carried forward that didn’t.
• Term codes don’t translate between systems. The ben admin says “termed.” The carrier reads it as “active.” Months of denied claims follow.

What to Do Instead

What usually goes wrong in open enrollment broken file feeds and payroll handoffs — Six failure modes that catch every first-time admin off guard.

Build your OE calendar at least 90 days before plan year start. Put every milestone on it: renewal dates, communication sends, portal open and close, cutover weekend, carrier file deadlines, payroll preview, January reconciliation, Mid-Year Benefits Audit: What to Check in June. I run mine in ClickUp because the recurring date logic actually holds across plan years.
Map every system that touches benefits and where data flows between them. Ben admin to carrier. Ben admin to payroll. HRIS to ben admin. If you can draw it on a whiteboard, you understand it.
Confirm receipt of every file feed in writing. Don’t trust “the file transmitted.” Get the carrier to send you a confirmation with the record count.
Reconcile a sample of elections against the payroll preview BEFORE the first paycheck of the new year runs. Twenty employees is enough. If something’s wrong, you’ll catch it.
Communicate “what doesn’t roll” before OE closes. FSAs, HSAs, voluntary benefits, tobacco attestations. Tell people which elections they need to make actively versus which carry forward.
Document everything. Every conversation with the carrier. Every approval from leadership. Every late enrollment exception. If you ever face an audit or a dispute, “I think I sent it” is not a defense.

REAL TALK

Open enrollment isn’t a calendar event. It’s a coordinated handoff between four systems and six humans, and you’re the one holding the baton. Nobody explained that to you because everyone teaching OE has forgotten what it felt like to not know. So now you know.

You Don’t Have to Figure This Out Alone

If you walked into this role with a binder, a calendar, and a prayer, you’re in the right place. The work isn’t to memorize every plan rule. The work is to learn the machinery, one system at a time, with someone who’s been where you are.

The free OE Survival Guide gives you the timeline, the cast of characters, and the printable checklist for your first OE. It’s the document I wish someone had handed me on day one at the 60K-employee company.

When you’re ready for the full system — the playbook, the calculator, the timeline with every milestone built in — the Open Enrollment Mastery Kit is the practitioner’s complete kit. Thirty-four pages of real-world OE execution and a nine-tab Excel calculator that does the math you don’t want to do twice.