Extract Plan Names, Coverage Tiers & Premiums from Any Benefits Enrollment Screenshot
Open enrollment ends and the confirmation screen disappears — the plan codes, per-paycheck deductions, and coverage tiers you picked for medical, dental, vision, and 401(k) live only in that screenshot. This one pulls the five fields you name from any ADP, Gusto, or BambooHR enrollment summary in about 5 seconds per screenshot.
5s per screenshot · Up to 99% accuracy on clear digital enrollment screens
Five Fields from One Confirmation Screen
Every benefits enrollment confirmation screen — ADP's table of plan codes, Gusto's summary card, BambooHR's checkmark-style elections — contains the same five data points. Type these column names and the AI finds each value by its label, wherever the layout put it.
What the employer calls it — "Blue Cross PPO" on Gusto, or the internal code "MED-PPO-80" on ADP. Both forms fill the same column.
Medical, Dental, Vision, Life, 401(k), HSA — the AI identifies each category by its label, mapping Gusto's "Health Insurance" and ADP's "MED" to the same column.
Individual, Employee + Spouse, Employee + Children, Family — the tier directly affects the premium amount, and each platform labels it differently.
The deduction per pay period — ADP and Gusto show per-paycheck costs, not monthly totals. Multiply by pay periods if budgeting needs monthly figures.
Enrolled or Waived — BambooHR shows a checkmark next to elections; ADP and Gusto show a dollar amount for enrolled and blank for declined.
ADP Uses Plan Codes, Gusto Uses Carrier Names — But the Data Structure Is the Same
ADP shows a dense table of plan codes, tiers, and deduction amounts. Gusto replaces the table with a clean summary card — one row per benefit, carrier name spelled out. BambooHR presents checkmark-style elections with costs inline. Three platforms, three visual languages, one shared data model: plan name, benefit type, coverage tier, per-paycheck cost, and election status. Fixed-template tools fail when a plan code changes or an employer switches platforms; semantic extraction reads the label and its value as a pair, regardless of layout.
"just wait till January 1st and hope you did it right"
— California state employee on open enrollment confirmation, r/CAStateWorkers
That is the anxiety behind every enrollment screenshot: six financial decisions on one screen, submitted, and the only record until the first paystub confirms the deductions weeks later. If HR disputes the dental election or the premium looks wrong, the screenshot is the only evidence.
Why Enrollment Screens Break Traditional Extraction
Plan codes are employer-specific, not human-readable. ADP displays "MED-PPO-80" and "DEN-HMO-Basic" inside table cells. The real plan names — "Blue Cross PPO," "Delta Dental HMO" — describe what was purchased, not the SKU in the payroll system.
The same data points multiply across benefit types. Medical, dental, vision, life, 401(k), HSA, FSA — each carries its own plan name, tier, and premium. Gusto shows them as labeled card rows; ADP lists them as table rows; BambooHR presents them as a vertical checklist. A parser that assumes one "Plan Name" per page breaks when there are six.
The screen disappears after the enrollment window closes. ADP removes the confirmation from the dashboard once the period ends; BambooHR lets admins lock it. The screenshot is the only permanent record the employee controls — and traditional OCR cannot structure its pixel grid into labeled columns.
How Semantic Field Location Reads It
Name five columns; the AI reads each benefit line independently. Type Plan Name, Benefit Type, Coverage Tier, Per-Paycheck Premium, Election Status — the model processes each row on the ADP table, each card on the Gusto summary, and each checkmark election on BambooHR as a separate output row. Six benefit types on one screen produce six rows in the spreadsheet.
Plan codes and carrier names both fill the Plan Name column. ADP's "MED-PPO-80" and Gusto's "Blue Cross PPO" both map to Plan Name because the AI reads the label semantically — it identifies the text paired with the benefit row's name, not a specific string pattern. If the screen shows both a code and a carrier name on separate lines, define two columns and the AI reads each independently.
ADP, Gusto, and BambooHR enrollment screens mix freely in one batch. A dozen ADP enrollment tables and a handful of Gusto summary cards — same five column names, same output spreadsheet. Each benefit row fills whichever columns have data; fields the platform does not show (like dependent names on a screen without them) stay empty rather than being guessed.
From One Enrollment Screenshot to a Complete Benefits Audit Row
Screenshot the Confirmation Page Before It Disappears
After you submit elections in ADP, Gusto, or BambooHR, capture the enrollment summary or confirmation screen. Include all benefit sections visible — medical, dental, vision, life, 401(k), and any supplemental plans. This is the only record you control: once the enrollment window closes, the ADP dashboard removes the confirmation and BambooHR may lock the election behind an admin-only view. JPG, PNG, or WebP — or the confirmation PDF if your platform generates one.
Name the Five Columns
Type Plan Name, Benefit Type, Coverage Tier, Per-Paycheck Premium, Election Status. The AI processes each benefit line on the screen as a separate row — the medical plan on row 1, dental on row 2, vision on row 3, and so on. ADP's plan code "MED-PPO-80" fills the same Plan Name column that holds Gusto's "Blue Cross PPO." A benefit row labeled "Waived" with no premium fills Election Status without a dollar amount.
Download One Row Per Benefit Election
Each benefit on the screenshot becomes one row — five columns wide. Six benefit types on one ADP confirmation screen produce six rows. About 5 seconds per screenshot versus several minutes of typing plan names, tiers, and deduction amounts by hand (~18x faster). Export as XLSX or CSV — one file per employee, ready for a household budget planner, benefits audit, or enrollment dispute documentation.
When an Enrollment Screenshot Works — and What It Does Not Do
The screenshot captures exactly what the platform displayed at the moment of confirmation. Here is what the tool can and cannot do with that data.
When It Works Best
Clear, full-resolution screenshots of the enrollment summary. Machine-rendered plan names, tiers, and premium amounts reach up to 99% accuracy. Six benefit types on one screen produce six output rows.
Screenshots from ADP, Gusto, and BambooHR processed in one batch. The same five column names work across ADP's plan-code table, Gusto's summary card rows, and BambooHR's checkmark election view — the AI reads by label meaning, not by platform layout.
Documenting elections for a benefits audit or enrollment dispute. The screenshot is the employee's only permanent record — extracting it into a sortable spreadsheet creates a reference that outlasts the enrollment window.
When to Be Cautious
The tool extracts what is on screen — it does not interpret plan codes. If ADP shows "MED-PPO-80" and the carrier name lives in a separate benefits guide PDF, the AI extracts the code as Plan Name. It does not translate codes into carrier names or advise which plan to choose.
No eligibility verification or plan comparison. The AI reads the elections you made — it does not check whether you were eligible for the plan you selected, whether the premium matches the rates published in your benefits guide, or whether the coverage tier is correct for the dependents listed.
Screenshots that only capture part of the enrollment summary. If the ADP table scrolls and you screenshot only the visible portion, benefit types below the fold are missing. Take a full-page screenshot or capture in sections.
Frequently Asked Questions
Can I extract Plan Name from ADP even though it shows plan codes like "MED-PPO-80"?
Yes. The AI extracts the plan label exactly as it appears on screen. ADP enrollment summaries display the internal plan code — "MED-PPO-80," "DEN-HMO-Basic" — in a table column labeled "Plan." Gusto shows the carrier name — "Blue Cross PPO," "Delta Dental" — on a summary card. Both fill the Plan Name column because the AI reads the text paired with each benefit row by meaning, not by string matching. If your screen shows both a code and a description line, type two columns and the AI reads each independently. The tool does not translate codes into carrier names or vice versa — it extracts what is visible.
Is the Per-Paycheck Premium extracted as the monthly cost or the per-pay-period deduction?
The tool extracts the dollar amount displayed next to the premium label — which on ADP, Gusto, and BambooHR is almost always the per-pay-period cost, not monthly. ADP labels this column "Per Pay Period Amount"; Gusto shows it as "Per Paycheck" under the plan summary. If your downstream spreadsheet needs monthly figures, multiply by pay periods per month outside the tool (×2 for biweekly, ×2 for semimonthly). The AI does not multiply automatically because it cannot know your pay frequency from a single screenshot.
Can I batch dental, vision, life, and 401(k) elections along with medical from the same screenshot?
Yes. The AI processes each benefit line on the enrollment summary as a separate output row in a single extraction. Medical, dental, vision, life, 401(k), and any supplemental benefits each occupy their own row with all five column values where available. The Benefit Type column identifies each row's category by reading the benefit label. A benefit line marked "Waived" produces a row with Election Status set to Waived and no premium value.
Is a PDF confirmation statement more accurate than a screenshot of the enrollment page?
Yes — a PDF generated by the benefits platform preserves vector text and is sharper than a screenshot at display resolution. Use "Download Confirmation" or "Print to PDF" when your platform offers it — especially for dense ADP tables with small deduction-line text. The screenshot path is for when you no longer have portal access — such as after leaving a job or after the enrollment window closes. On clear, uncompressed screenshots, the five named fields extract reliably.
Can I extract enrollment screenshots from ADP, Gusto, and BambooHR in the same batch — for multiple family members?
Yes. The same five column names work across all three platforms in one batch. ADP's plan-code table fills Plan Name with codes and Per-Paycheck Premium from the deduction column. Gusto's summary cards fill the same columns with carrier names and costs. BambooHR's checkmark view fills Election Status from the indicator and the inline cost from the plan description. If extracting for multiple household members, give each screenshot a distinct filename or run separate batches so you can identify which row belongs to which employee. Add an Employee Name column if the platform displays it on the enrollment page.
Return to the work & HR app screenshot overview for paystub, PTO, attendance, and more HR data extraction scenarios.
The same Custom Column Extraction approach also pulls gross pay, deductions, and YTD totals from ADP and Gusto paystub screenshots — the other side of the paycheck the enrollment preview doesn't show.
If you need PTO balances alongside benefits data, PTO accrual rates and remaining hours extract from Workday screenshots with the same column-name approach.