When is an AI system high-risk?

3 Legal interpretation of Article 6(3)(a) and (d)

s. 14–27pp. 14–27 · PDF 18–31

3.1 Structure and wording of Article 6(3)#s. 14

Keeping in mind the context set out in Chapter 2, I now move on to derive operative criteria from Article 6(3)(a) and (d), following the methods of interpretation set out in Section 1.4. I first examine the structure and wording of Article 6(3) as a whole.

3.1.1 The overarching condition of no significant risk of harm#s. 14

Article 6(3) first subparagraph provides that an AI system falling within one of the Annex III areas “shall not be considered to be high-risk where it does not pose a significant risk of harm to the health, safety or fundamental rights of natural persons, including by not materially influencing the outcome of decision making.” This overarching condition — the absence of significant risk, including the absence of material influence on decision-making — establishes a general threshold that is both abstract and subjective. The “materiality” qualifier is also inherently subjective, and may allow providers to claim that their system's influence on decisions is immaterial even where it significantly shapes the informational basis on which those decisions are made. If the overarching condition is too indeterminate to constrain the self-assessment effectively, the specified conditions must serve as the primary contributor to legal certainty.

3.1.2 Article 6(3) as a closed list of carve-outs#s. 14

The second subparagraph sets out four specific conditions under which the first subparagraph “shall apply”. They read as follows, with the conditions that are the focus of this thesis emphasised in bold text:

(a)the AI system is intended to perform a narrow procedural task;**

(b)the AI system is intended to improve the result of a previously completed human activity;

(c)the AI system is intended to detect decision-making patterns or deviations from prior decision-making patterns and is not meant to replace or influence the previously completed human assessment, without proper human review; or

(d)the AI system is intended to perform a preparatory task to an assessment relevant for the purposes of the use cases listed in Annex III.**

The list is connected by the disjunctive “or”, indicating that the conditions are alternative rather than cumulative: satisfying any one of the four is sufficient, provided that the overarching condition of no significant risk of harm is also met.

The question arises whether the four conditions are exhaustive: Can a provider invoke Article 6(3) on a basis not enumerated in the list? Do the four conditions serve as safe harbours, sufficient but not necessary, rather than as an exclusive gateway? The enumerative reading finds some textual support in the structure of the provision itself: the first subparagraph states the “no significant risk” standard as an apparently self-standing rule, and the second subparagraph opens with “the first subparagraph shall apply” where one of the conditions is met, which could be read as triggering a presumption rather than defining the only permissible path.

Textual and systematic considerations support the conclusion that the list is closed: First, the legislative technique of enumerating specific derogation conditions following a general prohibition clause is a well-established mechanism in EU law for delimiting the scope of a derogation. Had the legislator intended the conditions to be illustrative, one would expect the use of qualifying language such as “in particular” or “for example” – language that is absent here. Second, Article 6(6) empowers the Commission to adopt delegated acts amending the conditions set out in Article 6(3), “adding new conditions to those laid down in paragraph 3, or modifying them.” The express conferral of a power to add conditions would be superfluous if the existing list were already open-ended; the provision implies that the Article 6(3) conditions can only be expanded through formal legislative amendment. Third, reading the conditions as a closed list is consistent with the principle of strict interpretation of derogations in EU law, as established in the ECJ’s jurisprudence. This ensures that the scope of the carve-out is legally determinate and that providers cannot invoke unenumerated grounds to escape high-risk classification. The consequence of this reading is that an AI system deployed within an Annex III area that does not satisfy any of the four enumerated conditions remains classified as high-risk, even if the provider considers the system’s specific function to pose no significant risk of harm. The question is not beyond doubt, and future guidance from the Commission or the ECJ may clarify whether the overarching condition has any independent operative function beyond its role as an interpretive constraint on the four conditions.

