ISO/IEC 27701:2019 is a privacy extension to ISO/IEC 27001 and ISO/IEC 27002. It adds requirements and controls for managing personally identifiable information (PII), forming what the standard calls a Privacy Information Management System (PIMS).
Teams often ask what paperwork this involves. The standard does not hand you a fixed list of document titles. It requires documented information that is sufficient to run the system and prove it works. This article turns that into a practical working list.
Start with the foundation: your ISO 27001 documents#
ISO 27701 is built on an information security management system (ISMS). If you already have ISO 27001 documentation, you extend it rather than start again. If you do not, you need to build that base first.
The core management system documents are:
- Scope statement, extended to say which PII processing is in scope and whether you act as a PII controller, a PII processor, or both.
- Information security and privacy policy, either an updated security policy or a separate privacy policy approved by top management.
- Risk assessment and treatment methodology, updated so that privacy risks to individuals are assessed, not only risks to the organisation.
- Statement of Applicability (SoA), extended to cover the PIMS-specific controls and justify any exclusions.
- Risk treatment plan, covering both security and privacy risks.
- Objectives, competence, awareness and communication records, showing privacy is part of the management system.
- Internal audit programme and reports, management review minutes and corrective action records.
Privacy governance documents#
These show that privacy is owned and organised, not left to chance.
- Roles and responsibilities for privacy, including who is accountable for PII processing and who handles individual requests. Where your regulator or contracts expect a data protection officer or equivalent, record that appointment.
- Privacy policy for internal use, setting rules for staff on collecting, using, sharing and retaining PII.
- Legal and contractual requirements register, listing the privacy laws, regulations and customer commitments that apply to you.
- Privacy by design and by default procedure, describing how privacy is considered when new systems, products or processes are built or changed.
Core operational documents and records#
This is where ISO 27701 differs most from a plain ISO 27001 system. You need to document what PII you handle and how you treat it.
| Document or record | Purpose | Mainly relevant to |
|---|---|---|
| Record of processing activities (PII inventory) | Shows what PII you process, why, where it is stored, who receives it and how long you keep it | Controllers and processors |
| Lawful basis and purpose records | Documents why each processing activity is permitted and for what specified purpose | Controllers |
| Consent procedure and consent records | Shows how consent is obtained, evidenced and withdrawn where it is relied on | Controllers |
| Privacy notices | Tells individuals how their PII is used | Controllers |
| Individual rights request procedure and log | Defines how access, correction, deletion and other requests are received, verified, answered and tracked | Controllers, with support steps for processors |
| Privacy impact assessment (PIA/DPIA) procedure and completed assessments | Assesses higher-risk processing before it starts | Controllers, and processors where relevant |
| Retention and disposal schedule | Sets how long PII is kept and how it is securely deleted or returned | Controllers and processors |
| PII breach and incident response procedure | Extends security incident handling to cover notification of regulators, customers and individuals | Controllers and processors |
| Cross-border transfer records | Documents where PII goes and the mechanism that makes the transfer lawful | Controllers and processors |
Check which of these apply to you. A company that only processes PII on behalf of customers will not need the same consent and notice records as a company that collects data directly from consumers.
Third-party and processor documents#
Much privacy risk sits with suppliers, so the standard expects clear documented arrangements.
- Data processing agreements with every processor or sub-processor, setting out instructions, confidentiality, security measures, assistance with individual requests and breach notification.
- Customer contract terms, if you are a processor, describing the instructions you will follow and your obligations to the controller.
- Supplier assessment records, showing you checked privacy and security capability before sharing PII.
- Disclosure records, logging when PII is shared with third parties, including legally required disclosures.
- Sub-processor list, with a process for informing customers of changes where your contracts require it.
Security controls that need privacy-aware documentation#
Your existing ISO 27001 procedures usually need small additions rather than rewrites. Review these for PII-specific content:
- Access control policy, covering least-privilege access to PII and periodic access reviews.
- Information classification and handling, with PII identified as a category and handling rules defined.
- Cryptography and secure transmission rules for PII in storage and in transit.
- Test data and development rules, to avoid using live PII in test environments without protection.
- De-identification, anonymisation or pseudonymisation guidance, if you use these techniques.
- Media disposal and secure deletion procedures, matched to your retention schedule.
- Training and awareness material, with privacy content and attendance records.
Evidence auditors will expect to see#
Policies alone do not demonstrate a working system. Be ready with records such as:
- Completed privacy impact assessments and the decisions that followed them
- Logged individual requests and the dates and outcomes of responses
- Signed data processing agreements
- Privacy training attendance records
- Internal audit findings with PIMS controls covered
- Incident logs showing how PII-related events were assessed and handled
Keep the document set proportionate. A small processor with a narrow service can document simply. What matters is that each document matches how you actually operate.
Frequently asked questions#
Can I implement ISO 27701 without ISO 27001?#
The standard is designed as an extension to ISO 27001 and ISO 27002, so its requirements assume an ISMS exists. Organisations without one generally need to establish the ISMS foundation alongside the privacy additions. Confirm the expectations of your certification body early.
Does ISO 27701 replace the need for GDPR documentation?#
No. ISO 27701 is a certifiable management system standard, not a law. It can support your compliance work and many of the documents overlap, but you remain responsible for meeting the legal requirements that apply to you. Our article on what documents you need for GDPR implementation covers the legal side in more detail.
Are the documents different for controllers and processors?#
Yes, in part. The standard provides separate guidance and control sets for PII controllers and PII processors. A controller needs more documentation around purposes, lawful basis, notices and consent. A processor focuses on customer instructions, sub-processors, assistance to the controller and return or disposal of PII.
If you would rather not draft every policy and record from scratch, the ISO 27701:2019 Toolkit is a ready-to-use documentation toolkit you can review and adapt, or you can talk to the AdWiser team about your situation.
