What evidence do auditors commonly ask for on 4.3 Determining the scope of the privacy information management system?

Documented PIMS scope statement naming the processing of PII, services, locations, systems and legal entities covered; Rationale linking the scope to context, interested parties and interfaces with other organizations; Where an ISMS also exists, the relationship between the two scopes.

What is the most common gap auditors find on 4.3?

Scope that excludes a processing activity or subsidiary without justification

ISO/IEC 27701:2025 · Context of the organization

`4.3` Determining the scope of the privacy information management system

The organization shall fix the boundaries and applicability of its privacy information management system to define its scope, taking into account the internal and external issues identified under 4.1, the interested party requirements from 4.2, and the points where its own activities connect with or rely on work done by other organizations. The scope shall cover the processing of PII and be kept as documented information. The first edition's note that a PIMS scope might force a revision of the information security management system scope has been dropped, since the PIMS is no longer an extension of an ISMS.

Source: ISO/IEC 27701:2025, 4.3. 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.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Documented PIMS scope statement naming the processing of PII, services, locations, systems and legal entities covered · Policy repository / GRC workspace
Rationale linking the scope to context, interested parties and interfaces with other organizations · Policy repository / GRC workspace
Where an ISMS also exists, the relationship between the two scopes · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Scope that excludes a processing activity or subsidiary without justification
Scope stated by location only, with the PII processing activities unnamed
Scope inherited from an ISO/IEC 27001 certificate and never re-examined for PII processing

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 sheet

4.2 Understanding the needs and expectations of interested parties · 4.4 Privacy information management system