← Back to Insights

GDPR

How to Carry Out a DPIA in Ireland (2026): When One Is Required and What It Must Contain

Michael K. Onyekwere··Updated ·12 min read

A data protection impact assessment (DPIA) is required in Ireland, as everywhere the GDPR applies, before processing that is likely to result in a high risk to the people whose data is used. The Data Protection Commission (DPC) supervises the GDPR in Ireland and has published its own list of processing for which a DPIA is mandatory. This guide sets out when an assessment is required, what it must contain, when you must consult the DPC, and how the steps work in practice, using a worked example.

Our DPIA tool takes you through your own assessment in a conversation and drafts the document as you answer. It is free to complete.

When a DPIA is required

The test is in Article 35(1) of the GDPR. A DPIA is required where a type of processing, "in particular using new technologies", is likely to result in a high risk to the rights and freedoms of individuals, taking into account the nature, scope, context and purposes of the processing. It must be carried out before the processing begins.

Article 35(3) names three cases in which a DPIA is required in particular:

  1. a systematic and extensive evaluation of people based on automated processing, including profiling, on which decisions are based that produce legal effects or similarly significant effects;
  2. large-scale processing of special category data (such as health data) or of data about criminal convictions and offences;
  3. systematic monitoring of a publicly accessible area on a large scale.

Outside those three cases, the European guidelines on DPIAs (WP248 rev.01, endorsed by the European Data Protection Board) give nine criteria: evaluation or scoring; automated decision-making with legal or similarly significant effect; systematic monitoring; sensitive data or data of a highly personal nature; data processed on a large scale; matching or combining datasets; data concerning vulnerable people; innovative use or application of new technological or organisational solutions; and processing that prevents people from exercising a right or using a service or a contract. In most cases, processing that meets two or more of these criteria will need a DPIA, although the guidelines also say that processing meeting only one criterion may require one, and the count is a guide rather than the test itself. The guidelines count employees among vulnerable people, because of the imbalance of power between an employer and its staff.

The DPC's list

Article 35(4) requires each supervisory authority to publish a list of processing that needs a DPIA. The DPC's list states that a DPIA is mandatory for the following types of processing where a documented screening or preliminary risk assessment indicates that the processing is likely to result in a high risk:

  1. Use of personal data on a large scale for a purpose other than that for which it was initially collected (Article 6(4)).
  2. Profiling vulnerable persons, including children, to target marketing or online services at them.
  3. Use of profiling or algorithmic means or special category data as an element to determine access to services, or that results in legal or similarly significant effects.
  4. Systematically monitoring, tracking or observing individuals' location or behaviour.
  5. Profiling individuals on a large scale.
  6. Processing biometric data to uniquely identify, or enable the identification or authentication of, an individual, in combination with any of the other WP29 DPIA criteria.
  7. Processing genetic data in combination with any of the other WP29 DPIA criteria.
  8. Indirectly sourcing personal data where transparency requirements are not being met, including when relying on exemptions based on impossibility or disproportionate effort.
  9. Combining, linking or cross-referencing separate datasets where the linking significantly contributes to or is used for profiling or behavioural analysis, particularly where the datasets come from different sources, purposes or controllers.
  10. Large-scale processing where the Data Protection Act 2018 requires "suitable and specific measures" to safeguard individuals' rights and freedoms.

The DPC adds that the list is not exhaustive and that it is good practice to carry out a DPIA for any major new project involving personal data. The list is the DPC's document of 15 November 2018 (revised), which the DPC publishes as a PDF.

Whatever the result, record the screening. Where you conclude that no DPIA is required, a short written record of the reasons shows that the question was considered and makes it easier to revisit if the processing changes.

What the assessment must contain

Article 35(7) sets the minimum content:

  • a systematic description of the processing and its purposes, including any legitimate interest pursued;
  • an assessment of whether the processing is necessary and proportionate to those purposes;
  • an assessment of the risks to the rights and freedoms of the people affected;
  • the measures envisaged to address those risks, including safeguards, security measures and mechanisms to ensure the protection of personal data and to demonstrate compliance, taking into account the rights and legitimate interests of the people affected and others concerned.

In addition, where you have designated a data protection officer, you must seek their advice when carrying out the DPIA (Article 35(2)), and the document should record that advice and whether it was followed. Where appropriate, you must seek the views of the people affected or their representatives (Article 35(9)), and the document should record their views or your reason for not seeking them. Where necessary, and at least when the risk represented by the processing changes, you must review whether the processing is carried out in accordance with the DPIA (Article 35(11)), which in practice means setting a review date and the events that would trigger an earlier review.

