Keel Upload

Your census walks in.
Your enrollment walks out.

Hand us any census, even a messy spreadsheet. Amanda maps it to your plans, flags what needs a human, and stands up an enrollment your people can finish. No template, no data project.

Get a demoTry it yourself · 90 sec
Built for benefits teams. SSNs encrypted. We never touch claims or clinical data.

Drop a client's census.
Spin up their platform.

One file in, a branded enrollment out. Amanda maps it to the plans, flags what needs a look, and stands up your client's enrollment under your logo. No template, no data project.

Get a demoTry it yourself · 90 sec
Built for brokers. Your brand on the box. SSNs encrypted, clinical data never touched.
app.keel.com / upload
1Drop the file
acme-census.xlsx
312 rows · 18 columns
From Employee Navigator export
Uploaded · Amanda reading…
Raw file · as received
EMP_DOBDEP_SSNPLAN_CDREL
1984-03-11•••-44HDHP-2KS
1990-07-02•••-19PPO-STDC
1977-11-23•••-08HDHP-2KS
2Amanda maps it
EMP_DOB→Date of birth99%
DEP_SSN→Dependent SSN98%
PLAN_CD→Plan election97%
REL→Relationship?confirm
247 mapped automatically3 to confirm
3Enrollment goes live
AOpen enrollment · ready
Employees loadedMAJTRKSD312
Plans linked6
Dependents418
Branded · ready to send
A
Amanda mapped the census247 of 250 columns · 1.2s
Illustrative. Example census, representative figures, not audited customer results.
Reads the files you already have
ENEmployee Navigator XLExcel / CSV ADADP PXPaychex bsbswift EaEase +Carrier files
The old way

A census shouldn't be a data project.

Every group, every renewal, someone reformats a spreadsheet by hand, chases down missing SSNs and dependent birthdays, and re-keys the whole thing into a template. For days. Before enrollment can even start.

Every file is different
Different headers, different formats, dependents on their own rows. No two carrier exports look alike.
Errors hide until it's late
A missing SSN or bad birthday shows up mid-enrollment. Or worse, on the carrier feed.
Days you don't have
Open enrollment has a hard deadline. The clean-up work pushes the whole timeline back.
How it works

Four steps. No re-keying.

You bring the file you already have. Amanda does the parsing, mapping, and validation. You just confirm the edge cases.

1
Drop the file
Any format, any source. A carrier export, an Employee Navigator file, a spreadsheet someone emailed you. Drag it in, or connect the system directly.
acme-census.xlsx
312 rows · 18 cols
2
Amanda maps every column
She reads each header and the data underneath, matches it to the right field with a confidence score, and cleans up dates, names, and IDs along the way. No mapping template required.
EMP_DOB → Date of birth
PLAN_CD → Plan election
247 auto-mapped
3
You confirm the edge cases
A short review queue shows only what's ambiguous or missing. A dependent without a birthday, an unmapped column. Approve in a few clicks. No marathon.
3 to confirm
REL → Relationship?
2 missing dependent DOB
4
Enrollment goes live
Keel builds a branded, plan-aware enrollment from the clean record. Employees, dependents, and elections, all linked to your plan catalog. Ready to send the same day.
312 loaded · 6 plans
Branded · ready to send
Reads anything

Any file, not a template.

Most tools make you reshape your data to fit their importer. Keel works the other way around. Amanda reads the file as-is, odd headers, merged cells, dependents on their own rows, and works out what every column means.

"We used to spend the first week of every onboarding just reformatting the census. Now it's a drag and drop."Benefits operations lead (illustrative)
Column mapping 312 rows
EMP_FNAME→First name99%
DOH→Date of hire98%
COVTIER→Coverage tier96%
XREF9→Needs reviewconfirm
Validation

Catches what's wrong before you do.

Amanda checks the data the second it lands. Duplicate employees, missing SSNs, invalid birthdays, dependents with no relationship, elections that point at no real plan. You fix it now, not on the carrier feed.

