Understanding the analysis
Attrition risk
VooHr can show an attrition-risk percentage from the employee score calculation and a separate model-generated risk in conversation analysis. Neither is a reliable prediction of an individual's future decision.
Directory calculation #
The rule-based employee scoring function computes attrition_risk_pct as 100 minus wellness_score, bounded between zero and one hundred. Wellness starts at 100 and configured penalties or a small survey adjustment depend on overtime, absence, performance change, missed deadlines, and engagement survey score.
This is a deterministic transformation of those inputs, not a model trained to forecast resignations. Missing signals are not penalized, so an apparently low risk can reflect absent data rather than evidence that an employee plans to stay.
Conversation analysis value #
The AI analysis may also provide an attrition-risk field in the risks section. That value is generated from one transcript, so it may capture a topic or phrase without seeing broader context, and it can be mistaken. It is not the same calculation as the directory value.
Do not compare or combine these percentages as if they were calibrated on a shared scale. Check which screen and source produced the value before discussing it.
Use it as a prompt, not a forecast #
Ask what data supports the indicator, when it was collected, and what may be missing. If you need to understand an employee's plans, ask them respectfully rather than presenting an AI estimate as their intention.
Do not use an indicator by itself for an employment decision. Keep the conversation, organizational policies, privacy requirements, and human judgement at the center.
Use this guidance thoughtfully
This page describes the current product workflow; it is not an HR policy or a promise about every deployment. Before acting on information about an employee, verify the source record, consider context the system cannot see, and use your organization's process. If a control behaves differently from this guide, check the current workspace UI and confirm the saved result rather than assuming an action completed.