Loading...
hr

COBRA Election Form

COBRA Election Form for collecting a beneficiary’s coverage choice, dependent selections, and requested effective date after a qualifying event. Use it to document the election clearly and route the form for premium setup.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Healthcare · Manufacturing · Professional Services · Retail · Education

Overview

This COBRA Election Form template captures the information needed when a qualified beneficiary chooses whether to continue group health coverage after a qualifying event. It organizes the election into clear sections for participant information, qualifying event details, coverage election, premium acknowledgment, and certification, so HR or benefits staff can process the response without chasing missing details.

Use this template when you need a signed record of the election decision, the requested effective date, and any dependent coverage selections. It works well after termination, reduction in hours, divorce, death, or other events that trigger continuation rights. The form is also useful when you want a clean audit trail and a consistent intake process across multiple plan types.

Do not use this template as a substitute for the required COBRA notice or plan explanation. It is also not the right form if the person is only asking general questions and has not yet received election materials. Keep the form focused on the decision itself, and avoid collecting unnecessary PII. If your process needs more detail, use conditional logic and progressive disclosure so only relevant fields appear.

Standards & compliance context

  • Collect only the PII needed to process the COBRA election and avoid asking for unrelated identifiers or sensitive data.
  • Use clear consent and disclosure language if the form stores contact details or other personal information for follow-up.
  • Maintain an audit trail of the election, signature date, and submitted coverage choices so the record can support benefits administration.
  • If the form is adapted for HR intake, include reasonable-accommodation prompts only when they are relevant to the workflow and keep them separate from the election decision.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Participant Information

This section identifies the qualified beneficiary and gives the benefits team the contact details needed to send notices and follow up on the election.

  • Participant Full Name (required)
  • Relationship to Employee (required)
  • Preferred Contact Email (required)
  • Preferred Contact Phone

Qualifying Event Details

This section records the event that triggered COBRA eligibility and anchors the form to the correct coverage timeline.

  • Qualifying Event Type (required)
  • Date of Qualifying Event (required)
  • Current Coverage End Date (required)
  • Additional Event Details
    Provide only the details needed to process the election. Do not include sensitive personal information unless specifically requested by HR.

Coverage Election

This section captures the actual continuation coverage choice, including which plan types and dependents are included.

  • Do you want to elect COBRA continuation coverage? (required)
  • Coverage Types to Continue
  • Covered Dependents to Include

Premium Acknowledgment

This section confirms that the beneficiary understands premium responsibility and records any payment preference or questions.

  • I understand that I am responsible for paying the full COBRA premium, including any applicable administrative fee. (required)
  • Preferred Payment Method
  • Questions or Notes

Effective Date and Certification

This section locks in the requested effective date and signed certification so the election can be processed and audited.

  • Requested Effective Date (required)
    If applicable, this should align with the COBRA election rules and HR guidance.
  • I certify that the information provided is true and complete to the best of my knowledge. (required)
  • Signature (required)
  • Date Signed (required)

How to use this template

  1. 1. Add your plan-specific instructions, election deadline language, and any required disclosure text before sharing the form.
  2. 2. Configure the participant and qualifying event fields with the right validation, using date pickers for dates and required fields only where the information is truly needed.
  3. 3. Assign the form to HR or benefits staff for distribution, then send it to the qualified beneficiary with a clear note about what happens after submission.
  4. 4. Review the coverage election, dependent selections, premium acknowledgment, and certification for completeness before accepting the form into the audit trail.
  5. 5. Route the completed form to benefits administration, payroll, or your case workflow so coverage can be updated and payment setup can begin.

Best practices

  • Use conditional logic to show dependent fields only when the beneficiary elects a coverage type that includes dependents.
  • Mark required and optional fields clearly so the person completing the form knows exactly what is needed.
  • Use a date picker for qualifying event date, coverage end date, requested effective date, and signature date instead of free-text entry.
  • Keep the form limited to data needed for the election and administration of coverage, in line with GDPR data minimization and minimum-necessary principles.
  • Include a plain-language line that explains what happens after submission, including who reviews the form and how coverage changes are processed.
  • Offer an anonymous submission option only if your workflow allows it; otherwise make the identity requirement explicit to avoid confusion.
  • Capture the certification and signature in a way that preserves the audit trail and shows when the election was made.

