How to Report Human Risk to the Board: A One-Page Template

Publication Date

November 16, 2026

Category

Human Risk Management

Reading Time

9 Min

Author Name

Shubh Arya

How to Report Human Risk to the Board: A One-Page Template

To report human risk to a board, use one page: a one-sentence headline, three trend numbers, where the risk concentrates, what changed since last quarter and any decision needed. Express behaviour as a scenario the board already worries about, such as a payment-change request, with a fraction attached.

Boards are asked to oversee cyber risk in money and likelihood. Human risk is the hardest part to put that way, so it usually arrives as a training completion rate. This guide gives you a template to replace it, with examples for banks, financial firms and healthcare providers.

What boards are being asked to oversee

NACD's 2026 director handbook says boards should receive standardised, business-aligned cyber-risk reports, at least quarterly, with updates after material incidents. Its suggested indicators include quantified risk exposure, incident trends, time to detect and contain, patching, third-party exposure and one people-related item: the percentage of employees completing security training.

The audience is also stretched. In WTW's 2026 Global D&O survey, 65 percent of respondents agreed that their fellow directors have the skills to oversee cybersecurity and data privacy, and 35 percent did not. Only 5 percent ranked it as the single most important topic for board time. WTW's article does not publish the sample size, so read the figures as indicative.

The concern itself is real. The World Economic Forum's Global Cybersecurity Outlook 2026 says CEOs now rank fraud and phishing ahead of ransomware as their top concerns. A board that worries about fraud is a board that wants to hear about people.

Which measures to bring

The Human OS white paper lists seven things worth tracking: reporting behaviour, response speed, repeat patterns, role and exposure, scenario difficulty, channel resilience and improvement trend. It also says human risk cannot be reduced to one universal score. For a board, that is helpful. You do not need seven numbers on the page. You need three, chosen from the seven, and a plain account of the rest.

If the board asksLead withUse as context
Are we getting better?Improvement trendScenario difficulty, so a harder test does not look like failure
Would people spot a real attack?Reporting behaviourChannel resilience, because attacks do not stay in email
How fast would we know?Response speedRepeat patterns, to show whether the same mistake recurs
Where should we spend?Role and exposureWhich teams hold money, patient data or privileged access

The one-page human risk report

Five boxes. Each answers one question a director will ask.

BoxQuestion it answersWhat goes in it
1. HeadlineAre we better or worse than last quarter?One sentence, in plain words, with a direction. 'Our finance team is verifying unusual payment requests more often, but our regional offices are not.'
2. TrendHow do we know?Three numbers with last quarter's value: for example report rate, time to report and the share verifying a payment-change request. Define each in a footnote.
3. ConcentrationWhere is it worst?A short table of the weakest two or three teams, channels or regions. Name teams, not individuals.
4. What changedWhy did it move?One or two sentences: a new test, a new threat, a new control. Be honest when the cause is unknown.
5. Decision neededWhat do you want from us?A specific ask: budget, a policy change, an executive sponsor. If there is none, say 'none this quarter'.

Resist the urge to add a sixth box. A board page that needs a legend has already lost the room.

Two worked illustrations

The numbers below are invented to show the shape. They are not benchmarks and they do not come from any organisation.

A bank. The scenario is a late-afternoon request, apparently from a senior executive, to process a payment before close of business. It is realistic: the FBI's Internet Crime Complaint Center reported business email compromise losses of just over 3.04 billion dollars for 2025, according to figures cited in our own post on BEC.

BoxIllustrative content (bank)
HeadlineMore of our payments team now verify unusual requests before acting, but two regional offices have not moved.
TrendReport rate on simulated payment-change requests: 58% (last quarter 41%). Median time to report: 22 minutes (last quarter 47). Share that verified before acting: 7 in 10 (last quarter 5 in 10).
ConcentrationTwo regional offices below 40% report rate. Phone-based requests are weaker than email in every region.
What changedAdded phone and chat scenarios this quarter, which showed a gap email-only tests had hidden.
Decision neededApprove a second approver on new payees and changed bank details across all regions.

A hospital group. The scenario is a call to a ward clerk from someone claiming to be the IT help desk, asking for a password reset code. The population is different, with shift work, shared workstations and constant interruption, which is the environment layer in the Human OS.

BoxIllustrative content (hospital group)
HeadlineReporting is strong on day shifts and weak on nights, where most calls from 'IT' go unchallenged.
TrendReport rate on simulated help desk calls: 44% (last quarter 38%). Median time to report: 35 minutes (last quarter 52). Share that gave a code: 2 in 10 (last quarter 3 in 10).
ConcentrationNight shift in three units. Shared-workstation areas show the slowest reporting.
What changedAdded voice scenarios and a one-step report button on shared workstations.
Decision neededApprove a help desk call-back rule for any credential request.

Both examples share a feature. They use a scenario the board already understands and a fraction it can picture. An industry report on a single campaign on 1 June 2026 that reached more than 67,000 users at over 42,000 organisations in under three hours, with one email impersonating a CEO to divert payroll and neither email carrying a link or attachment, shows why. A director can picture it and ask the right question: how many of ours would have checked?

Questions directors ask, and the shape of a good answer

QuestionA good answer
Are we getting better?Yes or no first, then two numbers with last quarter's values.
Compared with whom?Compared with ourselves over time. External benchmarks are thin, and we say so.
Where is the exposure?Teams, channels and regions, named, not individuals.
What would a real attack look like here?One scenario, with a fraction: 'In a payment-change test, 7 in 10 verified.'
What did it cost, and what did we get?The cost of the programme beside the movement in the headline numbers. No inflated claims.
What do you need from us?A specific decision, or 'none this quarter'.
How do we know the test is realistic?Describe the scenarios, the channels and how they were chosen. Admit what is not tested.

Say this, not that

Instead ofSay
Click rate of 3.1 percentMost people did not act on a realistic payment request, and 58 percent reported it
Our people are the weakest linkOur people are where an attack meets a decision, so we measure how they decide
Completion is at 98 percentEveryone has been trained. Here is what they do in practice
Employee fell for a phishing testA team did not yet verify the request
Risk score of 72Risk improved from last quarter. Here are the two reasons

If you have no data yet

Run one realistic test per channel you rely on (email, text, phone, chat) over a few weeks. That is your baseline.

Choose three numbers and define them in writing before you run the test.

Present the baseline as a starting point, not a verdict. Boards respect a clear baseline and a plan more than a polished score.

Review each quarter and show the movement. If you want a ready-made view across individuals, teams and regions, a human risk dashboard such as SimuPhish's HDR score is built for that.

See SimuPhish in action

FAQs