What evidence do auditors commonly ask for on 4.1 Understanding the organization and its context?

Documented role determination per processing activity, controller, joint controller or processor; Context analysis naming the privacy laws, regulations, decisions and contracts that apply; Record of the climate change relevance determination; Where both roles are held, the boundary between the two control sets.

What is the most common gap auditors find on 4.1?

One organization-wide role declared when the role changes by service or processing activity

ISO/IEC 27701:2025 · Context of the organization

`4.1` Understanding the organization and its context

The organization shall identify the internal and external issues, relevant to its purpose, that bear on its capacity to get the outcomes its privacy information management system is meant to deliver. The privacy-specific step that the first edition added now stands as a requirement of its own: the organization shall establish whether it acts as a PII controller (joint controllership included), as a PII processor, or as both; where it acts as both, each role shall be established separately and given its own set of controls. Issues to weigh include the privacy laws, regulations, court and administrative rulings, contract terms and internal governance that affect how PII is processed. New to this edition, the organization shall form a view on whether climate change matters to its context.

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

artefacts

held by a system

at each review

moderate

to go live

Document repository

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

Record of the climate change relevance determination · Document repository

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Documented role determination per processing activity, controller, joint controller or processor · Policy repository / GRC workspace
Context analysis naming the privacy laws, regulations, decisions and contracts that apply · Vendor register / contract repository
Where both roles are held, the boundary between the two control sets · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

One organization-wide role declared when the role changes by service or processing activity
Context written at certification and never revisited when processing moves to a new jurisdiction
Climate change determination missing because the template predates the harmonized text

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