Getting Comfortable — Tell Us About Your Team

• What's your title and primary responsibility for benefits/COBRA decisions? Options: HR Director, Benefits Manager, Third‑Party Administrator (TPA), Payroll Lead, CFO/Finance, Other
• How many employees does your organization have (total headcount)? Options: 100–249, 250–499, 500–999, 1,000–4,999, 5,000–10,000
• Who typically signs off on selecting a COBRA vendor at your company? (select all who apply) Options: HR Director, Benefits Manager, Finance/CFO, Legal/Compliance, Broker/Consultant, Company Executive/CEO, Other
• How is COBRA handled today at your company? Options: Fully internal, Fully outsourced to a vendor, Shared between us and a vendor, Handled ad hoc by broker, We don’t have a formal process
• Roughly how many qualifying events do you process in an average year? Options: 0–50, 51–150, 151–500, 501–2,000, 2,000+
• Which benefits/HRIS systems are in use that touch eligibility and qualifying events? (pick all that apply) Options: Workday, ADP, BambooHR, UKG/ Kronos, Oracle HCM, SAP SuccessFactors, Paylocity, Custom/Proprietary, No HRIS / manual
• In your own words, what is the single biggest constraint on your team’s ability to manage COBRA well?

What Keeps You Awake About COBRA?

• If one COBRA mistake landed you in a compliance audit tomorrow, what would that mean for your team?
• Have you experienced a late notice, missed election, audit finding, or carrier dispute in the last three years? Options: Yes — late notice, Yes — missed election, Yes — audit finding, Yes — carrier dispute, No
• When an issue occurred, what were the immediate consequences for HR, finance, or the participant?
• How often do you have a 'near miss' where a notice deadline was narrowly met or an enrollment almost failed? Options: Weekly, Monthly, Quarterly, Rarely, Never
• How does COBRA-related risk affect your appetite for handling it internally vs. outsourcing? Options: We prefer to keep control, We’d rather outsource to reduce risk, Depends on cost, Unsure
• How long has this level of concern been present for your team? Options: Less than 6 months, 6–12 months, 1–3 years, 3+ years

Where the Process Breaks Down — The Real Bottlenecks

• Which step in the COBRA lifecycle causes you the most anxiety or manual firefighting? Options: Event intake / detection, Eligibility determination, Notice generation/mailing, Participant enrollment processing, Premium invoicing/collections, Carrier remittance, Terminations/reconciliations, Reporting/audits
• Walk me through the typical path from a qualifying event in your HRIS to the participant receiving an election notice—where do you see the most handoffs?
• Which of these root causes best explains why that step fails when it does? Options: Delayed feeds from HRIS, Poor data quality, Manual CSV uploads, Lack of staff bandwidth, Complex plan rules, Vendor/Carrier mismatches, Other
• When deadlines are missed, who ends up owning the remediation work? Options: Internal HR, Benefits broker, Finance, IT, Vendor, Shared
• How much time (team hours) does your organization spend monthly on COBRA exceptions, reconciliations, and manual follow‑ups? Options: <10 hours, 10–25 hours, 26–50 hours, 51–100 hours, 100+ hours
• Can you share a brief example of a recent breakdown and how it was resolved?

What Would Change the Game for You?

• If COBRA simply happened without manual intervention, what would your team do with that time and stress that would feel meaningful?
• Which outcomes would make you feel confident you've chosen the right solution? (pick up to 3) Options: 100% on-time notices, Higher participant enrollment rates, Faster premium collections, Zero compliance audit findings, Clear audit trail/reporting, Simpler reconciliations
• What specific KPIs or SLAs would you want the vendor to commit to? Options: Notice delivery within 14 days, Enrollment processing within 3 business days, Payment posting within 24 hours, Carrier remittance within agreed schedule, Error rate <1%
• What's an acceptable remediation plan if an SLA is missed (e.g., credits, root cause, timeline)? Options: Billing credit, Corrective action plan + root cause, Escalation to leadership, Contract termination clause, Other
• How would you measure success at 30/60/90 days after switching to a new COBRA vendor?
• What worries you most about changing vendors or moving processes off‑site? Options: Loss of control, Data security, Transition errors, Cost, Employee/broker pushback, Other

