Annual awareness training plan for security and privacy
Annual awareness training plan template
An annual awareness training plan for a Swiss SME is a one-page calendar: when security and privacy training happen, who attends, what proof you keep, and how new hires are covered between yearly sessions. It is not a forty-slide strategy deck. If you only need a date in the diary, start here. If you are comparing facilitators, use choosing a security awareness provider alongside this template. Cost depends on group size and format, not on this calendar page.
The plan fits firms with about 20 to 250 staff and no CISO. Someone in HR, finance, or the owner’s office usually owns the calendar; IT checks that examples match your mail system and MFA.
- Q1
Name the owner, review last incidents, book a live security date before summer holidays fill the calendar.
- Q2
Run live security awareness, or a combined security and privacy day if both topics are due.
- Q3
Onboarding micro-session for hires; optional e-learning refresh for people who missed Q2.
- Q4
Check report metrics and insurer questions; schedule next year or a follow-up conversation.
What belongs on the one-page plan
- Live session date(s), language (German or English), and room or remote link
- Audience: all staff, or core plus finance and reception for payment modules
- Onboarding rule: within two weeks of start for reporting path and password rules
- Where attendance and slide titles are stored for audits
- Follow-up call date a few weeks after the live session
Combined day format
The privacy service page describes a combined day with security as the usual format for many SMEs: one trip, one calendar block, separate modules for phishing and for FADP daily rules. Book through the overview at /security when both topics are due in the same year. If payroll is your only personal-data process and you trained privacy last quarter, security alone may be enough; Security Awareness Training describes prep, live hours, and follow-up without forcing a combined booking.
Security block topics
Build the security module from your own incident list, not a generic slide pack. Phishing and smishing, payment and CEO-style requests, how to report, passwords and MFA. According to the BACS half-year report 2025/2, fraud was 52 percent of voluntary reports in that period (external statistic, not our survey). Payment stories belong in every annual slot even if last year was “only” malicious links.
Keep finance and reception in the room for the payment section, even if HR leaves early for privacy detail.
Privacy block topics
Wrong-recipient mail, retention basics, when to escalate a possible breach to leadership, and what “report as soon as possible” means under the FADP (not a 72-hour EU rule). Deliver training framed as covering the FADP and the GDPR; do not promise wording that sounds like certification.
Proof to file
Store date, facilitator name, topic bullets, attendee names or departments, and language used. If you map to ISO/IEC 27001:2022 control A 6.3, keep the mapping letter separate from attendance. The session does not certify the company.
Keep it simple: a calendar invite or a sign-in sheet, slide titles or a one-page summary, and the language of the session. Save a PDF or scan in one folder per year: invitation, list, summary, follow-up notes, copied insurer replies.
Keep internal breach notes in a restricted folder, not in the training file.
Onboarding between annual sessions
New hires within two weeks: reporting path, password rules, payment verification if they touch invoices. Point them to the full session date if it is later in the year. E-learning completions, if you use them, go in the same yearly folder as live sign-in sheets.
Who should not over-plan
Five staff with no client data may only need one live hour per year. Enterprises with an LMS and a dedicated owner already have a different programme; this template is not a copy-paste for them.
Who this template fits
- 20 to 250 people, no awareness platform
- Insurer or customer asked for proof of training
- You want one owner and one folder per year
Who should skip it
- Groups with a CISO and rolling campaigns
- Firms that only need a single ad-hoc briefing
Working with your IT partner
Most SMEs run training with an external facilitator while IT owns mail rules and MFA. Agree who sends reminders, who collects attendance, and who answers report mail after the session. Without names on paper, annual training becomes an HR calendar entry that IT never sees.
Swiss context reminders
CEO-fraud reports rose from 719 in 2024 to 971 in 2025, according to BACS (external statistic). The cyberattack reporting duty for critical infrastructure does not apply to most SMEs; do not confuse staff with 24-hour BACS rules unless you know you are in scope.
Among firms under 250 staff, Deloitte’s 2026 study reports regular cyber training for 65 percent of small and 82 percent of medium companies (Deloitte Cyber Study 2026, external statistic). The gap is often proof and refresh, not whether anyone ever booked an hour.
Tie training to real processes
Mention the same IBAN verification steps in training that finance uses in ERP. Mention the same report mailbox IT monitors. When processes change after training, send a one-page update rather than waiting a year.
Respect labour and privacy limits
Inform staff before phishing simulations. Do not use awareness metrics for hidden performance scoring. Art. 26 ArGV 3 and Art. 328b OR frame monitoring; this is orientation, not legal advice. Link FDPIC guidance on workplace monitoring when HR asks.
A made-up example: a 45-person trading firm books a combined day in May after a near-miss on a changed IBAN. HR keeps the invite, sign-in sheet, and one-page summary in Training/2026/. IT adds the report address to the onboarding checklist. In November they only run a 30-minute refresh for new hires, not a second full day.
After the session
Within a week, send a one-page reminder with the report address and the IBAN rule. Schedule follow-up questions before people forget. If leadership changes, the folder survives turnover better than chat threads.
Discovery and booking
For both trainings in one day, start from /security and use the discovery conversation to confirm headcount band and language. Remote or on-site in Switzerland is described on the service pages; travel is included for on-site delivery.
Is one live session enough for ISO A 6.3?
No. Auditors expect a running programme with refresh and onboarding, not a single event with no follow-up. Keep dates and topics across years.
Should finance sit in a separate session?
Only if the core session already covers reporting and MFA for everyone. Payment modules should still reach anyone who can release money.
Can we skip privacy if we only process payroll?
If personal data beyond payroll is rare and you trained privacy recently, security alone may suffice. Revisit when you add EU customers or new data-heavy processes.
Book the first quarter date before year-end reporting and holidays crowd the calendar. Sliding it to “sometime” usually means December with no attendee list.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles