GDPR Training for Employees: What to Cover and How to Build It
8 min read Czytaj po polsku
Most GDPR courses fail in the same way: forty slides of article numbers and fine amounts, a quiz that asks "What does GDPR stand for?", and employees who still email a customer list to the wrong address the following week. A useful course is shorter and much more specific. This guide covers what to include, what to leave out, and how to build it in an afternoon from a template.
This article is about course design, not legal advice. Have your data protection officer or legal adviser review the content against your own procedures.
Is the training required?
The GDPR doesn't contain a sentence saying "train all employees". It does three things that make training the normal answer:
- Article 32(4) requires controllers and processors to take steps so that anyone acting under their authority with access to personal data processes it only on instructions.
- Article 5(2) makes the controller responsible for compliance and for being able to demonstrate it.
- Article 39(1)(b) lists awareness-raising and training of staff among the data protection officer's tasks.
A dated completion record in the LMS, tied to a course version, is simple evidence that staff were instructed. Many organizations train at onboarding and repeat yearly.
What a good course covers
Organize the course around what employees do, not around the regulation's chapters. These six modules cover what most staff need:
| Module | The learner can… | Key content |
|---|---|---|
| 1. What counts as personal data | Recognize personal data in their own work | Direct and indirect identifiers, special categories (health, beliefs, biometrics…), pseudonymised data is still personal data |
| 2. The principles in daily work | Apply minimization, purpose and storage limits to everyday tasks | Copy only what's needed, use data only for the purpose it was collected for, delete on schedule |
| 3. Security habits | Avoid the common causes of incidents | Wrong recipients, BCC, approved tools, locked screens, printing, phone verification |
| 4. Data breaches | Recognize a breach and report it at once | What counts as a breach, who to tell internally, why hours matter |
| 5. Requests from people about their data | Recognize a request and pass it on | Access, correction, deletion and objection, which people rarely label as "GDPR requests" |
| 6. Your rules | Find the organization's contacts and procedures | Data protection officer or privacy team, reporting channel, retention rules |
Two facts in module 4 are worth getting exactly right. A personal data breach is any breach of security that leads to personal data being destroyed, lost, altered, disclosed or accessed without authorization, accidentally or not (Article 4(12)). And where notification is required, the controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware (Article 33). Employees don't decide whether to notify; their job is to report internally straight away, because every hour they wait shortens that window.
For module 5: the organization must respond to requests without undue delay and within one month, extendable by two further months where necessary (Article 12(3)). Again, staff don't handle the request; they recognize it and forward it the same day.
What to leave out
- An article-by-article tour. Employees don't need Article 22 to do their job.
- Fine amounts as a scare tactic. One sentence is enough (up to €20 million or 4% of worldwide annual turnover for the most serious infringements). Fear doesn't change how people handle a spreadsheet.
- Legal bases in depth. Most staff need to know that consent isn't the only basis and who decides. Marketing and HR need more, in their own modules.
- History and definitions for their own sake.
Scenarios that work
Scenarios are what make the course stick. Use situations from your own organization; these are a starting point:
| Situation | The right action |
|---|---|
| Autocomplete sends a spreadsheet of salaries to the wrong "Anna", an external supplier | Report it internally right away, even if she says she deleted it |
| A caller says they're a customer and asks you to confirm their address | Verify identity the way your procedure says; never read data out to confirm it |
| A colleague asks you to send the customer list to a private email to work from home | Refuse; use the approved tools and remote access |
| You lose your phone with work email on it | Report it at once so IT can lock or wipe it; it may be a breach |
| A customer asks in chat "what data do you have about me?" | It's an access request, even without the word GDPR; forward it to the right team the same day |
| A shared folder holds CVs from candidates three years ago | Check the retention rule; don't keep data "just in case" |
| You email 40 external partners with every address in the To field | Use BCC; showing all addresses discloses personal data |
| Marketing wants to send a newsletter to addresses collected for invoices | Purpose limitation: check with the privacy team first |
Turn two or three of them into branching scenarios, where the learner makes the decision and sees the consequence, and use the rest as quiz questions.
The quiz
Eight to ten scenario questions, a pass mark of 80%, and feedback that explains the rule behind each answer. For example:
You email a spreadsheet with your team's salaries to the wrong Anna, a supplier's employee. She replies that she has deleted it. What do you do?
A. Nothing more. She deleted it. B. Report it to the privacy team right away, even though it was deleted. (correct) C. Mention it to your manager at the next team meeting. D. Ask Anna to confirm the deletion in writing and close the matter yourself.
Feedback: "This is a personal data breach, deleted or not. Whether it must be notified is decided by the people responsible, and the organization may have only 72 hours from becoming aware. The sooner you report it, the more of that time the right people have."
Avoid questions that test vocabulary, such as "What does DPO stand for?". How to write good quiz questions covers distractors and feedback in more depth.
Build it in an afternoon
With a template and your procedures at hand, this is a realistic plan for one author:
| Time | Task |
|---|---|
| 30 min | Collect your facts: privacy team contact, breach reporting channel, how data requests are forwarded, approved tools, retention rules |
| 60 min | Start from a template in the template library, or from last year's course, and replace generic text with your procedures and contacts |
| 60 min | Write three to four scenarios from your own organization and eight to ten quiz questions |
| 30 min | Review with your data protection officer or privacy lead |
| 30 min | Export, upload to a test course in the LMS, complete and fail it once |
If you'd rather start from your own policy document than from a template, an AI course generator can draft the course from the PDF, with the outline shown for approval before it writes slides. The review step matters more for a legal topic, not less: check every deadline and contact against the source. How to create a SCORM course from a PDF covers that review.
Records and versions
When someone asks "can you show that staff were trained?", they usually want four things: who completed, when, which version of the course, and with what result. The LMS stores the first, second and fourth if the course reports completion and score. The version is up to you: name it in the course title or on the first slide ("version 2026-03"), and keep the previous version's activity and reports when you publish a new one.
If reports need completion and pass/fail as separate facts, so that "read the whole course but failed the quiz" is visible, export SCORM 2004 4th edition; SCORM 1.2 vs 2004 explains why. And remember that the training records are personal data too: What an LMS records from a SCORM course lists what's stored.
Checklist before release
- Every contact, channel and deadline matches your current procedures
- Scenarios come from your organization, not only from the template
- The quiz tests decisions; every answer has feedback
- The privacy lead has signed off
- The version is named in the course
- Tested in the LMS: complete, fail, resume, report
Building it in Scormbee
The Scormbee template library is growing. When a template fits your topic, it opens in the editor like any course, where you replace the generic parts with your own procedures, adjust the scenarios and quiz, and export SCORM 1.2 or 2004. The project keeps a version history, so you can see what the course said in any year an auditor asks about. Like any template, it's a starting point, not a substitute for your legal requirements.
Frequently asked questions
Is GDPR training mandatory for employees?
The GDPR doesn't say 'train every employee' in those words, but it requires controllers to ensure staff process personal data only on instructions (Article 32(4)) and to be able to demonstrate compliance (Article 5(2)), and it lists staff training among the data protection officer's tasks (Article 39). Training records are one of the most common ways to show this.
How often should GDPR training be repeated?
Common practice is training at onboarding and a refresher every year, plus an update when procedures change. Your data protection officer or legal adviser should set the frequency for your organization.
How long should a GDPR course for all staff be?
Short enough to finish in one sitting: around 20 to 30 minutes for the general course works well. Put role-specific content for HR, marketing, IT or customer service into separate short modules.
Can we use a generic GDPR course?
As a starting point, yes. It becomes useful when you add your own procedures: who to report a breach to, how to recognize and forward a data request, which tools are approved, and how long you keep which documents.
Does the training itself process personal data?
Yes. The LMS stores each learner's completion, score and answers against their identity. Set a retention period for those records and avoid open questions that invite learners to type personal details.