EU AI Act: Design the first AI interaction notice
Does the planned EU-facing chatbot make its AI identity clear at the first interaction?
Providers must design direct human interactions to disclose AI identity unless obvious to a reasonably informed, observant and circumspect person in context; notice must be clear, distinguishable and accessible at first interaction. Review implication: Map each user entry point, notice timing, accessibility and any reasoned obviousness exception before accepting the interaction design.
Legal status: CURRENTLY APPLICABLE — 2026-08-02
Provision: 50(1),(5);113 · Operator: Provider of a system intended to interact directly with natural persons
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Obviousness is contextual, not a blanket chatbot exemption. The authorised criminal-law exception has safeguards and does not cover public crime-reporting systems. A screenshot does not establish every channel works.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Separate machine-readable marking from visible labelling
Is a visible AI label alone enough for the provider marking decision on a newly marketed generator?
For covered systems placed on the market on or after 2 August 2026, outputs must be machine-readably marked and detectable as artificial; effectiveness, interoperability, robustness and reliability are required as technically feasible, considering content limits, cost and state of the art. Review implication: Request output-format and detection evidence rather than treating a visible caption as machine-readable provenance.
Legal status: CURRENTLY APPLICABLE — 2026-08-02
Provision: 50(2);111(4);113 · Operator: Provider of a synthetic audio/image/video/text-generating AI system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Article 50(2) has standard-editing/non-substantial-alteration and authorised criminal-law exceptions. Marks alone do not certify compliance or establish authenticity; legacy systems require the separate 111(4) check.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check the narrow legacy marking transition
Does this generator qualify for the temporary Article 50(2) marking deadline?
Article 111(4) gives providers of qualifying systems placed on the market before 2 August 2026 until 2 December 2026 to comply with Article 50(2). Review implication: Require dated placement evidence and system identity; do not extend this marking-only transition to other disclosure duties.
Legal status: TRANSITIONAL — 2026-12-02
Provision: 111(4) added by 2026/1744 Art 1(39)(b);50(2) · Operator: Provider of a synthetic-content AI system placed on the market before 2 August 2026
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Transition only concerns 50(2), not all of Article 50, and is not a permanent exemption. A release-note date alone may not prove placing on the market.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Test the claimed standard-editing exception
Does an editing-only claim justify excluding this output transformation from provider marking?
The marking duty does not apply to the extent a system assists standard editing or does not substantially alter deployer input data or its semantics. Review implication: Compare representative input/output transformations and feature scope before accepting an editing exception; separate unsupported feature modes.
Legal status: CONDITIONAL — 2026-08-02
Provision: 50(2);113 · Operator: Provider relying on an Article 50(2) exception
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- The words editing assistant are insufficient. Unknown extent of alteration blocks a conclusion; no blanket exception for all outputs of a multipurpose generator.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Identify notices for biometric categorisation or emotion recognition
What notice evidence is needed before deploying an otherwise lawful emotion or biometric categorisation feature?
Covered deployers must inform exposed persons of the system operation and comply with applicable data-protection law; notice must be clear, distinguishable, accessible and no later than first exposure. Review implication: Request exposure/notice mapping and the separate lawful-use assessment; disclosure cannot legitimise a prohibited use.
Legal status: CURRENTLY APPLICABLE — 2026-08-02
Provision: 50(3),(5);113 · Operator: Deployer exposing natural persons to an emotion-recognition or biometric-categorisation system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Article 50 is not permission to operate a prohibited system. Criminal-law exceptions are narrow and safeguard-dependent. No conclusion on actual processing or GDPR lawfulness from a notice alone.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Scope deepfake disclosure and artistic presentation
How should a publisher document its deepfake disclosure decision, including creative material?
For content constituting a deep fake, covered deployers disclose artificial generation/manipulation. Evidently artistic, creative, satirical, fictional or analogous work permits appropriate disclosure that does not hamper enjoyment; it does not remove disclosure entirely. Review implication: Assess whether the content meets the legal deepfake definition, then document format/timing of disclosure including the creative-work rationale.
Legal status: CURRENTLY APPLICABLE — 2026-08-02
Provision: 50(4) first subparagraph;50(5);3(60);113 · Operator: Deployer publishing AI-generated/manipulated image, audio or video constituting a deep fake
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Not every AI image is a deep fake. The authorised criminal-law exception requires its own basis. No authenticity finding, identity adjudication or blanket satire exemption is supplied.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check the editorial exception for public-interest text
Can this publisher rely on human review and editorial responsibility instead of the AI-text disclosure duty?
Covered public-interest text requires artificial-generation/manipulation disclosure unless a specified exception applies; editorial exception requires human review or editorial control AND a natural or legal person holding editorial responsibility. Review implication: Identify responsible publisher and actual review/control evidence; approval by an unnamed reviewer does not establish the combined exception.
Legal status: CONDITIONAL — 2026-08-02
Provision: 50(4) second subparagraph;50(5);113 · Operator: Deployer publishing AI-generated/manipulated text to inform the public on matters of public interest
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- The criminal-law exception is separate. This is not a general exemption for every human-edited document; provider marking duties are independently assessed.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Establish EU territorial connection for a UK organisation
Does this UK-only or EU-connected deployment fall within the relevant AI Act operator scope?
The Act includes providers marketing/putting systems into service in the EU, EU-established/located deployers, and third-country providers/deployers whose AI outputs are used in the EU, subject to Article 2 exclusions. Review implication: Map establishment, market/service placement, output use and operator roles before importing EU obligations into a UK procurement decision.
Legal status: CONDITIONAL — 2025-02-02
Provision: 2(1)(a)-(c),2(3),(6),(8),(10);113(a) · Operator: UK-established provider or deployer, or procurement reviewer assessing its role
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- UK incorporation alone neither establishes nor excludes EU scope. Research/defence/personal exceptions have exact boundaries; real-world testing is not covered by the pre-market research exclusion. No UK-only automatic EU duty.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check both product-safety classification conditions
Does a product-related AI feature meet the Annex I high-risk route, rather than merely belonging to a regulated product?
Article 6(1) requires both the product/safety-component link to Annex I legislation and a required third-party conformity assessment. New 1a-1c distinguish non-safety assistance and assessment for non-health/safety risks; malfunction endangering health/safety remains material. Review implication: Require the precise product law, safety-function analysis and assessment route; use Chapter III Sections 1-3 future date only after category checks.
Legal status: FUTURE OBLIGATION — 2028-08-02
Provision: 6(1),(1a)-(1c) as amended 2026/1744;2(2),(13);113(c)(ii) · Operator: Provider/procurement reviewer of an AI product or safety component
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- A regulated product or voluntary third-party audit alone is insufficient. Annex I SectionB has Article 2(2) limited application;2(13) is not a self-declared blanket waiver. Other law can already apply.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Document a claimed AnnexIII non-high-risk exception
What supports a provider claiming its Annex III system is not high-risk under Article 6(3)?
Article 6(3) requires no significant risk of harm and one specified condition, such as a narrow procedural or preparatory task. Profiling natural persons remains high-risk. Article 6(4) requires the provider assessment documented before placement/service and registration under 49(2). Review implication: Inspect intended task, influence over decisions and profiling before accepting a documented exception; an internal label is insufficient.
Legal status: FUTURE OBLIGATION — 2027-12-02
Provision: 6(2)-(4);113(c)(i) · Operator: Provider assessing a system within an Annex III use case
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- No conclusion without exact category and actual task evidence. Registration rules outside Sections 1-3 need their own applicability review; this record does not delay all of Article 49.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Set provision-specific readiness deadlines
Which deadline should this high-risk readiness plan assign to Chapter III Sections 1-3?
Amended 113(c) applies Chapter III Sections 1-3 except 6(5) from 2 December 2027 for 6(2)/Annex III systems and 2 August 2028 for 6(1)/Annex I systems. Article 111 may alter legacy-system treatment. Review implication: Tag each obligation with chapter/section, system route and transition instead of assigning one date to the whole Act.
Legal status: FUTURE OBLIGATION — 2027-12-02 / 2028-08-02
Provision: 113(c)(i)-(ii) replaced by 2026/1744 Art 1(40);111 · Operator: Provider/deployer programme owner
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c).
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c). Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- This is not a blanket delay for all high-risk duties. Articles 72/73 and other chapters need their own analysis; Article 50 and prohibited-practice duties are not postponed by 113(c).
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check the open-source exclusion boundary
Can a free open-source licence alone exclude this AI system from relevant AI Act duties?
Article 2(12) excludes systems released under free/open-source licences unless placed on the market or put into service as high-risk systems or systems falling under Article 5 or 50. Review implication: Check intended use and applicable exception categories separately from licence metadata.
Legal status: CONDITIONAL — 2025-02-02 scope;2026-08-02 Article 50
Provision: 2(12);113(a);50 · Operator: Provider/deployer or buyer of a freely licensed AI system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established.
An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- An open-source label is not a universal exemption. This system-level provision does not determine every GPAI-model obligation; Article 50 marking transitions still require separate assessment.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Assign competent and empowered human oversight
Does naming a reviewer establish the oversight arrangements needed for this planned high-risk deployment?
Article 26(2) requires oversight assigned to natural persons with necessary competence, training and authority, as well as necessary support. Review implication: Request role assignment, relevant training, decision authority and support arrangements; then distinguish documentation from observed intervention ability.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 26(2);113(c);111(2) · Operator: Deployer of a covered high-risk system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- A name or policy alone does not prove competence, authority or functioning supervision. Article 2/6/111/113 classification and transition gates apply; no current blanket duty asserted.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Assess design support for human intervention
What evidence supports a claim that an overseer can interpret, disregard, override or stop the system?
Article 14 provides risk/proportionality-linked oversight design measures enabling assigned people to understand capacities/limits, recognise automation bias, interpret outputs, override/reverse outputs and interrupt via a safe-stop procedure as appropriate to context. Review implication: Map each claimed intervention to a usable mechanism and boundary, without treating design documentation as proof of live enforcement.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 14(3)-(4);113(c);111(2) · Operator: Provider designing a covered high-risk system; buyer assessing supplied design evidence
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- No determination of effective permissions, runtime safety or legal compliance. A button label is not evidence of successful safe interruption; risk and operating context matter.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Scope a fundamental-rights assessment and DPIA reuse
Is this deployer within the FRIA scope, and can existing DPIA material cover particular elements?
Article 27 covers specified public-law/public-service deployers and Annex III5(b)/(c) deployers, excluding Annex III point 2. Assessment is before deployment/first use, with updates for changed elements; amended 4 permits relevant DPIA cross-references or incorporated sections where requirements are already met. Review implication: Check deployer/use-case eligibility, then map each required FRIA element to actual evidence; do not equate a DPIA title with complete coverage.
Legal status: FUTURE OBLIGATION — 2027-12-02 subject to 111
Provision: 27(1)-(5),including amended 4-5;113(c)(i) · Operator: Covered Article 27 deployer of an Article 6(2) system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Not every enterprise requires a FRIA under 27. Reuse is element-specific; notification/template/exemption requirements remain separate. No fundamental-rights clearance or legal opinion.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check whether operating instructions support the proposed use
Do the supplied high-risk-system instructions contain enough specific information for this planned operation?
Article 13 requires accessible, comprehensible instructions covering purpose, tested performance/limitations, relevant risks, appropriate input/output information, predetermined changes, oversight, resources/maintenance and relevant log mechanisms. Review implication: Build a gap map against the proposed use and system version; separate documented performance claims from independently observed results.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 13(2)-(3);113(c);111(2) · Operator: Provider supplying instructions and deployer/procurement reviewer
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- A model card or marketing sheet is not necessarily complete instructions. This does not establish actual performance, permitted deployment or legal compliance.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Identify the deployer-controlled log retention boundary
Can a supplier retention setting establish that the deployer retains its required high-risk-system logs?
Article 26(6) addresses automatically generated logs to the extent under deployer control, for an intended-purpose-appropriate period of at least 6months unless applicable Union/national law provides otherwise, particularly data protection. Review implication: Map log custody, automatic generation, retention and competing applicable requirements before relying on a supplier dashboard setting.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 26(6);113(c);111(2) · Operator: Deployer of a covered high-risk system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- No universal rule to retain all personal data 6months. Supplier retention does not prove deployer access or complete event history; exact scope and transition gates apply.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Keep the technical documentation aligned with the system
What evidence supports that the system technical documentation was prepared before placement and kept current?
Article 11 requires pre-market/service technical documentation kept up to date, supplying Annex IV information; eligible SMEs/startups/SMCs may use simplified provision only via the prescribed Commission form. Product systems under Annex I Section A use a combined documentation set. Review implication: Check version/change linkage and evidence completeness rather than accepting a stale file or an invented simplified form.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 11(1)-(2) as amended;113(c);111(2) · Operator: Provider of a covered high-risk system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Documents do not demonstrate actual compliance automatically. No 10-year retention assertion here; that is a separate Article 18 duty. No assumption a Commission form exists or self-created form qualifies.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Check whether legacy high-risk treatment survives a design change
Does the pre-existing system qualify for the legacy transition after a later design change?
Article 111(2), without prejudice toArticle 5 and excluding 111(1) systems, applies the Regulation to qualifying older high-risk systems only if significant design changes occur from the relevant Chapter III application date; providers/deployers of systems intended for public authorities must take steps to comply by 2 August 2030. Review implication: Preserve the before/after design, placing/service date and use context; evaluate significance rather than using a version label as the trigger.
Legal status: TRANSITIONAL — Relevant Chapter III date;public-authority deadline 2030-08-02
Provision: 111(2) replaced by 2026/1744 Art 1(39)(a);113(c) · Operator: Operator of a high-risk system predating its applicable Chapter III date
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- Recital 177 explains significant design changes as equivalent in substance to substantial modification. Assess the actual design and intended-purpose change, not a version label alone. No blanket grandfathering or Article 5 exemption.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice
EU AI Act: Prepare the deployer response to a risk indication
What response evidence is needed when a deployer has reason to consider the system presents Article 79(1) risk?
Under 26(5), deployers monitor on instructions; where they have reason to consider instructed use may present 79(1) risk, they inform provider/distributor and relevant market-surveillance authority without undue delay and suspend use. Serious incidents have additional immediate notification rules. Review implication: Map risk trigger, accountable suspension authority and notification path; retain actual timestamps separately from written procedures.
Legal status: FUTURE OBLIGATION — Annex III 2 December 2027;Annex I 2 August 2028 subject to scope/transitions
Provision: 26(5);113(c);111(2) · Operator: Deployer of a covered high-risk system
Subject to Article2 EU scope; UK-only activity is not automatically in scope; exact role, purpose and exclusions must be established. High-risk readiness statements require the applicable Article 6 route and Article 111 transition. Annex I Section B has the limited Article 2(2) regime; Section A limitations under Article 2(13) require the relevant delegated measure, not a self-declared waiver.
This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed.
Law and documentary evidence are separate from observed implementation. No individual compliance determination or legal advice.
Documentation reviewed 2026-11-14. Primary source.
Boundaries
- Buyer-specific applicability, actual implementation and compliance are not independently demonstrated.
- This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed. Refuse a determination if operator, territorial connection, classification, applicable date or necessary factual evidence is unresolved.
- This does not establish that a risk or reportable incident actually occurred, nor resolve provider Article 73 deadlines. A procedure is not evidence it was executed.
- No supplier approval, legal advice, certification, runtime verification or new paid capability.
Complete record JSON · Exact free preview JSON · Source review
Required source attribution and distribution notice