A working tool for privacy officers and project leads

PIA builder: the privacy impact assessment your law expects, ready to fill in

Pick your law. See whether an assessment is required and where it goes, screen your project in a few questions, then work through the template your regulator publishes, with its guidance beside every question. Take it away as a Word file, or take the blank template. For 142 access and privacy laws, 60 with their regulator's own format.

Runs in your browser. Nothing you type is sent anywhere. A draft is kept on this computer only if you ask for that below.

Choose a law to load its template.

Templates exported from AccessPoint's jurisdiction packs (2026-11-18), which follow each regulator's published guidance. A starting point built from public information about the legislation, not legal advice: confirm what your law and your own policy require, and have the assessment reviewed before it is approved.

What is a privacy impact assessment?

A privacy impact assessment, or PIA, is a written review of a project that handles personal information, done before the project starts or changes. It sets out what information is involved and where it goes, tests each collection, use and disclosure against the law, lists the risks to the people the information is about, and records what will be done about each. Under the GDPR and the UK GDPR the same exercise is a data protection impact assessment, or DPIA. In Quebec it is an assessment of privacy-related factors.

The value is in the timing. A PIA done while the design can still change removes a field from a form, moves a server, or adds a clause to a contract. One done after launch can only describe the risk.

How to do a privacy impact assessment

  1. Screen the project. Before design is fixed, answer the screening questions: is personal information involved, is anything new or changed, is it sensitive or about many people. Keep the answer on file either way.
  2. Describe the project and its information. Say what the project does and why, then list each kind of personal information: about whom, from whom, used for what, kept where, seen by whom and for how long.
  3. Map the flows. Set out each movement of personal information: who collects it, where it is stored, who it is disclosed to and how it gets there, including vendors and other organizations.
  4. Test it against the law. For each collection, use and disclosure, name the legal authority, check that the information is needed, and check notice, consent, accuracy, safeguards, retention and people's rights.
  5. List the risks and what will be done. Write each risk down with how likely and how serious it is, the step that will reduce it, who owns that step and by when.
  6. Get it signed, file it and keep it current. Have the privacy officer review it and the accountable decision-maker approve it, send it to the regulator where the law says so, and review it when the project changes.

Where a PIA is required by law

Laws under which a privacy impact assessment is required, always or in some cases, with the provision and where the assessment goes. Checked against the legislation and the regulators' guidance in November 2026.

