An online retailer collects dates of birth at checkout “for age verification”. Two years later, marketing uses the same data for birthday vouchers, and analytics builds age groups from it for price tests. Nobody ever recorded what the data was actually for. A.1.2.2 requires every purpose of processing to be defined in advance, in concrete terms, and recorded in a way the people concerned understand.
The purpose is the pivot of privacy. It decides which lawful basis fits, which data is necessary, how long it is kept and what the data subjects are told. Without a clear purpose, none of these questions has a clean answer.
What does the standard require?
The control belongs to the conditions for collection and processing, the first group of controls for PII controllers.
- Define and document specific purposes. For every processing of personal data, the organization decides what it serves and records that in writing. Broad catch-all purposes do not meet the requirement.
- Understandable for data subjects. The organization is responsible for making sure the people concerned can follow the purpose. Consent and a real choice are only possible if the purpose has been named clearly beforehand.
- Written for reuse. The description is precise enough to be carried straight into the information for data subjects (A.1.3.3), into consent texts (A.1.2.4) and into the records under A.1.2.9.
- Shared vocabulary. For cloud services, the standard points to ISO/IEC 19944 as an aid to describing purposes consistently.
In practice
Take stock. Go through the processing activities of each department: HR administration, customer service, sales, marketing, IT operations. For each activity, ask what the data is really used for. This often shows that one activity pursues two or three different purposes.
Record purpose and lawful basis together. Enter the purpose in the record of processing activities right next to the lawful basis (A.1.2.3). Each entry checks the other: a purpose for which no lawful basis can be found is a warning sign.
Feed all texts from one source. Privacy notices, consent forms and internal policies take the description of the purpose from the record. The wording stays identical, and a change only has to be made in one place.
Give departments a template. Whoever registers a new processing activity answers three questions: what exactly happens to the data? Who benefits from it, and how? How do you know the purpose has been reached and the data can be deleted? The answers almost write a sound purpose statement on their own.
Manage changes of purpose. Decide that every new use of existing data is checked before it starts: is the new purpose compatible with the old one, does it need a lawful basis of its own, do data subjects have to be informed? Record the result.
Typical audit evidence
For A.1.2.2, auditors typically expect:
- Record of processing activities with a specific purpose per activity and the date of the last review
- Privacy notices and consent texts whose purposes match the record
- Procedure for changes of purpose with documented compatibility assessments (→ Change log in the Starter Kit)
- Policy or work instruction describing how purposes are worded and approved
- Training records for the people who set up new processing activities (→ Training register)
KPI
% of processing activities with fully documented processing purposes
Fully documented means: worded in concrete terms, linked to a lawful basis and found again in the information for data subjects. The target is 100%. On the first pass, many organizations score well below that, because older activities carry only catch-all purposes.
Supporting KPIs:
- Number of changes of purpose per year with a documented compatibility assessment
- Share of privacy notices whose purposes match the record word for word
- Average time from registering a new processing activity to approval of its purpose
Link to the GDPR
A.1.2.2 puts the principle of purpose limitation into practice. Under Article 5(1)(b) GDPR, personal data is collected for specified, explicit and legitimate purposes. Article 30(1)(b) requires the purposes in the record of processing activities, and Articles 13(1)(c) and 14(1)(c) in the information for data subjects. For later processing for a different purpose, Article 6(4) sets out the criteria of the compatibility assessment (→ GDPR in the Cenedril wiki).
Annex D of the standard also maps A.1.2.2 to Article 32(4). Under it, persons acting under the authority of the controller who have access to the data process them only on the controller’s instructions. The documented purposes frame those instructions.
Related controls
A.1.2.2 is the starting point for the other conditions of processing:
- A.1.2.3 Identify lawful basis: assigns each purpose the lawful basis that carries it.
- A.1.2.9 Records related to processing PII: keeps the purposes in the record of processing.
- A.1.3.3 Determining information for PII principals: carries the purposes into the information for data subjects.
- A.1.4.3 Limit processing: restricts processing to what the purpose requires.
Sources
- ISO/IEC 27701:2025, Annex A, Table A.1, A.1.2.2, and Annex B, B.1.2.2: Identify and document purpose
- Regulation (EU) 2016/679 (GDPR), Articles 5, 6, 13, 14, 30 and 32
- ISO/IEC 27701 in the Cenedril wiki: structure of the standard and roles