Integrations, Data, and Security — The Unsexy Make‑or‑Break

• How confident are you that your HRIS can be a reliable single source for every qualifying event without manual intervention? Options: Very confident, Somewhat confident, Not confident, Don't know
• Which integration methods would you prefer us to support for event intake and roster updates? (select all that apply) Options: Real‑time API/Webhooks, Daily SFTP/CSV batch, Manual CSV upload, HRIS native connector (prebuilt), Email-triggered workflows, Other
• What are the must-have data fields or validations you require from any integration feed? Options: Employee name, SSN/Last4, DOB, Event type and date, Plan identifiers, Dependent info, Coverage effective/termination dates, Other
• Do you have security, compliance, or audit requirements we must meet (e.g., SOC 2, HIPAA, encryption standards)? Options: SOC 2 Type II, HIPAA, Encryption at rest/transit, Data residency, Vendor security questionnaire required, None / unsure
• Would your team require SSO for participant or HR portals, and which providers do you support? Options: Yes — SAML/SSO, Yes — OIDC, No SSO required, We use Azure AD, We use Okta, Other
• If integrations are the biggest risk, what's your preferred approach: pilot a subset of populations, parallel run with current process, or full cutover? Options: Pilot subset, Parallel run, Full cutover, Unsure
• Anything unique about your data flows or security controls we should know up front?

Money, Carriers, and Reconciliation — Who Owns What?

• Who in your organization is ultimately accountable for carrier remittance accuracy? Options: Finance, Benefits/HR, Broker, COBRA Vendor, Shared
• How are participant premiums collected today? Options: Payroll deduction (active), Direct bill mailed checks, Online payment portal, Auto‑debit/ACH, No collections — employer subsidizes, Other
• What’s your typical remittance cadence to carriers and how strict is that timing? Options: Daily, Weekly, Monthly, Quarterly, On receipt
• How do you handle unapplied or late participant payments and refunds? Options: Automatic refund, Hold and reconcile, Apply to next period, Escalate to finance, Other
• What reconciliation pain points would you want eliminated (e.g., mismatched premiums, carrier reporting, stale receivables)?
• Would you accept vendor-led carrier remittance, vendor-managed lockbox, or require funds to flow through your finance team? Options: Vendor remits directly, Vendor lockbox with remittance, Funds through our finance team, Hybrid — depends on carrier
• How often do carrier disputes or misremittances happen, and who resolves them? Options: Weekly — we resolve, Monthly — vendor resolves, Quarterly, Rarely, Never

Timing, Decision, and Next Steps — What Would It Take to Move Forward?

• What would make you move from 'exploring' to 'committed' on a new COBRA solution this quarter?
• Who are the stakeholders that need to be involved before a contract can be signed? (select all that apply) Options: HR Director, Benefits Manager, Finance/CFO, Legal/Compliance, Broker, IT/Integration Lead, Other
• What procurement or legal hurdles typically slow down vendor selection here? Options: Security review, Contract terms, Budget approval, Broker approvals, Implementation resource availability, Other
• Which proof points would you need to approve a pilot? (pick all that matter) Options: Reference customers in our industry, SLA guarantees, Demo with our HRIS, Compliance audit report / SOC2, Sample notice templates, Pilot success metrics
• What is your ideal timeline from decision to go‑live? Options: <30 days, 30–60 days, 61–90 days, 90+ days, No fixed timeline
• If you could name one non‑negotiable for a pilot or initial implementation, what would it be?
• Would you like us to prepare a short pilot scope and technical questionnaire to share with your IT/broker team? Options: Yes — send pilot scope, Maybe — need internal alignment, No — not ready

• Experience Kickoff & Current-State Alignment
• Notice & Election Workflow Walkthrough — Termination Scenario
• Enrollment & Premium Flow Walkthrough — Election to Remittance
• Edge Cases, Exceptions & Integration Resilience
• Validation, Acceptance Criteria & Pilot Plan

