Understanding the analysis
Burnout index
The label 'burnout index' can refer to an indicator in a generated conversation analysis. It is not a clinical measure and must not be treated as an assessment of an employee's health.
Where it comes from #
The analysis payload can include a burnout-index value under its risks section. The language model generates that value from the transcript text supplied for that run, subject to the output validation and storage flow. It is therefore about one conversation and may be absent when the model provides no usable evidence.
Separately, the directory's wellness score uses a rule-based calculation. One input is overtime hours in the trailing three weeks, with specified penalties at configured thresholds; the page may also display a burnout-related indicator derived from other employee signals. Do not conflate these sources.
What it does not say #
A transcript-derived number cannot diagnose burnout or determine its cause. It cannot show whether a person's experience is persistent, whether the account is complete, or whether workplace and personal factors have been considered.
The directory's rule-based result is only as complete as its inputs. New employee records initialize several signals to zero and the engagement score to no value, so verify that relevant fields are maintained before interpreting the result.
How to review #
Read the source transcript or underlying signal inputs and look for evidence, dates, and missing context. Ask the employee about their experience without presenting a number as a conclusion. Where the measure conflicts with what the employee says or other reliable evidence, investigate the discrepancy rather than preferring the score.
See Scores explained and What the AI can and cannot tell you before using any indicator in an HR discussion.
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.