Skip to content

Regulatory Pulse

First AI Act harmonised standard: EN 18286 links quality management to Article 17

A newly cited standard provides a scoped presumption of conformity for high-risk AI quality-management requirements—not full AI Act compliance.

European Union / AI Act
AI governance, quality management, evidence and conformity
Guidance
Official source reviewed

PrivacyBuilt Editorial · Source published Harmonised standard reference announced · Reviewed 20 October 2026 · 6 min read

The 60-second summary

On 19 October 2026, the Commission announced the first AI Act harmonised standard reference: EN 18286:2026, supporting Article 17 quality-management requirements. Its use supports a presumption of conformity only for requirements it covers. It complements existing management systems rather than replacing them. Teams should obtain the standard and map the actual system, controls and evidence before making conformity claims.

Timeline that matters

  1. 19 October 2026

  2. Applicable system timetable

  3. 27 October 2026

What changed

A cited standard now provides a defined Article 17 conformity route.Existing management-system work should be mapped to covered requirements rather than treated as blanket compliance.

Who should care

Providers planning high-risk AI market accessQuality-management and product ownersLegal and conformity-assessment specialistsSuppliers contributing lifecycle evidence

Why this matters for global organisations.

AI assurance needs a documented link between applicable requirements, lifecycle controls and retained evidence. Map existing management systems to the actual product rather than assuming an organisation-wide certificate resolves every obligation.

13 actions to start now

  1. Determine provider role and system classification with counsel.
  2. Identify the applicable legal timetable.
  3. Obtain the official standard and current citation details.
  4. Record covered requirements and any conditions or exclusions.
  5. Inventory existing QMS controls and certifications.
  6. Map each relevant requirement to a system-level control.
  7. Assign evidence and approval owners.
  8. Trace data governance and supplier inputs across the lifecycle.
  9. Identify gaps requiring specialist review.
  10. Test representative controls and change handling.
  11. Review conformity claims against evidence and coverage.
  12. Plan ongoing maintenance after material system changes.
  13. Retain the mapping and independent review decisions.

Evidence worth retaining

  • Role and classification assessment
  • Standard edition and citation record
  • Requirement-to-control mapping
  • QMS scope and gap register
  • Lifecycle and supplier evidence
  • Control-test results and approvals
  • Conformity-claim review and change history

Questions to take to counsel or your conformity team

These are discussion prompts, not legal advice or conclusions.

  • Which precise Article 17 requirements are covered?
  • What does the existing QMS leave unaddressed?
  • Which other AI Act duties still require evidence?
  • What assessment route applies to the actual system?
  • Which changes require the mapping to be revisited?

Official sources

PrivacyBuilt / PrivacyBuilt is an independent educational publisher. It is not affiliated with, or endorsed by, any regulator or the European Union.

PrivacyBuilt publishes educational and technical guidance. Nothing on this site constitutes legal advice, and it should not be relied on as a legal determination for your organisation.