Decision Register
Regimes ยท GDPR

The GDPR

Attaches to a line that decides alone with a legal or similarly significant effect on a person (Article 22), with the information duties and the DPIA beside it; the information duty alone attaches to every line that faces a person.

On the register, tick "GDPR" and these rows appear on every line the regime reaches. Source framework: GDPR, Regulation (EU) 2016/679.

Which lines it reaches, and with what

On lines that carry the Article 22 flag and decide, where the line decides alone

Art. 22. A decision based solely on automated processing with a legal or similarly significant effect: the lawful route, and at least the right to human intervention, to express a view and to contest.

On lines that carry the Article 22 flag and decide

Art. 13, Art. 14. The information duty beside it: the existence of automated decision-making and meaningful information about the logic, its significance and its consequences.

Art. 35. The DPIA: a systematic evaluation of personal aspects on which decisions with legal or similarly significant effects are based is the case Art. 35 names.

On lines that face a customer or a candidate

Art. 13. Where personal data is collected from the person, the information duty applies to this line.

The record it expects

informsThe tool produces a summary, a ranking or a flag that a person reads before deciding; the person owns the decision. The record holds: who read the output and what it informed; date and the tool version; the output kept with the decision it informed.
draftsThe tool produces the draft of a document, a figure or a position that a person edits and signs; the person owns the content. The record holds: who edited and who signed; date and the tool version; the draft kept beside the signed version; what was changed, classed as omission, misstatement or wording.
decides with reviewThe tool takes the decision and a named person reviews every case or a stated share before the effect; the reviewer can change the outcome. The record holds: reviewer, role and the competence that qualifies them (Art. 26); date and the tool version; sample reviewed: the count out of the total, and the share; overrides: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26).
decides aloneThe tool takes the decision and the effect follows with no person in between; a person may audit afterwards. The record holds: who audits the line afterwards, role and competence (Art. 26); date, the tool version and the volume decided; audit sample: the count out of the total, and the share; reversals after audit: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26); incidents reported to the provider and the date (Art. 26).

Article 22 and the lines it reaches

Article 22 attaches where the tool decides alone and the decision has a legal or similarly significant effect on a person: credit scoring, insurance pricing, claims decisions, benefit eligibility, KYC refusals, candidate screening, shift allocation and personalised pricing carry the flag in the dictionary. The register renders it as a flag on the line and quotes the article beside the information duties (Art. 13 and 14) and the DPIA (Art. 35). Which lawful route applies, and whether the safeguards are enough, is the entity's and its counsel's judgement.

The clauses, quoted

4 of 40 in the framework

Requirement text in our own words, read clause by clause from the published standards: our statement of each clause, not the instrument verbatim.

GDPR Art. 22 Automated individual decision-making, including profiling

Do not subject a data subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning them or similarly significantly affects them, unless the decision is necessary for entering into or performing a contract between the data subject and the controller, is authorised by Union or Member State law that lays down suitable safeguards, or is based on the data subject's explicit consent. Where the contract or explicit consent route is used, implement suitable measures to safeguard the data subject's rights, freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express a point of view and to contest the decision. Such decisions must not be based on special categories of personal data unless explicit consent or substantial public interest applies and suitable safeguards are in place.

Evidence an auditor accepts: An inventory of automated decisions with the assessment of whether each produces legal or similarly significant effects; The exception relied on for each in scope decision, and for contract based ones the necessity reasoning rather than a convenience argument; The human intervention process, showing the reviewer has the authority and the information to change the outcome
Common gap: A rubber stamp reviewer treated as human involvement, which leaves the decision solely automated in substance
Source framework: GDPR, Regulation (EU) 2016/679
GDPR Art. 13 Information to be provided where personal data are collected

