Choosing an employee wellbeing app: 7 questions your vendor should answer

Wellbeing app demos almost always look good: tidy interface, colorful charts, a promise of "happier employees". What decides whether the program works is not the look but the design decisions behind it: who can see what, how data is treated, and what happens when there is a serious case. These seven questions help HR judge that in a single demo session.

1. Who can see individual answers?

Ask the vendor to show the screen a direct manager sees and the screen HR sees. If either one shows names together with scores or conversation content, employees will feel watched and their answers will adapt. Patterns per division with a minimum respondent count are far safer.

2. Is the anonymous feature really anonymous?

Ask what is actually stored. Can an administrator trace the sender? Can HR reply without knowing who it is? An anonymity promise that cannot be proven technically is more dangerous than no anonymous feature at all.

3. What happens if an employee writes something dangerous?

An app that offers a place to talk must have an answer for this: how crisis keywords are recognized, what message the employee sees, who is notified, and how every access to the case is logged. "We haven't thought about it" is a signal to stop.

4. Does the app diagnose?

A workplace app is not a medical or psychological service. Be wary of claims like "detects depression" or "measures mental health". Operational indicators such as workload and mood are fine, as long as they are described as indicators and not diagnoses.

5. How heavy is it for employees to use?

Adoption is the biggest risk. Ask how long a check-in takes, whether training is needed, and whether participation can be measured. A program employees fill in reluctantly produces data that looks complete but is not honest.

6. What happens once the data is collected?

A dashboard that only shows numbers leaves HR to work out the next step alone. Check whether there is a follow-up flow: a conversation with the manager, a team agreement, or recorded actions with owners and deadlines.

7. How is data deleted if we stop?

Ask for a written answer on storage location, retention period, and the deletion procedure after the contract ends. For employee data in Indonesia, also discuss your company's obligations under the Personal Data Protection Law (UU PDP) with your legal team.

How to judge the answers

A good vendor answers specifically and is willing to say "that doesn't exist yet" about features that really don't, including integrations with the systems you use. Answers that are always "yes, we can" deserve suspicion. Start with a small pilot of limited duration, decide up front which metrics you will judge, and decide whether to continue based on the pilot data.

RekanSapa is built on these principles: aggregates per division, a separate crisis path, no diagnosing. We do not claim what does not exist; integrations such as Jira, Trello, and SSO are still on the roadmap. We explain the details openly in the demo.