How to determine if an organization must appoint a DPO?

Michał Rutkowski • for management and executives • published June 30, 2026 • updated October 19, 2026 • 11 min read

Brief answer

The obligation to appoint a Data Protection Officer arises in three cases specified in Article 37(1) of the GDPR. The first concerns processing by a public authority or body, except for courts acting in their judicial capacity. In Poland the circle of such entities is defined by Article 9 of the Polish Personal Data Protection Act. The second concerns core activities consisting of processing operations which by virtue of their nature, scope or purposes require regular and systematic monitoring of data subjects on a large scale. The third concerns core activities consisting of processing on a large scale of special categories of data under Article 9 of the GDPR or of personal data relating to criminal convictions and offences under Article 10 of the GDPR. Outside these cases, the appointment of a DPO is voluntary, unless the obligation arises from another provision of Union or national law. None of the conditions refer to the size of the organization or the number of employees. Outside public bodies the nature of the core activity and the scale of processing are decisive, which is why the answer requires analysis rather than checking a single threshold. The conditions are assessed separately for the role of controller and of processor. The WP 243 guidelines of the Article 29 Working Party recommend documenting this analysis, unless it is obvious that there is no obligation.

Why this question arises at all

The conditions in Article 37(1) of the GDPR are imprecise. The Articles of the Regulation do not define ‘core activity’, ‘large scale’ or ‘regular and systematic monitoring’. Some guidance is given in recitals 24, 91 and 97. These concepts were clarified by the Article 29 Working Party guidelines, subsequently endorsed by the European Data Protection Board. The Personal Data Protection Office indicates that the provision is imprecise on purpose. According to the Office, the controller is meant to analyse its own situation and assess whether the obligation applies.

For organizations, this means an unusual situation. The provision imposes an obligation but does not provide a test that can be mechanically passed. The result depends on what the organization does and on what scale, not on how large it is.

The question usually reappears at three moments. These are when launching a new data-driven service, when changing the organizational structure or when an external party — a client, insurer or auditor — asks for the DPO’s contact details and it turns out that no one can indicate on what basis the organization does not have one.

What needs to be determined before making a decision

The analysis has three steps corresponding to the three conditions, plus two control questions. Go through them in order. If the first condition is met, it settles the matter without a scale assessment.

1. Is the organization a public authority or body?

The first condition applies regardless of the scale of processing. If processing is carried out by a public authority or body, a DPO is mandatory. The GDPR excludes only courts in the exercise of their judicial functions.

Polish law clarifies this scope. Under Article 9 of the Act of 10 May 2018 on personal data protection, the public authorities and bodies obliged to appoint a DPO are public finance sector units, research institutes and the National Bank of Poland. This list closes the matter for most public organizations. No further scale analysis is needed for them.

It is worth noting an intermediate situation. A municipal company or an institution performing public tasks under a contract does not always fall into this category, yet may be subject to the obligation on other grounds. In such a scenario, one proceeds to the next steps instead of stopping at the answer ‘we are not a public finance sector unit.’ The WP 243 guidelines of the Article 29 Working Party recommend as good practice that private organisations carrying out public tasks or exercising public authority appoint a DPO. Such a DPO covers all processing operations, including employee data.

2. Does the core activity require monitoring individuals on a large scale?

The second condition does not require monitoring itself to be the core activity. The core activity must consist of processing operations which by virtue of their nature, scope or purposes require such monitoring. Three elements must be assessed, and all of them must be present together.

Core activity is — according to the guidelines — key operations necessary to achieve the organization’s objectives, not ancillary activities. Processing employee data for HR and payroll purposes is an ancillary activity in almost every organization, even a large one. It is different where data processing is inextricably linked to the service. A security company monitoring facilities or a hospital maintaining medical records cannot provide its service without processing data, so it is an element of the core activity.

