Confirm Your Plan Administrator Before the Wrong COBRA Notice Clock Finds You

The Signal

Most operators who run their own group health plan know COBRA has a notice deadline. Fewer know which one applies to them. The regulation sets two different clocks depending on who sits in the administrator's chair. If a third-party administrator handles your plan, the clock is 14 days after they're told about the qualifying event. If you're the employer and the plan administrator — the common setup at a self-administered small or mid-size company — the clock is 44 days from the qualifying event itself, because there's no one else to notify you of something you already know happened. Treating both paths like the same 14-day rule is how a routine termination becomes a benefits-notice violation with its own penalty exposure, separate from anything else going on with the departure.

Why this matters now

Layoff and reduction activity has been steady through the back half of this year, and every termination (along with reduced hours that cause a loss of health coverage, divorce, a dependent aging off the plan, Medicare entitlement, or employer bankruptcy) is a COBRA qualifying event with its own notice clock. 29 CFR § 2590.606-4 is explicit: when the employer is also the plan administrator, the election notice is due "not later than 44 days after" the qualifying event or the loss-of-coverage date, whichever the plan uses as its trigger. That number isn't a guideline — it's the regulatory floor plan administrators are held to, and a late or missing notice carries its own excise exposure under the Internal Revenue Code, on top of whatever else is already in play around the separation. A company that handles HR, payroll, and benefits administration in-house — a lot of founder-run and family-run operators between 20 and 500 employees — is exactly the profile this 44-day rule targets, because there's no outside TPA clock running in parallel to catch it.

The mistake to avoid

The mistake is assuming COBRA notice timing is a single number memorized once. § 2590.606-2 sets a 30-day clock for the employer to notify the plan administrator of a qualifying event when those are two different parties. § 2590.606-4(b)(1) then gives that administrator 14 more days after receiving that notice to send the election paperwork — up to 44 days total in a split-administrator setup, but on two separate clocks with two separate failure points. § 2590.606-4(b)(2) collapses that into one 44-day clock measured directly from the qualifying event when the employer and administrator are the same entity, because there's no second party to notify. If your HR lead is tracking "14 days" as the rule because that's the number on a vendor's compliance sheet, and your company is self-administered, they're tracking the wrong number by a factor of three — and they won't find out until a terminated employee's lawyer does the math for them.

Where the 44-day clock actually starts

The start date matters as much as the day count. The clock runs from one of two points, and the plan document — not your calendar preference — decides which: either the date the qualified beneficiary actually loses coverage, or the date the qualifying event occurred, if the plan's terms tie notice timing to the event rather than the coverage-loss date. Pull your plan document or summary plan description and confirm which trigger it uses before building a tracking process around the wrong start date. A plan tied to loss-of-coverage, not the termination date, can shift your deadline by weeks if continuation coverage is structured to begin later than the last day worked.

What stays protected

None of this is about outsourcing benefits administration or installing a system that wasn't there before. Keep the plan document, the termination process, and the people who run both exactly where they are. What this adds is one explicit question at every termination, coverage-loss event, divorce notification, or dependent age-out: who is the plan administrator of record, and which notice clock applies to them. That's a question, not a system — it doesn't touch payroll, doesn't touch the plan's funding, and doesn't require a new vendor relationship to answer correctly.

The first move

Pull your group health plan's summary plan description or plan document and find the line that identifies the "plan administrator." If that name is the company, not a named third party, you are on the 44-day clock, not the 14-day one — and the clock starts at the date your plan document specifies, so read that line too. Then check your last three terminations, coverage-loss events, or qualifying dependent changes against actual election-notice-sent dates. If any took longer than 44 days from the triggering date, that's not a process problem for next quarter — it's an open notice violation sitting on your books right now.

The move this week

Put a single line in your termination checklist: "COBRA election notice due [event date + 44 days if self-administered / confirm clock in plan doc]." One line, one deadline, one owner — whoever currently signs off on termination paperwork is the right person to also own this date, because they already know the event happened on day zero. Don't build a compliance program around it. Build a deadline into the process that's already running.