What evidence do auditors commonly ask for on A.1.2.8 Joint PII controller?

Binding joint controller agreement covering each of the matters the standard lists; Identification of every joint controller relationship, distinguished from processor relationships; Named contact point for individuals and evidence it is reachable; Breach responsibility allocation naming who notifies whom and within what time; Information made available to individuals about the essence of the arrangement.

What is the most common gap auditors find on A.1.2.8?

Joint controllership misclassified as a processor relationship, so the wrong contract terms apply

ISO/IEC 27701:2025 · Annex A Table A.1 PIMS controls for PII controllers

`A.1.2.8` Joint PII controller

Where the organization is a joint controller, it must determine the respective roles and responsibilities for processing, including privacy and security requirements, transparently and in a contract or similar binding document covering matters such as the purpose of the sharing, the parties, the categories of data shared, the processing operations, the allocation of technical and organizational measures, responsibility in the event of a breach including who notifies and when, retention and disposal terms, liabilities, how obligations to individuals are met and how they can obtain information, and a contact point for individuals.

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

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

none for this control

periodic reviewEvidence produced at each review

Named contact point for individuals and evidence it is reachable · Document repository

governing documentDocuments that govern the control

Binding joint controller agreement covering each of the matters the standard lists · Vendor register / contract repository
Identification of every joint controller relationship, distinguished from processor relationships · Document repository
Breach responsibility allocation naming who notifies whom and within what time · Document repository
Information made available to individuals about the essence of the arrangement · Document repository

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

Joint controllership misclassified as a processor relationship, so the wrong contract terms apply
Agreement covering commercial matters while breach notification and obligations to individuals are unaddressed
No contact point, leaving individuals to guess which party to approach
Arrangement never disclosed to individuals in any form
Retention terms unstated, so each party retains on its own schedule

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

A.1.2.7 Contracts with PII processors · A.1.2.9 Records related to processing PII