"It caught eleven dependents missing a birthday that would've bounced at the carrier. That alone paid for it."Account manager, agency (illustrative)
Validation 5 issues found
3 missing SSNsrows 41, 88, 203fix
2 dependents · no birthdayauto-emailed to confirmreview
307 rows cleanready to loadok
Plan-aware

Maps to your plans, not generic fields.

Because Keel already knows your plan catalog, election codes map to the real plans people can pick. HDHP, PPO, dental, vision. The census doesn't just load. It becomes an enrollment that knows exactly what it's enrolling people into.

"The elections came in already tied to the right plans. We didn't rebuild a thing."HRIS administrator (illustrative)
Elections → plan catalog linked
HDHP-2K→HDHP Saver + HSA188 electedlinked
PPO-STD→PPO Standard96 electedlinked
DEN-HI→Dental High241 electedlinked
A worked example

A 250-life manufacturer, three weeks from open enrollment, sends over a carrier census. Dependents on their own rows, two columns nobody can explain. Amanda parses it in under four minutes, auto-maps 14 of 16 columns, catches 9 dependents missing a birthday, and emails them to confirm. By that afternoon the enrollment is live, branded, and ready. The HR team never opened a spreadsheet.

3 wks → same day
Census to live enrollment
14 / 16
Columns auto-mapped
0
Spreadsheets reformatted
By the numbers

Less data work, more enrollment.

0 min
Median file to enrollment
0%
Columns auto-mapped
templates
Mapping templates to build
0%
Validated before it loads
Handled with care

Census data is sensitive. We treat it that way.

A census carries SSNs and dependents, but never claims, diagnoses, or medications. Keel encrypts the sensitive fields, scopes access tightly, and stays deliberately out of the data it doesn't need.

SSNs encrypted at rest and in transitSensitive fields are encrypted field-level, not just disk-level.
No claims, diagnoses, or medicationsKeel never ingests clinical data. That's a line we don't cross, by design.
Least-access by roleOnly the people who need a record can see it; every access is logged.
Bank-level encryptionSSNs and sensitive fields encrypted per tenant; access scoped by role and fully logged.
Better together

Upload is the front door to the whole suite.

A clean census doesn't stop at enrollment. It flows into everything else Keel runs.

Keel Catalog
Feeds it
Your plan catalog is what Upload maps elections into. SBCs become live plans the census links to.
Keel Enroll
Picks up where it ends
The enrollment Upload spins up is the one employees actually finish. Branded, guided, plan-aware.
Keel Export
Closes the loop
Elections flow back out as a clean Employee Navigator bundle. The same record, round-tripped.
Questions

The details.

What file formats does Keel Upload accept?
Excel (.xlsx/.xls), CSV, and most carrier and ben-admin exports, including Employee Navigator files. You don't need to reshape anything first. Amanda reads the file as it is. You can also connect a system directly for ongoing syncs.
Do I have to build a mapping template?
No, and that's the point. Amanda infers the mapping from the headers and the data itself, with a confidence score on each column. You only touch the handful she isn't sure about. There's no template to set up or maintain across groups.
What happens to missing or bad data?
It's caught right away and shown in a short review queue. Missing SSNs, invalid birthdays, dependents without a relationship, elections with no matching plan. For some gaps, like a dependent's birthday, Keel can email the employee to confirm, so it's fixed before enrollment instead of on the carrier feed.
How is the sensitive data protected?
SSNs and other sensitive fields are encrypted at the field level, and access is scoped by role and fully logged. We never ingest claims, diagnoses, or medications. That data is deliberately out of scope.
How does this work when a broker delivers Keel?
Your broker uploads the census for you, or you do it under their branding. Either way the enrollment wears their brand, and the cleaned record flows straight into the rest of the suite they manage for you.
Keel Upload

Bring a census.
Leave with an enrollment.

Send us a real file and watch Amanda turn it into a live, branded enrollment. Usually before the call is over.

Get a demoGet a demo