LawRequired?UnderWhere it goesOpen in the builder
Canada
CACanada — Federal Required TBS Directive on Privacy Practices (October 2024), s. 4.2.11 to 4.2.15 and Appendix C The Treasury Board Secretariat and the Office of the Privacy Commissioner receive every approved assessment, and a summary is published. Build
BCBritish Columbia Required FOIPPA s. 69(5) and (5.3); PIA Directions 1-21 and 2-21 Ministries send it to the minister responsible for the Act while the initiative is being developed. Other public bodies keep it. For a common or integrated program the Commissioner is notified during development and given the assessment on request. Build
ABAlberta Required Protection of Privacy Act, s. 26(1); Alta. Reg. 143/2025, s. 7 The Commissioner, where a listed factor applies: highly sensitive information, a significant share of the population, data matching, a common or integrated program, innovative technology, or the Commissioner asks. Otherwise it is kept, and given to the Commissioner within 30 business days of a request. Build
ONOntario — FIPPA (provincial) Required FIPPA s. 38(3) to (6), in force 1 July 2025 Not filed. The Information and Privacy Commissioner can ask for a copy. Build
ONOntario — MFIPPA (municipal) Required From 1 January 2027: MFIPPA s. 28(3) to (6) Not filed. The Information and Privacy Commissioner can ask for a copy. Build
QCQuébec Required Act respecting Access, ss. 63.5, 64, 67.2.1, 68 and 70.1 Not filed. The body's access and privacy committee is consulted from the start of a system project. An agreement to collect for another body is sent to the Commission d'accès à l'information. Build
NSNova Scotia Required From 1 April 2027: S.N.S. 2025, c. 13, s. 53; N.S. Reg. 254/2026, ss. 24 to 27 Not filed with the Commissioner. Build
NLNewfoundland & Labrador Required ATIPPA, 2015, s. 72 (departments of the executive government) The minister responsible for the Act, for review and comment, during development. For a common or integrated program the Commissioner is notified early and receives the assessment. Build
YTYukon Required ATIPP Act, s. 11 (ministerial bodies) The access and privacy officer, a reasonable time before the start. For a specialized service or a data-linking activity, the Commissioner as well, who wants the office's checklist with it. Build
NTNorthwest Territories Required ATIPP Act, s. 42.1 The head of the public body, for review and comment. For a common or integrated program, the Information and Privacy Commissioner during development. Build
NUNunavut Required ATIPP Act, s. 42.1 (municipalities excluded) The Minister responsible for the Act, for review and comment. Build
ONOntario — PHIPA In some cases O. Reg. 329/04, s. 6(3); PHIPA ss. 55.3 and 55.25 The provider gives the written results to each custodian. Not filed with the Commissioner. Build
ABAlberta — HIA Required Health Information Act, ss. 64 and 64.1 The Commissioner, for review and comment, before implementation. The office closes its review with a letter of comments; it does not accept or approve the assessment. Build
NBNew Brunswick — PHIPAA Required PHIPAA s. 56(1), for custodians that are public bodies Not filed. The Ombud may review it. Build
PEPrince Edward Island — HIA Required Health Information Act, s. 25(1) The Commissioner, for review and comment, before it starts. Build
YTYukon — HIPMA Required Health Information General Regulation, s. 15 (the Department of Health and Social Services and the Yukon Hospital Corporation) The Commissioner, before the system starts or changes, with the office's checklist. Build
NTNorthwest Territories — HIA Required Health Information Act, s. 89(2), for public custodians A copy goes to the Information and Privacy Commissioner, who may comment. Build
QCQuébec — Renseignements de santé Required Act respecting health and social services information, ss. 44, 45, 73, 78, 83 and 106 Not filed with the Commission d'accès à l'information. A researcher's assessment goes with the request to the body's highest authority. Build
United States
USUnited States — Federal Required E-Government Act of 2002, s. 208; OMB M-03-22; OMB Circular A-130 Published, unless security or classification prevents it, and given to OMB with the funding request. Build
CACalifornia Required State Administrative Manual 5310.8 (state entities only) Kept by the organization Build
WAWashington In some cases WaTech policy DATA-03, s. 6 (state agencies only) The state Office of Privacy and Data Protection confirms whether a full assessment is needed. Build
PAPennsylvania Required Pennsylvania Office of Administration Privacy Policy, s. 4.2 (agencies under the Governor) Results are available to the Chief Privacy Officer on request. Build
OHOhio Required Ohio Revised Code 1347.15(B)(7) and (8) (state agencies) The point of contact works with the state's chief privacy officer. Build
MDMaryland — Public Information Act In some cases Maryland DoIT policy MD-POL-205-01, s. 200.1.2 (state agencies) The State Chief Privacy Officer directs when one is needed. Build
INIndiana — APRA In some cases State of Indiana Policy: Information Privacy, s. 8.2.1 (state agencies) Kept by the agency. The State Chief Privacy Officer is consulted where needed. Build
UTUtah Required Utah Admin. Code R895-8-8 (state agencies) Kept for four years. An annual privacy program report goes to the Office of Data Privacy by 31 December. Build
USUnited States — Privacy Act Required E-Government Act of 2002, s. 208; OMB M-03-22; OMB Circular A-130 Published, unless security or classification prevents it, and given to OMB with the funding request. Build
Europe
UKUnited Kingdom — FOIA In some cases UK GDPR Art. 35 The Information Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
UKUnited Kingdom — DPA / UK GDPR In some cases UK GDPR Art. 35 The Information Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
UKUnited Kingdom — EIR In some cases UK GDPR Art. 35 The Information Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
UKUnited Kingdom — DPA 2018 Part 3 In some cases Data Protection Act 2018, s. 64 The Information Commission, before processing that will form part of a filing system, where the assessment shows a high risk (s. 65). It answers within 6 weeks, which it can extend by a month. Build
UKUnited Kingdom — Access to Health Records In some cases UK GDPR Art. 35 The Information Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
SCOScotland In some cases UK GDPR Art. 35 The Information Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
IEIreland In some cases GDPR Art. 35(1) The Data Protection Commission, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
JEJersey In some cases Data Protection (Jersey) Law 2018, Art. 16 The Jersey Data Protection Authority, before the processing starts, where the assessment shows a high risk (Art. 17). It answers within 8 weeks, which it can extend by 6. Build
GGBailiwick of Guernsey In some cases Data Protection (Bailiwick of Guernsey) Law, 2017, s. 44 The Data Protection Authority, before the processing starts, where the assessment shows a high risk (s. 45). Build
IMIsle of Man In some cases Applied GDPR Art. 35 (Data Protection (Application of GDPR) Order 2018) The Information Commissioner, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
GIGibraltar In some cases Gibraltar GDPR Art. 35 The Information Commissioner (Gibraltar Regulatory Authority), before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
EUEuropean Union — GDPR In some cases GDPR Art. 35(1) Your supervisory authority, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
EUEuropean Union — Institutions (2018/1725) In some cases Regulation (EU) 2018/1725, Art. 39(1) The EDPS, before the processing starts, where a high risk remains that cannot be reduced by reasonable means (Art. 40). It answers within 8 weeks, which it can extend by 6. Build
EUEuropean Union — AI Act (deployers) In some cases Regulation (EU) 2024/1689, Art. 27 The market surveillance authority is told the results. Build
ATAustria — Informationsfreiheitsgesetz In some cases GDPR Art. 35(1) The Datenschutzbehörde, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
DEGermany In some cases GDPR Art. 35(1) The BfDI, or the Land's data protection authority, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
FRFrance In some cases GDPR Art. 35(1) The CNIL, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
NLNetherlands In some cases GDPR Art. 35(1) The Autoriteit Persoonsgegevens, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
BEBelgium — Publicité / Openbaarheid In some cases GDPR Art. 35(1) The Data Protection Authority (APD/GBA), before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
ESSpain In some cases GDPR Art. 35(1) The AEPD, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
PTPortugal — LADA In some cases GDPR Art. 35(1) The CNPD, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
ITItaly In some cases GDPR Art. 35(1) The Garante, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
PLPoland — UDIP In some cases GDPR Art. 35(1) The President of the UODO, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
SESweden In some cases GDPR Art. 35(1) The IMY, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
FIFinland In some cases GDPR Art. 35(1) The Data Protection Ombudsman, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
DKDenmark — Offentlighedsloven In some cases GDPR Art. 35(1) Datatilsynet, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
NONorway — Offentleglova In some cases GDPR Art. 35(1) Datatilsynet, before the processing starts, where the assessment shows a high risk that your measures do not reduce (Art. 36). It answers within 8 weeks, which it can extend by 6. Build
CHSwitzerland In some cases Federal Act on Data Protection, art. 22 The FDPIC, before the processing starts, where a high risk remains despite the measures planned (art. 23). It answers within 2 months, which it can extend by 1. Federal bodies cannot use the adviser alternative open to private controllers. Build
Rest of World
AUAustralia — Federal In some cases Privacy (Australian Government Agencies – Governance) APP Code 2017, s. 12 The agency keeps a register of its assessments and publishes the register. The Commissioner gets the register and the assessments on request. Publishing the assessment itself is optional. Build
WAAustralia — Western Australia In some cases Privacy and Responsible Information Sharing Act 2024, s. 79, in force 1 July 2026 A copy goes to the Information Commissioner on request, or within the time set when the Commissioner directs an assessment. Build
NZNew Zealand — Biometric Processing Privacy Code Required Biometric Processing Privacy Code 2025, in force 3 November 2025 Kept by the organization Build
INIndia In some cases From 13 May 2027: DPDP Act 2023, s. 10(2)(c); DPDP Rules 2025, r. 13 The Data Protection Board receives a report of the significant observations, sent by the person who carried out the assessment. Build
ZASouth Africa Required POPIA Regulations, reg. 4(1)(b), as amended 17 April 2025 Kept by the organization Build
BRBrazil In some cases LGPD, arts. 5 XVII, 10 §3 and 38 The ANPD, when it asks. Build