• Ensure state-specific compliance behavior aligns with the customer's multi-state footprint and regulator obligations.
• Validate the enrollment lifecycle steps and that enrollment records flow correctly from election to carrier enrollment.
• Confirm invoice format, payment methods, and reconcilement procedures satisfy the customer's finance and carrier needs.
• Agree on SLAs for payment posting, exception handling, and remittance timing.
• Seller to deliver sample invoice PDF, payment receipt flow, and a sample carrier remittance file aligned to customer specs.
• Customer finance contact to confirm payout cadence and remittance bank details or carrier file format requirements.
• Seller to document reconciliation processes and exception escalation paths for customer review.
• Customer to nominate a reconciliation owner and provide example carrier reports used today for matching.
• List & Prioritize Customer Edge Cases
• Confirm satisfactory handling for the customer's highest-risk edge cases with documented runbook outcomes.
• Agree on integration error alerting, remediation ownership, and SLA commitments.
• Introductions & Objectives
• Seller to produce an edge-case runbook documenting steps, templates, and timelines for each prioritized scenario.
• Customer to provide a ranked list of the top 10 historical exceptions and any state-specific nuances to validate.
• Seller to provide integration error examples and proposed SLA targets for customer IT approval.
• Customer IT to supply API/SFTP test credentials or confirm a sandbox export schedule for integration testing.
• Present Proposed Acceptance Criteria & KPIs
• Achieve mutual agreement on measurable acceptance criteria and KPI thresholds for the pilot.
• Define a clear, timeboxed pilot with assigned owners and documented success tests.
• Obtain customer commitment to provide data, validators, and sign-off decision-makers for the pilot.
• Seller to create and share a pilot plan document with test cases, KPI dashboards, reporting cadence, and evidence requirements.
• Customer to assign pilot approvers (HR, benefits, finance) and confirm pilot population and start date.
• Seller to provision a sandbox/test environment and schedule the initial pilot run with access details.
• Customer to confirm internal communication recipients and frequency for pilot status updates and compliance artifacts.
• Produce a single-sentence current-state description that all stakeholders accept.
• Agree on quantified consequences of the current state (risk, cost, hours) tied to at least one recent example.
• Define the future-state outcomes in operational terms for the Solution Experience to prove.
• Obtain a confirmed list of artifacts and assigned owners before the live walkthroughs.
• Customer to deliver sample qualifying-event export(s), HRIS field mapping, recent notice examples, and carrier remittance specs to the seller.
• Seller to prepare tailored walkthrough scripts that map each sample event to expected notice, enrollment, and remittance outcomes.
• Schedule the sequence and owners for the upcoming live walkthrough meetings and provision test access.
• Customer to designate internal validators (HR, benefits, finance) who will confirm acceptance criteria during live sessions.
• Seller to log any mapping adjustments and produce an updated HRIS field mapping document.
• Recap Current State & Desired Notice Outcome
• Confirm the intake-to-notice mapping is accurate for the termination scenario.
• Validate that the generated notice content, timing, and delivery evidence meet compliance and customer expectations.
• Identify and assign remediation for any data gaps or template edits discovered during the simulation.
• Seller to provide the generated sample notice PDF, delivery log, and timeline artifact for the simulated event.
• Customer to approve or provide redlines for notice wording and required fields.
• Customer to supply an additional sample record if address/email validation or bilingual notices need to be tested.
• Recap Notice Acceptance & Expected Enrollment Outcome
• Simulate Participant Election & Enrollment
• One-Sentence Current State
• Show Runbook Handling for Each Edge Case
• Pilot Scope, Duration & Success Tests
• Event Intake from HRIS
• Invoice Generation & Payment Options
• Owner RACI & Sign-off Process
• Explicit Consequence
• Integration Error Handling & SLAs
• Notice Timeline & Template Mapping
• Payment Posting, Reconciliation & Exception Handling
• Define Future-State Outcomes
• Schedule Pilot Runs & Communication Plan
• Simulated Notice Generation and Delivery
• State Mini-COBRA Variations & Compliance Overrides
• Final Validation & Commitment
• Customer Validation Checkpoint
• Artifacts & Pre-work Confirmation
• Carrier Remittance Example

• Automated HRIS Qualifying-Event Intake
• Generate and Mail COBRA Election Notices (14-day)
• Process Participant COBRA Elections and Enrollment
• Premium Invoicing and Online Payment Portal
• Collect Participant Premium Payments (ACH/card)
• Carrier Premium Remittance and Reconciliation
• Coverage Termination for Non-Payment
• Handle State Mini-COBRA Notices and Compliance
• Audit-Ready Compliance Documentation Delivery
• Real-Time Employer and Participant Status Dashboard
• Monthly Participation and Financial Reporting Package
• Participant Call Center and Email Enrollment Support

