Let’s talk
Wondering how this plays out in your organisation? Get in touch — I answer personally.
Short answer
The GDPR does not specify training frequency — there is no provision in it that would indicate “once a year” or any other interval. The controller’s obligation is to ensure that individuals processing data know how to proceed in their processes and to demonstrate this state with evidence. An annual cycle is often a reasonable benchmark for the entire organization, but the actual rhythm is set by changes in processes, employee turnover, conclusions from incidents, and test results. It is worth training a newly hired person or one changing positions before granting them access to data. It is different in the cybersecurity regime. The amended Polish KSC Act (Act on the National Cybersecurity System) directly specifies the training frequency for the head of an essential or important entity. The head of the entity undergoes training once per calendar year, as does the person entrusted with the head’s cybersecurity duties. According to the Minister of Digital Affairs, the first training of the head of the entity must take place no later than in 2027 in entities that already met the criteria on 3 April 2026.
Why this question arises at all
The question of frequency usually arises at two moments. One is when an organization is building a training schedule for the coming year and needs to enter a number, and the other is when an auditor or authority asks when the last training took place and who it covered. In both cases, a single number is expected, but the regulations do not provide one.
The source of doubt is the structure of the GDPR itself. The Regulation mentions staff training expressly as an element of the monitoring of compliance carried out by the data protection officer (Article 39(1)(b)). Binding corporate rules must also specify it (Article 47(2)(n)). Neither of these provisions sets a frequency. The Regulation builds the controller’s obligation around the result, not around the training event. The controller implements appropriate technical and organizational measures to ensure that processing is performed in accordance with the Regulation and to be able to demonstrate this (Article 24(1)). In doing so it takes into account the nature, scope, context and purposes of processing as well as the risks to the rights and freedoms of natural persons. It reviews and updates those measures where necessary (Article 24(1)). It also takes steps to ensure that every person acting under its authority who has access to personal data processes them only on its instructions, unless required to do so by Union or Member State law (Article 29 and Article 32(4)). Among the measures implemented as appropriate, the GDPR also lists regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing (Article 32(1)(d)). Training is one of the tools by which these requirements are met, not a separate obligation with its own deadline.
This difference has practical consequences. An organization that asks “is once a year enough” is asking something that cannot be resolved in isolation from its processes. An organization that asks “what needs to happen for us to train people before a change” is asking a question for which an answer exists.
It is worth separating training from technical security. In a case discussed by the UODO (Personal Data Protection Office), the Provincial Administrative Court in Warsaw ruled that a controller relying solely on training without technical safeguards does not implement appropriate measures.
Remember
Training changes how people act — it does not replace encryption, access control, or procedures.
What needs to be determined before making a decision
Who we are actually training
“All employees” is a category that most often dilutes the training program and means that no one receives content useful in their work. The starting point is a division into groups that process data differently and bear different risks. These are newly hired and changing positions, process owners, high-exposure teams (HR, customer service, sales, marketing, recruitment), IT and security departments, management staff, and the Data Protection Officer. Article 32(4) GDPR covers every natural person acting under the authority of the controller or processor who has access to personal data. It is therefore worth including contractors, interns and B2B collaborators in the plan.
This division determines frequency more than the calendar. A team where one-third of the members change during the year needs ongoing induction training, not a single event in November.
What has changed since the last training
The training cycle should respond to changes that genuinely alter how data is processed. In practice, this involves four types of events. These are launching or significantly redesigning a processing operation, implementing a new system or changing a vendor with access to data, and a change in the law or in an authority’s position affecting the organization’s obligations. The fourth is organizational change — a new structure, acquisition, or centralization of services.
If none of these events occurred in a given year, repeating the same training “because a year has passed” provides proof of attendance but changes little in behavior. If three occurred, the annual schedule is already outdated at the time of approval.
What incidents and reports say
The most reliable indicator of training needs are events that actually occur in the organization. Incorrect addressing of correspondence, sending to multiple recipients in the “cc” field, handing over documents to the wrong person, opening an attachment from a phishing email, using private tools to process work data — each of these indicates a specific group and a specific topic. In its guide on controllers’ obligations related to breaches, the UODO lists among example organizational measures the promotion of data protection rules among staff through regular training tailored to the nature of the work. Such training is meant to reduce the risk of human error.
In practice, it is worth linking the register of breaches and internal reports with the training plan as a constant input, rather than as an ad hoc reaction after a more prominent event. If the organization is only just organizing the process of identifying and assessing such events, assessing incidents and breaches is an earlier step than planning training.
How do we measure effectiveness
Article 32(1)(d) of the GDPR lists a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of processing — as one of the example measures, applied as appropriate. Where training serves the security of processing, measuring its effectiveness falls within this scope. The general requirement to review and update measures follows from Article 24(1). Organizations use knowledge tests after training, controlled phishing simulations, review of suspicious message reports, analysis of the repeatability of the same errors in subsequent periods, and short checks as part of internal audits.
The measurement result is what justifies changing the frequency. A group that repeats the same mistake in a test needs a shorter cycle and a different form of activity — not another presentation on general principles.
How do we prove that training took place
The controller must be able to demonstrate compliance with the principles of processing (Article 5(2)). The composition of the training records that serve this purpose is described in How to document training so that it serves as evidence for the authority?. It is worth recording at least the date and program of the training, the materials and named confirmation of attendance. A knowledge check result will also show what participants have learned.
What counts is the state before the incident. Decision DKN.5131.34.2023 of the President of the UODO of 13 June 2026 shows this. Before the breach the controller had not carried out a risk analysis and had not regularly tested the effectiveness of its safeguards. It introduced the risk analysis, new procedures and employee training only after the breach came to light, during the proceedings. The President of the UODO took these actions into account in the controller’s favor and reduced the fine by 50%. The infringement of the GDPR was nevertheless found for the whole period from 25 May 2018 until the non-compliance was remedied in 2023. Training carried out after an incident will therefore not show that staff were prepared earlier.
What other regimes cover the same organization
Some organizations are subject to both the GDPR and cybersecurity regulations, and the latter treat frequency differently. The amended KSC Act stipulates that the head of an essential or important entity and the person entrusted with the head’s cybersecurity duties must undergo training once per calendar year (Article 8e), and participation in the training must be documented. The scope of that training is set by Article 8e(2) through a reference to the catalogue of duties for which the head of the entity is responsible. For failure to perform the training obligation, the head of the entity may be fined separately where the duration, scope or nature of the breach justifies it (Article 73a(1)(4)). A head of the entity whose omission was a one-off may also be fined (Article 73a(2)). The penalty may reach 300% of the remuneration they receive, calculated under the rules for determining cash in lieu of annual leave, and as a rule 100% in a public entity (Article 73a(4) and (5)). This penalty may first be imposed two years after the entry into force of the amendment (Article 35 of the amending act). Entities that met the criteria for an essential or important entity on 3 April 2026 have 12 months to implement the obligations under Chapter 3 of the act (Article 33(1) of the amending act). This also covers the obligation under Article 8e. In the answers to questions on the amendment, the Minister of Digital Affairs indicates that in such entities the first training of the head of the entity must take place no later than in 2027 (Q&A 3.46). It may be held as early as 2026, with the next one in 2027. The deadline for the first training therefore does not end with the adjustment period.
For personnel, the act does not specify an interval — among the measures that the information security management system is to provide, it lists cybersecurity education for the entity’s personnel and basic cyber hygiene principles (Article 8(1)(2)). The Minister of Digital Affairs indicates that personnel education should take place on an ongoing basis (Q&A 3.8). It should also cover the personnel’s duties within the information security management system, existing procedures, cyber threats and examples of incidents. The head of the entity ensures that personnel are aware of their cybersecurity duties and know the entity’s internal rules in this area (Article 8d(4)).
The requirements for an important entity that is a public entity are built differently. It does not apply Article 8(1). It applies the requirements of Annex 4 to the act (Article 8(3)). The annex lists among them training of persons involved in the information processing process. The training is to address in particular types of cyber threats, cyber hygiene principles, incident response and awareness of the consequences of breaching information security rules. The annex does not set a training interval either. The entity reviews the information security management system at least once a year or promptly in two situations (Part III of Annex 4). The first is a recommendation of the Government Plenipotentiary for Cybersecurity concerning the entity’s information systems, ICT products or ICT services. The second is circumstances that may affect the risk of a significant incident and require the measures described in the system to be carried out again or the system itself to be changed.
The ISO/IEC 27001:2022 standard remains a voluntary reference point, which in Annex A provides for control 6.3 concerning information security awareness, education, and training. Applying the standard is not a legal obligation, but certified organizations must expect an auditor’s question about the cycle and effectiveness.
In practice, this means one thing. An organization covered by both regimes does not need two independent training programs. One plan is enough. In it the KSC deadline sets the rhythm for the head of the entity and the person under Article 8e(1). For other groups the scope combines the GDPR criteria with the personnel education required by the KSC Act.
Variants by role
The rhythm for each group is a practical assessment based on the typical organizational structure of a medium to large organization. It does not stem from regulations and requires confrontation with the risks of specific processes.
| Group | What triggers training | Rhythm applied in practice | How to demonstrate |
|---|---|---|---|
| Newly hired and changing positions | Granting data access, change of responsibilities | Before allowing processing, not on an annual cycle | Linking training to authorization and date of access grant |
| High-exposure teams (HR, customer service, sales) | Process change, recurring errors, conclusions from incidents | Shorter formats more frequently than once a year, tailored to the process | Thematic program, test results, incident report summary |
| Process owners | Process launch, DPIA, vendor change | Upon change and periodically | Workshop notes, process decisions, trace in process documentation |
| IT and security departments | Architecture change, new threats, post-breach conclusions | Continuous competence development, regardless of the general cycle | Competence development plan, certificates, exercises |
| Management staff | Managerial responsibility, KSC obligations | Statutory requirement under KSC for the head of the entity and the person under Article 8e(1) — once per calendar year; under GDPR determined by the organization | Under KSC (the head of the entity and the person under Article 8e(1)) a program linked to Article 8e(2) and a named confirmation of participation |
| Data Protection Officer | Legal changes, regulatory guidelines, supervisory practice | Continuous knowledge updating | Participation in training and conferences, resources provided by the controller or processor under Article 38(2) of the GDPR |
The obligation to provide the officer with the resources necessary to maintain their expert knowledge follows directly from Article 38(2) of the GDPR; the Guidelines for Data Protection Officers (WP243 rev.01), approved by the European Data Protection Board, develop it by indicating continuous training as an element of those resources. This requirement applies to the DPO role, not personnel — if the organization is also considering how to fill this function, the appropriate starting point is support from an external DPO.
Most common mistakes
- Treating the annual cycle as a legal obligation. The annual interval is an organizational practice. Referring to it as a GDPR requirement misleads management and makes it difficult to defend one’s position in case of an inspection.
- One training for all roles. Material general enough to fit every department usually does not change behavior in any of them.
- Stopping at the attendance list. Proof of participation without scope, materials, and knowledge verification shows that training took place, but not what it covered.
- Training as the only response to an incident. After a breach resulting from human error, training is one of the corrective actions, not a substitute for process change or technical security.
- Lack of connection with the register of processing activities and authorizations. Without this connection, it is impossible to demonstrate that individuals processing data in a specific process have been trained in its scope.
Conclusions and next steps
The question “how often” leads to a schedule that ages faster than the organization. It is more practical to establish two things at once. These are a minimum baseline rhythm that maintains awareness throughout the organization, and a list of events that trigger training outside the schedule. The first part provides predictability, the second — a reaction to change.
A sequence of actions that works well when organizing this area.
- Map target groups by processes and risk, rather than by organizational structure.
- Name training triggers outside the cycle. These are a new process, a new system or vendor, a legal change, an organizational change and conclusions from an incident.
- Establish a baseline rhythm for each group and document its justification — this justification, not just the date, is the essence of accountability.
- Choose a method for measuring effectiveness for each group and determine what result triggers a cycle correction.
- Link training documentation to processing authorizations and the register of processing activities.
- If the organization is an essential or important entity, include in the plan the annual training of the head of the entity and the person under Article 8e(1). According to the Minister of Digital Affairs, the first training of the head of the entity must take place no later than in 2027 if the entity already met the criteria on 3 April 2026. Treat this deadline as a fixed point around which you arrange the rest.
After going through this sequence, training frequency ceases to be a number from the calendar. It becomes a principle that the organization can justify and demonstrate.
Related materials
- How to determine if an organization must appoint a DPO? — the role whose task is to monitor compliance, including awareness-raising activities and training of staff (Article 39(1)(b)).
- Does every data breach need to be reported? — how to assess events whose conclusions should be included in the training plan.
- How to document training so that it serves as evidence for the authority? — what to record about training and how long to keep the record, so that the training can be demonstrated years later.
Sources
- Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), consolidated text — EUR-Lex: eur-lex.europa.eu
- Act of 23 January 2026, amending the Act on the National Cybersecurity System and certain other acts (Journal of Laws 2026, item 252) — Dziennik Ustaw: dziennikustaw.gov.pl (in Polish)
- Questions and answers on applying the amended Act on the National Cybersecurity System, October 2026 update (Q&A 3.8 and 3.46) — Minister of Digital Affairs: cyber.gov.pl (in Polish)
- Obligations of controllers related to personal data breaches, version of 20 February 2025 — Personal Data Protection Office: uodo.gov.pl (in Polish)
- WSA: an employee cannot replace the controller in fulfilling their obligations, communication of 11 April 2022 — Personal Data Protection Office: uodo.gov.pl (in Polish)
- Decision of the President of the UODO DKN.5131.34.2023 of 13 June 2026 — UODO rulings database: orzeczenia.uodo.gov.pl (in Polish)
- Guidelines for Data Protection Officers (WP243 rev.01), approved by the European Data Protection Board, translation on the UODO website: uodo.gov.pl (in Polish)
- ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection — Information security management systems — Requirements: iso.org
Let’s determine what the training cycle in your organization should look like
If your organization’s training program currently relies on a single annual event, the first sensible step is to define target groups, triggers, and how to demonstrate effectiveness. Training and workshops tailored to roles and processes begin with this diagnosis.
This material is general and educational in nature. It is not an individual legal opinion or a recommendation for any specific organisation. The scope of the obligations should be assessed against the situation of the organisation concerned.
Legal status: November 2026.