Pillar three · Workflow governance

Today, no one can answer the operational questions that decide whether an EOI program is healthy.

Who started. Who finished. Who abandoned. Who was approved. Did the write-back land. The blind spot costs carriers money and costs employees coverage they thought they had. This page is written for carrier governance and compliance leads; the same view serves carrier operations, brokers, and platform engineering.

The belief

Visibility is the governance mechanism. Not the dashboard. The discipline.

A carrier should not have to wait until the end of OE (Open Enrollment) to learn whether the rules they wrote landed correctly in the systems running enrollment. The administrative portal is built to put every workflow event in one place, with explicit status, owner, and timestamp on every record.

The portal has four areas, each a separate dashboard view, each serving a different audience. Applicant Tracking is per-case operations. Coverage Visibility is book-level reporting. API and Write-Back Visibility is integration health. Configuration and Governance Tracking is the auditable trail from rule to launch.

Pre-launch validation testing is tracked with six explicit statuses. Each test sits in exactly one of them at a time. Each transition is logged. The carrier can see the path from Pending to Certified for Launch before any employee touches the system.

A Director of Governance acts as air traffic control. They run the recurring governance call with the carrier, hold owners accountable for exceptions, and keep the rule changes synchronized across systems. EOIX is not making underwriting decisions. The carrier writes every rule. The underwriting engine executes the carrier's rules at digital speed. The Director of Governance runs the workflow that holds the discipline together.

The administrative portal

Four areas. One operating picture.

Each area renders the same underlying workflow event stream through a different lens.

Area A

Applicant Tracking

Per-applicant view across every employer group: identity, election, GI amount, amount subject to EOI, amount approved, final coverage, status, event timestamps.
Explicit statuses: Initiated, In Progress, Approved, Declined, Abandoned, Write-Back Pending, Write-Back Completed, Integration Exception.
Who cares most: carrier operations, employer HR, brokers.

Area B

Coverage Visibility

Aggregate and per-case view of total elected, GI amount, amount subject to EOI, amount approved above GI, and final approved coverage.
Answers the question: what coverage is the carrier issuing on this group, this cycle.
Who cares most: carriers, brokers.

Area C

API and Write-Back Visibility

Real-time view of API activity, write-back success and failure, integration exceptions, and synchronization issues between EOIX and connected systems.
When something breaks, the portal flags it and identifies the affected case so it can be fixed inside the same enrollment cycle.
Who cares most: carrier IT, ben admin engineering, EOIX operations.

Area D

Configuration and Governance Tracking

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

Pre-launch validation testing

Nothing goes live until the carrier certifies it.

Every test sits in one of six statuses. Each transition is logged. The carrier sees the path to launch before any employee touches the system.

Pending
The test exists in the plan. Nothing has been run yet.
In Review
Carrier validation in progress. Owner and timestamp recorded.
Validated
Carrier confirmed the test passed against the configured rules.
Exception Identified
The test surfaced a gap. The exception is logged with a named owner.
Retest Required
Configuration changed. The test must be re-run before certification.
Certified for Launch
Every test passed. The path is signed off for the enrollment window.

The role

Director of Governance.

EOI air traffic control for the carrier. The role that runs the workflow the architecture is built to support. We are hiring for this role now.

See the open role

What the role does

Runs the recurring governance call with the carrier. Owns the agenda. Owns the action log. Owns the close-out.
Holds owners accountable for exceptions surfaced in the portal. Drives them to Validated or to a logged decision.
Keeps rule changes synchronized across Ben Admin, EOIX, and the carrier’s downstream systems.
Carries the boundary in every meeting. EOIX is not making underwriting decisions. The carrier writes every rule.

EOIX is not making underwriting decisions. The underwriting engine executes the carrier’s rules. The Director of Governance runs the workflow around that decision.

The boundary

What EOIX does, and what it deliberately does not.

The carrier holds the risk. The carrier holds the rules. EOIX runs the workflow.

Next step

Book a 30-minute governance walkthrough.

We walk your governance, risk, and compliance leads through the portal, the validation statuses, and the Director of Governance cadence. No carrier names in the room without your consent.

Book a governance walkthrough See the portal