Regular and systematic monitoring is a notion that the guidelines explain through two groups of features. Regular means ongoing, periodic or recurring at fixed times. Systematic means occurring according to a system, organised or taking place as part of a general plan for data collection or a strategy. One feature in each group is enough. The guidelines give examples of activities that may constitute such monitoring. These include data-driven marketing, profiling and scoring for risk assessment, and location tracking by mobile apps. The guidelines also list loyalty programs, behavioural advertising and closed circuit television.

Large scale has no numerical threshold. The guidelines recommend considering four factors in particular. These are the number of data subjects, the volume or range of data, the duration of processing and its geographical extent. The number of data subjects may also be assessed as a proportion of the relevant population. As examples of large-scale processing, the guidelines give patient data processed by a hospital and customer data processed by an insurer or a bank. They also give behavioural advertising by a search engine and data processed by telephone or internet service providers.

The outcome of this step can be ambiguous, and that is normal. It is important that each of the three elements is actually assessed and the assessment documented.

3. Does the core activity consist of processing special categories of data on a large scale?

The third condition covers special categories of data under Article 9 of the GDPR or personal data relating to criminal convictions and offences under Article 10 of the GDPR. Special categories include data concerning health, biometric data for the purpose of uniquely identifying a natural person and data revealing trade union membership. One of these groups of data is enough, provided it is processed on a large scale as part of the core activity.

This is where the question of healthcare most often arises. When answering a question about a non-public medical entity serving approximately two thousand patients, the Personal Data Protection Office did not provide a definitive ruling but pointed to reference points from the guidelines. A hospital is an example of large-scale processing, while processing by a single doctor practicing individually is not. Between these two extremes, an organization must assess its own situation, considering the nature of its activity and the scale of documentation, and revisit this assessment when the scale changes.

4. Does the obligation not arise from another provision?

Article 37(4) of the GDPR allows for the obligation to appoint a DPO to arise from Union law or national law also in cases not covered by paragraph 1. Before concluding your analysis with a negative result, check the sectoral regulations applicable to your industry.

Distinguish between a DPO and roles introduced by other regimes. The Polish KSC Act (Act on the National Cybersecurity System) requires essential and important entities to appoint at least two persons responsible for maintaining contacts with entities of the national cybersecurity system; one person is sufficient only for a micro or small enterprise and for an important entity that is a public entity. This is a separate obligation, with a different basis and scope — its fulfillment does not replace the appointment of a data protection officer, and the appointment of a DPO does not exempt from that obligation.

5. Has the analysis been carried out separately for the role of controller and processor?

Article 37(1) of the GDPR addresses the obligation to both the controller and the processor. An organization that provides services to others — hosting, HR support, archiving, system maintenance — also assesses the conditions for processing carried out on behalf of others. It sometimes happens that the result is different for both roles. An entity may have no obligation as a controller of its own data. It may still have one as a processor, if the processing for clients meets the second or third condition. A large scale of processing alone is not enough. The DPO appointed by the processor then also covers processing in which the entity acts as a controller. The number of DPOs is a separate organizational decision. A group of undertakings may appoint a single data protection officer provided that the DPO is easily accessible from each establishment (Article 37(2)), and several public authorities or bodies may appoint a joint officer, taking account of their organizational structure and size (Article 37(3)).

Three possible outcomes of the analysis

OutcomeWhat it impliesWhat to prepare
At least one condition of Article 37(1) met, or an obligation under another provisionDPO appointment is mandatoryAppointment document, notification to the President of the UODO (Personal Data Protection Office), publication of data, ensuring conditions for performing the function
Conditions not met, organization voluntarily appoints a DPOThe WP 243 guidelines state that the same requirements apply to a voluntarily appointed DPO as to a mandatory oneThe same as for a mandatory appointment — voluntariness applies to the decision, not the regime
Conditions not met, organization does not appoint a DPONo obligation. The WP 243 guidelines treat the analysis as part of the documentation under the accountability principleA documented analysis, which the WP 243 guidelines recommend unless it is obvious that there is no obligation. It is worth adding the date, input data and the approving person

