Let’s talk
Wondering how this plays out in your organisation? Get in touch — I answer personally.
Short answer
The board should expect from the data protection officer a picture of the state of data protection, not a report of activities performed. That picture is made up of six things. These are the DPO’s work plan and how far it has been delivered, the result of monitoring compliance together with the weight of the departures identified, the risks treated as priorities, the recommendations issued together with what happened to them, the course of breach cases and of contacts with the supervisory authority and with data subjects, and the conditions in which the DPO works. The GDPR does not set the format or the frequency of such reporting — it does settle that the DPO is to be involved, properly and in a timely manner, in all issues relating to data protection, and that they report directly to the highest management level. The organization therefore sets the scope and the cycle itself, but it does not get to decide whether the flow exists at all. What should not be expected is that the DPO takes over responsibility for compliance or takes the processing decision on the board’s behalf.
Why this question arises at all
The GDPR describes the position and the tasks of the DPO, but it does not describe the route by which the results of their work are to reach senior management. The Regulation requires the controller and the processor to ensure that the DPO is involved properly and in a timely manner in all issues relating to the protection of personal data (Article 38(1)), settles that the DPO reports directly to the highest management level (Article 38(3)) and lists the tasks (Article 39(1)). These are informing and advising, monitoring compliance with the rules and with policies — including the assignment of responsibilities, awareness-raising, training of staff and the related audits — providing advice on request as regards the data protection impact assessment and monitoring its performance, cooperating with the supervisory authority, and acting as the contact point. On what exactly is to reach the board’s table, in what form and how often, it says nothing.
This creates an arrangement that is uncomfortable for both sides. Responsibility for compliance and for demonstrating it stays with the controller, that is, with the organization represented by its senior management — the DPO monitors and advises, but is not answerable for the consequences of decisions they do not take. The board therefore runs an organization answerable for an area of which it knows exactly as much as it has been told. Usually it also has no way of its own to check whether it has been told everything that matters.
The scale of this is known. In the coordinated enforcement action of the European Data Protection Board of 2023 the questionnaire was completed by 17,490 respondents from the European Economic Area. They included 15,108 organizations and 2,382 DPOs. The most frequent answer on the frequency of DPO reporting to the highest management level was “once or twice a year” (median 45.64%). In the same action 16.9% of respondents indicated that no reporting from the DPO is expected at all. Only 34.59% of respondents (median) document the reasons for departing from the DPO’s recommendations every time. The answer “most of the time” was chosen by 18.23% (median).
The third reason is practical. The list of questions the Personal Data Protection Office (UODO) puts to controllers and processors when verifying compliance with the rules on the DPO is largely about exactly this flow of information. It asks whether the DPO draws up a work plan and how often they pass on audit results. It also asks how the controller proceeds when it does not follow the DPO’s recommendations and whether it then documents the reasons. Finally, it asks whether and how the controller checks the DPO’s work. These are questions to the controller, not to the DPO. A board that does not know the answers finds out about the gap at the worst possible moment.
What must be determined before the decision
What follows from the rules and what from the organization’s own arrangements
From the rules follow the DPO’s position and the duty to maintain a flow of information, not the format of a report. Involving the DPO in all issues relating to data protection is to be proper and timely, and their reporting line — direct. Article 38(1) GDPR addresses the involvement rule to the controller and the processor. Direct reporting to the highest management level, by contrast, binds both sides. The DPO reports directly, and the organization has to provide such a line in its structure. When the duty to appoint a DPO arises at all, and how to document that analysis, is explained in How to determine if an organization must appoint a DPO?. The guidelines on data protection officers give, as an example of how that reporting line is realized, an annual report on the DPO’s activities prepared for the highest management level. That is an example from the guidelines, not a requirement of the rules. The whole difficulty lies in that distinction. The absence of a report is not in itself a breach. Without such a document, however, it is harder for the organization to show that the DPO reports directly to the highest management level.
From the organization’s own arrangements follows the rest. That means the scope of the information, its cycle, its form, the addressee on the board’s side and the escalation path in urgent matters. These arrangements are a management decision, not a technical one — and it is worth taking them deliberately rather than letting them take shape by accident.
Six areas worth asking about regularly
- The work plan and how far it has been delivered. According to UODO, monitoring compliance should not be one-off but continuous and long-term. The office considers it worth having an audit plan. According to UODO, the plan should take into account the specifics of the organization and must be adjusted to the risk assessment. The Regulation expressly requires the monitoring itself, not a plan (Article 39(1)(b) GDPR). Monitoring compliance also covers the related audits and the awareness-raising and training of staff. The board should know that plan, its scope, how much of it has been delivered, and what was moved and why.
- The result of the monitoring, not a list of activities. What has value is information on which areas were checked, where departures were found and how serious they are. A tally of training sessions and checks carried out, with no assessment of the result, tells the board nothing about the state of the organization.
- Priority risks and the areas checked less often. The DPO performs their tasks with due regard to the risk associated with processing operations, taking into account the nature, scope, context and purposes of processing — which in practice means setting priorities. The WP 243 guidelines state that this does not mean neglecting compliance monitoring of processing operations with a lower level of risk. The board should know which areas the DPO checks less often, and why.
- Recommendations and what became of them. This is the most important element of the whole flow. The board should know which recommendations were issued, which were implemented, which were not and on what reasoning. A decision differing from the DPO’s position is permissible, because decisions are taken by the controller. The WP 243 guidelines recommend as good practice documenting the reasons for not following the DPO’s advice. Without such a record the decision later looks not like a decision but like an oversight.
- Breaches, data subject requests and contacts with the authority. What matters is the aggregate picture. It shows how many events were assessed, how many were classified as personal data breaches, how many were notified to the authority and why the rest were not, what requests from individuals came in and whether the deadlines were met, whether any proceedings are pending. A single high-risk event obviously calls for immediate information, outside the cycle.
- The conditions in which the function is performed. Providing the DPO with the resources necessary to carry out their tasks, with access to personal data and processing operations and with resources to maintain their expert knowledge is an obligation of the controller and the processor under Article 38(2) GDPR. A question about conditions is therefore the board asking about the performance of its own obligation. The same area covers any conflict of interests and the designation of a person to deputize for the DPO during their absence, where the organization uses that option. When designating a deputy, the organization takes into account the criteria of Article 37(5) and (6) GDPR. After designating the deputy, the organization notifies the President of the UODO of the designation and makes the deputy’s details available (Article 11a(1) and (3) of the Polish Personal Data Protection Act). What the DPO’s resources cover and how to assess them is explained in What resources must a data protection officer receive?.
These six areas add up to a single piece of information. That information is whether the organization is in control of its data processing and whether it can demonstrate it. If the DPO’s report does not allow that question to be answered, its scope needs to change — however extensive it may be.
What the board should not expect from the DPO
Part of the friction in the board–DPO relationship comes from expectations the role simply does not cover.
According to the WP 243 guidelines, the DPO is not personally responsible for non-compliance with data protection requirements. When the DPO is answerable for neglecting their own tasks is covered in Is the data protection officer liable for a personal data breach?.
Remember
The duty to ensure and demonstrate compliance belongs to the controller — appointing a DPO does not transfer it.
Nor does the DPO take the controller’s place in the controller’s own tasks. Keeping the record of processing activities is a controller obligation (Article 30(1) GDPR). The WP 243 guidelines allow the controller to assign the DPO the task of maintaining the record. The obligation to maintain the record nevertheless remains with the controller. According to the same guidelines, a conflict of interests may arise if an external DPO is asked to represent the controller before the courts in cases involving data protection issues.
The DPO does not “approve” projects or decisions. They give a position; the decision is taken by whoever is answerable for the process. In a data protection impact assessment the division of roles is clear. The controller carries out the assessment and seeks the DPO’s advice when doing so (Article 35(1) and (2) GDPR). The DPO provides advice on request as regards the assessment and monitors its performance (Article 39(1)(c) GDPR). However, the DPO does not carry it out for the process owner.
Two limits run in the other direction and primarily bind the board. The controller must ensure that the DPO receives no instructions regarding the exercise of their tasks and is not dismissed or penalized for performing them. These are not recommendations addressed to the DPO but obligations of the organization — and therefore also the limits of what the board may require of them. An expectation of “a position that will let the project go ahead” is, in that arrangement, an impossible one.
The third limit sometimes comes as a surprise. The DPO is bound by secrecy or confidentiality concerning the performance of their tasks, in accordance with Union or Member State law (Article 38(5) GDPR). The WP 243 guidelines point out that employees may be reluctant to complain to the DPO if the confidentiality of their communications is not guaranteed. The board may expect a full picture of the state of data protection. In my assessment it may not expect every piece of information the DPO has obtained in individual cases, particularly from reports by individuals.
Cycle, form and evidence trail
A sensible arrangement has three levels, and it is worth keeping them apart, because mixing them produces either a flood of detail or silence. The first level is the periodic report — annual as a minimum, half-yearly or quarterly in organizations with intensive processing — covering the six areas of the report. The second level is immediate information outside the cycle, triggered by events that require a decision. These are a high-risk breach, proceedings by the authority, an impact assessment showing high residual risk, a planned change with a major effect on processing. The third level is direct access — the ability to approach the DPO outside the schedule, and the DPO’s ability to approach the board whenever they consider it necessary.
The second and third levels are worth treating as the standard rather than an extra. Article 38(1) GDPR requires that the DPO be involved, properly and in a timely manner, in all issues which relate to the protection of personal data. The WP 243 guidelines state that the DPO must be promptly consulted once a data breach or another incident has occurred. The EDPB states in its report that infrequent or irregular reporting by DPOs to the highest management level raises significant concerns about effective oversight and governance. An annual report alone will therefore provide neither the DPO’s involvement nor information for the board at the moment of decision.
All three levels are worth writing down in an internal rulebook, a resolution or the document appointing the DPO. The document sets expectations on both sides and at the same time evidences that the flow of information was designed in the organization rather than left to chance. The same value attaches to adopting the rule that the DPO’s position, and any board decision departing from it, go into the minutes together with the reasoning.
Most common mistakes
- An activity report instead of a report on the state of affairs. A document listing training delivered, opinions issued and checks carried out, with no assessment of the result, provides no basis for any decision.
- No trace of rejected recommendations. Departing from the DPO’s position without recorded reasoning is a weakness visible in the EDPB action. UODO asks about it directly when verifying compliance with the rules on the DPO.
- Reporting through an intermediary. In my assessment, passing information through the IT, HR or compliance director undermines the principle of direct reporting to the highest management level (Article 38(3) GDPR) and smooths out along the way exactly what matters most to the board.
- An annual cycle only. Without a path outside the cycle, the organization learns about the problem at a point when the decision is already late.
- Treating the report as a formality. A report accepted without discussion and without a decision differs in its effects not at all from a report that never existed.
- Expecting a guarantee. The question “are we compliant” has no unequivocal answer. The useful answer states which areas are in order, which are not, how serious the departures are and in what order it is worth closing them.
- Asking only after an event. Contact with the DPO only at the point of a breach or an inspection means the organization uses the role reactively and, for most of the year, does not know where it stands.
Questions for the next board meeting
The answers to these questions do not replace a report. They do let you check whether the flow of information you have so far is sufficient.
- Is there a work plan for the DPO for the current year, and how far has it been delivered?
- Which processing areas were checked in the last period, and with what result?
- Which three risks does the DPO consider the most serious today, and what reduces them?
- What recommendations were issued in the last period, which of them were implemented, and where the organization acted differently — where is the reason recorded?
- How many events were assessed as possible personal data breaches, how many were notified to the authority, and on what basis was notification not made in the remaining cases?
- Are there any pending proceedings, complaints or data subject requests that require management attention?
- Does the DPO have the resources, the time, access to data and processing operations and the means to maintain expert knowledge — and if not, what is missing?
- Has any arrangement arisen in the structure that risks a conflict of interests, particularly after organizational changes?
- Has it been settled in which situations the DPO contacts the board outside the schedule — and was that path used in the past year?
Conclusions and next steps
The flow of information between the DPO and the board is an element of the data protection system, not a matter of organizational culture. The rules give that flow its basis and set its minimum — proper and timely involvement of the DPO in all issues, and direct reporting to the highest management level — but they do not fill it with content. The organization fills it, and the organization is answerable for the consequences if it does not.
The order of actions is short. Establish whether the organization has a settled scope and cycle of information from the DPO; if not, adopt them first. Agree the scope of the report around the six areas. These are the work plan, the result of monitoring, priority risks, recommendations and what became of them, breach cases and contacts with the authority, and the conditions in which the function is performed. Introduce the rule of documenting decisions that depart from the DPO’s position. Define the events that trigger immediate information. Write these arrangements into a document that can be shown. Finally, check whether the DPO has the conditions to prepare such a report at all — because providing them is a controller obligation, and a report demanded of someone with no access to information and no time to analyze it will be worth exactly as much as those conditions.
Related materials
- How to determine if an organization must appoint a DPO? — the three grounds for the obligation and how to document the analysis.
- Does every data breach need to be reported? — the risk assessment and the notification decision, that is, the material behind the fifth area of the report.
- Where should the board begin preparing for NIS2? — management responsibility in the second regime.
Sources
- Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), Articles 30(1), 35(1)–(2) and 38–39, consolidated text — EUR-Lex: eur-lex.europa.eu
- Act of 10 May 2018 on personal data protection, Articles 8–11a, consolidated text — Chancellery of the Sejm, ISAP: isap.sejm.gov.pl (in Polish)
- Should the DPO draw up an audit plan? — Personal Data Protection Office (UODO): uodo.gov.pl (in Polish)
- Verification of compliance with the rules on the data protection officer, communication of 30 March 2022 — Personal Data Protection Office (UODO): uodo.gov.pl (in Polish)
- Guidelines on Data Protection Officers (WP 243 rev. 01), Article 29 Working Party, endorsed by the European Data Protection Board — European Data Protection Board: ec.europa.eu
- 2023 Coordinated Enforcement Action. Designation and Position of Data Protection Officers, report adopted on 16 January 2024 — European Data Protection Board: edpb.europa.eu
Check what your board knows today
If you are not sure whether the information reaching the board allows it to assess the state of data protection and take decisions, it is worth starting with a review of that flow and of the scope of the DPO’s report. Support of an external DPO covers putting the relationship with senior management in order, setting the scope and cycle of reporting, and taking over or supporting the DPO function.
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.