You've probably heard COBRA duration explained like a memorized fact: 18 months after termination or a reduction in hours, sometimes 29 months, sometimes 36 months. That's not wrong, but it misses how COBRA really works inside an HR stack.
COBRA duration isn't a single countdown timer. It's a set of overlapping clocks that start, pause, extend, or end early, depending on events, payments, and which family member is exercising rights. If you manage COBRA as one "coverage end date," you're creating conditions for eligibility errors, notice issues, billing confusion, and avoidable employee frustration.
A better model: the "coverage runway"
Instead of thinking "COBRA lasts 18 months," think in terms of a coverage runway. It's a living set of rules that determines how long continuation coverage can last for each qualified beneficiary, given what's happened so far and what happens next.
That runway is controlled by three separate clocks. Most organizations only pay attention to the last one.
The three clocks that actually control COBRA duration
1) The election clock (60 days)
COBRA is time-bound from the start. Qualified beneficiaries generally get 60 days to elect COBRA (measured from the later of the election notice date or the date coverage would otherwise be lost).
What trips teams up: people often wait until the end of the window, especially if a medical event happens. When they elect late, COBRA is typically retroactive to the loss-of-coverage date, which creates real downstream work. Eligibility files may need retroactive adds. Claims may need reprocessing. Provider checks can fail during the gap, frustrating members who did everything "on time" according to COBRA rules.
2) The payment clock (45 days after election)
Election doesn't automatically mean active coverage. After someone elects COBRA, they typically have 45 days to make the initial premium payment. If the payment doesn't come in on time, coverage never becomes effective.
That's why you should model COBRA duration as a status lifecycle, not a date range. A clean operational state machine looks like this: Elected, Pending Payment, Active, Grace, Terminated. If your internal process (or vendor platform) treats "elected" as "enrolled," you'll end up showing coverage as active when it isn't, or worse, sending incorrect eligibility updates to carriers.
3) The maximum coverage period (18/29/36 months)
This is the "headline" clock everyone knows, and the numbers map to specific events. Termination or a reduction in hours starts an 18-month maximum. An 11-month disability extension brings the family to 29 months. A second qualifying event, or an initial event such as the covered employee's death, divorce or legal separation, Medicare entitlement, or a dependent child's loss of dependent status, sets a 36-month maximum. Even so, this clock isn't straightforward; it can be affected by extension rules and early termination triggers. The maximum period is important, but it's rarely the only thing controlling when COBRA ends.
The part most people miss: COBRA is person-specific
COBRA rights attach to qualified beneficiaries, the employee, spouse, and dependent children who were covered the day before the qualifying event. That sounds technical until you see how it plays out: different people in the same family can end up on different COBRA runways.
A few common scenarios drive this. After a termination or reduction in hours (an 18-month maximum), a second qualifying event such as divorce or legal separation can extend the spouse's and dependent children's coverage to 36 months from the original loss date, while the covered employee stays on the 18-month runway. A dependent child who ages out of the plan gets a continuation runway tied to that event, even while other family members run a different timeline. A disability extension can lift the whole family from 18 months to 29, but only when the Social Security Administration finds the beneficiary disabled before or within the first 60 days of COBRA coverage and the plan is notified within 60 days of that determination, before the 18-month period ends. Each case breaks the "single end date for the family" model.
This is one of the clearest reasons to track COBRA administration at the qualified beneficiary level, not just the subscriber or "family enrollment" level.
Early termination: the real driver of COBRA "duration" disputes
Most COBRA participants don't reach their maximum coverage period. Coverage frequently ends early because of triggers like non-payment or other disqualifying events. Many disputes start when the system mishandles a change and the story doesn't line up across payroll, carriers, and notices.
Common early termination triggers include: non-payment after the grace period (30 days for monthly premiums after the initial payment); the employer ceasing to maintain any group health plan; the qualified beneficiary becoming covered under another group health plan after election; or the qualified beneficiary becoming entitled to Medicare after electing COBRA. A qualified beneficiary who engages in fraud or other conduct that would justify terminating an active participant's coverage can also lose it early.
Two of these triggers carry conditions. The other-plan rule applies only when the new plan does not impose a preexisting condition exclusion, and because the ACA bars those exclusions, the condition is met for most group plans. Medicare entitlement only ends COBRA early when it happens after election. If the covered employee became entitled to Medicare before a later termination or reduction in hours, the spouse's and dependents' coverage runs to the later of 36 months from the entitlement date or the 18/29-month period from the event. Teams that treat Medicare as a one-way termination trigger get the duration wrong.
The operational challenge is that those events are often detected in different systems: billing platforms, HRIS changes, carrier eligibility files, and member attestations. If those sources don't reconcile cleanly, you either terminate too soon (triggering appeals) or too late (triggering billing confusion and eligibility clean-up).
COBRA duration is also a notice and documentation problem
Even if you calculate everything correctly, you still have to communicate it correctly. COBRA is one of those areas where compliance risk is as much about what you can prove as about what you intended.
When COBRA disputes escalate, the questions are painfully practical: What was the loss-of-coverage date? When was the election notice sent, and to whom? What did the notice say about deadlines and end dates? What payments were received, and when? If you can't produce a coherent timeline with timestamps and artifacts, you'll end up trying to reconstruct the truth from scattered systems and email threads, exactly the situation you want to avoid.
Self-funded plans: COBRA duration affects your financial reporting
For self-funded employers, COBRA participants are still on the plan. Their claims continue to hit the plan's experience, and that can influence large-claim tracking, stop-loss processes, and renewal narratives.
Add retroactive elections into the mix and it gets even messier: claims that looked like "runout" or uncovered utilization can swing back into the plan after a late election and timely payment. If finance and HR aren't aligned on COBRA status changes, you'll be explaining surprises instead of managing them. WellthCare™ is a Health-to-Wealth™ Benefit System that supports self-funded employers by providing compliance-grade recordkeeping and rewarding employees for verified preventive actions, helping reduce claims and making financial outcomes more predictable.
What the runway costs: the 102% and 150% premiums
The duration clocks carry different price tags. Plans may charge participants up to 102% of the plan's cost of coverage: the full premium plus a 2% administrative charge. The disability extension is the exception. For months 19 through 29, the plan may charge the disabled qualified beneficiary up to 150% of the plan's cost, while non-disabled family members on the extension stay at the 102% rate if the disabled member does not participate. For a self-funded employer, that gap matters. It shifts who bears the cost of the extra 11 months, and it shows up in premium reconciliation and participant statements. A billing engine that prices every COBRA month at one flat rate will misprice the disability extension, and participants will notice.
A practical fix: build a "COBRA runway ledger"
If you want COBRA duration to be consistently correct and defensible, treat it like a ledger: a set of auditable entries that explain exactly why coverage is active (or not) at any point in time. The point is to prevent the avoidable chaos that comes from a single "end date" field.
At a minimum, track the following for each qualified beneficiary:
- Qualifying event type, event date, and loss-of-coverage date
- The rule basis for the maximum period (18/29/36) and the computed end date
- Any extension events (for example disability-related rules), with timestamps and evidence
- Any early termination event, with a reason code and data source
- Status transitions (Elected, Pending Payment, Active, Grace, Terminated)
- Notice artifacts (what was generated/sent, when, and by what method)
When you model COBRA this way, you get a transparent, traceable process for duration, exactly what a benefits environment needs to balance employee experience with compliance rigor.
What to review in your current COBRA setup
If you're auditing your COBRA administration process or vendor, these five questions will quickly tell you whether your duration handling is sound or fragile:
- Do we track COBRA eligibility and end dates at the qualified beneficiary level (not just one family record)?
- Can we handle retroactive elections without breaking carrier eligibility, ID cards, and claims?
- Do we distinguish clearly between election and paid/active status?
- Do we have reliable inputs for early termination triggers, with clean documentation?
- Can we produce a defensible timeline of notices, payments, and eligibility changes on demand?
If more than one of those answers is "not really," your COBRA duration risk is likely operational rather than legal, and that's good news, because operational risk is fixable with better data design, better integrations, and clearer workflows.