A second interpretive question is whether satisfying one of the second-subparagraph conditions deems the overarching “no significant risk of harm” threshold met (the automatic reading), or whether the overarching condition is a separate test the provider must also pass (the cumulative reading). The automatic reading reduces “no significant risk” to an interpretive constraint on the conditions. The cumulative reading is more protective, adding a case-by-case assessment on top of the condition-based classification, at the cost of legal certainty.

The automatic reading is, in my view, the better interpretation. Recital (53) describes the carve-out as covering “specific cases in which AI systems … do not lead to a significant risk of harm … because they do not materially influence the decision-making…” (my emphasis), indicating the significance/materiality threshold is integrated in the specific case conditions. The Article 6(7) power to delete conditions by delegated act “to maintain the protection of health, safety and fundamental rights” suggests the legislator already viewed the conditions as alone determining the boundary of the carve-out. The automatic reading is also more consistent with the Act’s ambition to provide clear, ex ante classification rules. The cumulative reading’s advantage is preserving the overarching condition as a safety net for edge cases the legislator did not foresee. The question would benefit from clarification.

3.1.3 The “profiling of natural persons” carve-out from the carve-outs#s. 16

Article 6(3) third subparagraph introduces an exception from the exceptions: AI systems “shall always be considered to be high-risk where the AI system performs profiling of natural persons.” This contributes to the systematic interpretation of the derogation condition interpretations, and will play an important role in the operationalised criteria developed in Chapter 4.

3.2 “Narrow procedural task” under Article 6(3)(a)#s. 16

3.2.1 Linguistic interpretation of “narrow”, “procedural”, and “task”#s. 16

Article 6(3)(a) provides that the carve-out applies where “the AI system is intended to perform a narrow procedural task.” The condition combines three lexical elements – “narrow”, “procedural”, and “task” – each of which contributes to delimiting the scope of the exception.

3.2.1.1 “Task”#s. 17

The term “task” has already been discussed briefly in Section 2.3.3 above. The Oxford English Dictionary (OED) gives the literal definition as “A piece of work imposed, exacted, or undertaken as a duty or the like; originally, a fixed or specified quantity of labour or work imposed on or exacted from a person; later, the work appointed or assigned to one as a definite duty.” It follows that “task” describes a defined, fixed and concretely specified piece of work, rather than a broader progress or abstract responsibility. “Identify if the applicant has a valid bus driver’s licence” is a task. “Find and hire a bus driver” is arguably not a task, instead representing a broader process (composed of many tasks). And “Bus driver staffing” is clearly an abstract responsibility rather than a task.

In the context of condition (a), “task” denotes a specific, delimited function that the AI system is intended to carry out: not the system’s general capabilities, but its specific operational role in the context of the process in which it is deployed.

3.2.1.2 “Narrow”#s. 17

While a “task” must be specific and defined, there is still variation: Some activities that might be described as tasks — such as the “find and hire a bus driver” example above — are broader, pushing against the upper bound of the definition, while others are more limited in scope. The adjective “narrow” clarifies we are here operating in the latter end of the range. A system extracting dates from CVs should qualify. A system that extracts dates, calculates work-history gaps, compares the gaps to a predefined significance threshold, and removes applicants on that basis might not. The narrowness criterion serves as a filter against systems that, while potentially classifiable as “procedural” in some respects, operate across a broader functional domain.

3.2.1.3 “Procedural”#s. 17

The adjective “procedural” is the decisive qualifier for condition (a). Literally defined broadly as relating to “…the established or prescribed way of doing something”, in legal theory, the distinction between “procedural” and “substantive” is a fundamental one. Procedural rules and acts concern the manner, method, or form by which a process is conducted, while substantive rules concern the merits, content, or outcome of the matter at hand. The procedural/substantive distinction is a foundational concept in legal theory and is reflected in the structure of EU law itself, where procedural rules (such as those governing actions for safeguarding EU rights) are distinguished from substantive rules (such as those defining EU rights and obligations).

Transposed to the AI Act context, a “procedural” task is one that relates to the form, order, or method of processing – the mechanics of handling information according to a fixed and defined course of action – rather than to the evaluation of the content or significance of that information. A system that converts unstructured data into a structured format manipulates the form of information without assessing its substance. A system that, to perform its given function, evaluates the quality, relevance, or risk implications of information performs a substantive task.

Recital (53) offers illustrative examples of tasks that may qualify under Article 6(3): “For instance, AI systems intended to perform narrow procedural tasks such as [1] transforming unstructured data into structured data, [2] classifying incoming documents into categories, or [3] detecting duplicates among documents should not be considered to be high-risk.” (numbers in brackets added for reference):

1)Transforming unstructured data into structured data involves imposing a pre-defined format on raw information – for example, extracting fields from a text document and mapping them to database entries. This is a clear example of a task involving only operations on the form or structure of data rather than on its content or meaning.

2)Classifying documents into categories is more difficult: On one hand, sorting based on formal characteristics (document type, language, sender) would clearly qualify as “procedural”. Sorting documents into less formal and more judgment-based categories such as “High risk”, “Low risk” would require evaluating the substance of a document’s content. The line between formal and substantive classification is unclear: even classification by language requires the system to engage with the content of a document to a degree. It must process enough of the text to identify the language, which involves something more than pure syntactic manipulation. The difficulty intensifies for intermediate cases. Consider a system that classifies incoming regulatory filings into pre-defined categories such as “employment matter,” “tax matter,” or “environmental matter.” The categories are fixed and externally imposed; the system does not evaluate the merits of any filing. Yet the classification necessarily requires a degree of content analysis – the system must understand what the filing is about, not merely what format it is in. A provider might plausibly argue that such classification is procedural because it operates within a closed and pre-defined taxonomy, while a regulator might counter that any classification requiring engagement with the substance of a document's content is inherently evaluative. The resolution, in my view, lies in the qualifier “narrow”: where the classification scheme is fixed (predetermined and independent of context), bounded (with clear ringfencing of the extent of the classification’s potential impact), and objectively verifiable, where the “correct” classification can be assessed by reference to formal or widely agreed criteria, the task retains its procedural character, even if it involves some degree of content engagement. Where the classification requires the system to make judgments about significance, quality, or risk, however, the task crosses from the procedural into the substantive.

3)Detecting duplicates involves comparing records for identity or near-identity, which is an operation on formal similarity.

Crucially, the Recital (53) examples are all deterministic or rule-based in character: the “correct” output is, at least in principle, objectively verifiable. That a date has been correctly parsed, a document has been correctly categorised as “English language” rather than “Norwegian language”, or that two files contain the same data, can all be assessed by reference to formal criteria without requiring evaluative judgment. This is not to say that the examples are wholly free of evaluative choice, but these judgments happen at the (human-driven) design stage – for instance, where a data structuring schema is designed to ignore or prioritise certain information (e.g. “capture if the applicant has a bus driver’s licence, ignore other certifications”). Such design choices, however, are made once and operate uniformly across inputs; they do not require the system to perform an evaluative judgment about the substance of any particular case. If the data structuring design choices themselves embed “black box” substantive evaluation of the kind that Article 6(3) seeks to capture, e.g. building a structured prioritised list of information snippets considered most “relevant” to a future assessment, the task crosses from procedural into substantive territory.

It is useful to conceptualise this distinction in terms drawn from information theory: the difference between syntactic and semantic processing. Syntactic processing operates on the structure or format of data – the arrangement, classification, or transformation of information based on formal properties. Semantic processing operates on the meaning or evaluative content of data – the assessment of what information signifies for a particular purpose, such as whether a candidate is suitable for a position or whether a claim is likely to be fraudulent. Article 6(3)(a) can be understood as limiting the carve-out to tasks that are syntactic in character: the AI system processes the form of information without generating evaluative conclusions about its content. The syntactic/semantic distinction is challenged by how modern AI systems built on large language models (LLMs) process information. An LLM tasked with “transforming unstructured data into structured data” may internally perform extensive semantic processing: e.g. named entity recognition requires contextual understanding of meaning to distinguish a person's name from an organisation’s name or a place name. At the technical level, the boundary between LLMs processing form and processing meaning is far less sharp than the legal distinction suggests. However, de lege lata the question under Article 6(3)(a) is not how the system technically processes information internally, but what the system's task is characterised as in terms of its input-output specification and its functional role in the decision-making process. A system that takes an unstructured CV as input and produces a structured table of dates, qualifications, and employer names as output performs a task that is procedural at the level of its observable function, regardless of the complexity of the internal computation required to achieve that result. The syntactic/semantic distinction operates at the level of the task's specification and output, not at the level of the model's internal representations.

