Tell Us the Story That Brought You Here

• In a sentence or two, what recent enrollment event or audit finding prompted you to explore a new platform?
• How large is the employee population affected by this issue? Options: 200–1,000, 1,001–5,000, 5,001–20,000, 20,001–50,000, 50,001–250,000
• What error rate did your audit reveal (percent of elections with wrong plan codes, missed dependents, or coverage gaps)? Options: <1%, 1–2%, 2–4%, 4–8%, >8%, Unknown
• Who did the audit impact most—executive leadership, HR team operations, employees, carriers, or a mix? Tell us which and why. Options: Executives, Benefits/HR team, Employees, Carriers, Mixed/All of the above
• How did this issue make your HR team feel or behave in the weeks after (e.g., crisis mode, manual fixes, policy changes)?
• If there was one moment during that cycle that felt worst—what happened and what made it stick in your mind?

If This Happens Again, What’s the Real Cost?

• Imagine the same enrollment errors repeat at next open enrollment—what would be the real consequences for your team and the business?
• Which of these outcomes concern you most if the problem repeats? Options: Employee loss of coverage, Executive escalations/ERISA risk, Increased manual headcount, Carrier billing disputes, Payroll mismatches, Reputational damage
• How much time does your HR team currently spend on post-enrollment corrections during a typical cycle? Options: <10 hours/week, 10–40 hours/week, 40–80 hours/week, >80 hours/week, We don't track this
• What financial or operational KPIs would you point to as being directly affected by enrollment errors? Options: Cost of manual processing, Carrier reconciliation costs, Employee support call volume, Time to resolve discrepancies, Loss of coverage claims, Other
• Which stakeholders would push hardest for immediate change if the risk increased—HR leadership, legal, finance, payroll, or someone else? Options: HR leadership, Legal/Compliance, Finance, Payroll/HRIS, COO/CEO, Other
• How do these risks make you feel about running another enrollment without changing the process? Options: Very anxious, Concerned but hopeful, Neutral, Confident

Who Really Owns Accuracy (And Is That Working?)

• Who do you believe has final accountability for enrollment accuracy today—and why might that ownership be unclear or risky?
• Which roles are involved in day-to-day enrollment ops and corrections? Options: Benefits Manager, HRIS Admin, Payroll Lead, HR Generalists, Broker/Consultant, Carrier Rep, Other
• How do decisions flow when there’s a mismatch between your system, payroll, and the carrier (e.g., who investigates, who signs off on fixes)?
• When a carrier or payroll mismatch surfaces, what’s your current escalation path and average resolution time? Options: Same day, 1–3 days, 4–10 days, >10 days, No formal path
• Are there internal handoffs that routinely create delays or data loss? Tell us one vivid example.
• If you could change one thing about ownership or governance to reduce errors, what would it be?

Where the Data Breaks: Feeds, Files, and Surprises

• What kinds of carrier feed or payroll connector failures have you seen (select all that apply)? Options: Wrong plan codes, Missing dependents, Late or missing deduction files, Mapping mismatches, Duplicate records, Format/schema changes, No failures observed
• Which carriers or payroll systems in your environment tend to be the most fragile or opaque?
• What monitoring or reconciliation do you currently run between your enrollment system and carriers/payroll (e.g., daily match rates, weekly audits)? Options: Daily match reports, Weekly reconciliation, Monthly audits, Ad-hoc checks, None
• What typical match rate would you accept before feeling confident about go‑live with a carrier feed? Options: >99%, 98–99%, 95–98%, 90–95%, <90%
• Tell us about a time you traced an error back to a mapping or timing issue—what was the root cause and how was it fixed?
• How comfortable is your team performing end‑to‑end tests with carriers and payroll vendors—do you have credentialed test accounts and contacts? Options: Fully set up with test contacts, Partially set up, Need help provisioning tests, No test capability

The Employee Experience That Keeps You Up at Night

