Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

Harmonised Standards and the AI Act: Why CEN-CENELEC Delays Change Your Compliance Plan

The EN standards meant to make AI Act compliance self-evident are arriving slowly. What presumption of conformity is worth today, and the routes that still work when no standard covers your system.

Renomira Team · 11 min read
A caliper measuring gemstones with handwritten notes nearby
Photo: Mauro Cateb / CC BY-SA 3.0 via Wikimedia Commons

The AI Act assumes a steady supply of harmonised European standards — published EN documents that turn essential requirements into clauses you can conform to, and in doing so earn a presumption of conformity. That supply has not arrived on schedule: CEN-CENELEC’s Joint Technical Committee 21 has published a handful of EN standards while the core set — risk management, data governance, transparency, human oversight, accuracy, robustness and cybersecurity — sits mostly in draft. For a mid-market company, that gap changes which compliance route you can take and how your December 2027 plan is sequenced.

What harmonised standards do under Article 40

Article 40 is the legal hook. It obliges the Commission to issue standardisation requests — formal mandates under Regulation (EU) No 1025/2012 — calling on the European standardisation organisations to draft harmonised standards covering the Act’s essential requirements. The standards are voluntary; nobody is forced to apply them.

The value is defined elsewhere. Article 40 creates the standards, but Article 42 defines their effect. Only conformity with a harmonised standard published in the Official Journal produces a presumption — a draft gives you foresight, not a defence.

Coverage is conditional and partial. The presumption extends only to what the standard addresses. A risk-management standard silent on logging depth gives you presumption on risk management and none on logging. Partial coverage is the norm.

The standardisation request — and why CEN-CENELEC slipped

The mandate is specific. The Commission’s standardisation request names CEN, CENELEC and ETSI, with JTC 21 doing most of the drafting, and sets which requirements to cover, in what order, and by when.

Mandate deadlines are targets, not law. Delivery follows the bodies’ own consensus procedures — committee draft, public enquiry, comment resolution, vote — on volunteer technical experts, a small, contested pool for AI. JTC 21’s programme spans terminology, trustworthiness, risk management, data quality, testing and documentation: much of Annex IV’s territory. Breadth plus consensus equals delay, and forecasts have been revised repeatedly through 2025 and 2026.

Obligations did not slip with them. The Digital Omnibus moved Annex III high-risk duties to 2 December 2027, absorbing part of the gap, but prohibitions, AI literacy, transparency and penalties are already live. A delay in publication never delays the obligation — assume EN coverage is still incomplete for employment, credit and education AI in December 2027.

What Article 42’s presumption of conformity is really worth

It is conditional. A provider benefits only where the system conforms to harmonised standards cited in the OJ, to the extent they cover it. Strict triggers: harmonised, published, applied.

It is rebuttable. Market-surveillance authorities can demand further evidence where they doubt conformity — a flawed test methodology, a standard applied outside its scope, or a system changed since assessment. Presumption is a procedural advantage, not immunity.

Deployers gain less than providers. Presumption attaches to the system as placed on the market. It does not discharge your Article 26 duties — human oversight, input-data relevance, logging, worker information — nor Article 4 registration or an Article 27 FRIA where triggered. Most mid-market companies are deployers.

Today’s real value is argumentation quality. Where no EN applies, auditors scrutinise rather than refuse your documentation. Aligning your Annex IV file to a draft standard’s clause structure makes self-assembled evidence legible to an external reviewer.

Compliance routes when standards are missing

Five routes exist; the trade-off is between what you inherit and what you author.

Route Legal basis What you must produce Evidence burden
Apply published EN standards Art. 40 + Art. 42 Assessment against OJ-cited clauses Low–moderate
Partial standards plus own documentation Art. 40 for covered clauses, Annex IV for the rest Assessment on covered parts, full documentation on gaps Moderate–high
Internal control, no standards Art. 43 + Annex VI Complete Annex IV file, testing evidence, QM system, written rationale High
Common specifications Art. 41 implementing act Conformity with the specification as adopted Moderate
Codes of practice Art. 56 (GPAI) Adherence evidence and documentation Moderate–high

Two points. No route removes technical documentation: Annex IV is the floor, and routes differ only in how much argument the standard carries for you. And common specifications are underused — Article 41 lets the Commission adopt technical details by implementing act where standards are insufficient, and conformity with them is citable today.

Conformity assessment under Article 43 without a standard

Article 43 fixes the procedure. For most Annex III systems it is internal control under Annex VI: the provider assesses, compiles technical documentation, issues the Article 47 declaration and affixes CE marking. Deployers do not run it — but must obtain and verify it, so your vendor’s route is a procurement question.