3.2.2 Systematic interpretation of “narrow procedural task”#s. 20

Article 14(4) requires that natural persons to whom human oversight is assigned are enabled “to properly monitor the operation of the high-risk AI system” and to “decide, in any particular situation, not to use the high-risk AI system or to otherwise disregard, override or reverse the output of the high-risk AI system.” A genuinely narrow procedural task does not produce outputs requiring such override mechanisms. The “procedural” character of a task should accordingly be assessed not only by its logical position in the workflow, but also by whether the output risks engaging automation bias in the subsequent human decision-maker. A task whose output is formally intermediate and procedural, but psychologically decisive – because it frames, narrows, or pre-structures the decision-maker’s cognitive field – is not procedural in the sense required by the provision: For instance, a case-management system preparing standardised documentation for cases judged to align with a simple “happy path” may, though the task being purely procedural, subconsciously tempt a time-pressed assessor to ignore signs that further investigation is needed, since investigating would forfeit the time-saving filing.

GDPR Article 22, on automated individual decision-making, supplies a parallel systematic reference. Its distinction between automated processing that produces legal or similarly significant effects on a natural person and processing that does not maps onto Article 6(3)(a)’s procedural/substantive divide: language identification or date-sorting facilitates a later decision without itself producing such effects, whereas evaluative judgment of a person’s characteristics or situation engages both Article 22 and the high-risk regime.

The ECJ’s judgment in Case C-634/21 (SCHUFA) provides an instructive illustration of this boundary in automated processing. The Court considered whether a credit reference agency’s calculation of a credit score amounted to a “decision based solely on automated processing” under GDPR Article 22, even though the formal lending decision was the bank’s. The Court rejected the agency’s argument that the score was merely preparatory, holding that where the probability value plays a “determining role” in the credit decision, describing it as preparatory would create a gap in the protection afforded by Article 22.

The SCHUFA reasoning transposes to Article 6(3)(a) by analogy: the “procedural” character of a task should be assessed not by its formal label or its position in a workflow, but by its functional role in relation to the decision affecting the natural person. A formally intermediate task may be functionally decisive. Sorting job applications by date of receipt is procedural; sorting them by “relevance” to the position, even if the provider characterises this as a classification task, and the deployer is not the one making the hiring decisions, is substantive. See also the discussion below on the interpretation of “preparatory task” in Article 6(3)(d).

3.2.3 Teleological interpretation: the purpose of carving out procedural tasks within high-risk activities#s. 21

The teleological analysis of Article 6(3)(a) must be situated within the AI Act’s dual objectives: the protection of fundamental rights and the promotion of innovation through proportionate regulation. The purpose of carving out narrow procedural tasks is to avoid imposing the full weight of high-risk compliance on AI systems that, despite operating in a sensitive domain, perform functions that do not engage the interests the regulation seeks to protect.

Recital (53) articulates this purpose: there are “specific cases in which AI systems referred to in pre-defined areas specified in this Regulation do not lead to a significant risk of harm to the legal interests protected under those areas because they do not materially influence the decision-making or do not harm those interests substantially.” Narrow procedural tasks should accordingly be read as only those whose output does not bear on the legal interests that justified the inclusion of the area in Annex III.