Automated HRIS Qualifying-Event Intake

• Which HRIS or payroll/benefits systems are in use that will supply qualifying events? Options: Workday, ADP, UKG/ Kronos, Paylocity, BambooHR, Oracle/PeopleSoft, Other (please name)
• How are qualifying events currently delivered today? Options: Real-time API/webhook, Daily batch SFTP/CSV, Manual spreadsheet upload, Email/phone notifications, No current delivery (manual logging)
• What data fields are required for each event (e.g., employee SSN, DOB, event type, event date, termination reason)? List required and optional fields.
• What is the expected volume of qualifying events per month? Options: Less than 50, 50-200, 200-1,000, More than 1,000
• Who will be the primary source(s) of event data (HR team, payroll vendor, benefits broker, TPA)? Options: HR team, Payroll vendor, Benefits broker, Third-party administrator (TPA), Other
• What SLAs do you require for event ingestion acknowledgement and error handling? Options: Real-time/within 1 hour, Same business day, Next business day, 48 hours, Custom (please specify)

Generate and Mail COBRA Election Notices (14-day)

• Do you require notices printed and mailed, emailed, or both? Options: Print & Mail, Email only, Both print & email, Electronic-only (employer/participant portal)
• Do you have custom legal or plan-language that must appear on election notices? Options: Yes, No
• Are there multiple notice templates required based on event type (termination, reduction in hours, divorce, death, etc.)? Options: Yes, No
• Who owns approval of notice templates and timing (employer legal, broker, carrier)? Options: Employer legal/HR, Broker, Carrier, Customer success/vendor
• Do you have address validation or NCOA (change-of-address) requirements before mailing? Options: Yes, No, Not sure
• What are your acceptance criteria for notice delivery SLA (e.g., notice generated within X days of event)?

Process Participant COBRA Elections and Enrollment

• Should participants be able to elect coverage via phone, online portal, mail, or all of the above? Options: Online portal, Phone (agent-assisted), Paper/mail, Email response, All of the above
• What enrollment data must be captured at election (plan selection, dependents, effective date, premium tier, beneficiary info)?
• Do you require real-time enrollment feeds back to the employer HRIS or carrier enrollment systems? Options: Yes - real-time API, Yes - daily batch, No - manual report
• Are carrier enrollment files/formats standardized or do carriers require custom formats? Options: Standardized (EDI/standard file), Carrier-specific custom files, Manual carrier portals
• Who is authorized to review or change participant elections (participant, broker, employer rep)? Options: Participant only, Participant + employer HR, Participant + broker, Participant + vendor support
• Do you need re-enrollment or retroactive enrollment handling processes defined? Options: Yes, No

Premium Invoicing and Online Payment Portal

• Do you want branded participant-facing payment portal and invoices? Options: Yes - employer-branded, Yes - vendor-branded, No preference
• What payment frequencies and billing cycles are required (monthly in advance, monthly in arrears, custom)? Options: Monthly in advance, Monthly in arrears, Quarterly, Custom (please specify)
• Should invoices include itemized plan/premium breakdown and carrier remittance mapping? Options: Yes, No
• Will participants receive electronic invoices only or paper invoices as well? Options: Electronic only, Paper only, Both
• Are there requirements for invoice timing relative to election date (e.g., first invoice due X days after election)?
• Do you require automated reminders for unpaid invoices and configurable reminder cadence? Options: Yes, No

Collect Participant Premium Payments (ACH/card)

• Which payment methods do you want to accept from participants? Options: ACH (bank debit), Credit/debit card, Check, Money order, Other
• Do you require saved payment methods for recurring billing? Options: Yes, No
• What PCI/PII or tokenization standards must be met for card/ACH storage and processing? Options: PCI-DSS required, Tokenization via payment gateway, No card storage, gateway only
• Do you need configurable grace periods and late fee rules for missed payments? Options: Yes, No
• What percentage of participants do you expect to pay by ACH vs. card vs. other? Options: Predominantly ACH, Predominantly card, Mixed (~50/50), Unknown
• Are refunds and payment reversals required to be handled by the system? Options: Yes, No