• When employees called about incorrect insurance cards or missing coverage, what were the most common reactions and questions they asked?
• How would you describe mobile and hourly worker completion rates in your last enrollment window? Options: >85% mobile completion, 70–85%, 50–70%, <50%, We don't track by segment
• Which employee segments worry you most for digital enrollment completion (select all that apply)? Options: Hourly on-site workers, Remote workers, Non-English speakers, Employees without corporate email, Older demographics, New hires
• What kind of employee communications have historically reduced confusion or calls—automated reminders, SMS, manager outreach, or something else? Options: Automated email reminders, SMS/text messages, Manager-led briefings, In-person kiosks, Video guides, Other
• Tell us about a time the user experience directly prevented an error or, conversely, created one. What changed as a result?
• How important is a mobile-first employee flow to your success criteria for a new platform? Options: Mission critical, Very important, Nice to have, Not important

What a Pilot Must Prove to Stop the Panic

• If we ran a pilot tomorrow, what single outcome would convince you it's safe to replace your current process?
• Which pilot acceptance metrics would you require (pick all that apply)? Options: Carrier match rate threshold, Payroll file integrity check, Employee completion % by cohort, No production coverage gaps, Successful feed reconciliation, SLA for issue resolution
• What pilot cohort size, employee mix, and duration feel realistic to validate carriers, payroll, and mobile UX? Options: Small cohort (50–200) for 2–4 weeks, Mid cohort (200–1,000) for 4–8 weeks, Large cohort (1,000+) for 8+ weeks, Other
• Which HRIS and payroll systems must be included in the pilot to make it meaningful?
• What internal stakeholders must sign off on pilot success before you consider rollout? Options: Benefits/HR, Payroll/HRIS, Finance, Legal/Compliance, Executive sponsor, Carrier reps
• What would be an acceptable number of open issues at pilot close (e.g., only cosmetic UX items vs. any data mismatches)? Options: Zero data mismatches, Only non-critical cosmetic items, Some data items with mitigation plan, Open items OK if SLA exists

Tradeoffs, Timelines, and Who Actually Does the Work

• What timeline are you targeting for pilot start and full rollout, and what internal deadlines drive that schedule? Options: Pilot in <1 month, Pilot in 1–2 months, Pilot in 2–4 months, Longer/Undecided
• Which tasks do you expect your team to own versus tasks you'd want the vendor to own? Options: Data mapping, Carrier test provisioning, Employee communications, Eligibility rule configuration, Payroll file testing, Issue triage/escalation
• Do you have an internal project sponsor or steering committee for benefits tech projects? Options: Yes—executive sponsor, Yes—cross-functional committee, No, just HR lead, Not yet identified
• What internal constraints could slow deployment (e.g., IT bandwidth, security reviews, carrier SLAs, union agreements)?
• How would you prefer responsibility and communication to be structured during the pilot (single point of contact, weekly calls, shared dashboard)? Options: Single SPOC + weekly calls, Weekly cross-functional working sessions, Shared realtime dashboard, As-needed emails/calls, Combination
• What would make your team feel confident that responsibilities are clear and won’t produce duplicate work?

Red Lines, Escalations, and Concrete Success Signals

• What carrier accuracy percentage would you require to sign off on pilot success (be specific)? Options: >=99.5%, 99–99.5%, 98–99%, 95–98%, <95%
• How quickly must payroll deductions reconcile after enrollment to avoid manual corrections? Options: Same pay period, Next pay period, Within 2 pay periods, Longer is acceptable
• What employee completion rates (overall and mobile/hourly segments) will you accept before rollout? Options: Overall >=85% and mobile>=80%, Overall 75–85%, Overall 60–75%, No specific threshold
• If a carrier or payroll mismatch is discovered post go‑live, what escalation path and SLA would you require?
• Which dashboards or reports would you need in real time to feel in control during launch? Options: Carrier match rate dashboard, Payroll file validation report, Employee completion by cohort, Open issue tracker with owners, Daily reconciliation summary
• Are there any contractual or regulatory thresholds (e.g., ERISA exposure, union rules) that create immovable 'red lines' for you? Options: Yes—ERISA/regulatory, Yes—union/contractual, No immovable red lines, Unsure/need to confirm

If We Could Remove One Risk — What Would You Ask Us to Prove First?

• If you could ask the vendor to demonstrate one capability tomorrow to relieve your single biggest fear, what would it be?
• Would you prefer a narrow technical test (carrier feed match) or a broader operational pilot (end‑to‑end employee enrollment + payroll) as your first step? Options: Narrow technical test, Broader end-to-end pilot, Combination/parallel
• What metrics or artifacts would make you comfortable recommending a rollout to your executive team (e.g., test logs, carrier confirmations, user session recordings)?
• What would be an acceptable next meeting or deliverable after this discovery to keep momentum? Options: Technical scoping call, Pilot proposal and timeline, Executive summary and ROI, Proof-of-concept plan
• Who else should we involve right away to reduce friction (name roles and preferred format of involvement)?

