COBRA Notice Requirements for Departing Employees

COBRA is a federal continuation-coverage mandate that applies to private-sector employers with 20 or more employees, state governments, and local governments that sponsor group health plans. It does not apply to federal government plans or church plans. The threshold question of whether a company is covered is more precise than most operators assume, and the counting method matters because fast-growing companies routinely miscount and assume they're under the line.

The 20-employee threshold uses a fractional method in which part-time employees count as a proportion of a full-time employee based on hours worked. Coverage applies only if 20 or more employees worked on more than half of the typical business days in the prior calendar year. A company with 15 full-time employees and 10 half-time workers sits at an effective count of 20, even though no one on the payroll works 40 hours across the whole roster. This calculation is not intuitive, and it's exactly where early-stage companies misjudge their exposure.

A group health plan covers medical care including inpatient and outpatient hospital care, physician care, surgery and other major medical benefits, prescription drugs, dental, and vision. Qualified beneficiaries who can get continuation coverage include the covered employee, their spouse or former spouse, and dependent children, along with retired employees on a retiree health plan and children born or adopted during a COBRA coverage period in limited circumstances. Employers may charge up to the full cost of coverage plus a 2 percent administration fee, and employees bear the entire premium unless an employer voluntarily subsidizes it as part of a severance arrangement.

Qualifying events: what starts the COBRA clock and for whom

The COBRA obligation is triggered by a defined set of qualifying events, and the specific event determines both who the qualified beneficiary is and how long continuation coverage must last. If you conflate these categories, you get both under- and over-notification errors, and each carries its own compliance risk. The point worth internalizing early is that the trigger universe is wider than most operators expect.

For the employee, the triggering events are job loss for any reason other than gross misconduct and a reduction in work hours. For the employee's spouse and dependents, the list expands considerably: job loss or hour reduction of the covered employee, divorce or legal separation from the covered employee, death of the covered employee, loss of dependent child status, and in limited situations the employee becoming entitled to Medicare. Coverage duration is generally 18 months, though extensions apply in certain circumstances, and the type of qualifying event governs the maximum period. Gross misconduct is a complete exception. An employee terminated for gross misconduct is not entitled to COBRA, but the employer bears the burden if that exclusion is challenged, so documentation of the basis for termination becomes the operative protection.

Divorce and dependent aging-out deserve special attention because they are the events most likely to fall through the cracks at a company without a unified HR data source. Unlike a termination, which triggers a formal offboarding workflow, a divorce or a child turning 26 does not announce itself to the systems that would otherwise start the notice sequence. The obligation exists regardless of whether anyone noticed the event occurred.

The three-notice sequence and its non-negotiable deadlines

COBRA compliance is a sequenced handoff of three legally distinct notices, each with its own trigger, responsible party, and deadline. A delay at any stage directly compresses or eliminates the time available for the next. The sequence begins long before anyone leaves the company.

The first notice, the General Notice, must be sent to every employee and their spouse within 90 days of the employee's health coverage start date. Its content must explain what COBRA is, what qualifying events look like, the qualified beneficiary's rights and obligations, how to notify the plan administrator of a qualifying event, and the importance of keeping contact information current. Most employers only think about COBRA notices at termination, which means skipping the General Notice at enrollment is a silent violation that goes undetected until a beneficiary claims they were never informed of their rights.

The second notice is the Employer-to-Administrator Notification of Qualifying Event. When a qualifying event is employer-initiated, meaning a termination, hour reduction, death, Medicare entitlement, or employer bankruptcy, the employer must notify the plan administrator within 30 days of the qualifying event. When the event is a divorce, legal separation, or dependent child losing eligibility, the employee or qualified beneficiary, not the employer, must notify the plan within 60 days of the event or the date coverage would be lost, whichever is later. That employee-notification obligation is only meaningful if the General Notice properly explained it, which is another reason the first notice is not optional.

The third notice is the COBRA Election Notice to the qualified beneficiary. If the employer also serves as the plan administrator, a common arrangement in smaller companies, the combined window is 44 days from the qualifying event. The election notice is the legally binding offer of continuation coverage, and the beneficiary then has 60 days from the later of coverage loss or receipt of the election notice to elect coverage. Its content requirements are specific: the notice must identify the qualifying event, identify the qualified beneficiaries, explain the right to elect, explain the consequences of not electing, state the premium and deadline for payment, and provide enrollment instructions.