At the same time, the purpose of the carve-out requires that it not be deprived of its effet utile. It is easy to construct scenarios in which even narrow procedural tasks could inadvertently cause harm: a duplication-removal algorithm wrongly drops a job applicant who shares a name and date of birth with another, or a date-parsing algorithm miscomputes the applicant’s years of experience because of inconsistent date formats. If the notion of “narrow procedural task” were read so strictly that any theoretical risk arising from such combinations of AI and human error sufficed to defeat it, no real-world AI system could satisfy the condition, the carve-out would exist on paper only, and the proportionality principle would be undermined. The ECJ has consistently held that derogations must be interpreted strictly, but not so as to deprive them of practical effect. Concretely, this means that the condition must be capable of covering genuinely low-risk procedural AI functions that are deployed within high-risk areas.

The Act’s dual purposes thus impose a two-sided constraint: Article 6(3)(a) must be read strictly enough to prevent substantive decision-support functions from being relabelled as procedural, yet broadly enough to permit genuinely low-risk procedural functions to escape full high-risk compliance.

3.3 “Preparatory task to an assessment” under Article 6(3)(d)#s. 22

3.3.1 Linguistic interpretation of “preparatory” and “to an assessment”#s. 22

Article 6(3)(d) provides that the carve-out applies where “the AI system is intended to perform a preparatory task to an assessment relevant for the purposes of the use cases listed in Annex III.” This condition is linguistically more complex than condition (a), and its interpretation requires attention to each of its constituent elements.

The term “task” must be interpreted as in condition (a) – it anchors the assessment to a specific delimited function performed by the AI system in its intended context of use.

The adjective “preparatory” denotes that this is a task “that prepares or serves to prepare for something following; preliminary, introductory.” In legal parlance, a preparatory act is one that precedes and contributes to a final determination without itself constituting that determination. The distinction between preparatory and definitive acts is a staple of EU administrative law. The distinction was central in the above-mentioned SCHUFA case, in which the Court found that classifying third party credit scoring as (only) a preparatory act to a subsequent credit decision would cause “a lacuna in legal protection” where the credit decision-maker would be unable to provide information on, and review the merits of, the automated credit scoring process.

The prepositional phrase “to an assessment” establishes that the preparatory task must be directed towards, and in service of, an “assessment.” This implies a temporal and functional sequence: first, the AI system performs a preparatory task; then, separately, an assessment takes place, using the output of the preparatory task. The use of the indefinite article “an” suggests the preparatory task must be tied to a specific assessment act, not a vague or diffuse process.

The term “assessment” itself is not defined in the AI Act, but its ordinary general meaning denotes an act of estimation or evaluation. In the context of the Annex III areas, “assessment” would refer to estimations and evaluations such as, but not limited to, a natural person’s state of mind, creditworthiness, insurability, suitability for employment, eligibility for social benefits, criminal risk, or medical condition, the state of critical infrastructure: water quality, highway traffic, power supply, the relevance of facts and laws in justice processes. The assessment task output would then in turn be input to the decision-making function that the high-risk regime seeks to regulate. Interestingly, unlike Article 6(3)(c), there is no specification that the assessment be a “human assessment”. An AI system could perform a preparatory task to an assessment by a (separate and different) high-risk AI system, and the former system would still qualify for the Article 6(3)(d) derogation condition.

The combined effect of these elements is that Article 6(3)(d) covers AI tasks whose outputs serve as inputs to functionally and temporally separate human- or AI-performed estimative or evaluative acts, without themselves constituting or pre-empting those acts.

3.3.2 Systematic interpretation of “preparatory task to an assessment”#s. 24

3.3.2.1 The distinction between the preparation stage and assessment stage#s. 24

The systematic context of the AI Act supports a clear functional separation between the preparation stage and the assessment stage. If the two stages are so intertwined that the AI system’s output effectively constitutes the assessment, the condition is not satisfied.

