7.5.1 General
The privacy information management system of the organization shall contain the documented information this document calls for, plus whatever documented information the organization decides it needs for the PIMS to work effectively; how much is needed can vary with the organization's size, how complex its processes are and how competent its people are. Records demanded by the annex controls, for example records of processing, consent, transfers and disclosures, count as documented information of the PIMS.
Source: ISO/IEC 27701:2025, 7.5.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27701:2025 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Register of PIMS documented information covering every item this document requires · Policy repository / GRC workspace
- Evidence the organization decided what further documentation its processing needs · Document repository
- Records required by the Annex A controls identified as documented information · Document repository
First move
Common gaps auditors find
- Documentation limited to the policy and the SoA
- Records of processing and consent kept outside the control regime of 7.5.3
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet7.4 Communication · 7.5.2 Creating and updating documented information