The third variant is the one most often forgotten. The guidelines explicitly recommend that the controller and processor document the internal analysis carried out — unless the lack of obligation is obvious — precisely to be able to demonstrate that the appropriate factors have been taken into account.

An organization without the obligation may entrust data protection tasks to an employee or a consultant. The WP 243 guidelines of the Article 29 Working Party state that it should then be made clear that this person is not a data protection officer. This applies to internal communications and contacts with the supervisory authority. It also applies to information for data subjects and the public at large.

What should management know?

The decision to appoint a DPO is not a technical decision of the IT or HR department. The choice of the role, its placement in the structure and ensuring independence are management decisions. Responsibility for them lies with the controller or processor that appoints the DPO, i.e. the organization represented by its management.

Three things management should understand before making a decision.

Remember

It is worth being able to demonstrate that there is no obligation. The WP 243 guidelines recommend documenting the analysis for this purpose, unless it is obvious that there is no obligation.

Secondly, appointing a DPO does not transfer responsibility for compliance to the DPO. The DPO monitors, advises and acts as a contact point. Decisions remain with the controller or processor. Thirdly, the function requires conditions. The DPO must be involved, properly and in a timely manner, in all issues which relate to data protection. The DPO must receive resources to carry out the tasks and maintain expert knowledge, as well as access to personal data and processing operations. The DPO receives no instructions regarding the exercise of the tasks and may not be dismissed or penalised for performing them. The DPO reports directly to the highest management level, and other tasks may not result in a conflict of interests. A DPO appointed without these conditions creates the appearance of compliance, not actual compliance. The Act also allows a deputy to be designated to stand in for the DPO during the DPO’s absence, taking account of the criteria in Article 37(5) and (6) of the GDPR (Article 11a(1) of the Act of 10 May 2018). The provisions on the DPO apply accordingly to the deputy in connection with performing the DPO’s duties during the DPO’s absence (Article 11a(2)). The deputy’s designation is subject to notification and publication on the same terms (Article 11a(3)).

Most common errors

  • Assessment based on organization size instead of activity nature. The number of employees is not a criterion under Article 37(1) of the GDPR. A small company conducting user profiling may be subject to an obligation that a large manufacturing plant does not have.
  • Oral or implied appointment. The President of the UODO indicates that the controller should strive for an internal act or a contract that indicates beyond doubt a specific person as the DPO. Examples of such an act are an internal order, a resolution or a delegation of duties. For evidential purposes, the written form is important. A precise scope of duties in line with Articles 38 and 39 of the GDPR is also necessary. According to the President of the UODO, an oral instruction does not make the appointment effective. In the President’s view, an authorisation, an information clause and a training certificate can only indirectly show that a person performs the function. A person ‘informally dealing with GDPR’ is not a DPO. Form alone is not enough. A DPO is designated on the basis of professional qualities, in particular expert knowledge of data protection law and practices and the ability to fulfill the tasks referred to in Article 39 of the GDPR (Article 37(5)).
  • Failure to notify and publish. The obligation to publish the DPO’s contact details and to communicate them to the supervisory authority arises from Article 37(7) of the GDPR; the Act of 10 May 2018 adds the deadline, the form, and the manner. Notification to the President of the UODO must be submitted within 14 days of appointment (Article 10(1) of the Act). It is made in electronic form and signed with a qualified electronic signature or a signature confirmed with the ePUAP trusted profile (Article 10(6)). The same deadline applies to changes in data and to the dismissal of a DPO (Article 10(4)). Where one DPO is appointed by several public entities or by a group of undertakings, each of those entities files its own notification (Article 10(5)). The DPO’s data must be made available without delay on the website, or if there is no website, in a generally accessible manner at the place of business. For example, the President of the UODO fined a district building supervision authority for failing to appoint a DPO and consequently for failing to publish the DPO’s details and notify the supervisory authority.
  • Conflict of interests. The WP 243 guidelines of the Article 29 Working Party state in particular that the DPO cannot hold a position that leads him or her to determine the purposes and means of processing. Such positions may include senior management positions, for example chief executive or head of IT, HR or marketing. They may also include roles lower down if those roles lead to the determination of purposes and means of processing. The guidelines state that this has to be considered case by case. This is one of the elements the office directly asks about during verification. The President of the UODO considers it inadmissible to designate as DPO a person who manages the controller or processor, for example a member of a company’s management board.
  • Confusing DPO with roles from other regimes. The contact persons appointed under the Polish KSC Act, an internal information security coordinator and the data protection officer are three different functions.
  • Treating the analysis as a one-off activity. A change in business profile, entry into new markets, launching a loyalty program, or acquiring another entity can change the outcome. An assessment without a date and without a review cycle ages with the organization.

