Onboarding a new health plan's eligibility feed goes fastest with a checklist that runs from kickoff to go-live: agree on the file and schedule, collect real samples, map and validate the data, set up delivery and alerts, test with scrubbed files and hand over to operations. This checklist is for data, engineering and operations teams at companies that health plans pay to serve their members, who onboard a new plan's eligibility file every time they sign a contract. Copy it for each new plan, work through it in order and keep the completed copy as the plan's record.

Most onboarding delays come from questions nobody asked at kickoff. This checklist puts those questions first.

Why a Checklist Beats Starting From Scratch

Every new plan brings the same questions: what format, how often, which fields, who to call when a file is late. Teams that answer them from memory miss some every time, and the gaps surface after go-live as rejected files and missing members.

A checklist makes onboarding repeatable. Anyone on the team can run it, nothing gets skipped and every plan ends up documented the same way. Paired with a pipeline template, it turns a new plan into a few days of configuration instead of a new build.

What You'll Need Before Starting

  • The signed contract or statement of work listing the plan's members and benefits in scope
  • A contact on the plan's side for file questions, and a backup contact
  • Your standard member schema and existing pipeline template
  • A dedicated SFTP folder ready for the plan's deliveries

The Onboarding Checklist

Phase 1: Kickoff and File Agreement

Agree on the file before anyone builds anything. These answers shape every later step.

Checklist:

☐ File format confirmed: 834, CSV, fixed-width or Excel

☐ Full file or change file confirmed, since the two are processed differently

☐ Delivery method confirmed: your SFTP, the plan's SFTP or another secure transfer

☐ Delivery schedule confirmed, including time zone and holiday rules

☐ File naming pattern agreed 

☐ Encryption agreed, such as PGP, with keys exchanged 

☐ File specification or 834 companion guide received

☐ Plan contacts recorded for routine questions and urgent issues

Output of this phase: A written agreement on what the plan sends, how and when.

Phase 2: Samples and Profiling

The specification shows what the plan intends to send. Samples show what it actually sends.

Checklist:

☐ Two or three sample files received, with member data scrubbed or de-identified

☐ Each sample profiled: columns, formats, row counts and encoding

☐ Differences between the samples and the specification listed 

☐ Questions about differences sent to the plan and answered

Output of this phase: A profile of the plan's real files and every gap from its specification.

Phase 3: Mapping and Normalization

Map the plan's layout to your schema so downstream systems see one format for every plan.

Checklist:

☐ Every source field mapped to your member schema

☐ Fields the plan doesn't send handled: null, default or rejected

☐ Dates, names, phone numbers and IDs normalized to your standard formats

☐ Benefit-level eligibility mapped, where members qualify for some benefits and not others

☐ Mapping documented where ops and engineering can both find it

Output of this phase: A documented mapping from the plan's layout to your schema.

Where Integrate.io helps: Mapping and normalization are configured with 220+ low-code expressions in the plan's copy of the pipeline template, and native 834 parsing turns enrollment files into rows with named columns before mapping starts.

Phase 4: Validation Rules

Decide what loads, what waits for review and what gets rejected.

Checklist:

☐ File-level checks set: empty, resent and wrong files rejected

☐ Structure checks set: required columns and column counts

☐ Field checks set: required fields, formats, allowed codes and date logic

☐ Duplicate member IDs routed to review

☐ Comparison with the previous delivery set, with a threshold for row count changes

☐ Review table or folder set up for held rows and rejected files

Output of this phase: Validation rules with an action attached to each. For detail, see how to validate health plan eligibility files before they load.

Phase 5: Delivery Handling and Alerts

Set up how files are picked up and how the team hears about problems.

Checklist: -

☐ Plan's SFTP folder connected and file pattern configured

☐ Each file processed once, then archived

☐ Failed-run alerts set, with plan and file details in the message

☐ Missing-file check scheduled against the plan's delivery calendar, with a grace period

☐ Alert channels set by severity: email, Slack or PagerDuty

Output of this phase: A delivery setup that processes each file once and alerts on failures and missing files. For detail, see how to get alerted when a health plan's eligibility file is late or missing.

Where Integrate.io helps: Each plan's copy of the template switches folder paths and connections through variables, and scheduled checks on SFTP or S3 locations confirm the plan's file arrived and alert when it hasn't.

Phase 6: Testing and Parallel Run

Prove the setup works before members depend on it.

Checklist:

☐ Scrubbed sample files run end to end, with every output field checked 

☐ A blank file, a wrong file and a file with duplicates tested to confirm validation fires

☐ A test alert triggered and received in the right channel

☐ Parallel run completed for one or two delivery cycles, with record counts matching

Output of this phase: A tested setup with matching results from the parallel run.

Phase 7: Go-Live and Handover

Hand the plan over to the team that will run it day to day.

Checklist: - ☐ First production file processed and reviewed - ☐ Owner assigned for the plan's held rows and alerts - ☐ Plan contacts and escalation path shared with the operations team - ☐ Completed checklist saved as the plan's onboarding record - ☐ Review scheduled after the first month to adjust thresholds and grace periods

Output of this phase: A live plan with a named owner and a documented setup.

Plan Intake Template

Copy this table for each new plan and fill it in during kickoff.

Field Value
Plan name
Plan contact (routine)
Plan contact (urgent)
File format 834 / CSV / fixed-width / Excel
Full file or change file
Delivery method and location
Delivery schedule and time zone
File naming pattern
Encryption
Grace period for late files
Benefits in scope
Internal owner
Go-live date

Common Mistakes to Avoid

  • Skipping the full-or-change question (phase 1): processing a change file as a full file can terminate members who are still covered.
  • Building from the specification alone (phase 2): plans drift from their specifications. Profile real samples first.
  • Going live without a missing-file check (phase 5): a file that never arrives doesn't cause a failed run.
  • Testing with live member data (phase 6): scrub samples before testing outside production.
  • No owner after go-live (phase 7): held rows and alerts without an owner get ignored.

Conclusion

Onboarding a new health plan's eligibility feed comes down to seven phases: agree on the file, profile real samples, map and normalize, set validation rules, configure delivery and alerts, test and hand over. Working through them in order, with the intake template filled in at kickoff, means nothing gets skipped and every plan is documented the same way. Integrate.io supports the build side, with low-code mapping, 834 parsing, per-plan templates and arrival alerts, so most of onboarding becomes configuration. For the full process behind this checklist, read how to onboard a new health plan's eligibility file without building a new pipeline.

Frequently Asked Questions

How long does it take to onboard a new health plan's eligibility file?

With a pipeline template and a checklist, most of the work is agreeing on the file and testing, which usually takes days to a couple of weeks, depending on how quickly the plan sends samples and answers questions. Building a new pipeline for each plan takes much longer.

What should you ask a health plan before receiving its eligibility file?

Ask for the file format, whether it is a full file or a change file, the delivery method and schedule, the naming pattern, encryption details, the file specification and the contacts for routine and urgent questions.

What should be tested before an eligibility feed goes live?

Run scrubbed sample files end to end, test that blank, wrong and duplicate-heavy files trigger validation, confirm alerts reach the right channel and run the new feed alongside the current process for one or two delivery cycles.

Integrate.io: Delivering Speed to Data
Reduce time from source to ready data with automated pipelines, fixed-fee pricing, and white-glove support
Integrate.io