EU GDPR
Map your processing and put data rights, safeguards and breach decisions into daily operations.
ISO/IEC 27701:2025 · Privacy information management systems
Build and audit a privacy information management system for controller and processor activities.
Organizations accountable for processing personally identifiable information and seeking a structured privacy management system.
A privacy information management system and, if pursued, an external certification decision.
Confirm the current certification scheme and transition rules with your provider if you already hold a certificate to a prior edition.
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Fill this in with your sponsor and send it to the people who own the work.
ISO 27701 kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Define the PIMS and privacy roles · Privacy lead + leadership [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define the PIMS and privacy roles | Privacy lead + leadership | Before assessment | Set a start date | PIMS scope; Role map; Obligations register | Open |
| Assess privacy risks and apply controls | Privacy + service owners | Before audit | Set a start date | Privacy risk register; Controls matrix; Processing records | Open |
| Operate the system and correct gaps | Internal auditor + leadership | Before external review | Set a start date | Internal audit; Management review; Corrective-action register | Open |
| Assess and maintain | Certification body + privacy lead | Agreed assessment and review cycle | Set a start date | External decision; Maintenance calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Select processing activities and identify applicable PII controller and processor responsibilities, interested parties and legal obligations.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Evaluate risks to people, document control selection and establish rights, retention, transfer and supplier processes where relevant.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Evaluate operating evidence, audit the PIMS, review outcomes and address corrective actions.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Confirm scheme scope, submit evidence and manage findings. Reassess changes in processing and applicable law.
Fictional details. Use the same fields with evidence from your work.
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
Fictional details. Use the same fields with evidence from your work.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.