Yes — human risk scores can be shared with employees individually, and when they are shared the right way they improve behaviour rather than damage morale. The design choices that matter are who sees what, in what framing, and what the employee can do about the number they receive. Cyber Aware's human risk reporting includes per-learner scores that admins control: shared with the individual, visible to managers, or kept admin-only. This guide covers what works, what backfires and how to set it up so the score is a coaching tool instead of a surveillance artefact.
TL;DR
- Yes, per-learner human risk scores can be shared with each employee individually — most platforms support it as a toggle.
- Sharing works when the score is framed as a habit indicator and paired with a clear next action, not as a ranking.
- Manager visibility works when scoped to team aggregates; individual scores visible to managers as league tables backfire.
- The score's purpose is behaviour change, not discipline — pair every score with a training or practice action.
- Privacy framing matters: scores derive from training and simulation behaviour, not from monitoring personal activity.
Why this matters
Human risk scores are the new core output of awareness platforms: a single number per learner that rolls up their training completion, phishing simulation behaviour and reporting habits. Whether to share that number with the employee is one of the most consequential programme-design decisions — get it wrong and the programme reads as surveillance; get it right and the score becomes the hook that makes staff care about their own security habits.
Can human risk scores be shared with employees individually?
Direct answer: yes, and in most platforms the choice is a setting rather than a custom project. What the setting controls:
- Individual visibility: the employee sees their own score and the components behind it — completions, simulation clicks, report rate — but not colleagues'.
- Manager visibility: team leads see aggregate team scores and, in some configurations, individual team-member scores.
- Admin-only: scores stay with the security team and are used purely to drive targeted training.
All three configurations run on the same underlying data; the difference is distribution.
What a human risk score actually measures
A score is a composite, and the components matter more than the headline number:
| Component | What it reflects | Weighting signal |
|---|---|---|
| Training completion | Whether required modules are done on schedule | Direct, most controllable by the employee |
| Simulation click rate | Whether the person clicks simulated lures | Behavioural, improves with practice |
| Phishing report rate | Whether suspicious email gets reported | Behavioural, improves fastest with feedback |
| Recency | Whether good behaviour is current or historical | Time decay, prevents coasting |
The honest framing for employees: the score measures habits, not intelligence or trustworthiness. Someone can click one sophisticated lure and still be a low-risk employee overall — the score is a trend line, not a verdict.
What works when you share scores
- Share the trend, not a single number. “Your report rate improved from 40% to 75% this quarter” beats “your score is 68” — the trend gives the employee credit for movement and a direction to keep moving in.
- Pair every score with an action. A score without a next step reads as judgement; a score plus “one 5-minute module this week” reads as coaching.
- Let employees see the components. The composite number is opaque; the underlying behaviours are actionable. Show clicks, reports and completions, not just the headline.
- Keep the comparison internal. Share each person against their own past, or the organisation average — never a ranked leaderboard of named individuals.
What backfires
- Public leaderboards. Naming and ranking individuals turns the programme into a competition with losers, and the people at the bottom stop engaging entirely.
- Scores in performance reviews. Linking the score to pay or appraisal corrupts the data: people stop reporting phishing because a report reads as a failure. See the separate question on phishing results and appraisal software.
- Manager league tables. A manager who can see individual scores for their whole team at once will inevitably use them socially, even with good intent.
- Opaque weightings. If employees cannot see what moves the score, they invent theories — usually wrong ones — and the score loses its coaching value.
Privacy and consent framing
The score derives from workplace training and simulation activity — behaviour that happens on employer-provided accounts in a programme the employee was enrolled in. That is a narrower data set than general activity monitoring, and it should be framed that way explicitly:
- Say what is collected: training completions and simulation outcomes on the work account.
- Say what is not: browsing, personal email, message content, screen activity.
- Say who sees it: the individual, the security admin, and managers only in aggregate.
- Put it in the programme's privacy note where staff can find it, not buried in an EULA.
This transparency is also what makes the score stick: employees who know the data's boundaries treat the score as useful rather than as surveillance.
How Cyber Aware handles score sharing
Cyber Aware's human risk reporting produces per-learner scores from training completions and simulation behaviour, with admin-controlled visibility: individual scores can go to each employee, stay admin-only, or be shown to managers at team level. Scores roll up to team and organisation views for the risk picture leadership sees.
Related questions
Should an employee see their own score? Yes, if it comes with the component breakdown and a next action. The self-serve view is the configuration most likely to change behaviour, because it lets the employee act without waiting for a manager conversation.
Can scores be used in performance management? No — not if you want accurate data. The moment a score affects appraisal, reporting behaviour collapses and the programme measures compliance theatre instead of risk.
What is a good score to aim for? Scores are comparative, not absolute. The useful target is improvement: report rate up, click rate down, completions on time — organisation-wide trends rather than a universal number.
How often are scores updated? Typically after each training wave or simulation campaign, so the score reflects current behaviour rather than a year-old snapshot.
One last thing
The single most effective addition to a shared score is the report-rate component: unlike clicks (which feel like failure) or completions (which feel like homework), reporting a suspicious email is a behaviour employees can win at every day. Programmes that show report rate prominently see the fastest behaviour change in the first quarter.
FAQ
Can human risk scores be shared with employees individually? Yes. Platforms including Cyber Aware support per-learner score visibility as an admin setting — the employee sees their own score and its components, not colleagues'.
Will sharing scores damage morale? Not when framed as habits with a next action. Morale damage comes from leaderboards, appraisal links and opaque numbers — all avoidable design choices.
What data feeds a human risk score? Training completions, simulation clicks and report behaviour on the work account. Not personal browsing, message content or general activity monitoring.
Should managers see individual scores? Team aggregates, yes. Individual team-member scores visible to managers tend to become social information quickly; most programmes keep that view admin-only.
Is a human risk score a compliance requirement? No — it is a programme-management tool. It becomes useful evidence for audits and insurers, but no standard mandates it.