What happens between upload and send.

The mechanics

1. 01

   What you upload

   Advisor reads what the carrier already gave you: SBCs, benefits guides, rate sheets, carrier plan documents. Workforce needs a roster — a spreadsheet import with up to 25 fields, and no benefits data required.

2. 02

   What happens to a document

   Parsing starts on upload, not when you hit build, and a file parsed once is never parsed again. Large PDFs are split into 20-page chunks; scanned pages that came in sideways are rotated before anything reads them. A document recognized as a prior-year guide is left out of the build, and a file that fails to parse still counts as done — one bad document cannot hang the build.

3. 03

   Where a person decides

   The machine stops where the decisions become judgment calls: which of these is a plan and which is a network tier, what the client calls it, who is eligible for what. You review the detected plan list, confirm or rename, set employee classes, fill a short intake, pick a template and hit build.

4. 04

   How the document gets built

   Verify: code checks every table's plan names against the list you confirmed. Canonicalize: every carrier writes labels differently, so “Deductible (Individual)” and “Calendar Year Deductible — Single” get one stable key — which is what makes year-over-year comparison possible. Hydrate: mechanical fields fill with no AI; only the prose that has to sound human is generated. Brand: the employer's colors, fonts and images come from their own website, and never block the build.

5. 05

   How it ships

   Publish a benefits website, download a PDF, or send a link employees open — which also hosts the ask-a-question chat. Your edits survive rebuilds: locked sections carry over verbatim, and your theme and section order persist. A confirmed plan matches itself next year, so the next renewal starts from this one.

6. 06

   How employees get reached

   Workforce sends to a phone number, with no app and no login. Segments run on the HR attributes in the roster — site, shift, class, 22 fields in all — and every send resolves to a per-person record of what was sent and received.

7. 07

   What it does not require

   No AMS integration. No carrier feed. No ben-admin platform. No IT project at the employer.