Cross-Module Signal Reader
Reads the dated facts every module writes on one model — billing, compliance, enrollment, participation, workflow, delegations, documents, sync, Athena quality — and adds none of its own.
BR Spotlight: The Short List of What Needs Attention Today
Not a dashboard, not an alert storm. One ranked list per role — the waive rate that turned, the invoice that will not reconcile, the approval nobody owns, the ACA member drifting toward 95% — each with a reason, an owner, a deadline and a drafted action.
Spotlight watches every module on one data model and ranks the signals a person should act on today: blockers first, risks next, optimizations last. It surfaces only what a person must decide — never a status the system could have prevented — and it draws on SuccessFactors data in real time and on Workday, UKG, ADP, Dayforce and Paycom data through HRIS Sync.
Blocker · risk · optimizationWhy am I seeing this?Owner and deadline on every itemAction drafted in the owning moduleAny HRIS signal
Attention Is the Scarce Resource — Spotlight Spends It Well
A benefits team has more dashboards than hours. Spotlight exists so that nobody has to open twelve of them to find out what matters this morning. It reads the same effective-dated model every module writes, scores each signal by consequence and by time left, strips out anything the platform could have prevented on its own, and hands each person a short list they can finish — with the reason behind every item and the action already drafted where it belongs.
WatchSignals from every module, one modelScoreConsequence × time left, per rule and modelRankBlocker · risk · optimization, per roleActDrafted in the owning module; a person commitsAny HRISSame list for every entity
3severity classes — blocker, risk, optimization — ordered so the list reads top-down without a legend
1reason on every item: “Why am I seeing this?” names the rule or model, the records and the threshold behind the spotlight
0preventable status errors surfaced — if a rule or an auto-action can stop it, Spotlight does not show it
12modules feeding one list: enrollment, participation, ACA, carrier billing, direct billing, four-way reconciliation, ReVerge, workflow, delegations, documents, HRIS Sync, Athena quality
One Monday Morning, Five Stages
Follow a carrier invoice that does not match from the four-way reconciliation that noticed, through the score that put it first, the list it landed on, the action drafted in Carrier Billing — and the same morning for an entity on UKG.
Every module is a source — Spotlight adds none of its own.
Spotlight does not collect data; it reads the records other modules already keep on the one effective-dated model. The four-way reconciliation posts a variance. Workflow posts an overdue step whose escalation target is the approver. ACA Intelligence posts a member's monthly offer rate. Benefits Participation posts a waive-rate trend. HRIS Sync posts an exception. Athena Insights posts a quality cluster. Each is a fact with a date, a cohort and a record behind it — which is what makes the next stage possible.
Signals Spotlight watches
- Billing: invoice variances, unmatched lives, premium leakage, payment approvals
- Compliance: ACA offer and affordability drift, readiness failures, notice deadlines
- Enrollment and participation: drop-off steps, waive surges, EOI and document deadlines
- Operations: overdue approvals, delegation coverage gaps, sync exceptions, Athena quality clusters
Why it matters
Because every signal is a record on one model, the reason behind a spotlight is always a link, never a sentence someone typed.
Spotlight never invents a signal: if a module has not written the fact, there is nothing to rank.
Consequence times time left — by rule where policy is clear, by model where it is not.
Every signal gets two scores. Consequence: dollars at stake, people affected, regulatory exposure, or an SLA at risk. Time left: the deadline the owning module already knows — the EOI grace date, the ACA month end, the approval due day, the invoice payment date. Where policy is explicit — an invoice over a threshold, a delegation about to lapse — a business rule sets the score. Where it is not — a waive trend, a billing anomaly, a drifting offer rate — the ML Engine scores it and states its confidence. Anything a rule or an auto-action could resolve on its own is resolved, and never scored.
How a score is built
- Consequence: money, people, exposure or SLA, taken from the record
- Time left: the module's own deadline, not a guess
- Rules where policy is explicit; ML with a stated confidence where it is not
- Prevented items — auto-approvals, auto-matches, auto-reminders — excluded
Why it matters
A $2,000 variance due in a month and an $18,000 variance due Thursday should never sit at the same height.
Delegation Spotlight, for example, surfaces acceptance gaps and unavailable delegates — never an “expired but active” status, because the platform makes that impossible.
One list per role — blockers, then risks, then optimizations.
The scored signals are cut by role-based permissions and by scope: the benefits manager sees enrollment, participation and cases for their population; the AP clerk sees invoices and payments; the compliance lead sees ACA and notices; the HRBP sees the approvals and delegations that touch their people. Each list is ordered the same way — blockers that stop something today, risks that will become blockers if ignored, optimizations that are worth doing — so it reads top-down without a legend. Every item opens “Why am I seeing this?”: the rule or model, the records, the threshold and the date.
What an item carries
- Severity: blocker, risk or optimization
- Why am I seeing this? — the rule or model, the records and the threshold
- Owner, taken from the owning module, and the deadline
- The drafted action, and the module it will run in
Why it matters
A list you can finish before lunch changes behaviour; a wall of alerts changes nothing.
Cohort suppression applies here too — a spotlight about four people in one site is folded into its region before it is shown.
The action is drafted where it belongs — and a person commits it.
Spotlight owns no actions. For each item it asks the owning module to draft the next step: Carrier Billing prepares the variance case with the 61 lives listed; Workflow prepares a temporary delegation and a template fix; Communication HUB prepares the plan-comparison campaign; BR Resolve prepares the Athena Quality Review; HRIS Sync prepares the exception case. The person reads the reason, opens the draft, changes what they want and commits it in that module — inside its own audit trail. Spotlight records that the item was actioned, snoozed with a reason, or dismissed with a reason, and learns from which items are dismissed.
Where the action runs
- Carrier Billing and 4-Way Reconciliation for invoice and payment items
- Workflow and Delegations for stalled approvals and coverage gaps
- Communication HUB for campaigns, reminders and job aids
- BR Resolve, ReVerge and HRIS Sync for cases, retro corrections and data exceptions
Why it matters
Nothing changes because Spotlight said so; something changes because a named person approved a draft in the module that owns it.
Dismissed items carry a reason; a rule that is dismissed often is flagged to the administrator for tuning.
One list for the whole group — whatever HRIS each entity runs.
A signal is a record on the model, and the model does not care where the employee came from. An entity on SAP SuccessFactors posts hires, terminations and pay changes in real time; an entity on Workday, UKG, ADP, Dayforce or Paycom posts them through HRIS Sync with the same fields. So a termination that was never sent to the carrier surfaces the same way in both — and a sync exception on a non-SAP feed is itself a Spotlight signal, with HRIS Sync as the owning module. Group-level roles see one list across entities; entity roles see only theirs.
How entities appear
- SuccessFactors entities: real-time signals inside the SuccessFactors sign-in
- Other HRIS entities: the same signals through HRIS Sync, plus feed exceptions as items
- Group roles see all entities; entity roles see their own scope
- Owners resolve from each HRIS identity through SSO
Why it matters
An acquired company on another HRIS gets the same morning list on day one, not after a migration.
Feed health itself is a signal: a file that did not arrive is a blocker for the entity that depends on it.
Core Capabilities of BR Spotlight
Built to ration a benefits team's attention — not to add another dashboard to the twelve it already has.
Rule + ML Scoring
Consequence and time left from the record; rules where policy is explicit, the ML Engine with a stated confidence where it is not.
Prevention Filter
Whatever a rule or an auto-action can resolve is resolved and never shown; Spotlight surfaces decisions, not status errors.
Role-Scoped Ranked Lists
Blocker, risk, optimization per role and scope, ordered so the list reads top-down; cohort suppression applied before an item renders.
Why Am I Seeing This?
Every item names the rule or model, the records, the threshold and the date behind it — a link, never a typed sentence.
Actions in the Owning Module
Drafts prepared by Carrier Billing, Workflow, Communication HUB, BR Resolve, ReVerge or HRIS Sync; a person commits inside that module's audit trail.
Alerts and Dashboards vs. BR Spotlight
Every platform can send an alert. Spotlight is what you get when the alerts are scored, filtered, explained and drafted — and the preventable ones never fire.
| Monday morning | Alerts and dashboards | BR Spotlight |
|---|---|---|
| Where do I start? | Twelve dashboards and forty emails. | One ranked list per role — blockers, risks, optimizations. |
| Why is this here? | A red number. | “Why am I seeing this?” — the rule or model, the records, the threshold, the date. |
| Who owns it? | Whoever opens the email first. | A named owner from the module, with the deadline the module already knows. |
| What do I do? | Open the module, find the record, decide. | A draft is waiting in the owning module — change it, commit it, audited there. |
| An invoice matched itself | Another green alert to dismiss. | Never shown — prevented items are counted, not listed. |
| A department of four | An alert that identifies a person. | Folded into its region before the item renders. |
| An entity on another HRIS | A separate inbox from a separate tool. | The same list, with the feed's own health as a signal. |
Athena beside Spotlight
Ask the List Why, What If, and What Else
Spotlight ranks; Athena explains and drafts. Ask why an item is first, what happens if it waits until Friday, which items share a cause, or what changed since yesterday — and Athena answers from the same records and rules, then prepares the action in the module that owns it.
- “Why is the invoice above the payroll change?” — consequence and time left, side by side, with the rule that set each
- “What if I leave it until Friday?” — the payment date, the lives affected and the credit window
- “Are these two items the same problem?” — the 43 terminations behind both the variance and the ACA drift
- “What changed since yesterday?” — items added, closed, snoozed and prevented, with the counts
- “Show me the UKG entity's list” — the same ranking, scoped to that entity, feed health first
Why is INV-2291 above the stalled pay-distribution change, and are they related to the ACA item?
Athena · from the records behind the itemsINV-2291 ranks first because $18,420 is at stake for 61 lives and payment is due Thursday; the pay-distribution change affects one employee and has two days to the payroll cut-off. The invoice and the ACA drift do share a cause: 43 of the 61 billed-not-enrolled lives are August terminations that were never sent to the carrier, and the same 43 are still counted as offered in ACA member 3's August month. Fixing the re-send resolves most of both.
Sources: 4-Way Reconciliation · INV-2291 · HRIS Sync · carrier outbound, August · ACA Intelligence · member 3 · August
Show the 43Open the variance case
Draft the re-send and the variance case, and tell me what's left.
AthenaDrafted, nothing sent: an HRIS Sync re-send of the 43 August terminations to the carrier, and a Carrier Billing variance case for INV-2291 with all 61 lives listed and the 43 marked “termination not sent”. After the re-send, 18 lives remain unexplained; the case asks the carrier for a credit on those. Both drafts wait for your approval, and the ACA month will recompute overnight.
Approve re-sendOpen case draft
Ask about any item on the list…
Why Benefits, Finance and Compliance Leaders Choose BR Spotlight
A List You Can Finish
Blockers, risks and optimizations per role — short enough to clear before lunch, ordered so the top is always the top.
Reasons, Not Red Numbers
Every item opens the rule or model, the records and the threshold behind it.
Prevented Means Silent
Auto-matches, auto-approvals and auto-reminders are counted, never listed — no alert storm.
Drafted Where It Runs
The action waits in Carrier Billing, Workflow, Communication HUB or BR Resolve, inside that module's audit trail.
Scoped and Cohort-Safe
Each person sees their scope; a spotlight about four people is folded up before it renders.
Every Entity, Every HRIS
SuccessFactors in real time, any other HRIS through HRIS Sync — with feed health as its own signal.
Where Spotlight Appears — Every Home Screen, One Engine
Spotlight is not a separate application. It is the top of the Benefits Admin Dashboard, the “For you today” band on Employee Home, the risk panel in the Workflow Control Tower, the readiness strip in ACA Intelligence and the next-best-actions band on the ACA execute screen — one engine rendering the slice each screen's role can act on.
- Benefits Admin Dashboard — the administrator's ranked list across every module, with the Employee 360 one click away
- Employee Home — the employee's own “For you today” — offers, deadlines and gaps, with a verb that matches the gap
- Workflow Control Tower — the risk panel: stalled steps, escalation loops, delegation coverage gaps
- ACA Intelligence — readiness failures and threshold drift as blocker → risk → optimization
- Carrier Billing and 4-Way Reconciliation — variances and unmatched lives ranked by dollars and payment date
Show Us Your Monday. We'll Show You the List.
Tell us what your team checks first thing on a Monday — the invoice queue, the approvals inbox, the ACA tracker, the OE report. We'll connect those signals on your data, set your thresholds, and show you the ranked list, the reason behind each item and the drafts waiting in the modules that own them.
Blocker · risk · optimizationWhy am I seeing this?Prevented, not shownAI proposes · a person commitsCohorts under 5 suppressed
BR Spotlight FAQs
The attention engine inside Benefits Reimagined: it reads the dated facts every module writes on one data model, scores each by consequence and time left, filters out anything the platform can resolve on its own, and gives each role a short ranked list — blockers, risks, optimizations — with a reason, an owner, a deadline and an action drafted in the owning module.
Alerts fire on a condition and leave the sorting to you; dashboards show everything and leave the finding to you. Spotlight ranks, filters and explains: it never shows an item a rule or auto-action could have prevented, it orders what remains by severity and deadline, and every item opens “Why am I seeing this?” with the records behind it.
Invoice variances, unmatched lives and payment approvals from Carrier Billing and 4-Way Reconciliation; ACA offer and affordability drift and readiness failures; enrollment drop-off, waive surges, EOI and document deadlines; overdue approvals, escalation loops and delegation coverage gaps from Workflow; HRIS Sync exceptions and late feeds; and Athena quality clusters from Chatbot Analytics.
Consequence — money, people, exposure or SLA taken from the record — multiplied by time left, using the deadline the owning module already knows. Where policy is explicit, a business rule sets the score; where it is a trend or an anomaly, the ML Engine scores it and states its confidence on the item.
No. It asks the owning module — Carrier Billing, Workflow, Communication HUB, BR Resolve, ReVerge, HRIS Sync — to prepare a draft, and a named person commits it there, inside that module's audit trail. Spotlight records only that the item was surfaced and whether it was actioned, snoozed or dismissed, with the reason.
If a rule or an auto-action can resolve something — an invoice that matches, a step that auto-approves by condition, a reminder that sends itself — the platform does it and Spotlight counts it rather than listing it. The list is for decisions a person must make; a status the system could have prevented is a defect, not a spotlight.
Every list is cut by role-based permissions and scope, and any item whose cohort is below the configured minimum is folded into the next level before it renders. Employees see only their own “For you today”; administrators see the populations they are scoped to.
Yes. Signals are records on the model, so an entity on Workday, UKG, ADP, Dayforce or Paycom feeding through HRIS Sync produces the same items as an SAP SuccessFactors entity feeding in real time. Feed health is itself a signal: a late file becomes one blocker that holds the items depending on it, with HRIS Sync as the owner.
Fewer Things to Look At. The Right Things First.
One ranked list per role, a reason on every item, a draft in the module that owns it — across SAP SuccessFactors entities and every entity on another HRIS.