• Current State & Audit Findings Alignment
• Pilot Scenario Walkthrough — Data, Mappings & Employee Flows
• Carrier Feed & Payroll Integration Proof
• Exception Handling & Remediation Playbook
• Decision & Pilot Acceptance Confirmation

• Customer: Assign internal owners and backup contacts for each exception type and confirm SLAs.
• Confirm the reconciliation reports provide the necessary visibility for the HR team and payroll admin.
• Agree on escalation SLAs and automated retry behaviors for any rejections.
• Seller: Provide a sample reconciliation report with annotated match-rate calculations for the pilot cohort.
• Customer: Share carrier contact for test acknowledgements and confirm timing windows for feed acceptance.
• Seller: Document the error-handling runbook that will be used during the pilot, including notification recipients and SLA targets.
• Both: Schedule an end-to-end test exchange with the carrier sandbox where possible, including payroll file ingestion.
• Catalog of Expected Exceptions
• Have a documented playbook for triage, remediation, and communication for each high-risk exception.
• Ensure owners and SLAs are assigned and understood by both customer and seller teams.
• Confirm test cases that will be executed during pilot to validate the playbook.
• Seller: Deliver the remediation playbook document with step-by-step instructions and owner contact info.
• Introductions & Meeting Objective
• Both: Approve employee notification templates and cadence to be used if remediation affects coverage.
• Seller: Create automated test scripts to validate remediation flows in the sandbox environment.
• Recap: Problem, Consequence & Agreed Future State
• Obtain formal acceptance (go/no-go) to proceed with the pilot based on evidence against criteria.
• Document the pilot start date, checkpoints, owners, and escalation path.
• List outstanding gaps and assign owners with deadlines if decision is go.
• Customer: Provide formal sign-off on pilot acceptance criteria and pilot start date.
• Seller: Publish the pilot execution plan with checkpoints, evidence collection requirements, and stakeholder RACI.
• Both: Confirm weekly validation meeting cadence and the first checkpoint agenda.
• Seller: Remediate any pre-pilot gaps identified and report completion before pilot start.
• Agree on one concise current-state sentence that will guide the Solution Experience.
• Validate the audit findings as accurate and sufficient for pilot scenario creation.
• Surface and quantify the business, legal, and operational consequences of the current failures.
• Define and document the pilot acceptance criteria that will determine success.
• Customer: Share the full audit CSV, sample employee records, and the methodology used to generate the audit (due before the next meeting).
• Seller: Produce a one-page summary translating audit errors into quantified consequences (hours, $ exposure, impacted headcount).
• Both: Agree and record the pilot acceptance criteria checklist for use in subsequent meetings.
• Pre-work Confirmation
• Demonstrate that the platform produces exact carrier plan codes for representative pilot enrollments.
• Confirm the mobile and hourly employee experiences produce accurate transmissions and clear confirmation to employees.
• Surface any edge-case mappings that require configuration changes before pilot execution.
• Seller: Run three sample enrollments and deliver exported carrier files showing plan-code outputs for the cohort (high-priority examples selected by customer).
• Customer: Identify any additional edge-case employees or scenarios to include in the pilot and provide their records.
• Seller: Flag any mapping gaps and propose configuration adjustments or data-cleaning steps required before pilot start.
• Both: Confirm a test schedule for executing the same scenarios in a sandbox carrier feed within pilot dates.
• Setup Recap & Roles
• Prove that carrier feeds and payroll outputs match platform transmissions within the agreed acceptance thresholds.
• Current State Statement
• Carrier Feed Mapping Review
• Define Pilot Cohort & Test Cases
• Triage & Ownership Workflow
• Review Evidence vs Acceptance Criteria
• Decision: Pilot Acceptance & Go/No-Go
• Remediation Steps & Tools
• Reconciliation Report Walk-through
• Mapping Demo: Selection -> Plan Code
• Audit Findings Walk-through
• Employee & Executive Communications
• Consequence Quantification
• Payroll Deduction File Validation
• End-to-End Employee Flow (Mobile + Hourly)
• Roles, Timeline & Escalation Paths
• Error Handling, Retry & Escalation Flow
• Validation of Audit Data & Acceptance Criteria
• Mismatch Simulation & Impact Check
• Validation Test Cases
• Next Steps & Immediate Action Items

