Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.2.5 Obtain and record consent

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A chain of opticians receives a complaint: a customer denies ever agreeing to marketing emails. The CRM holds just one field for him, “newsletter: yes”. Nobody knows when it was set, through which form or with which text, because the form has been rebuilt twice since. The chain cannot prove the consent and has to stop the marketing to this customer at once. A.1.2.5 requires consent to be obtained by the defined process and recorded so that each individual consent can be proven on request.

The control carries out what A.1.2.4 plans. That control states when and how consent is to be obtained. This one is about the actual event and the record it leaves behind.

What does the standard require?

The control sits in the group of conditions for collection and processing and builds directly on the process from A.1.2.4.

  • Follow the documented process. Each consent is obtained by the route the organization laid down in advance.
  • Be able to answer requests. The record is set up so that the details can be produced at any time. The standard gives as examples the time, the identification of the person and the wording of the consent statement.
  • Inform first. What the person learns before deciding follows the guidance for A.1.3.4.
  • Three qualities of consent. It is given freely, relates specifically to the purpose in question and is unambiguous and explicit.

In practice

Define a fixed record. Every consent creates an entry with the time including time zone, an identifier for the person, the text version, the channel and the individual purposes with their status. A customer or case number is often enough as the identifier; the consent record does not need the person’s full master data.

Check forms for free choice. Each purpose gets its own switch, and all of them start in the off position. Refusing costs the person nothing, and the core service stays available without agreement. Pre-ticked boxes and blanket consents behind a single button invalidate the consent, and with it the lawful basis for everything that rests on it.

Secure the identity sensibly. For email marketing in Germany, the double opt-in procedure has become the accepted proof: the sign-up only takes effect once the person confirms through a link in the email. Record the time of confirmation in the entry.

Do not forget paper. Consent collected at trade fairs, in the shop or for photos of employees is scanned, captured with the same structure and linked to the original. Otherwise a second, unchecked filing system grows.

Protect the records. Consent data is secured against later alteration and unauthorized access, and changes of status are logged. Proof that anyone with database access can rewrite carries little weight with a supervisory authority.

Typical audit evidence

For A.1.2.5, auditors typically expect:

  • Consent records with time, identifier of the person, text version and purposes, checked by sampling
  • Versioned consent texts with approval (→ Document Control Register)
  • Acceptance of forms with evidence of empty defaults and separate purposes (→ Change Log)
  • Safeguards for consent data, such as an authorization concept and logging of status changes
  • Retention period for the records (→ Records Retention Schedule)

KPI

% of consent instances properly obtained and recorded with audit trail

This is measured by sampling: a case counts if it went through the approved process and time, person and wording are fully documented. The target is 100%. Legacy data from earlier forms often pulls the figure down noticeably until it has been collected again or deleted.

Supporting KPIs:

  • Time from receiving a query to producing the consent record
  • Number of forms with pre-selected options (target: 0)
  • Share of paper consents captured in structured form

Under Article 7(1) GDPR, the controller has to be able to demonstrate that the data subject consented. Article 4(11) describes consent as freely given, specific, informed and unambiguous, expressed by a statement or a clear affirmative action. Recital 32 makes clear that silence, pre-ticked boxes or inactivity do not count as consent, and the Court of Justice confirmed this for pre-ticked boxes in its 2019 Planet49 judgment (C-673/17). The GDPR asks for explicit consent only in certain cases, such as Article 9(2)(a) for special categories. By saying “explicit”, the standard therefore sets the bar higher. On free choice, see also Article 7(4) and Recital 43 (→ GDPR General Data Protection Regulation).

The record connects planning, information and withdrawal:

Sources

Frequently asked questions

What belongs in a consent record?

At least the time, an identifier for the person and the exact wording of the statement, which the standard itself gives as examples. In practice, channel, the individual purposes and the current status are added. Store the text as a reference to an approved version, so that no record has to carry its own copy.

Is a ticked box enough for explicit consent?

A box the person ticks next to a clear statement is an unambiguous affirmative act. Consent becomes explicit when the statement itself names the type of data and the purpose in a sentence of its own that the person actively agrees to. The GDPR requires this for special categories, for example, while the standard expects it for every consent.

How long are consent records kept?

For as long as the processing rests on the consent and beyond that for as long as the organization has to expect questions or claims. After a withdrawal, the record stays, because it proves that the earlier processing was lawful. The specific period belongs in the records retention schedule.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.