Sweden's new AI standard is here – how to get started

What the standard does

EN 18286 is a guide to building the quality management system required for high-risk AI ^[1]. If you provide AI for credit scoring, hiring, biometric identification, law enforcement or any of the other areas in Annex III, the AI Act will require you to have quality management in place from 2 December 2027 ^[2].

The Act itself says what must be managed: risk, data, documentation, monitoring and human oversight. It doesn't say how. EN 18286 fills that gap. Think of it like this: if the AI Act is the rule that you must keep a kitchen clean, the standard is the checklist for how you actually do it.

The standard maps Article 17 of the AI Act to a structure most quality professionals already know. If you have ISO 9001, much of the groundwork is already there. If you don't, the standard gives you a place to start.

Why it matters now

High-risk requirements come into force in just over a year. That sounds like time, but it isn't. You need to set up processes, document them, train people and, if you are in one of the areas where third-party assessment is required, arrange a conformity assessment with a notified body ^[2].

The standard is voluntary, but it is the clearest roadmap available. Notified bodies are likely to check whether your quality system follows it, even if they don't have to.

There is also a practical reason to act early. If your high-risk AI makes decisions about people, those decisions will be questioned, and the questions tend to come months or years later. A quality system built now means you can show, when the time comes, that your processes were sound on the day the decision was made.

What this means for you

If you provide high-risk AI, start by reading EN 18286 alongside Article 17. The standard is published by SIS and available for purchase ^[1]. You don't have to follow it word for word, but you do have to meet Article 17, and the standard is the map most people will use.

Here are the first questions to ask:

• Which of your AI systems count as high-risk under Annex III?
• Do you already have a quality management system, and if so, what needs adding to meet Article 17?
• Who in your organisation will be accountable for AI quality, and do they have the training and authority?
• Where are your gaps in risk management, data governance, technical documentation and logging?

If you already follow ISO 9001, much of the work is mapping: showing where your existing processes meet the AI Act's demands and where they need extending. If you don't have ISO 9001, EN 18286 is still a usable guide, but you will be building more from scratch.

One piece often overlooked is logging. Article 12 requires high-risk AI systems to allow for the automatic recording of events over their lifetime ^[3]. The logs must exist, and later, when a decision is questioned, they must hold up. A log your own staff can quietly edit is easy to challenge. That is where a digital witness fits.

Making logs hold up

Say a lender's AI declines a credit application. Six months later, the applicant asks for an explanation and disputes the decision. The quality system says the decision was logged. The question is whether the log can be trusted.

Here, the thing to seal is each decision record as it is written to the log: the applicant reference, the model version, the score and the reviewer, if there was one. Sealing takes a fingerprint of the record, not the record itself, so the data never leaves your systems. If it is challenged half a year later, anyone you share the record with can check that it is the one written on the day.

Internal audit can check it, a supervisor can check it, and if it reaches a hearing, a court can check it. The fingerprint is sealed on WitniumChain, a public chain where any change would show, even one made by us. That is the point: fewer people to trust, more things anyone can verify.

What it shows is that the record is exactly what was written at that time. What it doesn't show is that the decision was fair, lawful or correct. Those are separate questions, and they matter, but they rest on having a log people can actually rely on.

You seal records through the REST API, the SDK or the MCP server. The content stays with you. The first 2,000 witnesses a month are free. Read more in the documentation.

What to watch

The date to keep in mind is 2 December 2027, when the high-risk requirements under Annex III come into force ^[2]. Between now and then, the European Commission is expected to publish codes of practice and additional guidance on Article 17.

Notified bodies are being designated, and their assessment procedures are being finalised. If your AI requires third-party conformity assessment, contact a notified body early. Waiting until late 2027 means joining a queue.

EN 18286 itself may see updates as the first wave of assessments reveals what works and what doesn't. Standards are living documents.

For now, the task is simpler than it sounds: read the standard, map your systems to Annex III, and start building the quality management you will need in a year's time. The Act is long, but the first step is always the same: know which of your AI systems it covers.