Benefits Admin Dashboard
Six pulse cards, a workbench, quick links, Essential Insights, and Recent Activity & Alerts on one admin-only home screen — every count a queue with an action.
Benefits Administration · Employee Management · Admins only
The Benefits Admin Dashboard That Answers the Call
See what every employee is waiting on, open the whole person with one search, and fix it on their behalf — before they have to ask twice.
Employee Management in Benefits Reimagined is the administrator's console — employees never see it. The Benefits Admin Dashboard counts the life events nearing deadline, the Evidence of Insurability overdue, the documents still missing, and the terminations with COBRA due; one search opens an Employee 360 with nineteen views of one effective-dated record; and the Workbench lets the agent create events, resume enrollments, verify dependents, and terminate benefits for the employee, with every action attributed and logged. Built for the moment an employee calls.
Admins only6 pulse cards19-tab Employee 360On-behalf actionsBR Resolve inside
Reimagining Employee Management for Benefits Administrators
"When an employee calls, the agent has about ninety seconds to find the real problem: a deduction that changed because a child was added, a life event four days from its deadline, a birth certificate that never arrived, an Evidence of Insurability decision the carrier is still sitting on. Benefits Reimagined puts all of it on one admin-only dashboard, opens the whole person with one search, and lets the administrator fix it on the employee's behalf — so the call ends with an answer, not a ticket."
The PulseWhat every employee is waiting onFind the PersonOne search → the Employee 360Diagnose on the Call19 views of one recordAct on Their BehalfWorkbench · events · enrollmentClose the LoopTickets, cases, notes, follow-ups
6pulse cards on the admin dashboard — life events, hires, enrolled benefits, terminations, Evidence of Insurability, documents — each a queue with an action
19views of one employee in the Employee 360 — from overview and portfolio to leave, military, documents, tickets, cases, and notes
1search — name, ID, or department — from the dashboard to the whole person, scoped to the entities the administrator may see
0hand-offs — events, enrollments, dependents, EOI, terminations, and tickets are handled on the employee's behalf from the same screen
One Call, Five Moments the Dashboard Owns
Jane Doe calls because her medical deduction went up. Follow the administrator from the morning dashboard to the closed ticket — without leaving Employee Management.
The dashboard shows the trouble before the phone rings
The Benefits Admin Dashboard is the administrator's home screen, and employees never see it. Six pulse cards count what is at risk right now — qualified life events nearing their election deadline, new hires whose enrollment windows are closing, terminations with COBRA due, Evidence of Insurability overdue, documents not yet uploaded, enrollment activity that has stalled. Each card carries two actions: the blue one opens the employees at risk, the green one opens the whole population.
What it delivers
- Six live counters, each with a one-line diagnosis (“6 overdue by 12 days · 5 within deadline”)
- At-risk and all-population actions on every card — a queue, not a chart
- “Show suggested additions”: Athena proposes new cards from where tickets cluster
- Quick links to the Communication HUB and Business Rules from the same screen
Why it matters
The next call is usually already on the board.
An employee who calls about a deadline is one click away from the list she is on — and the administrator saw the list at 8 a.m.
One search opens the whole person
Type a name, an employee ID, or a department into the dashboard search and the Employee 360 opens on the record — identity, title, department, pay frequency, benefit group, entity, and status in the header. The Overview tab leads with “For you today”: the open items on that employee, ranked by deadline and blocker, so the agent is reading the problem list while the employee is still saying hello.
What it delivers
- Search by name, ID, or department across every entity the administrator is scoped to
- Header context in one line: ID, title, department, pay frequency, benefit group, employment status
- “For you today” — deadlines, missing documents, overdue EOI, open tickets, unsubmitted enrollments
- Cost tiles, AI insights, and the concierge portal on the same first screen
Why it matters
Average handle time starts falling before the first question is answered.
No “let me pull that up” across four systems — the record is the search result.
Nineteen views of one effective-dated record
The Employee 360 is organized the way a call unfolds. Overview, Requests, Profile, Benefits Eligibility, Unified Benefits Portfolio, Benefit Events, Dependents, Beneficiaries, Medical Information, Physicians & Drugs, Date Specification, Leave, Military & Veteran, Documents, Enrollment, Terminations, Tickets, Cases, and Notes all read the same effective-dated record. “Why did my deduction go up?” is answered in the Portfolio's Costs panel: the tier moved from Employee to Employee + Child on the birth event's date, and the plan, option, and employer share are right there with it.
What it delivers
- Unified Benefits Portfolio: Health, Insurance, Savings, FSF, Miscellaneous, Credit, and COBRA records with plan data, administration, and costs
- Benefit Events: coverage today per plan, active and completed life events, upcoming deadlines and the actions still due
- Requests: every workflow touching the employee with its current step (“Document approval · step 0 of 2”)
- Profile with change history, eligibility records with access controls, leave with the 50/75 and key-employee indicators
Why it matters
The agent explains the cause, not just the symptom.
A deduction question that used to need payroll, HR, and the carrier is one tab and one date away.
Do it for the employee — with the same guardrails
Administrators do not just look. From the Benefits Administration Workbench and the employee's own tabs they create qualifying life events on the employee's behalf, resume or submit an in-progress enrollment, add or verify a dependent, request a document, follow up an Evidence of Insurability case, run automatic and default enrollment, or terminate elected benefits with the COBRA event, carrier terminations, and final deductions derived from one action. Every action is attributed — performed by the administrator, for the employee — scoped by role, and written to the change history.
What it delivers
- Workbench: Participation Monitor, Event Reasons, Evidence of Insurability, Automatic & Default Enrollment, Terminate Benefits
- Enrollment cards with progress, deadline, and current cost — resume, review, and submit on the employee's behalf
- Life events created for the employee with the event window, required documents, and IntelliSuggest guidance applied
- Termination preview: Spotlight, Insights, and IntelliSuggest show the effect before anything is committed
Why it matters
Problems are fixed on the call, not logged for later.
Role scoping, mandatory reasons, and attributed delegation mean “on behalf of” never means “unaccountable”.
Tickets, cases, and notes live on the record
Tickets and Cases tabs bring BR Resolve into the Employee 360 — SLA state, priority, category, owner, and the conversation — so the agent resolves the ticket on the same screen that answered it. Notes are saved against the employee, the explanation goes out through the Communication HUB, and the follow-up the call uncovered (a document still missing, an EOI still pending) becomes the next ticket automatically, back on the dashboard's pulse cards.
What it delivers
- Ticket and case management per employee with SLA, priority, category, status, owner, and due date
- Recent Activity & Alerts across eight categories — profile, integrations, payroll, compliance, documents, communications, tickets, system
- Notes and communications filed to the record and the Document Center
- Follow-ups created from the call route through BR Resolve and surface on the dashboard
Why it matters
First-contact resolution with a paper trail.
The employee hangs up with an answer, a confirmation, and nothing to chase.
Core Capabilities of Employee Management
The admin console for seeing, diagnosing, and fixing an employee's benefits — on the governed, effective-dated record every other BR module shares.
Employee 360
One search opens nineteen views of one effective-dated record — overview, requests, profile, portfolio, events, dependents, documents, enrollment, tickets, cases, notes.
On-Behalf Actions
Create life events, resume and submit enrollments, verify dependents, follow up EOI, run default enrollment, terminate benefits — attributed, scoped, logged.
Tickets & Cases in the Record
BR Resolve inside the employee view: SLA, priority, owner, conversation, notes, and follow-ups created from the call and routed automatically.
The Governed Record Beneath
HRIS sync with provenance, rule-resolved benefit groups, verified dependents and beneficiaries, and employment events that re-evaluate eligibility the same day.
Access Control & Audit History
Field-level RBAC, scoped and time-boxed delegations, immutable change history with actor and rule version, and as-of-date views for audits and disputes.
Under the Dashboard, Five Governed Controls
The dashboard is only as trustworthy as the record it reads. Every tab above sits on one effective-dated employee record — 140+ SuccessFactors fields mapped through Intelligent Services Center, or any HRIS through the integration control plane — resolved to benefit groups by rules and auditable to the day. Follow Jane from sync through a transfer and a leave.
The employee record arrives mapped, not re-keyed
Employee Management starts with HRIS Sync: employment, organization, compensation, and dependent data flow in from SAP SuccessFactors through Intelligent Services Center events, or from Workday, UKG, ADP, Ceridian, and Paycom through the integration control plane. Every field carries provenance — source, transformation, and the sync that delivered it — and validation runs before the record touches eligibility.
What it delivers
- Employment status, class, hours, location, entity, and union code mapped once per HRIS
- Dependent and beneficiary records with relationship codes and verification state
- Field-level validation with exceptions routed to a worklist, never silently defaulted
- Delta sync on events — hire, change, leave, termination — plus a full reconciliation run
Why it matters
Benefits sees the same employee HR and payroll see — on the same day.
A mismatch is an exception with a source, not a mystery discovered at carrier file time.
Business rules place every employee in the right benefit group
Eligibility is not a checkbox on the employee. Client-scoped business rules read class, scheduled hours, location, entity, union status, and seniority and assign the benefit area, benefit group, and benefit status that drive which plans, contributions, and waiting periods apply. Rules are effective-dated and versioned, so a change to the rule and a change to the employee are both explainable later.
What it delivers
- Benefit area, group, and status assigned by rule — never typed
- Waiting periods, seniority bands, and variable-hour measurement evaluated on every change
- Multi-entity and PEO client scoping: an employee's benefit area must resolve to their own entity or the change is blocked with an exception
- Rule simulation before go-live: see who moves groups before the rule takes effect
Why it matters
Incorrect enrollments are prevented at the record, before an election exists.
"Why is Jane in BG-HRLY-02?" is answered by a rule version and four data values, not by whoever set it up.
Dependents and beneficiaries with proof attached
A dependent on the employee record carries a relationship, a date of birth, an eligibility status, and the evidence behind it. Dependent verification runs through BR IntelliVerify against the document catalogue; verified evidence lives in the Document Center with a validity period and is reused across Open Enrollment, life events, and audits instead of being requested again. Beneficiaries follow the same pattern — designations, percentages, and contingents, with e-signature where the plan requires it.
What it delivers
- Relationship, DOB, student and disability status, and coverage eligibility per dependent
- Verification state with evidence, validity dates, and the catalogue version it was judged under
- Beneficiary designations per plan with primary/contingent splits that must total 100%
- Age-out, divorce, and death events change dependent eligibility automatically, with notices
Why it matters
Only eligible dependents stay covered, and nobody proves the same relationship twice.
A child turning 26 leaves the plan on the right date with the right notice — without HR watching a calendar.
Every employment change re-evaluates benefits the same day
Hires, class changes, transfers between entities, hours changes, leaves, and terminations arrive as events, not as tickets. Each one re-runs eligibility, derives the coverage effect and its date, and hands off to the module that owns the next step — a new-hire enrollment window, Direct Billing for an unpaid leave, a COBRA qualifying event on termination, a retro recalculation through BR ReVerge when the change lands late.
What it delivers
- New hire: waiting period, enrollment window, and IntelliSuggest-guided elections opened automatically
- Transfer: benefit area re-resolved; a cross-entity move is blocked until it resolves cleanly
- Leave: Leave Impact orchestrates premium continuation, arrears, and eligibility hold — without becoming an absence system
- Termination: coverage end dates, COBRA event, final deductions, and carrier terminations from one event
Why it matters
High-risk changes stop depending on someone remembering the downstream steps.
A late-arriving change is a retro calculation with an audit trail, not a manual correction.
Who can see and change an employee record — and the proof
Role-based access control scopes every screen and field to the population an administrator is allowed to touch — an entity, a client inside a PEO tenant, a plant, a union group. Approval delegations are temporary, scoped, and attributed ("performed by X, acting for Y"). Every change to an employee, dependent, or beneficiary keeps its before-and-after values, who made it, which rule applied, and which sync or event caused it.
What it delivers
- Role and population scoping down to field level; sensitive fields masked by role
- Delegated approvals with mandatory end dates, delegate acceptance, and never-delegatable actions
- Immutable change history: old value, new value, actor, source event, rule version, timestamp
- Point-in-time views — "show me this employee as of 03/31" for any audit or dispute
Why it matters
Audit questions become filtered views, not reconstructions.
Section 508 and WCAG-conformant screens, so public-sector and higher-education administrators work in the same console as everyone else.
Athena for Admins · inside Employee Management
The Analyst on Every Call, The Lookout Between Them
Athena reads the employee record alongside the agent: why this deduction, which event caused it, what is still missing, and what to say. Between calls it watches the dashboard — who is about to miss a deadline, whose document never arrived, which tickets will breach — and proposes the outreach for a person to approve.
- "Why did her deduction change?" — the event, the tier move, the effective date, and the plan cost in one sentence, drafted for the employee in plain language
- Who calls next — employees with events closing in days and no elections saved, ranked by how often that pattern ends in a ticket
- Suggested cards — “Show suggested additions” proposes new pulse cards from where tickets and cases are clustering this month
- Dependent hygiene — dependents approaching age-out, evidence expiring, or coverage without a verified relationship, surfaced on the employee before the audit
- Eligibility drift — hours, class, or location changed in payroll but not yet in benefits, flagged in the 360 before the carrier file goes out
Jane says her medical deduction went up this month. Why?
AthenaHer Birth Event (LE-2026-3182) added Maya on 08/14, which moved Standard Medical from Employee to Employee + Child. The per-paycheck cost went from $1,000.02 to $1,344.18 starting with the 08/31 pay date. Nothing else on the record changed. One item is still open: Maya's birth certificate has not been uploaded, so dependent verification is pending.
TierEE → EE+C · effective 08/14
Per paycheck$1,000.02 → $1,344.18
Send Jane the explanationRequest birth certificateResolve #9510
Anyone else I should call before they call me?
AthenaNine employees have a divorce or birth event closing in under five days with no elections saved; three of them also have a document missing. I can queue reminders for all nine and a call-back list for the three — you approve, I send.
Ask Athena about this employee…
What Employee Management Changes
Problems surface before calls
Pulse cards count what employees are waiting on; the agent starts the day with the list, not the inbox.
One search, the whole person
Name, ID, or department opens nineteen views of one effective-dated record.
Causes, not symptoms
Costs, events, requests, and documents agree with each other because they read the same record.
Fixed on the call
Events, enrollments, documents, EOI, and terminations handled on the employee's behalf — attributed and logged.
Tickets close where they open
BR Resolve, notes, and communications live on the record; follow-ups route themselves.
Admins only, by design
Employees never see the console; role scoping and delegation decide exactly who does.
Where It Shows Up in the BR Experience
Employee Management is the administrator's entry point to the whole platform — the same React console where plans, rules, and workflows are configured, backed by one effective-dated data model. Employees see their own record in the portal and the BR mobile app; administrators see everyone they are scoped to, with everything that is waiting.
- Admin: Benefits Admin Dashboard — pulse cards, Workbench, quick links, Essential Insights, and Recent Activity & Alerts on the admin-only home screen
- Admin: Employee 360 — nineteen tabs on one record, opened by one search, with “For you today” leading the overview
- Admin: on-behalf actions — life events, enrollments, dependents, documents, EOI, default enrollment, and terminations performed for the employee with attribution
- Service desk: tickets and cases — BR Resolve inside the record, notes on the employee, explanations through the Communication HUB
- Analytics: where employees get stuck — documents, EOI, unsubmitted enrollments, deduction questions, and sync exceptions by count, with small-cohort suppression
Ready to take the next employee call with the answer already open?
Bring three real scenarios your service desk handles every week. We'll run them through the Benefits Admin Dashboard and the Employee 360 — find the person, find the cause, fix it on their behalf, close the ticket — and time it.
Admins only · RBACAttributed on-behalf actionsSuccessFactors · any HRISSOC 2ISO 27001GDPR · PIPEDA
Employee Management FAQs
Administrators only. The Benefits Admin Dashboard and the Employee 360 are role-gated screens for benefits administrators, HR agents, and service-desk staff. Employees use their own portal and the BR mobile app; they never see the admin console, and what an administrator can see or change is scoped by role and population.
One search. Typing a name, ID, or department opens the Employee 360 with “For you today” at the top — deadlines, missing documents, overdue Evidence of Insurability, open tickets, and unsubmitted enrollments ranked by urgency — so the likely reason for the call is on screen before the employee finishes describing it.
Create qualifying life events, resume and submit in-progress enrollments, add and verify dependents, request documents, follow up EOI cases, run automatic and default enrollment, and terminate elected benefits with the COBRA event, carrier terminations, and final deductions derived automatically. Every action is attributed (“performed by X, for Y”), reason-captured, and written to the change history.
Six pulse cards (qualified life events, hires, enrolled benefits, terminations, Evidence of Insurability, documents), the Benefits Administration Workbench (Participation Monitor, Event Reasons, EOI, Automatic & Default Enrollment, Terminate Benefits), quick links to the Communication HUB and Business Rules, Essential Insights, and Recent Activity & Alerts across eight categories.
Nineteen tabs on one record: Overview, Requests, Profile, Benefits Eligibility, Unified Benefits Portfolio, Benefit Events, Dependents, Beneficiaries, Medical Information, Physicians & Drugs, Date Specification, Leave, Military & Veteran, Documents, Enrollment, Terminations, Tickets, Cases, and Notes.
Yes. The Tickets and Cases tabs bring BR Resolve into the Employee 360 with SLA state, priority, category, owner, and the conversation, so the agent resolves the ticket on the screen that answered it. Follow-ups uncovered on the call become new tickets that route automatically and appear on the dashboard.
It maintains the employee, dependent, and beneficiary data that eligibility, enrollment, payroll deductions, carrier files, and compliance all depend on — synced from the HRIS, resolved to benefit groups by rules, and kept effective-dated so every past state can be shown — and gives administrators the dashboard and 360 view to act on it.
No. SAP SuccessFactors, Workday, UKG, ADP, Ceridian, or Paycom stays the system of record for employment. Benefits Reimagined syncs the fields benefits needs, adds the benefits-specific attributes (benefit area, group, status, verification state), and writes deductions back to payroll.
By effective-dated business rules that read class, scheduled hours, location, entity, union status, and seniority. Rules are simulated against the population before they take effect and approved by someone other than the author; every assignment keeps the rule version that made it.
Yes. Different rule sets apply to different populations on the same record structure — including CBA-specific waiting periods, variable-hour measurement for hourly staff, and entity-scoped benefit areas for organizations with many legal entities or operating regions.
The event re-runs eligibility and hands off automatically: enrollment windows for hires and transfers, Leave Impact and Direct Billing for unpaid leave, COBRA qualifying events and carrier terminations for separations, and BR ReVerge when a change arrives late and needs retroactive recalculation.
Dependents are verified by BR IntelliVerify against an administrator-maintained document catalogue, with evidence stored in the Document Center and reused until it expires. Beneficiary designations are captured per plan with primary/contingent splits and e-signature where required.
Access is role- and population-scoped down to the field, approvals can be delegated temporarily with attribution, and every change keeps before and after values, the actor, the source event, and the rule version — with as-of-date views for audits and disputes.
Every Employee's Problem, Visible Before They Call
An admin-only dashboard, a nineteen-view Employee 360, and the power to act on the employee's behalf — on one governed, effective-dated record.