• Import Employee Census and Eligibility Data
• Configure Benefit Plans and Contribution Rules
• Set Up Eligibility Rules and Event Triggers
• Map and Activate Carrier EDI/API Feeds
• Transmit Elections to Carriers and Confirm Receipts
• Configure Payroll Deduction Mapping and File Exports
• Execute Pilot Enrollment for Target Employee Group
• Enable Mobile-First Guided Enrollment Experience
• Activate Decision-Support Cost Modeling per Household
• Deploy Dependent Documentation and Verification Workflow
• Reconcile Carrier Responses and Create Exception Batches
• Train HR and HRIS Admins on Platform Operations

Import Employee Census and Eligibility Data

• Do you have an export of current employee census and eligibility data to import? Options: Yes, No
• What format(s) are your census/eligibility files in? Options: CSV/Excel, HRIS API, SFTP/XML, Database export, Other
• Which specific fields must be mapped during import (e.g., SSN, DOB, hire date, job class, FTE, pay frequency)?
• Approximately how many employee and dependent records need to be imported? Options: Less than 1,000, 1,000-5,000, 5,001-25,000, 25,001-100,000, More than 100,000
• Are dependent and beneficiary records included in your export or maintained separately? Options: Included in export, Provided separately, Not available, Other
• Does the data require cleaning, deduplication, SSN masking, or other normalization before import? Options: Yes, No
• Who will own the field mapping and sign-off for the census import (HR, HRIS admin, vendor, other)? Options: HR, HRIS Admin, Benefits Vendor, Third-party Consultant, Other

Configure Benefit Plans and Contribution Rules

• Which benefit plans and plan types need to be configured (medical, dental, vision, FSA, HSA, life, disability, voluntary)?
• Do you have carrier plan codes and SPD/plan documents available to map to platform plan records? Options: Yes, No, Partially
• What employer contribution models apply (percentage of premium, flat dollar, tiered by employee class, per-plan exceptions)? Options: Employer %, Flat $, Tiered by class, Per-plan exceptions, Other
• Are contribution rules different by employee class, union, location, or job code? Options: Yes, No, Partially
• Will the platform enforce pre-tax vs post-tax deduction types and HSA/FSA limits? Options: Yes, No, Partially
• Who will be the approver for final plan configuration and sign-off? Options: Benefits Manager, HR Leader/VP, HRIS Admin, Finance/Payroll, Other

Set Up Eligibility Rules and Event Triggers

• Which eligibility dimensions must be supported (employee class, FTE %, hire date waiting period, location, job code)?
• Which life events or triggers should open enrollment outside the annual window (new hire, qualifying life events, marriage, birth, loss of coverage, etc.)? Options: New Hire, Open Enrollment, Qualifying Life Event, COBRA, Other
• Are there waiting periods or effective date rules that differ by plan or class? Options: Yes, No, Some plans
• Should eligibility be evaluated dynamically during enrollment (auto-validate) or reviewed by HR before finalization? Options: Auto-validate, HR review required, Hybrid
• Do dependent eligibility rules require age limits, student status, or other documentation-based checks? Options: Yes, No, Partially
• Who will maintain eligibility rules going forward (HRIS admin, Benefits admin, Vendor)? Options: HRIS Admin, Benefits Admin, Vendor, Other

Map and Activate Carrier EDI/API Feeds

• Which carriers do you need feeds for? Please list carrier names and plan lines.
• Which feed protocols do carriers support for your plans? Options: EDI 834, Carrier API/REST, SFTP CSV/XML, Carrier portal uploads, Other
• Do carriers provide test endpoints and test files for validation? Options: Yes, No, Some carriers
• Are carrier plan codes and broker mapping files available to align platform plan codes? Options: Yes, No, Partial
• Do any carriers require specific transport security (TLS version, IP allowlist, certificates)? Options: Yes, No, Unknown—need to verify
• Who is the primary carrier connectivity contact for testing and activation (carrier rep or broker)?