What this template typically catches

Issues teams running this template most often surface in practice:

Missing or unclear qualifying event details that make it hard to confirm eligibility.
Using a free-text field for dates, which creates validation problems and inconsistent records.
Leaving the coverage election ambiguous by not specifying which coverage types were selected.
Forgetting to capture dependent information when the election includes family coverage.
Omitting the premium acknowledgment, which can lead to later disputes about payment responsibility.
Failing to include a signature date, which weakens the record of when the election was made.
Collecting more personal data than needed for the election and administration process.

Common use cases

Benefits Administrator After Termination
A benefits administrator sends the form to a former employee after a termination event and uses the completed record to confirm whether medical, dental, or vision coverage is being continued.
HR Generalist After Divorce Notification
An HR generalist provides the form to a spouse who became eligible after divorce and needs a signed election record with the requested effective date and contact details.
COBRA Vendor Intake Workflow
A COBRA administrator uses the template as the intake document that feeds a downstream case system, keeping the election, dependent selections, and premium acknowledgment in one place.
Multi-Plan Employer Benefits Team
A benefits team customizes the coverage types and conditional logic so the same form can handle medical, dental, and vision elections without showing irrelevant fields.

Frequently asked questions

Who should use this COBRA Election Form?

Use this form for employees, spouses, dependents, or other qualified beneficiaries who need to elect continuation coverage after a qualifying event. It is designed to record the election itself, not to explain plan benefits in detail. HR or benefits administrators can use the completed form to confirm the coverage choice and start the next administrative step.

When should this form be sent and returned?

Send it after a qualifying event has been identified and the beneficiary is eligible to make an election. The form should be returned within the election window set by the plan and applicable notice rules. Include the coverage end date and requested effective date so the beneficiary can make a timely, informed choice.

What information does this template collect?

It collects participant identification, relationship to the employee, contact details, qualifying event details, coverage election choices, dependent selections, premium acknowledgment, payment preference, and certification with signature. The fields are focused on what is needed to process the election and maintain an audit trail. It does not need unrelated personal data, which helps support data minimization.

Does this form replace the COBRA election notice?

No. The election form records the beneficiary’s decision after they have received the required notice and plan information. If your process also needs the notice, keep that as a separate document or section so the election form stays focused. That separation also makes it easier to track what was disclosed and when.

How often is this form used?

It is used each time a qualifying event triggers COBRA eligibility and a beneficiary chooses whether to continue coverage. It is not a recurring monthly form. If multiple family members are eligible under the same event, each qualified beneficiary may need their own election record depending on your plan workflow.

Can this template be customized for different plan types?

Yes. You can adjust the coverage types, dependent fields, payment options, and notes section to match your medical, dental, vision, or other continuation coverage rules. Use conditional logic so only relevant fields appear for the selected plan or beneficiary type. That keeps the form shorter and easier to complete.

What are common mistakes when using a COBRA election form?

Common mistakes include leaving the qualifying event details incomplete, using free-text fields where a date picker or multi-select would be clearer, and failing to capture a signature date. Another frequent issue is asking for more personal data than the form needs. A clear confirmation line about what happens after submission also helps avoid confusion.

How should this form connect to HR or benefits systems?

The completed form can feed a benefits administration workflow, case management record, or document archive. If you use integrations, map the coverage election, effective date, and dependent selections to the downstream system fields. Keep the audit trail intact so you can show what was submitted and when.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A shift handoff is the structured transition between the outgoing and incoming crew at the change of a shift. It covers what was done, what wasn't done, what...
Related guides

Ready to use this template?

Get started with MangoApps and use COBRA Election Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?