PeopleHR Ideas Portal
We have been utilising the new People Analytics feature in People HR and have found it really useful so far. We have realised a few things that could help to iron out the process though.
For example, it seems like when an employee is added to the system they are put down as starting that day, skewing the numbers on the analytics.
E.g. If I added someone today that was starting in March, they would be down as a January Starter.
A similar thing happens when we add a "test" employee to quickly try a new process and then remove them - they are counted as a new starter and leaver despite being deleted from the system, not processed as a leaver.
| Describe the Challenge | We want to improve the new People Analytics integration |
what i have found today is this: I have filtered to April 2026 to get the data on headcount, starters and leavers. I know that two staff left on 30/04/2026 but they are not showing as leavers on the dashboard in april. i check that i've entered leaving dates correctly and yes i have. i query on digital assistant to be told that they'll show as leavers in may 2026. I got this explanation: The final day of employment is treated as a working day, and the employee is only reported as exited the day after that date. So if their last working day is 30/04/2026, they will show as a leaver in May 2026, not April 2026. So on 07/05/2026, you should see them counted as leavers for May. This is not business logic - if I report the april headcount as it is in the dashboard the integrity will be undermined for the following reasons: It contradicts common business logic
Most people interpret “April leavers” as “people whose employment ended in April”, not “people whose first non-employed day was in May”.
It masks known facts
You know two people left on 30 April. A report showing zero leavers for April looks wrong — and it is wrong in a narrative sense, even if the system can justify it technically.
It creates false monthly trends
April is understated
May is overstated
This can distort turnover rates, attrition commentary, and any month-on-month comparisons
Even the digital assistant agrees!!! here's its response which would be funny if it wasn't so frustrating:
You’re not wrong – what you’re describing is a genuine limitation in how the Dashboard is designed.The Dashboard counts leavers based on the day after the final working day, so a 30/04/2026 leaver is recorded in May. That means it’s effectively tracking status change timing, not “events by month”, which can skew monthly reporting and trends. If you need reporting aligned to business logic (leave date in April = April leaver), you’ll need to use reports that rely on the final employment date, such as:
Staff Turnover Report (uses leave date in the year)
A custom query filtered by Final Day of Employment within April
That approach will give you the narrative you’re expecting, even though the Dashboard won’t.
So in effect this all presented/sold as "all singing all dancing" dashboard is ineffectual and i'll have to run manual reports and add to an excel spreadsheet and manually create graphs. Yet another example of the reality of PeopleHR
This idea is 12+ months old and nothing has changed obviously. The continued emphasis on new stuff/the roadmap/less than 3 clicks blah blah is great but you've not got the foundations and don't fix the issues. stop developing and get stuff right
As others have said, it would be really useful to be able to choose who was included, especially when we have set up test employees to check on how new features work, or for training people on the system - we wouldn't want to use a "real employee" for this - and so to exclude these types of account holders from the analytics would be useful. As a result of not being able to, I do not use the Analytics feature as the data is skewed
I have added/deleted a test employees too only to find they show up in the analytics. Very disappointing for such a simple fix.
People Analytics looks to offer some really great features to ease up a lot of running queries. With new starters joining mid year or current employees leaving it is common practice to have to create a new candidate to calculate annual leave allowance/remaining entitled annual leave. As mentioned, I have also noticed that when adding candidates to the system prior to their start date month it logs the new starter as joining in the incorrect month. Is there a way where test candidates can be removed from the statistics and if new starters are based on their start date not the date they are added to the system? This would really enhance this feature that looks to be a great solution to a lot of HR reporting/data collating!