How to Read a Harmonized Standard the Way an Assessor Will
The document is voluntary. The verbs are not. Ten checks that decide whether your conformity file survives contact with enforcement.
Executive Summary
The AI Omnibus deferred the high-risk obligations — Annex III systems to 2 December 2027, Annex I embedded systems to 2 August 2028 — and the stated reason was that the harmonized standards weren’t ready. Read that carefully. The extra time wasn’t granted to you. It was granted to the standards pipeline.
The texts moving through enquiry and finalization now are the documents your conformity file will be assessed against. Once a standard’s reference is cited in the Official Journal, compliance with its normative clauses confers presumption of conformity with the essential requirements those clauses cover — the burden of proof shifts in your favor. That is the entire value of the document, and it attaches to a fraction of the text: the sentences that bind, read the way an assessor reads them.
This piece delivers that reading. One governing test, the verb hierarchy that carries it, ten checks that expose where a requirement dissolves — and a worked example showing the difference between a conformity file that survives the question and one that becomes the exhibit.
The comfortable version of standards reading ends here. The assessor’s version is below.