Carrier Premium Remittance and Reconciliation

• Do carriers require individual participant-level remittance files or pooled remittances? Options: Participant-level detail, Pooled remittance with mapping file, Carrier portal manual payment
• What carrier file formats or remittance standards are required (EDI, CSV, ACH with detail)? Options: EDI/standard format, Custom CSV spec, Carrier portal entry, Other
• What frequency of remittance is required to carriers (daily, weekly, monthly)? Options: Daily, Weekly, Monthly, On-demand
• Do you require a reconciliation process to match participant payments to carrier remittances? Options: Yes - automated, Yes - manual review, No
• Who is the payment recipient for carrier remittances (employer, carrier, TPAs), and do they require payee-specific setup? Options: Carrier, Employer, TPA, Other (specify)
• What SLA do you require for identifying and resolving remittance discrepancies? Options: 48 hours, 5 business days, 15 business days, Custom

Coverage Termination for Non-Payment

• What non-payment rules govern termination (number of missed payments, grace period length)? Options: 30-day grace, 60-day grace, After X missed payments (specify), Employer-defined policy
• Do you require automated termination notices to participants and carriers, and at what stages? Options: Pre-termination notice, Termination notice, Final accounting
• Should termination actions be reversible (reinstatement on back payment) and under what conditions? Options: Yes - automatic on full payment, Yes - manual review required, No
• Are there state-specific rules for termination we must enforce in addition to federal COBRA? Options: Yes - list states, No, Not sure
• Who approves termination actions (employer HR, vendor, broker)? Options: Employer HR, Vendor/Cobra administrator, Broker, Automated per policy
• Do you require retainment of terminated participants’ records for audit and appeals? If so, retention period.

Handle State Mini-COBRA Notices and Compliance

• Which states with mini-COBRA rules apply to your population? Options: California, New York, New Jersey, COBRA not applicable, Other (list)
• Do state-specific notice language and deadlines differ from federal requirements for these groups? Options: Yes - needs mapping, No - same as federal, Unsure
• Do you require automatic regulatory updates for new or changed state rules? Options: Yes, No
• Are there multi-state employees or participants whose notices must follow the most protective jurisdiction? Options: Yes, No, Unknown
• Who will validate state notice compliance and sign-off on templates (employer legal, broker, vendor)? Options: Employer legal, Broker, Vendor compliance team, Other
• Do carriers in any states require additional filings or notices beyond participant communications? Options: Yes, No, Unknown

Audit-Ready Compliance Documentation Delivery

• What level of documentation is required for audits (notice timestamps, delivery proof, enrollment confirmations)? Options: Full audit trail with timestamps, Summary reports only, Custom (specify)
• How long must compliance documentation be retained (years)? Options: 1 year, 3 years, 6 years, Employer-specified
• Do you require automated exportable audit packages for regulators or internal audit teams? Options: Yes, No
• Who should have access to audit documentation (employer admins, auditors, broker)? Options: Employer admins, Internal auditors, Broker, Vendor compliance only
• Do you require periodic compliance attestations or SLA reports as part of audit deliverables? Options: Yes, No
• Are there encryption or privacy controls required for stored audit artifacts? Options: Encrypted at-rest, Role-based access controls, PII redaction, Other

Real-Time Employer and Participant Status Dashboard

• Which user roles need dashboard access (HR admins, benefits managers, brokers)? Options: HR admins, Benefits managers, Brokers, TPA, Auditors
• Which KPIs are most important on the dashboard (notice timeliness, open election rate, payment rate, remittance lag)? Options: Notice timeliness, Election/enrollment rate, Payment collection rate, Remittance accuracy, Custom KPIs
• Do you require real-time alerts for missed SLAs, failed integrations, or payment failures? Options: Yes - email alerts, Yes - SMS/push, Yes - in-dashboard only, No alerts
• Should the dashboard support downloadable reports and scheduled email digests? Options: Yes - downloadable, Yes - scheduled emails, No
• Do you need role-based visibility or row-level data restrictions on the dashboard? Options: Yes, No
• Are integrations required to populate the dashboard (HRIS, carrier status feeds, payments gateway)? Please list.

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• Business Associate Agreement (BAA)
• Fee Schedule & Commercial Terms
• Payment Authorization (ACH / Payment Portal)
• Broker Authorization & Commission Agreement
• Integration & Data Access Agreement
• Notice & Template Approval
• Acceptance Criteria & Go‑Live Signoff
• Indemnification & Insurance Schedule
• Regulatory Compliance & Audit Rights

