Safeguarding and support approach
How Cura identifies signs of pressure and connects users with appropriate support.
Last updated 9 September 2026
Purpose. This overview explains Cura's safeguarding design for adult workplace users: what the platform can recognise, when Orion signposts support, what clients need to provide and the boundaries of the service.
1. Approach at a glance
Principle | What this means |
|---|---|
Proportionate | Support becomes more prominent as Human OS scores move below defined thresholds. |
Available at any time | Urgent and confidential support routes remain accessible whether or not a score trigger has been reached. |
Non-clinical | Human OS scores guide practical development. They are not diagnostic measures or validated clinical cut-offs. |
Private by design | Personal responses and insights are not shared with an employer at an identifiable level. |
Clear boundaries | Cura does not provide emergency response, clinical care, crisis monitoring, triage or case management. |
2. How support is triggered
Cura only uses answers selected from predefined options; users do not submit free-text responses. Scores run from 0 to 100 and are updated from those selections. Orion applies the following product rules:
Support level | Response |
|---|---|
Always available | Urgent, confidential and workplace routes |
Some pressure noticed | Gentle prompt plus workplace and urgent-support routes |
Higher levels of pressure indicated | Stronger prompt plus NHS, GP, workplace and urgent-support routes |
Application rule. If both score conditions are met, Orion shows the higher-level message rather than presenting both. A low score prompts support; it does not identify the cause, establish a diagnosis or confirm that someone is in crisis.
3. Privacy, reporting and service boundaries
Orion does not read or interpret free text, because no free-text response route is available in the current experience.
Receiving or opening a support message does not automatically notify the user's employer.
Clients receive aggregated engagement reporting; individual responses and Human OS insights are not exposed at an identifiable level.
Cura signposts appropriate routes but does not monitor whether a user contacts them or manage the support they receive.