Where AccessPoint fits

The builder gives you the template and a Word file. AccessPoint runs the assessment as a record: the screening decides whether one is opened, each answer is saved against the project, risks carry an owner and a due date, the privacy officer's advice and the approval are captured with their dates, and the assessment is brought back for review on schedule or when the project changes. The templates are the same ones, kept current with each regulator's guidance.

Questions about PIAs

What is a privacy impact assessment?

A privacy impact assessment (PIA) is a written review of a project, system or program that handles personal information, done before it starts or changes. It describes what personal information is involved and where it goes, checks each collection, use and disclosure against the law, lists the privacy risks and says what will be done about each. Under the GDPR and UK GDPR the same exercise is called a data protection impact assessment (DPIA).

When is a PIA required?

It depends on the law. Some laws require one before any new or significantly changed program or system that handles personal information; the GDPR requires a DPIA where processing is likely to result in a high risk; some laws require one only for particular activities, such as linking data sets; and many set no requirement and leave it to policy. The builder shows what the law you pick requires, with the section, and whether the assessment has to be sent to a regulator.

How do I know if my project needs one?

Screen it. A screening asks a short set of yes-or-no questions: does the project collect, use or disclose personal information, is that new or changing, is the information sensitive, is a vendor or new technology involved. The builder uses the screening questions from the regulator's own template where there is one, tells you the result, and gives you a screening record to keep, which matters most when the answer is no.

