Carrier Enrollment Feed Builder
Turn approved benefits elections into clean, validated, per-carrier enrollment files (adds, changes, terminations) with a human approval gate - so manual re-keying and rejected files stop happening.
A private internal tool where you load approved benefits elections, map them to each carrier's exact file layout, catch errors before they cause rejections, review the per-carrier file, approve it, and download a carrier-ready CSV or fixed-width file - with a full audit trail and duplicate protection.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- Your list of carriers and their file layouts (or a sample file from each)
- A spreadsheet or export of approved benefits elections/changes
The problem this kills
Every enrollment, every life event, every termination - and you're back in the carrier portals re-keying the same data, or hand-building a file in the exact picky layout each carrier demands. One carrier wants a CSV with columns in one order and dates as MM/DD/YYYY. Another wants a fixed-width text file with coverage codes you have to look up. Get one field wrong and the whole file bounces back rejected, and now you're hunting for which record broke.
It's slow, it's error-prone, and a single typo in an SSN or a wrong coverage code can mean a member shows up uncovered at the pharmacy. This tool stops the re-keying and stops the rejected files.
What you'll build
A small private web app where you:
- Load a batch of approved benefits elections and changes (from a spreadsheet or export).
- Let the tool map each record into every carrier's required layout - column order, codes, and date formats per carrier.
- Validate every record against that carrier's rules (required fields, valid plan and coverage codes, sane dates) before anything leaves the building.
- See a clean per-carrier review screen: record counts, how many adds vs. changes vs. terms, and a list of any errors to fix.
- Approve each carrier's file - the human gate - and only then download a carrier-ready CSV or fixed-width file.
- Keep a full audit trail of who approved what and when, with duplicate guards so the same change never gets sent twice.
What's inside the Implementation Plan
The plan is a step-by-step runbook you paste into an AI coding agent (Claude Code). It builds the whole tool with you, one prompt at a time - no prior coding needed.
It opens by interviewing you about your business - your carriers, your real field names, your coverage and plan codes, your typical and peak volumes, your approval rules, and your messy edge cases (mid-month effective dates, COBRA, dependents, retro terms). It reads back a short tailored spec and waits for your thumbs-up, so the tool fits your carriers and your data - not a generic template. Then every later step is shaped by your answers.
Inside you'll find: the discovery interview, the data model tuned to your fields, a per-carrier mapping and format spec, the validation engine, the review-and-approve screen, the export builder (CSV and fixed-width), and a verification checklist.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each organization only ever sees its own data.
- A complete audit trail: who loaded, validated, approved, and exported each batch, and when.
- A hard human-in-the-loop approval gate: the tool drafts and validates the file, but a benefits admin must review counts and clear all errors before it can be marked sent.
- Duplicate guards keyed on employee ID + carrier + change-effective-date, so the same change can't go out twice.
Who it's for
Benefits administrators and HR ops pros who today re-key elections into each carrier's portal, or wrestle each carrier's finicky file format by hand - and who are tired of files bouncing back rejected.
You've got this - paste the first prompt and let the agent interview you.