Skip to content
VooHr Support Contact Sign in

Understanding the analysis

Root Cause

Root Cause offers possible explanations for what was discussed in one conversation. A plausible explanation in the output is a hypothesis to check, not a verified cause.

What it shows #

The generated section may name a primary trigger, secondary contributors, evidence, missing information, a reasoning summary, and possible next actions. Its source is the transcript sent for analysis, not an investigation across all records or a direct interview conducted by the system.

The model may connect statements that are not causally related or overstate what a short exchange can establish. A well-written narrative can still be speculative, and a missing-information field does not mean the system has found every gap.

Why causes are uncertain #

A transcript records only selected words from a particular setting. It may leave out workload, workplace events, health, personal preferences, organizational context, or information the employee did not choose to share. These factors can change the meaning of what was said.

A confidence label or quoted passage can help you find the basis for a suggestion, but neither establishes causation. Root-cause statements are probabilistic model output and should not be copied into a formal record as confirmed facts without verification.

Check the hypothesis #

Compare the explanation with the source text and what you know from legitimate, relevant records. Ask the employee what else may be contributing and give them room to disagree. Keep more than one explanation open until there is reliable evidence.

Use the result to prepare a thoughtful question, not to decide an employment outcome. If the evidence is sparse or conflicting, say so and gather appropriate context through your normal HR process.

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.