Skip to content
VooHr Support Contact Sign in

Understanding the analysis

Behavioural Intelligence

Behavioural Intelligence describes patterns the model believes may appear in the words provided. It is not a personality profile and should not be treated as a fact about an employee.

What it shows #

The generated step may summarize observed behaviour, offer an interpretation, point to supporting evidence, give an alternative interpretation, and provide a qualitative confidence label. The interface can also surface selected behavioural interpretations in its overview panel. It uses the conversation transcript rather than independently collected behavioural data.

The model is asked to avoid definitive labels and to ground observations in text. Still, the model may miss context, mistake a speech pattern for intent, or repeat assumptions in the source transcript.

Separate observation from interpretation #

An observation should be something you can point to in the record, such as a phrase or a change in topic. An interpretation is one possible explanation for that observation. The latter is less certain and should be checked with the employee, not written down as a confirmed cause.

Signal strength labels are descriptive categories in the generated result. They do not supply an independently calibrated confidence percentage or establish that a behavioural pattern is recurring across time.

Review before acting #

Open the source transcript and verify the quote and speaker. Consider other reasonable readings, especially where the transcript is short or language is mixed. If the evidence does not support a conclusion, set it aside rather than forcing a pattern.

This analysis cannot diagnose, assess personality, or establish misconduct. Human judgement and your organization's fair-process requirements remain essential.

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.