Conclusions and next steps

The answer to the question of the obligation to appoint a DPO is the result of an analysis of three conditions and of sector-specific provisions, not a check of a single criterion. For public entities listed in the Act, the matter is settled. For other organizations, the nature of the core activity and the scale of processing are decisive. Scale is assessed according to the factors from the guidelines. These are in particular the number of data subjects, the volume or range of data, duration and geographical extent.

The sensible sequence of actions is brief. Determine whether the organization falls within the catalog of public entities under Article 9 of the Act. If not, assess both scale conditions separately for the role of controller and processor. Check sectoral regulations for Article 37(4) of the GDPR. Document the result along with input data, date and approving person. For a negative result, the WP 243 guidelines recommend a record unless it is obvious that there is no obligation. If the obligation exists or the organization decides to appoint voluntarily, immediately plan three things. These are the appointment document with the scope of tasks, notification within 14 days, and data publication. The DPO may be a staff member of the controller or processor, or perform tasks under a service contract (Article 37(6)) — the choice of model is an organizational decision, not a condition for the effectiveness of the appointment. Finally, set a moment for re-review — the simplest way is to link it to the review of the record of processing activities.

Sources

  • Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), Articles 37–39, consolidated text — EUR-Lex: eur-lex.europa.eu
  • Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), text as published in OJ L 119 of 4 May 2016, recitals 24, 91 and 97 — EUR-Lex: eur-lex.europa.eu
  • Act of 10 May 2018 on personal data protection, Articles 8–11a — ISAP: isap.sejm.gov.pl (in Polish)
  • Act of 5 July 2018 on the National Cybersecurity System (the Polish KSC Act), Article 9 — ISAP: isap.sejm.gov.pl (in Polish)
  • Should a DPO be appointed in a non-public healthcare facility with approximately 2000 patients — Personal Data Protection Office: uodo.gov.pl (in Polish)
  • Verification of compliance with regulations concerning the data protection officer — Personal Data Protection Office: uodo.gov.pl (in Polish)
  • Fine for failing to ensure the independence of the data protection officer, communication of 31 August 2026 on decision DKN.5131.24.2025 — Personal Data Protection Office: uodo.gov.pl (in Polish)
  • Effective DPO appointment as a necessary condition for effective data protection — Personal Data Protection Office: uodo.gov.pl (in Polish)
  • Guidelines on Data Protection Officers (WP 243 rev. 01), Article 29 Working Party, adopted 13 December 2016, amended 5 April 2017, approved by the European Data Protection Board, English original — European Commission: ec.europa.eu; Polish version — Personal Data Protection Office: uodo.gov.pl (in Polish)

Settle it once and for all

If the result of the analysis in your organization is not unambiguous, or if a DPO has been appointed but it is unclear whether effectively, it is worth resolving both issues before further organizational decisions. External DPO/DPO support includes assessing the obligation, organizing appointment documentation and notifications, and taking over or supporting the DPO’s function.

Author

Michał Rutkowski — LabLogic. He combines the legal, organisational and technological perspective in his work with the boards of medium-sized and large organisations: support for and performance of the DPO role, preparation for NIS2 and the Polish KSC Act, incident response, audits and training. Contact: M.Rutkowski@LabLogic.pl · LinkedIn

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.

Scroll to Top