The Data Protection Commission (DPC), which supervises the GDPR in Ireland, publishes a Sample DPIA Template. It is a nine-page PDF with seven steps, from identifying the need for a data protection impact assessment (DPIA) to signing off the outcome, and each step lists the questions the DPC expects the assessment to answer. You can download the template from dataprotection.ie, and the same text appears at the end of the DPC's Data Protection Impact Assessments page.
The DPC describes the template as an example of how the DPIA process and its outcome can be recorded, to be read with its DPIA guidance. It is "for use as a guide only", and "the obligation is on the Data Controller to expand on areas or identify additional areas on a project-by-project basis". The DPC suggests starting it "at the commencement of any major project which involves the use of personal data or sees major changes to existing processes", and building the outcome into the project plan.
Our DPIA tool covers these topics in its own format, in a conversation, under the EU GDPR as applied in Ireland. It asks one question at a time and drafts the DPIA as you answer, and it is free to complete.
When a DPIA is required in Ireland
Article 35(1) of the GDPR requires the controller to carry out a DPIA before the processing begins where a type of processing, in particular using new technologies, and taking into account the nature, scope, context and purposes of the processing, is "likely to result in a high risk to the rights and freedoms of natural persons". A single assessment may cover a set of similar processing operations that present similar high risks.
Article 35(3) states that a DPIA is required in particular in three cases:
- a systematic and extensive evaluation of personal aspects relating to individuals which is based on automated processing, including profiling, and on which decisions are based that produce legal effects concerning the individual or similarly significantly affect them;
- processing on a large scale of special categories of data under Article 9(1), or of personal data relating to criminal convictions and offences under Article 10;
- systematic monitoring of a publicly accessible area on a large scale.
The DPC has also adopted a list under Article 35(4). It makes a DPIA mandatory for the following types of processing "where a documented screening or preliminary risk assessment indicates that the processing operation is likely to result in a high risk to the rights and freedoms of individuals":
- Using personal data on a large scale for a purpose other than the one for which it was first collected (Article 6(4)).
- Profiling vulnerable people, including children, to target marketing or online services at them.
- Using profiling, algorithmic means or special category data as an element in deciding access to services, or in a way that produces legal or similarly significant effects.
- Systematically monitoring, tracking or observing individuals' location or behaviour.
- Profiling individuals on a large scale.
- Processing biometric data to identify an individual uniquely, or to enable or allow the identification or authentication of an individual, in combination with any of the other criteria in the WP29 DPIA Guidelines.
- Processing genetic data in combination with any of the other criteria in the WP29 DPIA Guidelines.
- Obtaining personal data indirectly where the GDPR's transparency requirements are not being met, including where an exemption based on impossibility or disproportionate effort is relied on.
- Combining, linking or cross-referencing separate datasets where the linking significantly contributes to or is used for profiling or behavioural analysis of individuals, particularly where the datasets come from different sources and were processed for different purposes or by different controllers.
- Large-scale processing of personal data where the Data Protection Act 2018 requires "suitable and specific measures" to safeguard the fundamental rights and freedoms of individuals.
The DPC says this list is not exhaustive and does not affect the requirement in Article 35(3). The European guidelines give nine screening criteria. Meeting two will usually indicate that a DPIA is required, and one can be sufficient. The DPC's October 2019 guide also discusses transfers outside the EU. If two criteria apply and you conclude that the processing is unlikely to present a high risk, document your reasons in full.
Whatever the outcome, the DPC expects a controller to "assess, decide and document whether a DPIA is necessary for each proposed data processing operation". It also considers it good practice to carry out a DPIA for any major new project involving personal data, even where there is no specific indication of a likely high risk. Our guide to carrying out a DPIA in Ireland covers the screening in more detail.
The worked example used below
Each step below ends with an example entry for a fictional company, Example Fitness Ltd. It runs three gyms in Cork with about 2,400 adult members and plans to replace membership cards with fingerprint readers at the entrances, using a system hosted by a supplier acting as its processor. The example shows the level of detail each box needs. It is an illustration only, and it does not express a view on whether fingerprint entry is proportionate for a gym.
Step 1: Identify the need for a DPIA
The template asks for a broad explanation of the project's aims and the type of processing involved, and suggests referring to other documents such as the project proposal. It then asks you to "Concisely detail why you believed there to be a need for a DPIA."
Give the specific reason. If the processing falls within Article 35(3) or an item on the DPC's list, say which one. If a combination of WP248 criteria led you to the conclusion, name them. A general statement that the project involves personal data does not show how the decision was reached.
Article 35(1) also requires the assessment to be carried out before the processing begins, and the DPC's guide says that the possibility of having to update a DPIA once processing has started "is not a valid reason for postponing or not carrying out a DPIA".
Example: Example Fitness will replace membership cards with fingerprint entry at its three gyms. The system identifies each member from a fingerprint template, which is biometric data processed to identify a person uniquely. Our documented screening found that this falls within item 6 of the DPC's list, in combination with the innovative use of technology, and indicated a likely high risk, so a DPIA is required. See the project proposal dated 3 November 2026.
Step 2: Describe the processing
Step 2 has four boxes, which follow the four factors in Article 35(1): the nature, scope, context and purposes of the processing. This description is what the later steps rely on, so incomplete answers here weaken the whole assessment.
Nature. The first box asks you to outline the type of processing: how the data will be collected, used, stored and deleted, where it comes from, whether it will be shared with anyone, and whether any of the processing is of a type identified as high risk. The template notes that "A flow diagram or some other way of describing data flows may prove useful." The DPC's guide adds that you should record any new personal data the project will generate, giving the example of answers to psychometric test questions that are processed into a psychometric profile.
Scope. This box covers the types of data involved and whether any are special category data, how much data you will collect and use, how often, how long it will be retained, how many people it concerns and the geographical area covered. Give numbers wherever you have them.
Context. This box covers your relationship with the people concerned, how much control they will have, whether they are aware their data will be used in this way, whether children or other vulnerable groups are included, any existing security concerns, whether the processing is novel, the state of the technology involved, any prevailing public concerns, and whether you are part of an approved code of conduct or certification scheme. Article 35(8) requires compliance with an approved code of conduct to be taken into account in assessing the impact of the processing.
Purposes. This box covers what you want to achieve, the effect you expect the processing to have on individuals, and the benefits for you and more widely. List each purpose separately, because step 4 assesses the lawful basis and necessity for each one. Where you rely on legitimate interests, Article 35(7)(a) requires the description to include the legitimate interest pursued.
The most common gaps in step 2 are a description of the system with no account of the data, missing processors and recipients, and no retention period.
Example: Members enrol at reception, where the reader converts the fingerprint into a template stored on the supplier's hosted system. Each visit is matched against the template and the entry time is logged. Templates are deleted within 30 days of a membership ending. The data is fingerprint templates (special category data under Article 9(1)) and entry logs for about 2,400 adult members at three sites in Cork. Members are adults with a membership contract, and members who do not consent keep a card. The purposes are faster entry at peak times and preventing members from sharing cards.
Step 3: Consultation process
The template asks you to detail how and when you will seek the views of individuals, or to explain why it may not be appropriate to do so. It also asks who within your organisation needs to be involved, whether you need your processor's assistance, and whether you plan to consult information security or other technical experts.
Article 35(9) requires the controller, where appropriate, to seek the views of the people concerned or their representatives on the intended processing, without prejudice to the protection of commercial or public interests or the security of processing operations. The DPC's guide gives examples of how to do this: staff could be consulted through a trade union and customers through a survey. If your final decision differs from the views expressed, record the reasons. If you decide it is not appropriate to seek views, document the justification. The guide also says a processor involved in the processing should assist with the DPIA and provide any necessary information.
Leaving this box empty because no consultation took place is a common error. The decision not to consult, and the reason for it, belong in the record.
Example: A short survey of a sample of members before the decision is taken. Front-desk staff and the supplier's security lead are consulted, and the supplier is asked for its security documentation and its deletion process.
Step 4: Assess necessity and proportionality
The template asks whether there is a lawful basis for the processing, whether the processing actually achieves your purpose, whether there is another way to achieve the same outcome, how function creep (the gradual use of data for purposes beyond those originally intended) will be prevented, how data quality and data minimisation will be assured, what information individuals will be given, how their rights will be safeguarded, how processor compliance is arranged and how any international transfers will be protected.
Article 35(7)(b) requires an assessment of the necessity and proportionality of the processing operations in relation to the purposes. Answer the lawful basis question for each purpose listed at step 2. Where special category data is involved, Article 9(1) prohibits the processing unless one of the conditions in Article 9(2) applies, so record that condition as well. If you considered a less intrusive alternative and rejected it, explain why.
Example: For optional fingerprint entry, the gym proposes consent under Article 6(1)(a) and explicit consent under Article 9(2)(a). Members can choose card entry on the same terms and return to it at any time. Before enrolment, the gym will document how it obtains and records informed consent for each stated purpose, handles withdrawal and assesses whether fingerprint processing is proportionate. The supplier hosts the system in the EU. The gym will check support access, subprocessors and onward disclosures before recording its transfer assessment.
Free download
Get the AI API Compliance Checklist
OpenAI / Anthropic DPA setup, zero-retention config, and the documentation a procurement or DPIA review will ask for. Worked example included.
Built for engineers implementing AI and the founders or compliance leads responsible for signing it off.
- ·DPA setup steps for OpenAI and Anthropic API accounts
- ·Zero-retention configuration: when it applies, what it changes, how to evidence it
- ·Retention and logging questions to answer before launch
- ·Audit documentation pack a procurement reviewer will accept
Your email is used to deliver the PDF and (if you opt in) the newsletter. No spam. Privacy policy.
Step 5: Identify and assess risks
The template sets out the risk assessment as a grid:
| Describe the source of risk and nature of potential impact on individuals: where appropriate, include associated compliance and corporate risks. | Likelihood of harm | Severity of harm | Overall risk |
|---|---|---|---|
| Remote, possible or probable | Minimal, significant or severe | Low, medium or high |
The DPC's guide says that "The focus of a DPIA should be on potential harm to the rights or freedoms of data subjects, whether it is physical, material, or non-material." The template allows you to add compliance and corporate risks where appropriate, alongside the assessment of harm to individuals.
The template does not define remote, possible and probable, or say how likelihood and severity combine into the overall rating. Record the reasons for each score so that a reviewer can follow them. The guide says a DPIA must consider both the likelihood and the severity of any impact on individuals, and that severity depends on the sensitivity of the data, the number of people likely to be affected and how they might be affected. It also gives an indicative list of risks to consider, including inappropriate internal disclosure, loss of equipment, hacking, anonymisation that turns out to be ineffective, data used for purposes people did not expect, merged datasets, data kept longer than required, unnecessary data collected, and transfers to countries with inadequate data protection regimes. The guide suggests keeping these in a data protection risk register that is updated as the project progresses.
Example:
| Source of risk and impact on individuals | Likelihood | Severity | Overall |
|---|---|---|---|
| A breach at the supplier exposes fingerprint templates. A fingerprint cannot be changed in the way a password can, so the exposure would be lasting. | Possible | Severe | High |
| Entry logs are kept after a membership ends and used to contact former members. | Possible | Minimal | Low |
Step 6: Identify measures to reduce risk
The template asks you to "Identify additional measures you could take to reduce or eliminate risks identified as medium or high risk in Step 5", using this table:
| Risk | Options to reduce or eliminate risk: explain how these measures will reduce the specific risk that you have identified | Effect on risk | Residual risk | Measure approved |
|---|---|---|---|---|
| Eliminated, reduced or accepted | Low, medium or high | Yes/no |
The DPC's guide gives examples of measures: deciding not to collect particular types of data, strict retention periods, reviewing physical and IT security, training, protocols for handling personal data, anonymisation or pseudonymisation, informing individuals fully, providing a contact point for concerns, selecting experienced processors and putting legal arrangements in place, and not proceeding with an element of the project whose risks cannot be justified. It says to weigh the costs and benefits of each measure, and that risks which cannot be eliminated or reduced can be accepted if they are proportionate to the outcomes of the project. Record any decision to accept a risk.
The "Measure approved" column keeps proposed measures apart from those the organisation has agreed to implement. Base a residual score on approved measures, and mark a score as provisional where it depends on something a supplier has not yet confirmed.
Example: Risk: a breach at the supplier exposes fingerprint templates. Options: templates stored encrypted, supplier staff access restricted, deletion within 30 days of a membership ending, and contract terms requiring security measures and prompt notice of any breach. Effect: reduced. Residual risk: medium. Approved: yes.
Step 7: Sign off and record outcomes
The final table records who approved the outcome and what the data protection officer (DPO) advised. Its rows and notes are:
| Item | Notes |
|---|---|
| Measures approved by: | Integrate actions back into project plan, with date and responsibility for completion |
| Residual risks approved by: | If accepting any residual high risk, consult the DPC before going ahead |
| DPO advice provided: | DPO should advise on compliance and whether processing can proceed |
| Summary of DPO advice: | |
| DPO advice accepted by or overruled by: | If overruled, you must explain your reasons |
| Comments | |
| Consultation responses reviewed by: | If your decision departs from individuals’ views, you must explain your reasons |
| Comments: | |
| This DPIA will be kept under review by: | The DPO should also review ongoing compliance with DPIA |
DPO advice. Article 35(2) requires the controller to seek the advice of the DPO, where one is designated, when carrying out a DPIA, and the DPC's guide says the advice and the decisions taken should be documented. Article 37(1) sets out when a controller or processor must designate a DPO. If you have not designated a DPO, record that in the DPO rows.
Prior consultation with the DPC. Article 36(1) requires the controller to consult the DPC before processing where a DPIA indicates that the processing "would result in a high risk in the absence of measures taken by the controller to mitigate the risk". The DPC's guide states: "If the DPIA suggests that any identified risks cannot be managed and the residual risk remains high, you must consult with the Data Protection Commission before moving forward with the project." If the measures reduce the risk so that no high residual risk remains, Article 36(1) does not require prior consultation. If any residual risk remains high, the controller must consult the DPC before starting the processing.
When you consult, Article 36(3) requires you to provide, where applicable, the respective responsibilities of the controller, any joint controllers and the processors involved; the purposes and means of the intended processing; the measures and safeguards to protect the rights and freedoms of the people concerned; where applicable, the contact details of your DPO; the DPIA itself; and any other information the DPC requests. If the DPC considers that the intended processing would infringe the GDPR, in particular because the risk has been insufficiently identified or mitigated, Article 36(2) requires it to give written advice to the controller and, where applicable, the processor within eight weeks of receiving the request, and it may use its powers under Article 58. That period may be extended by six weeks for complex processing, in which case the DPC must notify the controller and, where applicable, the processor of the extension and its reasons within one month of receiving the request. The periods may be suspended until the DPC has obtained information it has requested.
Sign-off and the record. The DPC's guide says that a DPIA does not necessarily require a formal sign-off process, although your organisation may require one, particularly where the DPIA recommends significant changes to the project or accepting significant risks. It also states: "There is no requirement to produce a final DPIA report but it is good practice to do so." If the risks cannot be mitigated consistently with the project's goals and it would not be proportionate to accept them, the guide says this stage should be used to re-evaluate the project, either by changing its goals or by abandoning it.
Review. Article 35(11) requires the controller, where necessary, to review whether the processing is performed in accordance with the DPIA, at least when the risk represented by the processing changes. The guide adds that you should check whether the measures are having the intended effect, and assess whether a further DPIA is needed if the project's aims change or expand. Publishing the DPIA is not mandatory, although the guide notes the benefits of publishing it or a summary of its main findings.
Example: Measures approved by the operations director on 24 November 2026, with each action entered in the project plan with an owner and a date. Residual risks (medium) approved by the managing director. Example Fitness has not designated a DPO, which is recorded in the DPO rows. Survey responses reviewed by the managing director, with reasons recorded where the decision departs from members' views. The DPIA will be reviewed in 12 months, or earlier if the supplier or the hosting arrangements change.
Checks before sign-off
Before signing off, check that step 1 names the specific reason a DPIA was required and step 2 identifies the data flows, processors, retention and the number of people affected. Step 4 should assess the lawful basis for each purpose, with an Article 9(2) condition for any special category data. Step 5 should assess harm to individuals and record the reason for each score, and step 6 should distinguish approved measures from proposals. Finally, confirm that the DPO's advice is recorded where one is designated, and that any residual high risk has led to prior consultation with the DPC before the processing begins.
Using the Janus DPIA tool for the same steps
Our DPIA tool carries out a DPIA in a conversation under UK GDPR or the EU GDPR as applied in Ireland. It asks where your organisation is established and where the people affected are, and for Ireland it applies the EU GDPR with the Data Protection Commission's list of processing that requires a DPIA. It screens first, then asks about the project one question at a time, reads any documents you add (such as a supplier's data processing agreement or a product description), and drafts each section as you answer. The finished document is in the tool's own format. The table shows where the matters covered by each step of the DPC's template appear in it.
| DPC template step | Where it appears in the tool's DPIA |
|---|---|
| 1. Identify the need for a DPIA | Screening: whether a DPIA is required, with the reasons |
| 2. Describe the processing | Description of the processing, including the data flows |
| 3. Consultation process | Consultation: the DPO's advice where one is designated, and the views of the people affected or the reason they were not sought |
| 4. Necessity and proportionality | Lawful basis and conditions for each purpose, and necessity and proportionality |
| 5. Identify and assess risks | Risk register: the scoring definitions, then each risk scored for likelihood and severity |
| 6. Measures to reduce risk | Each risk's measures, residual risk, owner and date in the risk register |
| 7. Sign off and record outcomes | Outcome and actions: the decisions you have recorded and the points still to resolve, then the documents relied on, the assumptions and a sign-off section |
The tool's method page explains that each risk is scored as remote, possible or probable for likelihood and minimal, significant or severe for severity, giving a rating of low, medium or high, which are the same scales the DPC's template uses. Where a high risk remains after the measures, the tool says so and prepares the information the regulator needs. Where the project uses AI, the document also includes a section on the AI system.
Completing the assessment is free, and you can read the whole draft on screen as it is written. If the screening shows that no DPIA is required, the screening record is also free to download. Downloading a finished DPIA as a Word document costs £39. The decisions on risk, measures and whether to go ahead are recorded as your organisation's decisions, and a review by a CIPP/E certified privacy professional is available from £120.
For organisations working under UK GDPR, our guide to completing the ICO's DPIA template covers the UK template step by step. If the project uses AI, our guide to writing a DPIA for an AI system covers the additional points to address.
Sources
All checked on 20 November 2026.
- Data Protection Commission, Sample DPIA Template (PDF, nine pages).
- Data Protection Commission, Data Protection Impact Assessments (web page).
- Data Protection Commission, Guide to Data Protection Impact Assessments (DPIAs), guidance note, October 2019, linked from the DPC's guidance page.
- Data Protection Commission, List of Types of Data Processing Operations which require a Data Protection Impact Assessment, revised 15 November 2018.
- Regulation (EU) 2016/679 (General Data Protection Regulation), Articles 9, 35 and 36, on EUR-Lex.
Free download
Get the AI API Compliance Checklist
OpenAI / Anthropic DPA setup, zero-retention config, and the documentation a procurement or DPIA review will ask for. Worked example included.
Built for engineers implementing AI and the founders or compliance leads responsible for signing it off.
- ·DPA setup steps for OpenAI and Anthropic API accounts
- ·Zero-retention configuration: when it applies, what it changes, how to evidence it
- ·Retention and logging questions to answer before launch
- ·Audit documentation pack a procurement reviewer will accept
Your email is used to deliver the PDF and (if you opt in) the newsletter. No spam. Privacy policy.
Frequently Asked Questions
How do I carry out a data protection impact assessment in Ireland?
Start by screening the planned processing and recording the result. Under Article 35(1) of the GDPR, a DPIA is required before processing where a type of processing, in particular using new technologies, and taking into account the nature, scope, context and purposes of the processing, is likely to result in a high risk to the rights and freedoms of individuals. It is required in particular in the three cases in Article 35(3), and the Data Protection Commission's Article 35(4) list makes it mandatory for ten further types of processing where a documented screening indicates a likely high risk. If a DPIA is required, carry it out before the processing begins. The DPC's guide sets out the stages: describe the information flows, identify the risks to individuals, identify measures to reduce them, sign off and record the outcome, and integrate the outcome into the project plan. The DPC's Sample DPIA Template records this in seven steps. Under Article 35(7), the assessment must contain at least a systematic description of the processing and its purposes, including where applicable the legitimate interest pursued by the controller; an assessment of the necessity and proportionality of the processing in relation to the purposes; an assessment of the risks to the rights and freedoms of 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. Seek the advice of your data protection officer where one is designated, and consult the DPC before going ahead if the DPIA shows that a high risk remains (Article 36).
Is there an official DPIA template in Ireland?
The Data Protection Commission publishes a Sample DPIA Template, a nine-page PDF on dataprotection.ie with seven steps: identify the need for a DPIA, describe the processing, consultation, necessity and proportionality, identify and assess risks, identify measures to reduce risk, and sign off and record outcomes. The DPC describes it as an example of how the DPIA process and outcome can be recorded and says it is 'for use as a guide only'. The DPC's guide explains that the GDPR does not prescribe the exact process beyond the minimum content in Article 35(7), so the controller can determine the structure and form of the DPIA. You can use the DPC's template or another format, and whichever you use, the DPC says all DPIAs should include all the elements listed in Article 35(7).
When is a DPIA mandatory in Ireland?
A DPIA is mandatory where processing is likely to result in a high risk to the rights and freedoms of individuals (Article 35(1)); in the three cases in Article 35(3), which are systematic and extensive evaluation of personal aspects based on automated processing, including profiling, on which decisions producing legal or similarly significant effects on the individual are based, large-scale processing of Article 9(1) special category data or Article 10 data relating to criminal convictions and offences, and large-scale systematic monitoring of a publicly accessible area; and for the ten types of processing on the DPC's Article 35(4) list where a documented screening or preliminary risk assessment indicates a likely high risk. The DPC's guide also applies the European DPIA guidelines (WP248), under which processing that meets at least two of the listed criteria will usually require a DPIA.
How are risks scored in the DPC's DPIA template?
Step 5 asks for the likelihood of harm (remote, possible or probable), the severity of harm (minimal, significant or severe) and the overall risk (low, medium or high). The template does not define the terms or say how the two scores combine into the overall rating, so record the reasons for each score. The DPC's guide says the assessment must consider both the likelihood and the severity of any impact on individuals, and that severity depends on the sensitivity of the data, the number of people likely to be affected and how they might be affected.
When do I have to consult the Data Protection Commission?
Article 36(1) requires the controller to consult the DPC before processing where a DPIA indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk. The DPC's guide puts it this way: if the identified risks cannot be managed and the residual risk remains high, you must consult the DPC before moving forward with the project. The template's sign-off table says the same: 'If accepting any residual high risk, consult the DPC before going ahead'. If the measures reduce the risk so that no high residual risk remains, Article 36(1) does not require prior consultation. If any residual risk remains high, the controller must consult the DPC before starting the processing.
Do I have to publish my DPIA or send it to the DPC?
The DPC's guide says it is not mandatory to publish a DPIA, although publishing it, or a summary of its main findings, can help build trust, particularly for public bodies. When you consult the DPC under Article 36, you must provide the DPIA together with the other information listed in Article 36(3). Even where consultation is not required, the DPC's guide says it may review the DPIA later in the event of an audit or investigation.
Can the Janus DPIA tool produce a DPIA for an organisation in Ireland?
Yes. The tool asks where your organisation is established and where the people affected are, and applies the EU GDPR with the Data Protection Commission's list of processing that requires a DPIA, UK GDPR with the ICO's list, or both. It screens first, then drafts the DPIA in its own format as you answer. Completing it is free, and downloading the finished DPIA as a Word document costs £39.
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.
Related Articles
GDPR
The ICO's DPIA Template (2026): How to Complete It, Step by Step
How to fill in the ICO's sample DPIA template under UK GDPR: what each of its seven steps asks for, what a complete answer contains, how to score the risks on the ICO's scales, when you must consult the ICO, and checks to help you avoid an incomplete DPIA.
GDPR
How to Carry Out a DPIA in Ireland (2026): When One Is Required and What It Must Contain
When a data protection impact assessment is required in Ireland, the Data Protection Commission's list of ten processing types, what the assessment must contain under Article 35(7), when to consult the DPC, and a worked example.
GDPR
Free DPIA Tools and Templates Compared (2026)
The free DPIA templates and tools available in 2026, from the ICO, the Irish DPC, the EDPB, the CNIL and the Spanish AEPD to online generators: what each one is written for, what it costs, whether it helps with screening and drafting, and how what you enter is handled. Each described from its publisher's own page, checked on 10 November 2026.