Qualifying Life Event: The Employer Guide

An employee walked into my office in March holding an ultrasound photo and asked whether the baby could go on the plan. I said yes, obviously, congratulations, and then spent the next hour discovering that my confident yes came with a deadline, a documentation standard, and a rule about what else that employee was and was not allowed to change at the same time.

That is the whole problem with qualifying life events. The employee experience is a happy announcement. The employer experience is a clock that started running on a date you may not learn for three weeks, a plan document that may be stricter than the regulation, and a change you either process correctly or unwind painfully in an audit.

This is the employer side of it: which events qualify, how long the employee actually has, what your plan document controls and what federal law will not let it shorten, the documents worth collecting, and the consistency rule that decides whether the change you processed was legal. I build the people and records tooling for businesses without an HR department at FirstHR. This is general information, not legal or tax advice.

What a Qualifying Life Event Is

A qualifying life event is a change in an employee's circumstances that permits a mid-year benefit election change outside open enrollment. It exists because pre-tax elections are otherwise locked for the plan year, and life does not organize itself around your enrollment calendar.

The lock itself is the point worth understanding. Employees pay premiums pre-tax through a cafeteria plan, and the price of that tax treatment is an election that is irrevocable for the plan year. The qualifying event rules are the narrow, defined exits from that deal, not a general customer service policy.

Two Rulebooks, One Request

The single most useful thing an employer can learn here is that two separate bodies of law sit behind one employee request, and they answer different questions. Confusing them is where most mistakes start.

Section 125 governs the tax side. It asks whether an employee may revoke a pre-tax election mid-year and make a new one, and its permitted events and consistency requirement are set out in the cafeteria plan regulations (26 CFR 1.125-4). It permits changes. It never requires your plan to allow them.

HIPAA governs the coverage side. It gives certain employees and dependents an enforceable right to enroll in the group health plan mid-year, on a timetable your plan cannot shorten, under the special enrollment rules (29 CFR 2590.701-6).

Most real requests touch both. A marriage is a HIPAA special enrollment event and a change in status, so the employee has a federal right to enroll the new spouse and a section 125 basis to change the pre-tax election that pays for it. A dependent aging out of your own plan is a change in status but not a HIPAA special enrollment, so it runs on the window your plan document sets and your summary plan description communicates.

Which Events Qualify

The cafeteria plan regulations list five categories of change in status, and an event outside them is not a change in status no matter how significant it is to the person living it.

Beyond those five, the regulations permit election changes for several other situations: a judgment, decree or order such as a child support order requiring coverage for a child, entitlement to or loss of Medicare or Medicaid, and significant changes in the cost or coverage of a benefit option. Each has its own conditions.

Two more sit outside the original regulation and are worth knowing because employees ask about them. IRS Notice 2014-55 permits a plan to allow revocation when an employee's expected hours fall below an average of thirty per week even though plan eligibility continues, provided the revocation matches an intended enrollment in other coverage that qualifies as minimum essential coverage (Internal Revenue Service). IRS Notice 2022-41 later added prospective revocation of family coverage so that family members can enroll in a marketplace plan instead. Both are optional and both require a plan amendment.

What is not on any list: a raise, a promotion without an eligibility change, a rate increase the employee dislikes, a change of heart about the plan they chose, or a spouse deciding they would prefer your plan to theirs outside their own open enrollment. Those are the requests you will actually receive most often, and the answer is no.

The Election Change Window

There is no single deadline, and the belief that there is one is the most common error I see. There are federal minimums for some events and nothing at all for others, and your plan document fills the gap.

For HIPAA special enrollment events the regulation requires the plan to allow at least thirty days after the event. That is a floor. A plan can offer forty-five or sixty days if it wants to, but a plan whose handbook says twenty-one days is out of compliance the moment it enforces it.

For change in status events that are not HIPAA special enrollments, no federal rule sets a deadline at all. A dependent aging out of your plan, a change of residence, a spouse gaining coverage: for these your plan document is the only source of the window, and thirty days is the near-universal choice.

Watch the overlap before you rely on that. The same divorce or loss of dependent status that ends someone's eligibility under another employer's plan is a loss of eligibility for other coverage, and that is a HIPAA special enrollment carrying the federal thirty day floor. The label on the event matters less than which side of the coverage line it lands on.

That has a consequence employers underrate. The plan document controls the shorter windows, so if yours says thirty days and you process a request on day forty-five as a favor, you have not been generous. You have administered the plan inconsistently with its own terms, which is exactly the pattern that turns a single accommodation into a precedent you cannot refuse the next person.

The Consistency Rule

An election change is only permitted if it is on account of and corresponds with a change in status that affects eligibility for coverage. That sentence is the entire test, and it disqualifies more requests than the event list does.

Two things have to be true. The event has to cause someone to gain or lose eligibility for coverage. And the change the employee is asking for has to match that gain or loss. An event that changes nothing about eligibility supports nothing, even if it is one of the five listed categories.

