A company that has its GDPR affairs in order often already has a folder full of privacy documents. Which of these count for ISO 27701, and what do you still need to add? After reading this article you will know which standard documents every management system requires, which documents follow from the controls in Annex A, what you already have from the GDPR and how the auditor uses your documents in stage 1 and stage 2.
Documented information in ISO 27701
ISO 27701 calls everything you record on paper or digitally "documented information". That covers two kinds of documents. Documents are kept up to date, such as your privacy policy. Records show what you have done, such as a handled access request. The standard does not say in what form. A wiki, a folder in your document management system or a privacy tool are all fine. It must be findable, though, and you must know which version applies. This is set out in clause 7.5 of the standard.
Standard documents for ISO 27701
ISO 27701:2025 has the same fixed structure as ISO 27001. That is why it also asks for the same standard documents, but for privacy. Those standard documents are:
- Scope. Which processing activities, systems and locations fall under your system, and which role you have in each processing activity.
- Privacy policy. The policy that top management sets. Your privacy statement on the website is a different document.
- Privacy objectives. What you want to achieve this year, and how you measure it.
- Risk assessment and treatment. For ISO 27001 you record the method and the results of your risk assessment. ISO 27701:2025 has the same structure, with its own privacy risk assessment in 6.1.2 and 8.2. So expect the auditor to want to see the method and the results here too.
In addition, you keep the records that every management system requires. These are evidence of the competence of your people, results of measurements, the programme and results of your internal audit, the results of your management review and nonconformities with what you did about them. That list is the same as for ISO 27001. How to set up those documents is explained in the mandatory documents of ISO 27001. If you already have ISO 27001, you extend those documents with privacy. You do not need to create a second set.
Documents that follow from Annex A of ISO 27701
Most documents for ISO 27701 follow from the controls in Annex A. Many controls already say in their name that you record something. These are the most important, with the article of the GDPR that requires the same:
| Document | Table in Annex A | Also required by the GDPR |
|---|---|---|
| Purpose of each processing activity | A.1 | yes, in the record of processing activities (Article 30) |
| Record of processing activities | A.1 and A.2 | yes, Article 30 |
| Recorded consent | A.1 | yes, you must be able to demonstrate consent (Article 7) |
| DPIA | A.1 | yes, in case of high risk (Article 35) |
| Contracts with processors | A.1 | yes, Article 28 |
| Agreements with customers and subprocessors | A.2 | yes, Article 28 |
| Records of transfers to other countries | A.1 | partly, in the record of processing activities |
| Records of data you provide to third parties | A.1 and A.2 | partly, the record names the categories of recipients (Article 30) |
| Incidents and data breaches | A.3 | yes, as a controller you record every data breach (Article 33(5)) |
Annex D of the standard shows for each element which article of the GDPR it relates to. This lets you put your GDPR documents side by side with the standard.
A processor often has fewer documents from table A.1. From table A.2 there are more. Think of the list of subprocessors that the processor shows to customers, and of evidence that data is returned or deleted after an assignment. A software company that has both roles keeps both sets.
What is new if your GDPR affairs are already in order
What a company with its GDPR affairs in order often lacks is the system around the documents. The documents themselves are then usually already there. There is no fixed owner, no moment at which you review the record and no measurement of whether it works. ISO 27701 does require that. A record that nobody keeps up to date therefore raises questions at the audit, even if it is otherwise complete.
Privacy manual and procedures for ISO 27701
ISO 27701 does not require a privacy manual. You write a procedure where it helps. Think of handling an access request or reporting a data breach. Several people need to know what to do there, often within a fixed deadline. Ready-made packages with dozens of policy documents mainly make your system heavier. An auditor checks whether you do what you write down. So only write down what you actually do.
Documents in stage 1 of the ISO 27701 audit
In stage 1 the auditor reads your documents. That rule is in ISO/IEC 17021-1. The auditor uses them as a map for stage 2. Make sure these documents are ready by then:
- your scope with your role for each processing activity;
- your privacy policy and your privacy objectives;
- your privacy risk assessment and your choice of controls from Annex A;
- your record of processing activities;
- the planning of your internal audit and your management review.
If something is missing, the auditor notes it as a point for stage 2. That can delay your stage 2.
Documents in stage 2 of the ISO 27701 audit
In stage 2 the auditor checks whether you do what your documents say. This is done with samples. For example, you get questions about the latest access request and how quickly you handled it. The auditor also checks whether a new processing activity got a DPIA when that was needed. And the auditor puts a contract with a subprocessor next to your record. The records are the evidence here. A system that has only been running for a few weeks has few records. So give it a few months before you schedule stage 2.
Comparing ISO 27701 certification bodies on the audit of your documents
How a certification body reviews your documents also depends on the auditor. In your quote request, ask what experience the auditor has with the GDPR and with your role. Also ask whether the auditor can do ISO 27701 and ISO 27001 in one audit if you want both. Then the auditor does not have to read the same documents twice.
At CertificeerWijzer you request quotes with one request from certification bodies that may certify ISO 27701 under accreditation. That way you compare their approach and their price side by side.
Sources
- ISO/IEC 27701:2025, introduction and table of contents (preview via EN ISO/IEC 27701:2025, STN) normy.normoff.gov.sk
- UKAS, F659 Transition Requirements and Gap Analysis, ISO/IEC 27701:2025 and ISO/IEC 27706:2025 ukas.com
- Regulation (EU) 2016/679 (GDPR), Articles 7, 28, 30, 33 and 35 eur-lex.europa.eu
- IAS, summary of ISO/IEC 17021-1:2015 section 9 iasonline.org