The distinction finds support in the broader architecture of Annex III. The high-risk categories in Annex III identify specific decision-making contexts – such as “AI systems intended to be used to evaluate the creditworthiness of natural persons” or “AI systems intended to be used by public authorities … to evaluate the eligibility of natural persons for public assistance benefits and services.” The verb “evaluate” in these descriptions denotes the assessment stage: the act of forming a judgment about a person’s situation. A preparatory task, by contrast, is one that provides the foundation on which the evaluation is performed – the visualised data, the retrieved documents, the translated texts – without itself performing the evaluation.

3.3.2.2 The role of human oversight and responsibility#s. 24

The systematic relationship between Article 6(3)(d) and Article 14, as for condition (a), has two implications.

First, for a task to be genuinely preparatory it must leave the human decision-maker in a position to conduct the assessment independently. If the output pre-structures the assessment – by filtering information, by ranking, or by issuing a recommendation the assessor must affirmatively reject – the system has shifted the cognitive burden, and the carve-out should not apply.

Second, the output of a preparatory task should be transparent and verifiable. Whether it is verifiable in fact depends on the assessor’s capabilities: an Urdu-to-Norwegian translation in an asylum case is preparatory only where the assessor has practical access to Urdu proficiency. The same AI system may therefore qualify in one deployment context and not in another, which makes it important that the provider documents the assumed “specific context and conditions of use” and that the deployer adheres to them, otherwise risking attaining provider obligations through the Article 25(1)(c) mechanism.

Similarly, if a system is classified as not-highrisk on the ground that its task is merely preparatory, the Article 14(4)(b) safeguards against “automation bias” do not apply. This is the case where the output is factual and verifiable (such as a list of documents or the above-mentioned translation example), but less so where the output is probabilistic and evaluative (such as a relevance score or an executive summary). In the latter case, the cognitive dynamics of automation bias mean that the AI system effectively contributes to the assessment, even if the assessor technically has access to the underlying data for review when making the assessment.

3.3.3 Teleological interpretation: the purpose and limits of excluding preparatory tasks from high-risk classification#s. 25

The purpose of Article 6(3)(d) parallels that of condition (a): to keep the high-risk classification from extending to AI systems whose function does not engage the interests the regulation seeks to protect. Its specific rationale is that many Annex III use cases involve multi-stage processes in which AI is deployed at the preparatory stage but not at the stage of evaluative judgment – for example, an AI database search for candidates matching formal recruitment criteria while a human interviewer performs the substantive suitability assessment, or AI-assisted retrieval and translation of case law while the judicial assessment remains the prerogative of the judge.

The purpose of the carve-out is thus to recognise that the high-risk regime is concerned with AI functions that bear on the substance of assessments and decisions affecting fundamental rights, and that functions which merely facilitate the administrative preconditions for such decisions – making information available, organising files, translating documents – do not require the same intensity of regulation. At the same time, the carve-out must not be allowed to become a vehicle for exempting decision-support systems that, in substance, perform or pre-empt the assessment. In any case the SCHUFA doctrine of GDPR Article 22, discussed in Section 3.2.2 above, provides an upper boundary by analogy: A task should not be considered genuinely preparatory in the context of Article 6(3)(d) if its output plays a “determining role” in the following assessment.

3.4 The distinction between “procedural” tasks and “preparatory” tasks#s. 26

What is perhaps less clear in the context of the AI Act is the distinction between the “procedural” tasks of Article 6(3)(a) and the “preparatory” tasks of Article 6(3)(d). As discussed above and in Section 3.2 they both share the characteristic of being separate from and not substantially affecting estimative or evaluative tasks, or the decision-making based on such assessments. Why did the legislator deem it necessary to include both Articles 6(3)(a) and (d) as separate conditions? An obvious difference is that Article 6(3)(a) contains no temporal qualification: A procedural task may well be performed after the assessment or decision to which it belongs, for instance to document and communicate the decision according to a set procedure. Apart from this, for tasks performed before an assessment or decision, “preparatory” casts a broad net that absorbs “procedural”: All preceding procedural tasks are by nature also preparatory, but not all preparatory tasks are merely procedural.