Transmit Elections to Carriers and Confirm Receipts

• What transmission cadence do you require for sending elections to carriers? Options: Real-time, Daily batch, Weekly batch, Ad-hoc
• What acknowledgement or receipt evidence do you require from carriers (834 ack, portal confirmation, email PDF)? Options: 834 ack, Portal confirmation, Email confirmation, Other
• How should rejected or failed transmissions be handled (auto-retry, create exception queue, notify HR)? Options: Auto-retry, Create exception queue, Immediate HR notification, Other
• What SLA is acceptable for confirmation of receipt from carriers? Options: Within 24 hours, 48 hours, 72 hours, Other
• Do you require reconciliation of transmitted elections against carrier responses automatically or as a manual review step? Options: Automatic reconciliation, Manual review, Hybrid
• Are there special handling rules for retroactive elections or effective date changes? Options: Yes, No

Configure Payroll Deduction Mapping and File Exports

• Which payroll/HRIS system(s) must receive deduction files or integrations? Options: ADP, Workday, UKG/Paylocity, Ceridian, Oracle, SAP, Other
• What file format or API payload does payroll require for deductions (CSV, XML, API, fixed-width)? Options: CSV, XML, API/JSON, Fixed-width, Other
• What is your payroll cadence and deduction effective timing (per pay period, first check after enrollment, next month)? Options: Per pay period, Monthly, Next pay period, Other
• Do you need mapping for deduction accounting codes, earning codes, or cost center allocation? Options: Yes, No, Partially
• How should retro deductions or arrears be handled when elections change mid-cycle? Options: Apply retro via supplemental file, Adjust next pay period, Manual adjustments by Payroll, Other
• Who will sign off on payroll mapping and test files (Payroll lead, Finance, HRIS)? Options: Payroll lead, Finance, HRIS Admin, Benefits Manager, Other

Execute Pilot Enrollment for Target Employee Group

• What is the desired pilot cohort and selection criteria (size, location, hourly employees, remote, department)?
• How many employees should be included in the pilot? Options: Less than 50, 50-200, 201-1,000, 1,001-5,000, More than 5,000
• What pilot timeframe do you expect (dates for enrollment window, testing, reconciliation)?
• What acceptance criteria will determine pilot success (carrier match rate threshold, completion rate, payroll file accuracy)?
• Will the pilot include mobile and hourly worker scenarios that require device testing or kiosk support? Options: Yes, No, Some cohorts
• What rollback or contingency steps should be in place if pilot uncovers critical carrier or payroll mismatches?

Enable Mobile-First Guided Enrollment Experience

• Is a mobile-first enrollment experience required for your population? Options: Yes, No, Partial (some cohorts)
• Approximately what percentage of employees are hourly or mobile-first users? Options: 0-10%, 11-30%, 31-60%, 61-100%
• Do you require support for multi-language content or localized messaging? Options: Yes, No
• Are there accessibility (WCAG) requirements or device constraints we should test against? Options: Yes, No, Unsure—need assessment
• Do you want custom branding, copy, or employee-facing FAQs integrated into the enrollment flow? Options: Yes, No, Partial
• How will employees be notified and authenticated for mobile enrollment (email link, SMS, SSO, employee ID)? Options: Email link, SMS code, SSO, Employee ID verification, Other

Activate Decision-Support Cost Modeling per Household

• Do you require household-level cost modeling and recommendation logic during enrollment? Options: Yes, No
• What household data is available for modeling (spouse income, dependents, other coverage, expected claims)?
• Which cost elements should the model surface (premium, estimated out-of-pocket, deductibles, copays, total cost)? Options: Premium, Estimated OOP, Deductible impact, Copays, Total cost, Other
• Should modeling assumptions be editable by admins (e.g., utilization rates, spouse coverage assumptions)? Options: Yes, No
• Do you require audit logs or explainability for recommendation results presented to employees? Options: Yes, No
• Do you want reporting on modeling outcomes and adoption (how many employees followed recommendations)? Options: Yes, No

Deploy Dependent Documentation and Verification Workflow