An often-overlooked fourth obligation sits at the back end of the sequence. If a qualified beneficiary's COBRA coverage ends before the maximum allowable period, for example due to non-payment of premiums, the plan administrator must provide a written early-termination notice explaining why coverage is ending, the termination date, and any rights to enroll in other coverage. COBRA does not require plans to send monthly premium bills or reminders, since qualified beneficiaries are responsible for timely payment, but the early-termination notice when coverage ends remains mandatory.

Delivery rules and documentation: how proof of sending becomes the actual defense

Sending the correct notice on time is necessary but not sufficient. A notice that cannot be proved delivered is treated as a notice never sent, which makes documentation discipline a legal asset in its own right. Acceptable delivery methods include hand delivery, first-class mail, and electronic delivery, though electronic delivery requires specific conditions to be met, including obtaining the recipient's consent. That consent requirement is a trap for employers who assume modern delivery is automatically compliant.

Mailing to a covered employee's last known address is treated as reasonably calculated to reach the recipient and constitutes good faith compliance. When qualified beneficiaries at different addresses are entitled to notice, separate notices are generally required for each. A single notice to a shared address suffices when a covered employee and spouse live together, and a notice to a parent can satisfy the requirement for a dependent child who lives at that address. Electronic delivery is administratively convenient but requires upfront consent infrastructure that many companies haven't built.

Keeping contact information current is part of the General Notice's required content precisely because a stale address undermines the entire delivery defense. In Marrow v. The case was later dismissed when Marrow could not produce evidence tracing her injuries to the notice deficiencies, but the initial ruling stands as a warning that the content of a notice is subject to the same scrutiny as its delivery.

What noncompliance actually costs: the penalty structure across IRS and DOL

COBRA noncompliance exposes employers to concurrent penalty regimes from two separate federal agencies, and those penalties scale with the number of affected beneficiaries and the duration of the violation. The IRS levies an excise tax of $100 per day per qualified beneficiary for each day of noncompliance, and the per-day rate doubles to $200 when more than one family member is affected. On audit, the minimum IRS excise tax for any noncompliance period is $2,500, and for unintentional failures the maximum is the lesser of 10 percent of prior-year group health plan expenditures or $500,000.

The DOL separately imposes penalties of up to $110 per day per qualified beneficiary for failure to provide required notices. These run concurrently with IRS excise taxes, not as an alternative. Enforcement authority is divided: the DOL governs disclosure and notification requirements, the IRS governs eligibility and premium payment rules, and the Department of Health and Human Services administers provisions for state and local government plans. A company with a systemic notice failure affecting multiple employees simultaneously does not face one capped penalty, because each beneficiary's violation period runs independently.

Why delegating COBRA administration to a third party does not transfer legal liability

Employers who outsource COBRA administration to a third-party administrator remain the legally responsible party when notices fail, and the 2025 ruling in Casillas-Guardiola v. In the case, the U.S. District Court for the District of Puerto Rico dismissed the COBRA claim not by articulating a rule about fiduciary delegation but by finding that Casillas suffered no prejudice and that Bayer did not act in bad faith. The employer survived the penalty claim for one reason: it had documented the certified mailing. That documentation, not the fact of delegation, was the compliant act.

The practical implication is that outsourcing COBRA administration shifts operational burden but not legal exposure. If the TPA misses a deadline or uses an outdated notice template, the employer answers for it. It's that using one does not replace the need for internal compliance records.

Mini-COBRA laws and the patchwork state layer that applies before a company hits 20 employees

The federal 20-employee threshold is not a safe harbor. The DOL advises checking with the state insurance commissioner's office, and more than 40 states plus the District of Columbia have enacted mini-COBRA laws covering employers with fewer than 20 employees. There is no uniform mini-COBRA template.

California's Cal-COBRA covers employers with 2 to 19 employees and provides up to 36 months of continuation coverage for those small-employer workers. For employees of larger employers, it can add 18 months after federal COBRA for a combined total of 36 months. Oregon stands at the other extreme of the spectrum: employees there can have as few as 10 days to elect continuation coverage, far shorter than the 60-day federal election window.

