What evidence do auditors commonly ask for on 4.2 Understanding the needs and expectations of interested parties?

Register of interested parties with the privacy requirement each imposes; PII principals listed as an interested party with their rights and expectations recorded; Decision on which requirements the PIMS addresses; Evidence the register considers climate-related expectations.

What is the most common gap auditors find on 4.2?

Interested parties listed without the requirement each imposes

ISO/IEC 27701:2025 · Context of the organization

`4.2` Understanding the needs and expectations of interested parties

The organization shall identify which interested parties matter to its privacy information management system, what those parties require, and which of those requirements the system will deal with. PII principals are named expressly as interested parties; others can include customers, supervisory and data protection authorities, partners, suppliers and subcontractors, and their requirements may be legal, regulatory or contractual. A note taken over from the harmonized text observes that interested parties may have climate change requirements. The definition of customer, retained from the first edition, separates the organization's customers from PII principals and from third parties.

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

Decision on which requirements the PIMS addresses · Document repository

governing documentDocuments that govern the control

Register of interested parties with the privacy requirement each imposes · Policy repository / GRC workspace
PII principals listed as an interested party with their rights and expectations recorded · Document repository
Evidence the register considers climate-related expectations · 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

Interested parties listed without the requirement each imposes
Supervisory authorities in the operating jurisdictions missing from the register
Customers of a processor listed, PII principals not

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.1 Understanding the organization and its context · 4.3 Determining the scope of the privacy information management system