Skip to main content

Reporting & Data Discrepancies

Understand why numbers may differ across dashboards and how data refresh timing works.

Written by Mohamed Shantory

Before You Start

  • Different roles see different data by design this is not a bug

  • Filters applied on one dashboard do not carry over to another

  • Some reports aggregate data on a schedule and may not reflect changes instantly


Numbers Don't Match Between Dashboards

Why two dashboards can show different counts

There are four common reasons numbers differ:

Filters: One dashboard may have an active filter (department, date range, job role) that the other does not. Always check the filter bar and reset filters before comparing.

Data scope: The admin dashboard shows organization-wide data. A manager dashboard shows their team only. These will always produce different numbers.

Timing: One view may have refreshed more recently than another. Refresh the page on both views before comparing.

Deactivated users: Some reports exclude deactivated talents from their counts; others include them. Check whether the report you're reading explicitly states how deactivated users are handled.

What to do

  1. Reset all active filters on both dashboards

  2. Confirm you're comparing the same date range on both

  3. Confirm both views are set to the same scope (organization vs. department vs. team)


Completion Rates Look Wrong

Rate is lower than expected

  • Talents who have not started an activity count as 0% and pull the average down

  • Deactivated talents may still be included in the denominator

  • A talent enrolled in an activity but later removed may still appear in some counts

Rate is higher than expected

  • An active filter may be narrowing the participant set to a group with higher completion

  • Records marked complete manually by an admin count the same as self-completed records


Data Not Updating

A change I made isn't reflected in the report

  • Try refreshing the page first

  • If data still hasn't updated after a few minutes, log out and back in

  • Some aggregated reports have a short delay before reflecting new changes

A talent completed something but it doesn't show in the report

  1. Check the talent's individual profile confirm the completion is recorded there

  2. If the completion appears on the profile but not the report, the report may be cached try refreshing

  3. If it's not on the profile either, the completion may not have saved correctly — ask the talent to verify


Different Users See Different Numbers for the Same Report

This is expected behavior. Lumofy applies role-based data scoping:

Role

What They See

Super Admin / Admin

Organization-wide data

Manager

Their direct reports only

Talent

Their own data only

If a manager reports a number that doesn't match the admin view, they are seeing their team's subset not the full organization total. This is correct behavior, not a discrepancy.


FAQ

How often does Lumofy refresh dashboard data?

Most dashboards update in near real-time. Aggregated reports may have a short delay. Refreshing the page usually resolves stale-looking data.

Can I export report data to verify numbers?

Most dashboards update in near real-time. Aggregated reports may have a short delay. Refreshing the page usually resolves stale-looking data.

A talent is showing as not enrolled but I enrolled them. Why?

Check the talent's profile directly. If the enrollment is confirmed there, the dashboard may need a refresh. If it's not on their profile, the enrollment may not have saved try enrolling again.

Why does my eNPS score differ from what our HR team is reporting?

Confirm you are both viewing the same survey and the same date range. Also check whether the dashboard is filtered by department or division a filtered view produces a subset score that will differ from the organization-wide score.

Did this answer your question?