Free download

See what a DPIA actually looks like

A redacted sample of the DPIA structure we use for an AI chatbot or similar AI system, section by section, so you can see the shape of one before you write yours.

For anyone who has worked out they need a DPIA and does not want to start from a blank page.

  • ·All seven sections, from system summary through risk assessment to residual risk and sign-off
  • ·The roles section: the controller and processor map, lawful basis by processing purpose, and Article 9 or child-data issues
  • ·The data flow and transfer map: entry points, storage, model providers, cross-border transfers, DPAs and SCCs

Your email is used to deliver the PDF and (if you opt in) the newsletter. No spam. Privacy policy.

The steps in practice

A DPIA is easier to write in a fixed order, because each step depends on the one before it.

  1. Screen. Check the processing against Article 35(3), the nine criteria and the DPC's list, and record which apply and why.
  2. Describe the processing. What personal data, about whom, from where, for which purposes, shared with which suppliers or recipients, stored where and for how long. A table of the data flows makes the later steps much clearer.
  3. Identify the lawful basis for each purpose, and the Article 9 condition for any special category data. Where you rely on legitimate interests, weigh the interest against the people's rights separately for each purpose.
  4. Assess necessity and proportionality. Could the purpose be achieved with less data, less often, or in a less intrusive way?
  5. Consult. Seek your DPO's advice, and seek the views of the people affected or their representatives where appropriate, recording the reason if you do not.
  6. Assess the risks to people. For each risk, describe what could go wrong in the processing and the harm it could cause to individuals, then score its likelihood and severity.
  7. Decide the measures, and score each risk again assuming only the measures you have committed to take.
  8. Record the outcome. The residual risk, the decisions taken, who owns each action and by when, whether the DPC must be consulted, and the review date.

Consulting the DPC

Prior consultation is required where the DPIA indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate it (Article 36(1)). The European guidelines explain that this means consultation is required whenever the controller "cannot find sufficient measures to reduce the risks to an acceptable level (i.e. the residual risks are still high)". A risk that is high before your measures but medium or low after them does not on its own require consultation.

The request to the DPC must include the information listed in Article 36(3), including the DPIA itself, the purposes and means of the processing, the measures and safeguards, and the contact details of any DPO. Where the DPC considers that the intended processing would infringe the GDPR, it must give written advice within up to eight weeks of receiving the request, which may be extended by six weeks for complex processing; the DPC tells the controller of any extension, with the reasons, within one month of receiving the request, and the periods may be suspended until it has obtained information it has requested (Article 36(2)). The DPC's response, or the passing of those periods, is not an approval of the processing; the decision whether and how to proceed remains the controller's.

AI systems

Where the project uses an AI system, the DPIA should also cover the system and its supplier, whether your data is used to train the supplier's models, any decisions made about people by automated means, accuracy and bias testing, and human oversight. An organisation established in Ireland that deploys an AI system is generally within the scope of the EU AI Act, subject to the Act's own exclusions. The Act's transparency duties in Article 50 apply from 2 August 2026, although providers whose generative systems were on the market before that date have until 2 December 2026 to meet the marking duty in Article 50(2). The duties for high-risk systems listed in Annex III, such as those used in recruitment or to evaluate workers, apply from 2 December 2027 under Regulation (EU) 2026/1744; for high-risk systems already placed on the market or put into service before that date, Article 111(2) provides that the Act applies to their operators only if the systems are subject to significant changes in their designs from then on, without prejudice to the prohibited practices in Article 5, and providers and deployers of high-risk systems intended to be used by public authorities must take the necessary steps to comply by 2 August 2030. Systems covered by Article 111(1) follow their own rule. Those duties apply in addition to the DPIA rather than replacing it, and a DPIA for an AI system can record which of them apply.

A worked example

A parcel delivery company in Limerick (a fictional example) is fitting telematics to its 40 vans. The supplier's system records each van's location every 30 seconds while the ignition is on and gives each driver a weekly efficiency score, which the company is considering using in the quarterly bonus. Two vans were fitted last week as a trial, and the drivers have not yet been told.

Screening finds several criteria at once: systematic monitoring of location, evaluation or scoring, and vulnerable data subjects (employees). Together, the continuous location tracking, the scoring of individual drivers and the employment relationship indicate that the processing is likely to result in a high risk, and the processing falls within item 4 of the DPC's list, systematically monitoring individuals' location or behaviour, so a DPIA is mandatory.

