EOI Exchange

The administrative portal

Inside the EOIX admin portal.

Centralized visibility is the differentiator. Four areas, one underlying event stream, one operating picture for the carrier. This page shows what is in the portal today; real screens are not exposed publicly until a partner walkthrough.

Applicant trackingCoverage visibilityIntegration healthGovernance trail

Area A

Every application, in one place, every status.

Per-applicant view across every employer group. Who they are, how much they elected, the GI amount, the amount subject to EOI, the amount approved, the final coverage, the workflow status, event timestamps, and abandonment status.

Status taxonomy

InitiatedIn ProgressApprovedDeclinedAbandonedWrite-Back PendingWrite-Back CompletedIntegration Exception

Each application sits in exactly one status at a time. Every transition is logged with owner and timestamp.

Who cares most:Carrier opsEmployer HRBrokers

Area B

See the coverage picture across the book.

Aggregate and per-case view of total elected, GI amount, amount subject to EOI, amount approved above GI, and final approved coverage. The answer to: what coverage is the carrier issuing on this group, this cycle.

Worked example

Coverage Visibility, one case, end to end

  • Employee elects$500,000 voluntary life
  • Guaranteed Issue (GI) threshold$100,000
  • Amount subject to EOI$400,000
  • Carrier rules returnFull approval
  • Approved above GI$400,000
  • Final coverage in cart$500,000

Payroll deductions are calculated by the Ben Admin off the final coverage number. EOIX does not own payroll.

Who cares most:CarriersBrokers

Area C

Watch integrations work, or know the moment they fail.

Real-time view of API activity, write-back success and failure, integration exceptions, and synchronization issues between EOIX and connected Ben Admin and carrier systems. When something breaks, the portal flags it and identifies the affected case so it can be fixed inside the same enrollment cycle.

What gets tracked

  • API activity across EOIX, Ben Admin, and carrier systems
  • Write-back success and failure, per case
  • Integration exceptions, with the affected case identified
  • Synchronization issues between connected systems
Who cares most:Carrier ITBen Admin engineeringEOIX ops

Area D

The auditable trail from rule to launch.

End-to-end record of underwriting rules received, rules transmitted to Ben Admin, testing completed, validation status, write-back testing confirmation, and launch certification status. The carrier's show-me-you-ran-the-playbook-I-gave-you answer, in writing.

Validation status taxonomy

PendingIn ReviewValidatedException IdentifiedRetest RequiredCertified for Launch

Pre-launch validation testing transitions through these statuses. Nothing goes live until Certified for Launch is set by the carrier.

Who cares most:Carrier complianceRiskUnderwriting leadership

The human in the loop

A Director of Governance behind the portal.

The portal is the operating picture. The Director of Governance is the role that runs the workflow around it: the recurring governance call, the action log, the close-out of every exception. The role lives more fully on the workflow governance pillar.

See pillar three: Workflow governance

What the portal does not do

The portal shows what happened. It does not write the rules and it does not make underwriting decisions. The carrier writes every rule. The underwriting engine, configured by the carrier, returns approved or not approved. EOIX provides the visibility around that decision so the carrier can govern the program in real time instead of finding out at year-end.

EOIX is not making underwriting decisions. The portal exposes the workflow. The carrier owns the rules.

The boundary

What EOIX does, and what it deliberately does not.

Especially in the portal. Visibility is not authority. EOIX exposes the events; the carrier owns the rules and the decisions.

Next step

Request a portal preview.

We schedule a guided walkthrough with your operations, IT, and compliance leads. Real screens, against a test dataset, with the validation tracking turned on. No carrier names in the room without your consent.

Request a portal previewSee the full workflowPillar three: Workflow governance