Technically, yes — most phishing simulation platforms can export per-person results and push them into HR systems through an API or integration. Practically, you almost certainly should not. Security bodies across the industry treat phishing failures as learning signals, not performance metrics, and wiring them into appraisals tends to destroy the reporting culture that makes the programme work.
TL;DR
- Export and integration make it possible; policy makes it a bad idea in most workplaces.
- Verizon's 2025 Data Breach Investigations Report found a human element in roughly 60% of breaches (Verizon 2025 DBIR) — the goal is fixing behaviour, not punishing it.
- Simulations run on voluntary engagement: clickers who fear consequences stop reporting, and reporting is the reflex you actually need.
- Aggregate metrics — team click rates, report rates, trend lines — belong in appraisals for managers; individual clicks do not.
- If you need a per-person signal, use a Human Risk Score that everyone can see, not a hidden feed into HR software.
Can phishing results feed into performance appraisal software?
Yes, mechanically. Modern platforms expose per-learner data — clicks, reports, course completions, risk scores — through dashboards, exportable PDFs and APIs. Many also connect to workflow tools through automation platforms: Cyber Aware, for example, connects to thousands of apps via Zapier, and its phishing simulations produce per-person results that could be routed anywhere an integration can reach.
Whether that data should land in a performance system is a different question, and the answer for most organisations is no.
Why feeding clicks into appraisals backfires
Three failure modes show up in every programme that tries it:
- Reporting collapses. The whole value of a simulation programme is that staff report suspicious emails. The moment people believe a click goes into their file, some stop reporting anything — including real attacks. A hidden click rate and a visible report rate measure different things, and only one protects you.
- The metric rewards the wrong behaviour. Someone who clicks nothing may simply never receive a simulation, while the employee who clicks one in January and reports every one after is the programme's success story. Raw click counts cannot tell those two apart; trend lines can.
- Trust in the programme dies. Staff who think the phish is a trap in both senses disengage from the training itself. The psychological contract — 'this is practice, not punishment' — is the asset; appraisals break it.
There is a genuine dispute-resolution question too: simulated results are noisy, and a false positive from a shared mailbox or a forwarded email can land on the wrong appraisal line with no fair way to appeal.
What does belong in an appraisal
Aggregate and directional signals, yes. Individual click events, no.
| Signal | Feeds appraisal? | Why |
|---|---|---|
| Individual phishing clicks | No | Punishing clicks kills reporting |
| Individual report behaviour | No — coach instead | Reports should be celebrated, not graded |
| Team click-rate trend | Yes, for managers | Shows whether the programme works |
| Training completion rates | Yes | A management responsibility |
| Repeat-failure patterns | Yes, as a support flag | Signals someone needs extra help |
For managers, a team trend line in a quarterly review is fair game: it shows whether the cadence is being maintained and where support is needed. That is how human risk reporting is designed to be used — a score per learner that starts at zero each month and climbs only on real behaviour, visible to the learner and the admin, designed for follow-up rather than punishment.
If you still need a per-person signal
Some roles — finance, executives, IT — genuinely warrant closer monitoring, and regulators sometimes expect evidence of individual completion. The workable middle ground:
- Make the score visible to the learner. Transparency converts a surveillance metric into a self-improvement tool.
- Use score trends, not single events. One click is noise; three months of rising risk is a conversation.
- Route it to coaching, not compensation. Assign the remediation course automatically, which platforms do on click — the failure becomes a lesson the same day.
- Document the policy. Whatever you decide, write it down: who sees what, what it is used for, and what it is never used for.
FAQ
Can phishing simulation results be exported to HR software? Yes — most platforms support per-learner exports and API or automation-platform connections that can route results into HR systems.
Should phishing clicks appear in performance appraisals? No. Individual click data in appraisals suppresses reporting, which is the behaviour that actually reduces breach risk. Use aggregate trends for managers instead.
What can we legitimately use from phishing results in reviews? Team-level click and report-rate trends, completion rates and repeat-failure patterns — signals for coaching and resourcing, not individual discipline.
Is it legal to use phishing results in appraisals? Mechanically yes in most jurisdictions, but workplace monitoring rules and fairness expectations apply — document the policy, keep the data proportionate and expect disputes over false positives.
What is the alternative for high-risk roles? A transparent per-learner risk score with automatic remediation on failure — the failure triggers training the same day, and the trend line, not a single click, drives the conversation.
One last thing
If your programme's report rate has been flat or falling for two quarters, check whether staff believe clicks have consequences. The belief alone is enough to suppress the reporting reflex that catches real attacks.