What goes into a PIA?

Most templates cover the same ground: a description of the project and its purpose; the personal information involved and how it flows; the legal authority for each collection, use and disclosure; notice and consent; safeguards and vendors; retention; how people can see and correct their information; the risks with the steps to reduce them; and sign-off. The builder follows the template your regulator publishes, section by section, with its guidance beside each question.

Is the information I type sent anywhere?

No. The page loads the template for your law and everything else happens in your browser: nothing you type is posted to a server. A draft is kept in your browser only if you tick the box asking for that, and you can save it to a file on your own computer instead and open it later.

Can I just have the blank template?

Yes. Pick your law and choose Download the blank template: you get a Word file with every section, question and piece of guidance and space for the answers, with nothing to fill in online. The filled-in version is also a Word file, so either way the document is yours to edit.

Is this legal advice?

No. The templates follow each regulator's published guidance and come from AccessPoint's jurisdiction packs, which are built from public information about each law. They are a starting point: confirm what your law and your organization's policy require, and have your privacy officer or counsel review the assessment before it is approved.

Related tools and guides

The PIA program readiness check looks at how your organization runs assessments as a whole. Guides to particular regimes: Ontario, British Columbia, Alberta, Canada's federal institutions, the GDPR, the UK and EU institutions, with the general guide to privacy impact assessments. The starter kit has a short-form assessment, a worked example and the rest of a privacy program's paperwork, and the privacy breach response planner is for the day something goes wrong.

Last reviewed: November 2026. General information for privacy practitioners, not legal advice.

© 2026 Realizer Services Inc. About Privacy Terms Hosted Terms