A startup that operates across multiple states inherits a different notice and election-window obligation for each state where it has employees, and those obligations begin before the company is large enough to be subject to federal COBRA. A single departing employee in a state with a 10-day election window requires faster action than the federal sequence, and payroll tax deregistration for that state runs simultaneously. The practical effect is that a company's COBRA compliance map is as wide as its employment footprint, not as wide as its largest state.

What breaks down when COBRA administration runs on manual processes across disconnected systems

The COBRA notice sequence is a workflow that depends on a qualifying event in one system triggering coordinated actions in payroll, benefits, and HR records. Manual processes and disconnected tools are structurally unable to run that sequence reliably as headcount grows. A qualifying event like a termination must simultaneously trigger notification to the plan administrator within 30 days, preparation and delivery of the election notice within 14 additional days, payroll cutoff, revocation of system access, device recovery, and in multi-state situations, state-specific continuation-coverage notice under mini-COBRA law.

When HR, payroll, and benefits live in separate systems that do not share a real-time data layer, the termination event in one system may not propagate to the benefits system. The 30-day employer-notification clock runs whether or not the benefits system knows the employee has left. Manual systems have no mechanism to remind employees of their 60-day notification obligation or flag when that window has passed.

The failures described earlier are not primarily errors of legal ignorance. What is a manageable spreadsheet at 30 employees becomes an audit risk at 200, because each missed notice is a separate violation with its own per-day penalty clock. The early-termination notice obligation is particularly prone to being missed in manual processes, since it requires the plan administrator to act at the moment coverage lapses, not at a scheduled interval.

How automated offboarding infrastructure closes the COBRA compliance chain

The COBRA notice chain is a sequenced workflow with hard deadlines triggered by a system event, which means it is exactly the kind of process that automated, integrated infrastructure can own end to end in a way that manual administration cannot. If you integrate qualifying-event data across HR, payroll, and benefits, automated compliance systems can trigger the employer-to-administrator notification the moment a termination or hour reduction is recorded. That eliminates the gap between when the event occurs and when the 30-day clock is acknowledged internally. For qualifying events that depend on employee self-reporting, automated systems can surface the 60-day notification obligation to the employee at the point of the event and log whether the notification was received. An AI-native platform that processes offboarding as a single coordinated workflow, revoking system access, processing final payroll, triggering benefits termination, and initiating the COBRA notice sequence, removes the dependency on manual handoffs between disconnected systems that is the root cause of most notice failures. The Bayer Puerto Rico defense, documented mailing, is exactly the kind of output an automated system generates automatically and stores permanently without requiring an HR team member to remember to create a paper trail.

A practical COBRA compliance checklist for employers managing departing employees

COBRA compliance reduces to a sequenced set of verifiable actions tied to defined triggers. Treating it as a checklist that can be owned by a system rather than tracked by a person is what separates companies that stay compliant at scale from those that discover violations during an audit. The following reference reflects each obligation developed in this article and should be read as an action set, not a restatement of the law.

On health plan enrollment, send the General Notice to the employee and their spouse within 90 days of the coverage start date, document the delivery with date, method, and address used, and instruct employees in that notice to keep contact information current and to report qualifying events such as divorce and dependent aging-out within 60 days. At an employer-initiated qualifying event, notify the plan administrator within 30 days, confirm the administrator has the qualified beneficiary's current address, and track the administrator's 14-day election-notice deadline from the date of employer notification, with the combined window at 44 days from the qualifying event if the organization is both sponsor and administrator. For employee-reported events, establish a clear procedure referenced in the General Notice for reporting divorce, legal separation, or dependent aging-out within 60 days, log receipt of that notification with date and method, and begin the administrator's 14-day election-notice clock from receipt.

On templates, use DOL model notices and verify that the version in use has not expired, since an expired model notice eliminates the good-faith compliance safe harbor, and schedule a periodic review of notice templates when regulatory updates are announced. For multi-state operations, identify which states have mini-COBRA laws covering the employee population regardless of whether federal COBRA applies, and map each state's notice deadline, election window, and coverage duration as separate compliance chains running in parallel with or instead of the federal sequence. On TPA relationships, document the TPA's notice procedures and audit their delivery records, since the employer remains legally liable for notice failures even when a TPA is contractually responsible for sending them, and request and retain delivery confirmation from the TPA for each notice sent.