Internal control without a standard means self-defined adequacy. Annex VI asks you to show documentation demonstrates conformity. With no EN defining “adequate” robustness testing, you define it, justify it, and evidence consistent application. Documented methodology substitutes for standardised methodology.

Expect reasoning, not just artefacts. Whether the reviewer is an ISO 42001 auditor, a buyer’s assessor or a market-surveillance officer, the question is what threshold you applied, why, and who approved it. Cite a draft standard or sector guidance and a weakness becomes a documented decision.

Vendor contracts are the bottleneck. A provider waiting on ENs to finish assessment makes their slippage your dependency. Ask in the contract for their Annex IV status and intended route, plus change notification.

The fallback stack: documentation, Article 41, codes of practice

Start from Annex IV and work outward. System description, design specifications, data governance, oversight design, accuracy and cybersecurity validation, post-market monitoring — Annex IV is effectively a specification for a complete compliance file. Build it first and map EN clauses on later: Annex IV will not change, ENs still might.

Use common specifications where they exist. Track the Official Journal and sector implementing acts under Article 41 — the fastest-moving substitute for late standards.

Codes of practice cover a narrower slice than assumed. Article 56 codes serve general-purpose AI model obligations — the GPAI Code of Practice is the worked example, not a conformity route for Annex III systems. Where a code does apply to your stack, adherence plus documented downstream measures is defensible.

Scaffolding still helps. National market-surveillance guidance, sector regulators and ISO/IEC 42001 give structure. None creates an Article 42 presumption, but together they answer the question a standards gap leaves open.

What the delay means for a December 2027 plan

Sequence around dependencies, not publication. Register and classification reasoning first — nothing else can be scoped without it. Then the Annex IV file per system, which takes longest and needs vendor input. Standards mapping comes last: when an EN reaches the OJ, you run existing evidence against it rather than restarting.

Budget for authorship. Teams that treated standards as an outsourced solution will find themselves writing risk methodologies, validation protocols and oversight designs internally — legal and engineering hours. Name it in the plan now, not in October 2027.

Plan two passes. Pass one, before 2 December 2027, produces the register, the documentation and a defensible self-assessed position. Pass two, as EN coverage matures, maps that evidence to published standards and claims presumption. Design pass one so pass two is a mapping exercise, not a rewrite.

Do not let the gap become a delay narrative. “We are waiting for the standard” is not a position a market-surveillance authority accepts, and buyer questionnaires have no checkbox. The obligations are defined; only the shorthand for proving them is late.

How to check your own position

  1. List what you expected a standard to cover. Walk each system against Annex IV and its applicable articles. Mark every line reading “per the EN standard”: an open dependency.
  2. Confirm what is published in the OJ. Drafts confer no presumption. Anything still a prEN moves to your own-documentation column today.
  3. Record the conformity route per system. Annex VI internal control, notified body where required, or partial-standard-plus-gap — with the rationale in your register.
  4. Check vendor status. For each in-scope tool, get their intended route, Annex IV status, and a commitment to notify you when an EN is applied. No answer means unconfirmed.
  5. Check for Article 41 common specifications. If any cover your area, conformity is available now and shortens your evidence burden.

If most marks land in the “waiting on a standard” column, you have a documentation project, not a standards-watching problem.

Frequently asked questions

What are harmonised standards under the EU AI Act?

Voluntary European standards the Commission requests from CEN, CENELEC and ETSI under Article 40, drafted mainly by CEN-CENELEC JTC 21 and cited in the Official Journal. Conforming gives a provider a presumption of conformity with the essential requirements they cover, under Article 42. Not applying them is lawful; you demonstrate conformity directly against the Act.

Will EN standards be ready before December 2027?

Only partially. JTC 21 has published a limited number of EN standards while much of the core set remains draft. Assume coverage for Annex III uses such as employment, credit and education is incomplete when duties apply on 2 December 2027, and build your evidence on Annex IV documentation.

What if no EN standard covers our system?

Conformity remains possible. Article 41 common specifications, where adopted, provide citable technical detail. Otherwise it is Article 43 with Annex VI internal control: full Annex IV documentation, a quality management system, testing evidence, and a written rationale for your thresholds.

Does presumption of conformity cover deployers too?

Mostly not. Article 42 attaches to providers placing a conforming system on the market. Deployers carry Article 26 duties — human oversight, input-data relevance, logging, worker information — which no standard discharges for you. Your benefit is indirect: you inherit stronger vendor documentation.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

harmonised standards ai actcenelec ai act standardisationai act presumption of conformity standardsen standard ai act timelineai act standards gaps 2027conform to harmonised standards ai actstandardisation request ai act

Keep reading