> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HRI and scorecard scores

> How the Human Risk Index and the security behavior scorecard differ, when each one updates, and how to ask for an HRI recalculation.

The platform has two kinds of person score. They use the same signals, but they are calculated at different times and for different purposes.

| | Human Risk Index (HRI) | Security behavior scorecard |
| - | - | - |
| **What it is** | The Living Security risk model. It is the same for every organization. | A score that your organization designs. You choose the signals, their weights, the range, and the bands. |
| **Scale** | 0–1000. 500 is neutral. Higher is better. | The range you set. New scorecards use 0–100 with a starting score of 75. |
| **When it updates** | Once a day, at 02:17 UTC. | Each time someone views it. |
| **Past dates after a change** | Stay the same until a recalculation runs. | Use your current weights for every date, past dates included. |
| **Who changes the weights** | Living Security. | Your admins. |

A scorecard is also called a custom index or a behavior score.

## What 500 means in HRI

HRI starts every person at **500**, the neutral point. A person with no scored evidence has a score of 500. It does not mean average risk, and it does not mean the person did something wrong.

* **Risk signals** move the score down, toward 0. Examples are phishing clicks and overdue training.
* **Protective signals** move the score up, toward 1000. Examples are reported phishing and completed training.

A score at or near 500 does not prove that there is no evidence. Risk and protective signals can balance out near 500. Open the person's signal breakdown to see which signals apply. If there are few or none, confirm that the expected data sources are connected and reporting before you compare that person with others.

A scorecard has its own starting score. It is not 500, unless you set it to 500. A person with no matching signals gets the scorecard's starting score.

## When HRI updates

The platform builds a new HRI snapshot for each organization **once a day, at 02:17 UTC**. Each snapshot uses the activity that the platform has received up to that time.

New activity does not change HRI immediately. This includes a CSV upload. The new activity appears in HRI at the next daily snapshot.

HRI for past dates is recalculated only in these cases:

* Living Security support recalculates HRI for a date range at your request. See the next section.
* Living Security updates the HRI model. The platform then recalculates the last 90 days.
* The platform reprocesses data for your organization, for example after a data source correction or when two person records are merged.

## Recalculate HRI for a date range

Ask for a recalculation when data arrived late, when you corrected an upload, or when you need HRI for past dates to include new activity before the next daily snapshot.

Only admins with the **Manage settings** permission can start a recalculation. Your organization can run only one recalculation at a time. If one is already running, Livvy tells you to wait until it finishes.

Ask Livvy to recalculate HRI:

**1. Ask Livvy**

Open Livvy and ask for a recalculation, for example "Recalculate HRI for October 1 to October 20". Without dates, Livvy uses the last 30 days.

**2. Check the preview**

Livvy shows the date range and does not start anything yet.

**3. Confirm**

Livvy starts the recalculation. It runs in the background and can take several minutes.

If Livvy cannot start the recalculation, contact Living Security support. Give the date range and the reason, for example "CSV upload on October 20 corrected training completions".

> [!NOTE]
>
> Recalculation rebuilds HRI from the activity that the platform has. It does not change the HRI model or its weights.

## When a scorecard updates

The platform calculates a scorecard each time someone views it. It uses the scorecard's current settings and the newest signal data.

* **New activity:** a scorecard shows new activity as soon as the platform has processed it into signals. You do not need to wait for the daily HRI snapshot. Signals that filter on activity details, such as a specific campaign or event name, refresh once a day.
* **Weight changes:** when you change a weight, a signal, or the range, the next view uses the new settings for every date, past dates included. You do not need to ask for a recalculation.
* **Saved snapshots:** a [scorecard snapshot](https://docs.livingsecurity.com/features/outcomes/scorecard/snapshots.md) keeps the scores that were calculated when it was made. A later change to the scorecard does not change a saved snapshot, or the Engage **Trend** tab that is built from snapshots. To keep a record before you change weights, create a snapshot first.

## How training and engagement count toward HRI

Training is one factor group in the HRI **Behavior** component. HRI looks at the last 90 days of these activities:

| Activity | Effect on HRI |
| - | - |
| Completes security training | Raises the score |
| Passes a training assessment | Raises the score |
| Completes voluntary training | Raises the score |
| Engages deeply with training content | Raises the score |
| Fails a training assessment | Lowers the score |
| Has overdue training | Lowers the score |

HRI does not count the format of the training. A completion has the same effect whether the person completed online training or an in-person session, if the source reports it as a training completion.

HRI does not add a fixed amount for each completion. It puts each signal's count into a low, medium, or high level. A new completion changes HRI only when it moves the count to a higher level. When the count is at the high level, more completions add nothing. The training group also has a limit, so training alone cannot raise HRI to 1000. Risky actions have a larger effect than a training completion. For example, clicking a real phishing link or entering credentials in a phishing simulation lowers HRI more than one completion raises it.

### In-person and live events

The platform records these engagement activities as their own signals:

* Attended live training, in person or virtual
* Attended an optional cyber awareness event, such as a talk, fair, or lunch-and-learn
* Completed CyberEscape online training

These signals do **not** change HRI at this time. You can see them in reports, and you can add them to a scorecard with the weight that fits your program. If you want an in-person event to count in HRI, report it as a training completion.

## Common questions

> [accordion] I uploaded a CSV today. Why is HRI the same?
>
> HRI updates once a day, at 02:17 UTC. Your upload appears in HRI at the next daily snapshot. If you need it in HRI for past dates, ask Living Security support to recalculate HRI for those dates. A scorecard shows the upload when the platform has finished processing it.

> [accordion] We changed scorecard weights. Do past scores change?
>
> Yes. A scorecard uses its current weights for every date, so past dates change on the next view. Saved scorecard snapshots, and the Engage Trend tab that is built from them, do not change.

> [accordion] Can we change HRI weights?
>
> No. HRI weights are part of the Living Security model and are the same for every organization. To weight signals for your own program, use a scorecard.

> [accordion] Why do HRI and the scorecard show different results for the same person?
>
> They use different signals, weights, and scales, and they update at different times. HRI can be up to one day behind. A scorecard uses the newest signal data.

## Related

> [card] [Human Risk Index (HRI)](https://docs.livingsecurity.com/reference/hri.md)
>
> Learn what HRI measures and how teams use it.

> [card] [Scorecard snapshots](https://docs.livingsecurity.com/features/outcomes/scorecard/snapshots.md)
>
> Freeze scorecard scores as of a date.

> [card] [Custom scorecards](https://docs.livingsecurity.com/guides/scorecards/custom-scorecards.md)
>
> Choose signals and weights for your own scorecard.

> [card] [Signal Library](https://docs.livingsecurity.com/signals/overview.md)
>
> Learn how the platform turns source activity into defined signals.


## Related topics

- [Human Risk Index (HRI)](https://docs.livingsecurity.com/reference/hri.md)
- [Glossary](https://docs.livingsecurity.com/reference/glossary.md)
- [General FAQs](https://docs.livingsecurity.com/faqs/general.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.