A privacy impact assessment consultant working on contract maps how a project collects, uses, discloses, stores and destroys personal information, tests whether that processing is necessary and proportionate, and records the risks and the mitigations the organization agrees to. In Canada the work is driven mainly by Quebec Law 25, Ontario PHIPA and other health statutes, and by good practice under PIPEDA.
Where PIA work comes from in Canada
The legal trigger for a PIA varies by statute and by sector, and getting it right is the first thing a client will test you on. A short version of the ones that come up most in private-sector contract work:
- Quebec Law 25. The amended Quebec private sector act requires an enterprise to conduct a PIA for any project to acquire, develop or overhaul an information system or electronic service delivery that involves personal information. It also requires a PIA before communicating personal information outside Quebec, and that assessment has to consider the sensitivity of the information, the purposes, the protection measures including contractual ones, and the legal framework where the information is going. The communication can proceed only if the assessment shows the information would receive adequate protection, and it has to be backed by a written agreement. The act also says the assessment should be proportionate to the sensitivity, purpose, amount, distribution and medium of the information, and that the person in charge of the protection of personal information is consulted from the outset of the project.
- Health information in Ontario. PHIPA applies to health information custodians and the agents and service providers who handle personal health information for them. Custodians commonly run PIAs on new systems as expected practice, the Information and Privacy Commissioner of Ontario publishes PIA guidance, and the PHIPA regulation requires health information network providers to assess their services for privacy and security risk and give the results to the custodians they serve. Health tech vendors selling into hospitals and clinics are regularly asked for a PIA, or for the input to one, as part of procurement.
- Health information in Alberta. Alberta's Health Information Act requires custodians to prepare a PIA and submit it to the Information and Privacy Commissioner before implementing proposed administrative practices or information systems that involve health information.
- PIPEDA. PIPEDA has no general requirement for private-sector organizations to conduct PIAs. The Office of the Privacy Commissioner of Canada recommends them, and a PIA is a practical way to show accountability, purpose limitation and appropriate safeguards when the OPC or a customer asks. Federal government institutions are a different story: PIAs are required under Treasury Board policy.
Public bodies in several provinces have their own PIA obligations under their access and privacy statutes, which matters if you work with vendors selling into government. For the broader shape of a privacy consulting practice under these laws, including retainers and the outsourced privacy officer role, see our post on working as an independent privacy consultant under PIPEDA and Law 25. This post stays on the PIA itself.
How a contractor runs a PIA
A PIA is a structured conversation that ends in a document.
1. Confirm the trigger and the scope. Write down why the PIA is being done (a new system, an overhaul, a communication outside Quebec, a customer's procurement requirement) and what is in scope: which system, which processing, which populations of individuals. A PIA that tries to cover the whole company is a privacy program review, not a PIA. Confirm who the privacy officer is and when they will be involved, since under Law 25 that consultation starts at the beginning of the project, not at sign-off.
2. Map the data flows. This is most of the work. For each category of personal information, record where it comes from, the purpose, the legal basis or consent relied on, who inside the organization accesses it, which service providers receive it and where they host it, how long it is kept and how it is destroyed. Draw the flow; it usually reveals a vendor or a copy of the data nobody had mentioned.
3. Test necessity and proportionality. For each element of personal information, ask whether the project needs it for the stated purpose, whether less identifying data would do, and whether the intrusion is proportionate to the benefit. Law 25 also has specific rules on things like technology that can identify, locate or profile a person, and on privacy by default settings for technological products and services offered to the public. Flag where those apply.
4. Identify risks and mitigations. Describe each risk in terms of what could happen to individuals, not just to the organization: inappropriate access, use beyond the original purpose, re-identification, loss through a breach, unexpected disclosure to a service provider, data kept too long. Rate likelihood and impact on a stated scale. For each, propose a mitigation the project can actually implement: a contractual clause with a vendor, a role-based access change, a shorter retention period, de-identification, a consent change, a notice update.
5. Record decisions and sign-off. The organization decides which mitigations it accepts, who owns each, and when they will be in place. Residual risks are recorded and accepted by someone with authority. The privacy officer signs off. Your name goes on the document as the assessor, not as the decision-maker. If the project changes materially, the PIA is updated, so leave the client with a version they can maintain without you.
The line with legal advice
PIA work sits right next to legal advice, and a contractor who is not a lawyer needs to know where the line is. You can describe what a statute requires in general terms, map processing against it, and identify where a practice looks inconsistent with it. You should not give a legal opinion on whether a specific practice is lawful, draft binding contract terms as if you were counsel, or tell a client that a cross-border transfer is definitely permitted. When those questions come up, and they will, write them down as questions for counsel and keep going.
If you are a lawyer, be explicit about which hat you are wearing on the engagement, since your professional obligations follow you either way.
How a Canadian PIA compares with a GDPR DPIA
Clients with European customers often ask whether one assessment can serve both. Under GDPR Article 35, a data protection impact assessment is required where processing is likely to result in a high risk to individuals, with examples such as large-scale processing of special categories of data and systematic monitoring of publicly accessible areas on a large scale. If the DPIA shows high residual risk the controller cannot mitigate, Article 36 requires prior consultation with the supervisory authority.
The differences that matter in practice:
- Trigger. GDPR uses a high-risk threshold. Law 25's system project trigger does not, though the assessment itself is proportionate.
- Cross-border. Law 25 has its own PIA requirement for communication outside Quebec. Under GDPR, transfers are handled through adequacy decisions and safeguards such as standard contractual clauses, with a transfer impact assessment often done alongside.
- Content. Both expect a description of the processing, an assessment of necessity and proportionality, the risks to individuals and the measures to address them. A well-built template can cover both, with a section for each regime's specific points.
Our buyer guide on GDPR readiness assessments and the comparison of Quebec Law 25 and PIPEDA show how clients think about these regimes before they hire anyone.
Who does well at contract PIA work
The best PIA contractors combine three things: they understand the law well enough to know which questions to ask, they understand systems well enough to follow data through an architecture diagram and a vendor list, and they write clearly enough that a project manager and a privacy officer both understand the result. People come into it from privacy office roles, from GRC and security assessment work, from health information management, and from law.
The CIPP/C from the IAPP is the most recognised Canadian privacy credential, and the CIPM and CIPT are useful companions. No PIA work in Canada legally requires a particular certification. A redacted sample PIA, or one written against a fictional project, does more for a firm deciding whether to engage you than a list of courses.
Practical setup is similar to other compliance contract work: professional liability insurance, a clean and encrypted work machine, a clear retention rule for client data, and GST/HST registration once you pass the small supplier threshold.
Where the TrazTech Associate Network fits
We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network is how TrazTech brings independent practitioners into client work, and privacy, covering PIPEDA, Law 25, PHIPA and GDPR, is one of its practices. Other practices include compliance readiness, security leadership, cloud, offensive security, AI governance and audit, and every role is listed on our careers page.
Associates are independent contractors working remotely from Canada or the US, part-time or full-time, with no exclusivity. You need at least five hours a week, and if you are employed, your employer has to allow side work. There is no experience minimum. Newer associates are paired with a paid senior mentor.
Applying takes about five minutes. A verified credential such as the CIPP/C lets you skip the simulated assessment. Otherwise you complete a simulated client engagement of about three hours of work, with 72 hours to submit, followed by a selection call and portal setup with the agreement signed online.
Work is offered as fixed-scope work orders: you see the scope and the fee before you accept, you can decline, and the fee is fixed per milestone and agreed before work starts. Payment goes out every Friday by Interac e-Transfer or against your own invoice in CAD or USD. Coverage checklists keep the work consistent, larger engagements run as teams with a Lead, and a TrazTech Principal reviews and signs off every deliverable before the client sees it. You also get a TrazTech email address, a verified credential for LinkedIn, paid mentoring and Lead reviews, referral bonuses, and a path from Associate to Senior, Lead and the core team. Work follows client demand in your practice, so approval does not guarantee a volume of work.
Common questions about privacy impact assessment consulting
When is a privacy impact assessment required in Canada?
It depends on the statute. Quebec Law 25 requires one for projects involving information systems or electronic service delivery with personal information, and before communicating personal information outside Quebec. Alberta's Health Information Act requires custodians to submit PIAs. PIPEDA has no general requirement for the private sector, though the OPC recommends them.
Can a non-lawyer conduct a privacy impact assessment?
Yes. PIAs are routinely done by privacy, security and GRC practitioners. The assessor maps the processing and identifies risks; legal interpretations of specific practices should be referred to counsel and recorded as open questions.
Who signs off a PIA?
The organization, not the consultant. Typically the privacy officer and the project or business owner accept the mitigations and residual risks. The consultant is named as the assessor.
Is a Law 25 PIA the same as a GDPR DPIA?
They overlap heavily in content but differ in trigger. GDPR requires a DPIA for likely high-risk processing, while Law 25 ties the requirement to system projects and communication outside Quebec. One well-structured document can often serve both.
What certification helps with PIA contract work?
The CIPP/C is the most recognised Canadian privacy credential, with the CIPM and CIPT as useful additions. None is legally required, and a strong sample PIA often counts for more.
Take scoped PIA and privacy work as an independent associate. Every work order shows the scope and fee before you accept, and a verified CIPP/C skips the simulated assessment.
Apply to the networkSee the role