• Are dependent documents required for eligibility verification (birth certificate, marriage certificate, school records)? Options: Yes, No
• Which document types will be accepted and what file formats are allowed? Options: PDF, JPEG/PNG, Scanned image, Other
• Who will perform verification (HR team, third-party verifier, carrier)? Options: HR team, Third-party verifier, Carrier, Automated system
• Do you require automated OCR or metadata extraction to speed verification? Options: Yes, No
• What retention and compliance rules apply to stored documentation (retention period, encryption, access controls)?

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Pricing & Payment Schedule
• Pilot Acceptance Criteria
• RACI / Responsibilities Matrix
• Timeline & Milestones Plan
• Data Processing & Security Agreement (DPA)
• Carrier & Payroll Reconciliation Agreement
• Escalation & Issue Resolution Plan
• Change Control / Change Order
• Implementation Support & Training Commitments
• Final Sign-off & Execution

• Pilot Outcomes Review
• Go‑Live Outcomes & Immediate Remediation
• Retrospective — Lessons Learned
• Open Issues & Enhancement Backlog Triage
• Operational Handoff & Continuous Improvement Governance

• Collect and store all project artifacts (config snapshots, mapping docs, acceptance sign-offs) in the agreed repository.
• Publish a Lessons Learned document with prioritized recommendations and owners within 5 business days.
• Update runbooks and configuration checklists to prevent recurrence of identified issues.
• Schedule training sessions for HR/benefits admins on any updated processes or UI flows.
• Add instrumentation/monitoring where visibility gaps were identified.
• Backlog Overview
• Prioritize open issues and enhancement requests by business impact and feasibility.
• Assign owners, target releases, and acceptance criteria for prioritized items.
• Establish an agreed cadence and SLAs for ongoing backlog management.
• Produce a prioritized backlog with owners, impact scores, and proposed release windows.
• Create acceptance criteria for each remediation/enhancement to ensure validation.
• Schedule recurring backlog grooming meetings (bi-weekly or monthly) with key stakeholders.
• Notify customer of which enhancement requests are accepted into roadmap and estimated timelines.
• Confirm Operational Owners & Roles
• Complete formal handoff to BAU owners with documented responsibilities.
• Establish monitoring dashboards and KPIs to detect regressions early.
• Agree an escalation path and governance cadence for continuous improvement.
• Obtain stakeholder sign-off to transition project to operations.
• Publish an operational runbook with owners, dashboards, SLAs, and escalation contacts.
• Provision and share monitoring dashboards with agreed KPIs and alert thresholds.
• Schedule the recurring governance meetings and invite required stakeholders.
• Introductions & Objectives
• Confirm whether pilot met each acceptance criterion with evidence.
• Surface and quantify pilot discrepancies and their business impact.
• Agree on immediate next steps: remediation plan or go/no-go for rollout.
• Assign owners and timelines for any required corrective actions.
• Prepare and share a one-page pilot results report (metrics, issues, recommended decision) within 24 hours.
• Create tickets for all pilot discrepancies, tagging severity and owner.
• If pilot fails criteria, schedule remediation sprint with target dates and owners.
• If pilot passes, prepare go-live readiness checklist and external communications draft.
• Go‑Live Health Snapshot
• Contain and reduce the impact of production incidents within agreed SLAs.
• Assign clear owners and timelines for fixes and workarounds.
• Coordinate consistent external communications to affected stakeholders.
• Open severity-tagged incident tickets with owners, remediation steps, and target resolution times.
• Publish employee and carrier notification templates and schedule sends.
• If needed, schedule an emergency engineering deployment window and rollback plan.
• Log lessons from each incident for the Retrospective meeting.
• Timeline Recap
• Create a prioritized list of process and product improvements tied to root causes.
• Assign owners and timelines for all retrospective actions.
• Define measurable success signals for each improvement to validate effectiveness.
• Acceptance Criteria Recap
• Monitoring & KPIs
• What Worked (Start/Continue)
• Incident Review (Severity 1–3)
• Impact & Effort Assessment
• Root Cause Quick Checks
• Data Summary: Carrier & Payroll
• Escalation Path & SLA
• What Didn't Work (Stop)
• Prioritization Exercise
• Assign Owners & Releases
• Triage & Fix Assignment
• Governance Cadence
• User Experience & Completion Metrics
• Root Cause & Systemic Fixes
• Feedback Loop & SLA
• Communication & Carrier Coordination
• Closeout & Sign-off