Acting on it
Surveys and reports
VooHr supports HR-created survey templates and recorded employee responses. Survey-derived engagement data can feed the directory's rule-based wellness calculation; it is not an anonymous research service.
Survey templates and responses #
Authorized signed-in users can create, update, publish, archive, and list survey templates, then record structured answers for an employee. Question types include five- or ten-point Likert scales, numeric values, and text. Templates are organization-scoped and responses are attached to employee records.
The response workflow stores answers and computes an engagement score from eligible numeric questions. Updating or deleting responses can refresh the employee's latest engagement value. Check the survey screen's actual permissions before collecting sensitive answers.
How survey data is used #
The most recent survey response's normalized engagement score is copied to the employee signal used by the existing wellness calculation. The scoring function gives only a small configured adjustment for high or low engagement values; other missing signals are handled separately.
A survey score is not a clinical measure and does not establish an employee's overall engagement. Response selection, question wording, participation, and recency all affect how useful it is.
Reports and limits #
VooHr includes employee summaries, meeting and conversation views, alerts, and analysis outputs. Do not assume a report is an audited export or a complete record of all organization activity. Confirm what screen and filters are active before relying on counts or averages.
There is no claim here about anonymity or survey response confidentiality. [CONFIRM: survey privacy and reporting policy for customer deployments] Commercial and support details are not inferred from product code: [CONFIRM: current pricing] [CONFIRM: refund policy] [CONFIRM: support response times]
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.