Because the trial is already running, the assessment also has to deal with what has happened so far. The two drivers in the trial have not been given the information Article 13 requires, which should have been provided when their data was first collected, so they need to be told now rather than at go-live. The assessment recommends pausing the trial tracking until the drivers have been given that information and the DPIA has set the conditions on which tracking may resume. Whether location data from outside working hours has already been collected needs to be checked with the supplier, and if it has, its deletion arranged. Carrying out the DPIA now does not cure the fact that the trial started without one or without the drivers being informed; the document records that history as well as the plan.

The risks include drivers being tracked outside working hours, a score that may be inaccurate or biased being used in pay decisions, and drivers not knowing that they are monitored. Each risk is scored twice: as it stands now, with the trial running as it is, and as it would be once the safeguards are in place. The proposed measures, which count only once the company commits to them, include tracking only during working hours, telling every driver in writing, testing the score before it affects pay, and keeping a manager's review before any decision based on it. The outcome records the company's decisions, the points still to resolve with an owner and a date for each, and whether any risk remains high after the measures, which would require consulting the DPC.

Templates

The DPC does not require a particular format, provided the assessment contains what Article 35(7) requires. The European Data Protection Board adopted a DPIA template in March 2026 for public consultation; it is voluntary, and the EDPB says the supervisory authorities will adopt it as their standard or as a meta-template once it is finalised. Our article on the EDPB's DPIA template explains what each of its sections asks for.

The method our DPIA tool follows sets out how it applies the DPC's list and the European criteria, records the screening and scores risks. A review of a finished assessment by a CIPP/E certified privacy professional is available if you want it checked before you rely on it.

Sources

Regulation (EU) 2016/679, Articles 35 and 36; Article 29 Working Party, Guidelines on DPIA, WP248 rev.01, endorsed by the EDPB; Data Protection Commission, "List of Types of Data Processing Operations which require a Data Protection Impact Assessment", 15 November 2018 (rev), retrieved 3 November 2026; Regulation (EU) 2024/1689 (the AI Act), Articles 50 and 113, as amended by Regulation (EU) 2026/1744; EDPB, Template [2026] for DPIA, version 1.0, adopted 10 March 2026 for public consultation.

Free download

See what a DPIA actually looks like

A redacted sample of the DPIA structure we use for an AI chatbot or similar AI system, section by section, so you can see the shape of one before you write yours.

For anyone who has worked out they need a DPIA and does not want to start from a blank page.

  • ·All seven sections, from system summary through risk assessment to residual risk and sign-off
  • ·The roles section: the controller and processor map, lawful basis by processing purpose, and Article 9 or child-data issues
  • ·The data flow and transfer map: entry points, storage, model providers, cross-border transfers, DPAs and SCCs

Your email is used to deliver the PDF and (if you opt in) the newsletter. No spam. Privacy policy.

Frequently Asked Questions

When is a DPIA required in Ireland?

Under Article 35 of the GDPR, a DPIA is required before processing that is likely to result in a high risk to people's rights and freedoms, and in particular in the three cases in Article 35(3). The Data Protection Commission has published a list of ten types of processing for which a DPIA is mandatory where a documented screening indicates a likely high risk, and the European guidelines (WP248) give nine criteria, two or more of which usually mean a DPIA is needed.

What must a DPIA contain?

Article 35(7) requires at least a systematic description of the processing and its purposes, an assessment of necessity and proportionality, an assessment of the risks to the people affected, and the measures to address those risks, including safeguards, security measures and mechanisms to protect personal data and demonstrate compliance, taking into account the rights and legitimate interests of the people affected and others concerned. Where a data protection officer is designated, their advice must be sought; the controller must seek the views of the people affected or their representatives where appropriate; and, where necessary and at least when the risk changes, the controller must review whether the processing follows the DPIA.

When do I have to consult the Data Protection Commission?

Where the DPIA shows that the processing would still result in a high risk after the measures the controller will take, the controller must consult the DPC before the processing begins (Article 36(1)). Where the DPC considers that the processing would infringe the GDPR, it must give written advice within up to eight weeks, which may be extended by six weeks for complex processing. The DPC tells the controller of any extension, with the reasons, within one month of receiving the request, and the periods may be suspended until it has information it has requested.

Is there a template the DPC expects?

The DPC does not require a particular format. The European Data Protection Board adopted a DPIA template for public consultation in March 2026; it is voluntary, and the EDPB says the authorities will adopt it as their standard or as a meta-template once it is finalised.

Start with a £500 scoping review

If you need GDPR documentation, AI Act work, or a compliant AI build, the first step is a written scoping review. You get a written report you can act on.

DPIAIrelandGDPRData Protection CommissionAI complianceEU AI Act