Where personal data is collected from the data subject, provide at the time it is obtained the identity and contact details of the controller and any representative, the contact details of the data protection officer, the purposes and the legal basis, the legitimate interests where that is the basis, the recipients or categories of recipient, and any intention to transfer to a third country with the existence or absence of an adequacy decision and, for Article 46, 47 or 49(1) transfers, reference to the safeguards and how to obtain a copy. Provide in addition the storage period or the criteria used to determine it, the existence of the rights of access, rectification, erasure, restriction, objection and portability, the right to withdraw consent where consent is the basis, the right to lodge a complaint with a supervisory authority, whether providing the data is a statutory or contractual requirement and the consequences of not providing it, and the existence of automated decision-making including profiling with meaningful information about the logic involved and its significance and envisaged consequences. Before further processing for a new purpose, provide that purpose and the further information first.

Evidence an auditor accepts: The privacy notice mapped item by item against every information element Article 13 lists; Evidence of the point and timing at which the notice is presented for each collection channel, including forms, telephone and in person; The storage periods or criteria as published, reconciled against the actual retention schedule
Common gap: Recipients described only as third parties or trusted partners, which names neither a recipient nor a category
Source framework: GDPR, Regulation (EU) 2016/679
GDPR Art. 14 Information where personal data have not been obtained from the data subject

Where personal data has not been obtained from the data subject, provide the same identity, contact, purpose, legal basis, recipient and transfer information as Article 13, plus the categories of personal data concerned and the source the data came from including whether it was a publicly accessible source. Provide it within a reasonable period and at the latest within one month of obtaining the data, or at the latest at the first communication with the data subject if the data is used to communicate with them, or at the latest when the data is first disclosed to another recipient. The obligation does not apply where the data subject already has the information, where provision proves impossible or would involve disproportionate effort in which case appropriate protective measures including making the information publicly available must be taken, where obtaining or disclosure is expressly laid down by Union or Member State law with appropriate safeguards, or where the data must remain confidential under an obligation of professional secrecy.

Evidence an auditor accepts: A source register showing, per dataset, where the data came from and whether the source was publicly accessible; Evidence of the notification sent with its date, tested against the one month, first communication and first disclosure triggers; The disproportionate effort assessment where the exemption is relied on, showing what was weighed rather than only that a conclusion was reached
Common gap: Purchased or enriched marketing data used with no Article 14 notification at all, which is the most common finding in this area
Source framework: GDPR, Regulation (EU) 2016/679
GDPR Art. 35 Data protection impact assessment

Where a type of processing, in particular using new technologies and taking account of the nature, scope, context and purposes of the processing, is likely to result in a high risk to the rights and freedoms of natural persons, carry out an assessment of the impact of the envisaged processing operations on the protection of personal data before the processing begins; a single assessment may address a set of similar operations presenting similar risks. An assessment is required in particular for systematic and extensive evaluation of personal aspects based on automated processing, including profiling, on which decisions producing legal or similarly significant effects are based, for large scale processing of special category or criminal offence data, and for systematic monitoring of a publicly accessible area on a large scale. Seek the advice of the data protection officer where one is designated, and where appropriate seek the views of data subjects or their representatives. The assessment must contain at least a systematic description of the envisaged operations and purposes including any legitimate interest pursued, an assessment of the necessity and proportionality of the operations in relation to the purposes, an assessment of the risks to the rights and freedoms of data subjects, and the measures envisaged to address those risks including safeguards, security measures and mechanisms to protect personal data and demonstrate compliance. Carry out a review where necessary and at least when the risk represented by the processing operations changes.

Evidence an auditor accepts: The screening or threshold process applied to new and changed processing, with its outcomes recorded including the negative ones; Completed assessments checked against the four minimum content elements Article 35(7) requires; The data protection officer's advice sought and given on each assessment, recorded as advice rather than as approval
Common gap: An assessment opened at project start and never revisited, so its residual risk conclusion is never tested against how the processing actually turned out
Source framework: GDPR, Regulation (EU) 2016/679

See what it attaches to your list

Paste the list, tick the regime, and every line it reaches carries these rows. Eight lines free, no account.

Build my decision register