> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/heart/risk.md).
# Risk
What the Risk dimension measures, how Validator compliance data feeds the score, and when it activates.
Risk is the HEART[^1] dimension that measures how well data compliance safeguards are followed. It shows where Validator[^2] checks are bypassed or failed, giving a compliance signal for the application.
## What Risk measures
Risk answers three questions about an application:
* Are data compliance safeguards respected or bypassed?
* Where does non-compliance create exposure?
* Which tasks or audiences show the most deviation?
Task Success and Efficiency measure task performance. Risk measures whether the right data is entered and the right process is followed, whether or not the task itself completes.
The Risk dimension detail in the HEART scorecard.
{% hint style="warning" %}
Risk needs Validators configured and actively monitoring. Without at least one active Validator, Risk does not activate and does not contribute to HEART.
{% endhint %}
## How the score is calculated
The Risk score equals the data compliance metric, on a scale of 0 to 100.
When Risk is inactive, for example because no Validators are configured or there is not enough data yet, HEART handles it as described in [How the score is calculated](/intelligence/heart.md#how-the-score-is-calculated).
## What feeds the score
### Data compliance
The share of Validator-monitored interactions that end in a compliant state when the session closes.
Compliance is decided when the session ends, based on the final outcome. Five scenarios contribute:
* The user entered correct information on the first attempt: compliant.
* An error appeared at field level and the user corrected it within the session: compliant.
* An error appeared at form submission and the user corrected it within the session: compliant.
* An error appeared and the user did not correct it (abandoned, navigated away, or the session timed out): non-compliant.
* A silent Validator observed the interaction without showing anything to the user: compliant or non-compliant based on the observed outcome.
Silent observations are marked separately in the data but count toward the score the same way as visible Validator interactions.
### Activation
Risk activates once the application has enough Validator-monitored interactions over a sufficient period. At least one active Validator must be configured.
## Relevant articles
{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}
{% content-ref url="/pages/BJ6uX7MdEouMq5jZDQtF" %}
[Creating validators](/assistance/in-app-guidance/validators.md)
{% endcontent-ref %}
{% content-ref url="/pages/qR8g756lNxBfOkNQzq3W" %}
[Regex patterns for input validation](/assistance/in-app-guidance/validators/regex-patterns-for-input-validation.md)
{% endcontent-ref %}
## FAQ
What happens if no Validators are configured?
Risk does not activate, and HEART is calculated from the remaining active dimensions. [Create a Validator](/assistance/in-app-guidance/validators.md) to start scoring Risk.
Do silent Validators count?
Yes. Silent observations count toward the Risk score the same way as visible Validator interactions. They are marked separately in the data for analysis.
What decides whether an interaction is compliant?
The final state when the session closes. If the user corrected the error before the session ended, the interaction is compliant. If the session ended with the error unresolved, it is non-compliant.
What is the difference between Risk and Efficiency?
Efficiency measures the speed and consistency of task completions. Risk measures whether data compliance safeguards are followed, regardless of completion speed.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.
[^2]: A Validator is a Userlane content type that checks field-level or form-level data entry. Validators run visibly (shown to the user) or silently (observing only).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.userlane.com/intelligence/heart/risk.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
