Most HR reports name people after they resign. Retention Radar looks at records you already have - attendance, leave, time in the company, overtime, recent exits nearby - and explains why someone is flagged. It is a prompt for a conversation. It is not a reason to punish anyone.
HR runs the check when they choose. Every score shows its reasons. Nothing is emailed on its own, and the score is not shown to the employee or their manager.
A band, plus how sure the picture is
The reasons in sentences, not a mystery number
A stay chat, a 1:1, a growth plan, or a workload look
You can dismiss a false alarm, with a reason
This version is an HR screen. The point is a timely conversation, not a score that follows someone into a pay meeting without context.
You press Run when you want a fresh picture. The overview shows how many people sit in high, medium, and low, which departments are warmer, and which reasons come up most. Open a person and you see each factor: what was measured, how much it counted, and a sentence you can read. Then log what you will do - a stay conversation, a one-to-one, a pay review, a growth plan, a workload look - or dismiss the flag if it is wrong, with a reason and a date to hide it until.
Leadership wants to know if a team is tired, if strong people have not moved in years, or if exits are clustering. They do not want a secret score used to block a promotion. The page says so in plain language: an early warning for a conversation, not a basis for a harsh decision. Small teams are hidden on the department view so a group of three is not exposed. Individual mood answers are never used.
In this version, managers and employees cannot open Retention Radar. That is deliberate. A manager should not discover their team as a ranked risk board. If HR decides a conversation is warranted, they log it - a one-to-one, a workload review - and own the follow-up. The product will not email the manager a score overnight.
Companies can list who resigned. They struggle to see, while the person is still at their desk, which patterns usually show up first - and to do something other than worry.
An attrition report after the quarter
The people on it have already left
A check of people who are still employed and not already exiting
A sealed “AI resignation score”
HR cannot say why, so they either ignore it or misuse it
Reasons, weights, and a confidence note when data is thin
Manager dashboards of individual mood
Breaks the promise that a mood answer was not a surveillance tool
Department mood totals only, and only when enough people answered
A spreadsheet of “flight risks” in someone’s laptop
No reason, no follow-up, no record of who opened it
A register, a logged next step, and a record when a person’s detail is opened
One bad week of lateness equals “they will quit”
Not enough history, and no comparison with their previous weeks
Attendance needs enough working days, and it is compared with the previous window
Automatic emails to managers naming “risky” people
The conversation starts as an accusation
No automatic messages. HR decides whether a conversation should happen
Each one is a workplace pattern the product can point at - and explain.
The attrition report arrives after the resignation.
The check looks for patterns while the person is still employed and not already in an exit.
A single “risk score” that nobody can explain in a 1:1.
Each factor shows its sentence, its weight, and how much it added. The pieces add up to the score.
Someone is flagged because a part of HR you do not use showed “zero”.
If there is no performance history, or not enough attendance yet, that factor is left out. It is not treated as a failing mark. Confidence drops instead.
A new joiner of three weeks looks “at risk” because there is no history.
People who are too new, already leaving, or inactive are left out of the check. You can set how new is too new.
Mood answers that were promised anonymous get reused to score a person.
Only a department’s overall mood shift is used, and only when enough people in that department answered. One person’s mood is never read.
A false alarm sits on someone’s name for a year.
Dismiss it with a reason of substance and a date. It stays out of the “needs attention” list until then. The score is still kept.
HR sees a red name and does not know what to do on Monday.
Log a follow-up: stay conversation, manager 1:1, pay review, growth plan, workload change, or something else you name. Mark it done.
Leadership wants a department story and HR has twenty individual guesses.
The overview has a department view, the common reasons, and risk by how long people have been with you.
A score gets used to deny leave, promotion, or a rating.
The screen states it is not a basis for adverse decisions. Nothing in the product auto-starts a warning or blocks a promotion.
If you cannot see why someone is on the list, you should not be having the conversation.
The list is people who are still here. Someone already resigning is excluded, because that warning is no longer early.
Tenure windows, worsening attendance, odd leave patterns, a rating drop, a long time without a move, overtime, a new manager, probation trouble, a team mood shift, nearby exits. You can read them.
If you do not run performance reviews, or there are not enough attendance days yet, that factor is left out. The score uses what you actually have, and shows how complete the picture is.
Individual mood answers and private feedback are not inputs. Department mood is a team total, hidden when the group is too small.
A flag without a follow-up is gossip. Stay chats, 1:1s, growth plans, and workload reviews live on the same page, with an owner and a due date.
There is no overnight job and no automatic email. HR presses Run. Old results can be marked stale so you know when to run again.
Starter does not get a locked people-risk tile. Both higher plans get the same check, the same explanations, and the same follow-ups.
Retention Radar is not on Starter - on purpose.
Same Retention Radar on both plans.
The first thing on the page is that the score is not grounds for a harsh employment decision. The product will not start one for you.
Weights are visible. If performance data is missing, it says so. You are not asked to trust a sealed number.
Gender, age, religion, marital status, disability, medical, and family details are not factors. Anonymous feedback is not re-identified.
A department with too few people does not get a public risk number. The same idea applies to department mood: too few answers, and it is not used.
There is a cooldown so a double-click does not fire two runs, and a note when results are getting old. There is no background send.
Running a check, opening a person, changing settings, logging a follow-up, dismissing a flag, and downloading are written to the change record.
Book a short walkthrough: run a check, open one person, read the reasons, and log the conversation you would actually have. The disclaimer on the screen is part of the product: this is an aid, not a verdict.