- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Checklist · Workforce Security
Security Awareness Program Checklist

Written for
HR, IT and compliance leads
Time needed
1 hour
Items
25 across 5 areas
An annual slide deck satisfies an auditor and changes little. Programs that work are short, regular, relevant to each role and measured by what people do.
Use this checklist to design a program or to test the one you have.
0 of 25 in place (0%)
Foundations
Ownership and scope.
Content
Relevant and short.
Phishing simulation
Practice, not punishment.
Reporting culture
The behaviour that matters most.
Measurement
Know if it works.
How to get the most from this list
- 01
Tick only what you can prove
If you could not show an auditor or your board the evidence today, leave it unticked. A lower honest score is more useful than a high hopeful one.
- 02
Give every gap an owner
For each unticked item, name one person and one date. Gaps without an owner are the ones still open next year.
- 03
Re-run it every quarter
Your environment changes faster than policy. Repeat the list each quarter and after any major change, and compare the scores.
Gaps we see most often
- Click rate tracked, reporting rate ignored
- Executives exempt from training
- Same generic content every year
Take it with you
Download the checklist as a PDF
A designed 6-page version with tick boxes, the common gaps and the questions people ask. Useful for a team review or as audit evidence.
Want a second pair of eyes?
Bring your completed list to a risk review. We will check the items that matter most for your environment, confirm the evidence and turn the gaps into a short, prioritized plan.
Common questions
How often should we train?
Short sessions several times a year work better than one long annual course. Most frameworks expect training at least annually and on joining.
What is a good phishing click rate?
Lower is better, but reporting rate is the more useful measure. A workforce that reports quickly limits the damage when someone does click.
Should people be disciplined for failing simulations?
No. Punishment reduces reporting, which is the behaviour you most need.