• Weekly Compliance KPI Review
• Incident Triage & Root Cause Analysis
• Backlog Grooming & Continuous Improvement
• Participant Experience Audit
• Quarterly Executive Compliance & Risk Review

• Create portal UI ticket(s) for top two UX defects and assign engineering owner.
• Maintain a prioritized backlog where items are ranked by compliance risk and customer value.
• Ensure each prioritized item has clear acceptance criteria and owner.
• Define a realistic short‑term roadmap for delivering top risk‑reducing items.
• Eliminate blockers by confirming engineering/ops dependencies and timelines.
• Convert agreed top backlog items into tracked tickets with acceptance criteria and owners.
• Schedule quick-win deployments and communicate change windows to the customer.
• Assign engineering champions for multi‑sprint projects and identify required resources.
• Update backlog status in the shared workspace and notify stakeholders of re-prioritization.
• Pre-read & Sample Case Review
• Confirm participant touchpoints that are causing enrollment/payment drop-offs and rank them by impact.
• Agree on concrete remediation actions and measurable success criteria for each change.
• Define a validation cohort and monitoring plan to confirm improvements post-deployment.
• Reduce expected participant support volume by addressing top UX friction points.
• Update the notice template(s) and prepare A/B test variants for approval.
• Pre-read & Data Validation
• Implement enhanced payment retry rules and document expected change in payment rates.
• Schedule a post‑deployment participant validation run and collect success metrics.
• Executive One‑Sentence Current State
• Obtain executive alignment that the compliance posture is acceptable or agree on mitigation plan and timelines.
• Approve any required budget or resourcing changes to address systemic risk.
• Authorize contractual or SLA amendments when required and define next steps.
• Ensure regulatory changes are triaged and assigned for implementation.
• Produce and distribute the executive one‑pager and appendices with evidence and remediation timelines.
• If required, prepare a contract amendment or SLA notice for customer's legal review.
• Allocate budget/resources for approved remediation projects and notify engineering/ops leads.
• Schedule follow-up checkpoints for any unresolved high-risk items before the next quarter.
• Agree on validated KPI values and their source of truth for the period under review.
• Identify any KPI breaches or anomalies requiring remediation and assign owners with SLAs.
• Ensure customer confirms KPI accuracy and understands consequences of any deviations.
• Produce action list for the week with clear owners and deadlines.
• Produce and share an audit packet (raw exports + calculations) for the reviewed period.
• Open incident tickets for any KPI breaches and assign owners with target resolution dates.
• Update the shared dashboard and note the chosen 'source of truth' for each KPI.
• Schedule follow-up verification meeting for any remediations due within the week.
• Incident Summary & Impact
• Contain customer impact and stop further exposure within agreed SLAs.
• Determine a root cause that ties directly to the incident evidence.
• Agree on a corrective action plan with owners, timelines, and verification criteria.
• Define the participant and carrier communications required and owner for each.
• Create incident remediation ticket(s) with priority, owner, and target resolution date.
• Execute agreed immediate mitigations (e.g., re-send notices, manual remits) and document steps taken.
• Notify legal/compliance and the customer's benefits broker if regulatory exposure meets threshold.
• Schedule a post-remediation verification session and assemble evidence for closure.
• Review Open Backlog Items
• Consequence Framing
• Prioritize by Risk, Impact, Effort
• One‑Sentence Current State
• Show the Evidence
• KPI Trends & Variance Analysis
• Root Cause Workshop
• Define Acceptance Criteria & Success Metrics
• Consequence Review
• Live Walkthrough of Portal & Notices
• Material Incidents & Remediation Status
• Regulatory Changes & Risk Outlook
• KPI Deep Dives — Notice Timeliness
• Plan Quick Wins vs. Projects
• Immediate Mitigations & Communication Plan
• Payment Failure Analysis