Group-term life insurance and disability coverage get a deliberate exception. For those benefits, an election to increase coverage or an election to decrease it is deemed to correspond with the change in status, which removes the argument about direction and is a small mercy for whoever administers the plan.

The practical version of this test is a sentence you write on the request form: this event caused X to gain or lose eligibility, and this change corresponds because Y. If you cannot write it, do not process the change. If you can, you have both the answer and the documentation of your reasoning in one line.

What Documentation to Collect

Neither the cafeteria plan regulations nor the HIPAA rules hand you a prescribed document list, which surprises employers who expect one. The standard comes from your plan document and your own written administrative procedures, and the only real requirement is that you apply it to everyone the same way.

The government does publish a useful reference for the individual market. The marketplace tells applicants which documents it accepts to confirm a special enrollment period, and once job-based coverage has ended a person has sixty days to pick a marketplace plan and thirty days after that to send the documents (HealthCare.gov). Borrowing that document standard for your own plan is a reasonable way to set a bar you can defend.

One narrow rule does exist and is worth using. A plan may require an employee who declines coverage to state in writing that they are declining because they have other coverage, but only if the employee was told about that requirement, and its consequences, at or before the time they declined. Get it in your declination form or you cannot rely on it later.

Keep the documents where employment records live rather than in an email thread, and treat them as confidential. A divorce decree and a hospital birth record are not items you want sitting in a shared inbox that half the company can search. Consistent benefits administration is mostly a filing discipline problem wearing a compliance costume.

When New Coverage Starts

Effective dates are not uniform, and two of them reach backward in a way that catches employers who wait for perfect paperwork before processing anything.

The retroactive ones matter operationally. A newborn is covered from the date of birth, so a delivery that happens before the paperwork arrives is still a covered claim. Tell the employee that in the first conversation, because the fear that the hospital bill will land uncovered is what drives frantic calls to you at week three.

The forward-looking ones matter differently. If an employee loses spousal coverage on the fifteenth and does not ask you until the twenty-eighth of the following month, there is a genuine gap, and it was created by the delay rather than by your plan. That is an argument for telling employees the deadline exists at hire and again at every open enrollment rather than only when they ask.

FSAs and Spending Accounts

Spending accounts follow their own logic, and the health FSA is the strictest of them. The cost and coverage change rules that permit election changes for other benefits explicitly do not apply to a health FSA.

That means a premium increase or a plan redesign gives an employee no route to change a health FSA election, even though it may permit changes to their medical election. Change in status events can still support an FSA change where the consistency rule is met, which in practice means events that change who is covered rather than what things cost.

A dependent care FSA behaves differently again, because a change in the care provider or a significant cost change can itself justify an election change in circumstances the health FSA never allows. The cost route has one condition worth remembering: the regulation only counts a cost change imposed by a provider who is not a relative of the employee. Employers running both accounts under one enrollment form and one rule set are the ones who get this wrong.

The mismatch to watch for: a change that is fine on the medical plan and impermissible on the FSA in the same request. Handle them as two decisions on one form rather than one decision applied to two benefits.

Where COBRA Fits

Some qualifying life events are simultaneously COBRA qualifying events, and the two run on completely separate clocks with separate notice duties. A divorce is the clearest example: it lets the employee drop the ex-spouse from the plan, and where federal COBRA or a state continuation law reaches your business it obliges you to offer that ex-spouse continuation coverage.

That second obligation is a different body of law with its own deadlines, its own notice requirements, and its own penalties. It is covered properly in the guide to COBRA qualifying events, and I am not going to duplicate it here beyond the pointer.

The operational point for this article is narrow: build the handoff. When your election change form records a divorce, a death, a dependent aging out, or a reduction in hours that ends eligibility, something has to route that fact to whoever runs continuation coverage. The most expensive failures in this whole area are not wrong election changes. They are correct election changes that nobody forwarded.

Running the Change

The process is short and the discipline is in the dates. Seven steps, and the first one is the one that saves you.

Written confirmation is worth more than it looks. A short message stating the event, the effective date and the new deduction closes the loop with the employee and creates the record you will want if anybody asks two years later what you did and when. Good benefits communication is mostly this.

Where Employers Get This Wrong

Five patterns, and the first one costs the most.

Running a single thirty-day rule for every event is first. It denies legitimate Medicaid and CHIP requests that carry a sixty-day statutory period, and denying an enrollment right is a different order of problem than an administrative slip.

Processing whatever the employee asks for is second. The event opens the door; the consistency rule decides how far. A marriage does not entitle somebody to upgrade to the richest plan option unless the eligibility line connects.

Waiting for perfect paperwork is third. Newborn coverage reaches back to the birth date, so processing on the announcement and reconciling the document later is both correct and kinder than the alternative.

Making exceptions for the people you like is fourth. Inconsistent administration of a plan is the underlying failure in most of the benefits disputes I have watched small employers lose, and it always starts as a favor.

And treating the election change as the end of the process is last. The divorce that changed the medical election also started a continuation coverage obligation, and the handoff between those two facts is where small businesses without an organized benefits process quietly accumulate liability.

Frequently Asked Questions