Recital (53) reinforces this reading by offering examples of tasks that may fall within the preparatory category. The recital mentions AI systems that constitute “smart solutions for file handling, which include various functions from indexing, searching, text and speech processing, or linking data to existing data sources, or AI systems used for translation of initial documents.” A shared feature of these “preparatory” examples compared to their “procedural” counterparts is that they create or significantly transform information to make more accessible and usable for a later assessment, without assigning evaluative weight. A search system creates indexing metadata to better facilitate the search for relevant files and insights. A transcription system converts audio into more easily searchable text. A translation system converts a document into a language the decision-maker can read. This is something more than purely procedural processing, but neither function involves judgments about the significance of the information for the outcome of an assessment.

As with procedural tasks, the preparatory boundary becomes contested where the AI system’s output does more than organise or present information – where it synthesises, ranks, transcribes, translates, or summarises in a way that structures the decision-maker’s cognitive field. A system that generates indexes that allow retrieval of documents matching a search specification and presents them in chronological or alphabetical order is preparatory – at least if the indexing/retrieval algorithm is formal and transparent. A system that retrieves documents and also highlights the passages deemed most “relevant” to a given assessment – thereby directing the assessor’s attention and framing the analysis – occupies an intermediate zone: Such a relevance classification might easily qualify as an assessment in itself. And a system that generates a summary “risk classification” or “recommendation” based on a synthesis of all the retrieved information has clearly crossed from pure preparation into the assessment stage.

3.5 “Profiling of natural persons” under Article 6(3) third subparagraph#s. 27

The third subparagraph of Article 6(3) establishes a categorical override to the carve-out mechanism: “Notwithstanding the first subparagraph, an AI system referred to in Annex III shall always be considered to be high-risk where the AI system performs profiling of natural persons.” This carve-out from the carve-outs is absolute, “always” underscores that it leaves no room for case-by-case risk assessment of profiling systems.

Article 3(52) ties the definition of “profiling” to GDPR Article 4(4): “‘profiling’ means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person’s performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements.”

The profiling override creates an important interaction between the AI Act and the GDPR. Because the AI Act imports the GDPR definition of profiling, developments in the interpretation of that definition – including guidance from the European Data Protection Board and future ECJ jurisprudence – will directly affect the scope of the Article 6(3) carve-out. The Article 29 Working Party (now the EDPB) adopted guidelines which interpret the concept of profiling broadly and emphasise that the evaluative element is a decisive criterion: processing that merely handles personal data without evaluating the person does not constitute profiling, while processing that draws inferences about personal characteristics does constitute profiling, even if no material decision follows immediately from the assessment. This interpretative guidance, while not binding, provides a relevant point of reference for the application of the profiling override under the AI Act.

A full review of the concept of “profiling” in GDPR is outside the scope of this thesis. For present purposes it suffices to note that the override is engaged whenever an AI task uses personal data within the meaning of GDPR Article 4(1) to evaluate personal aspects of a natural person. The list of aspects in Article 4(4) is illustrative and non-exhaustive: any automated evaluation of a personal aspect falls within the definition, whether or not the specific aspect is enumerated.

The term “evaluate” indicates such profiling would involve estimates and assessments that would in themselves quickly challenge the procedural/preparatory boundaries of the Article 6(3)(a) and (d) conditions. The override sets an absolute floor for the carve-outs: an AI system that evaluates personal aspects on the basis of personal data is always high-risk in an Annex III context, with far-reaching consequences in sectors whose core function is the assessment of individuals. For example, in creditworthiness evaluation, AI systems typically assess a person’s “economic situation” and “reliability” — both enumerated profiling aspects — and accordingly cannot benefit from the carve-out regardless of how the provider characterises the task. Health and life insurance prediction provide a parallel example. The categorical override forecloses case-by-case auditing of harmful profiling claims, confining the Article 6(3) carve-outs to purely administrative and logistical tasks without human-evaluative elements.