Qualifying Life Event: The Employer Guide
Which events qualify for a mid-year benefits change, the 30 and 60 day windows, the documents to collect, and how to satisfy the consistency rule.
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 guide covers the employer side: 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).
| Question | Section 125 change in status | HIPAA special enrollment |
|---|---|---|
| What it controls | Whether a pre-tax election may be changed | Whether the person may enroll in the health plan |
| Is it mandatory? | No, the plan may permit it | Yes, for the listed events |
| Request window | Set by the plan document | At least 30 days, at least 60 for Medicaid and CHIP |
| Can the plan shorten it? | There is no federal floor to shorten | No, the period is a minimum |
| Consistency test applies | Yes | Enrollment right stands on its own |
| Covers dropping coverage | Yes, where consistent | No, it is an enrollment right |
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.
Some events touch only one. 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 six 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. Five of them apply across the qualified benefits your plan offers. The sixth reaches only adoption assistance.
Beyond those six, 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.
Three more routes sit outside the original regulation, and employees ask about them. IRS Notice 2014-55 gives a plan the option of letting an employee revoke coverage when their expected hours fall below an average of thirty per week, even though plan eligibility continues. The revocation has to match an intended enrollment in other coverage that qualifies as minimum essential coverage (Internal Revenue Service).
Notice 2014-55 also created a second route. An employee may revoke coverage to enroll in a marketplace plan, either in a marketplace special enrollment period or during the marketplace's annual open enrollment. The new coverage has to start no later than the day after the old coverage ends.
IRS Notice 2022-41 later added a third route: an employee may revoke family coverage going forward so that one or more family members can enroll in a marketplace plan instead (Internal Revenue Service).
All three routes are optional for your plan. Each needs a plan amendment adopted by the last day of the plan year in which the change is allowed, and participants must be told about the amendment.
What is not on any list: a raise, a promotion without an eligibility change, a minor 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.
Is Pregnancy a Qualifying Life Event?
No. Pregnancy on its own is not a qualifying life event, but the birth is. Pregnancy appears nowhere in the six change in status categories and nowhere in the HIPAA special enrollment list, so an employee who tells you in March has no route to change an election until the baby arrives or open enrollment comes around.
The federal marketplace draws the same line. HealthCare.gov states plainly that being pregnant does not qualify a person for a special enrollment period, while the birth of a child does. That is worth knowing before you send someone off to look for coverage elsewhere, because in states that use HealthCare.gov the answer they find will match yours.
New York is one exception for individual coverage. Its insurance law lets a pregnant person enroll at any time once a health care professional certifies the pregnancy, with coverage starting on the first day of the month of certification or, at the person's choice, the following month (New York Insurance Law 4328).
What you tell the employee next matters more than the denial. Your plan already covers the pregnancy if the pregnant person is enrolled, because pre-existing condition exclusions are gone from group and marketplace coverage alike.
You can also point out that Medicaid and CHIP take applications year-round rather than only at open enrollment. And the birth reaches backward: the newborn is covered from the date of birth, not from the date the paperwork reaches you.
The one thing to fix in advance is the deadline. An employee who is expecting is an employee who will have a thirty-day window opening on a date nobody can schedule, so say the number out loud during the pregnancy rather than after the delivery, when a new parent is not reading benefits email.
Is Changing Jobs a Qualifying Life Event?
Yes, and which rule applies depends on whose job changed. A change in employment status for the employee, a spouse, or a dependent is one of the six change in status categories, so it can support an election change. Whether it also carries a federal enrollment right turns on whether coverage was lost.
The common version is a spouse who starts a new job and loses the old plan on the way. That is a loss of eligibility for other coverage, so it is a HIPAA special enrollment carrying the federal thirty-day floor. Under the regulation, such a loss includes one caused by termination of employment or a reduction in hours.
Two losses are carved out of that rule, and they are the ones to check before you say yes. Coverage that ended because premiums went unpaid on time, and coverage terminated for cause such as a fraudulent claim, are not a loss of eligibility, so neither one opens a special enrollment window on your plan.
A new hire arriving from another company is a different question entirely. That person is not changing an election mid-year; they are making a first election, which runs on your waiting period and the initial enrollment window in your plan document rather than on any of the rules above.
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.
The windows your plan document sets have a consequence employers underrate. 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.
| Event | Minimum window | Set by |
|---|---|---|
| Marriage | At least 30 days | HIPAA special enrollment |
| Birth, adoption or placement for adoption | At least 30 days | HIPAA special enrollment |
| Loss of eligibility for other coverage, or exhaustion of COBRA | At least 30 days | HIPAA special enrollment |
| Loss of Medicaid or CHIP coverage | At least 60 days | Statute, CHIPRA amendment |
| Becoming eligible for Medicaid or CHIP premium assistance | At least 60 days | Statute, CHIPRA amendment |
| Divorce or legal separation, dropping an ex-spouse | No federal minimum | Your plan document |
| Dependent aging out of your own plan | No federal minimum | Your plan document |
| Change in residence or worksite | No federal minimum | Your plan document |
The Consistency Rule
Under the change in status rules, 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 six 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. 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 the marketplace's 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.
Dwight SchruteSales3 people
Darryl PhilbinWarehouse1 person
Kelly KapoorCustomer Service1 personWhen 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.
| Event | Coverage begins | Practical effect |
|---|---|---|
| Birth | The date of birth | Retroactive. Process on the announcement, not on the certificate |
| Adoption or placement for adoption | No later than the date of adoption or placement | Retroactive to the placement date |
| Marriage | No later than the first day of the first month after the request | Forward-looking. The request date drives it |
| Loss of other coverage | No later than the first day of the first month after the request | Gaps are possible if the employee waits |
| Divorce or dependent aging out | Per the plan document | Usually end of month or date of event |
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 twenty-eighth and does not ask you until the third 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 who run both FSAs under one enrollment form and one rule set are the ones who get these differences wrong. The other 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.
The operational point here 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.
One sheet per event fixes this, and it is worth keeping even at three events a year, because the line you forget is never the one you were thinking about.
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.
Where Employers Get This Wrong
Employers get this wrong in five recurring ways, 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; under section 125, 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. Where federal COBRA or a state continuation law reaches your business, 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.
Nick Anisimov, FirstHR founder
Frequently Asked Questions
What is a qualifying life event?
A qualifying life event is a personal or job change that lets an employee add, drop, or change benefit elections partway through the plan year instead of waiting for open enrollment. Employers deal with two overlapping rule sets behind that one term. The section 125 cafeteria plan rules list the change in status events and decide whether a pre-tax election can be revised mid-year. The HIPAA special enrollment rules give certain employees and dependents a federal right to join the group health plan after specific events. In practice the events that come up most are marriage, divorce, birth, adoption, a dependent aging out, a change in employment status, a move, and loss of other coverage.
How long does an employee have to report a qualifying life event?
At least 30 days for most events that carry a federal enrollment right, 60 days or more when Medicaid or CHIP is involved, and whatever your plan document allows for everything else. Employers misjudge this more than any other part of the topic, because the right number depends on which rulebook the event belongs to. The 30-day minimum comes from the HIPAA special enrollment rules and covers marriage, birth, adoption, placement for adoption, and loss of other coverage. The 60-day minimum covers losing Medicaid or CHIP coverage and gaining eligibility for premium assistance through either program. A plan may offer longer windows but never shorter ones. Section 125 change in status events outside the HIPAA list carry no federal deadline, and most plan documents set 30 days.
What is the section 125 consistency rule?
The consistency rule is the test a mid-year change to a pre-tax election must pass under the section 125 change in status rules. The change has to be made because of a change in status that affects someone’s eligibility for coverage, and it has to line up with that effect. In plain terms, two links must hold: the event makes someone gain or lose eligibility, and the change the employee wants mirrors that gain or loss. Adding a new spouse after a wedding passes. Moving to a richer plan option on the back of the same wedding, for reasons that have nothing to do with it, generally fails. Group-term life and disability coverage get a special rule: an increase and a decrease are both treated as corresponding to the change in status.
Can an employer require documentation for a qualifying life event?
Yes, and you should. Neither section 125 nor the HIPAA special enrollment rules spell out which documents to ask for, so your plan document and your written administrative procedures set the standard. Whatever you request, make sure it carries a date: a marriage certificate, a birth or hospital record, an adoption or placement document, a divorce decree, or a letter from the other carrier showing which coverage ended and when. Then hold every employee to that same standard. Asking some people for proof and waving others through is worse than asking nobody, because uneven administration is how a small mistake becomes a discrimination problem.
When does coverage start after a qualifying life event?
Under the HIPAA special enrollment rules the effective date depends on the event. Coverage for a newborn begins on the date of birth, and coverage after an adoption or placement for adoption begins no later than the date of the adoption or placement, so both reach backward. For marriage and for loss of other coverage, coverage begins no later than the first day of the first calendar month after the plan receives the enrollment request. That backward reach on births is why a slow-arriving birth certificate should not stop you from processing the change.
Can an employee drop coverage mid-year without a qualifying event?
Not if the premium is paid pre-tax through a cafeteria plan, which is the normal arrangement. The whole reason the election is locked is the tax treatment: employees get the pre-tax break in exchange for an irrevocable election for the plan year, with a short list of permitted election changes as the only exits. If the coverage is paid entirely after tax and sits outside the cafeteria plan, the tax constraint disappears and the plan document and carrier rules decide. Check which arrangement you actually run before answering the question.
Does a plan have to allow every permitted election change?
No. The regulations say a cafeteria plan may permit these changes, not that it must. Your plan document decides which of the permitted events it adopts, what documentation it requires, and how long the request window is for events with no federal minimum. That cuts both ways: a plan that quietly allows changes it never adopted in writing has an operational failure on its hands, and one that refuses a HIPAA special enrollment because its own window is shorter than 30 days has a compliance failure. Read the document, then administer it exactly as written.
Is a change in residence a qualifying life event?
Yes, it can be. The cafeteria plan regulations list a move by the employee, a spouse, or a dependent among their six change in status categories, which makes it a valid basis for a mid-year election change. The move still has to pass the consistency rule, and in practice that means it must change someone’s eligibility. Relocating outside the plan’s network area, for example, supports switching to an option offered in the new location, or dropping coverage where the new area has none. A move across town that leaves everyone fully eligible for the same plan usually supports no change at all, because nobody’s eligibility changed.
Make HR the easy part of running your business
Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.
- 7-day free trial
- No credit card required
- Cancel anytime