Skip to content

Technical regulation

Last reviewed:
A government-issued document laying down mandatory requirements for products or their related processes, with which compliance is compulsory as a matter of law rather than choice.

Technical regulation is the top layer of the modern two-layer architecture used by the EU, the Eurasian Economic Union and others: the regulation states the essential, mandatory requirements — safety, health, environment — and stays deliberately general, while voluntary standards underneath it provide detailed methods whose use grants a presumption of conformity with the regulation. Follow the listed standard and you are presumed compliant; follow another route and you carry the burden of demonstrating equivalence yourself.

The architecture's purpose is to keep the law stable while the technology moves: regulations change rarely, the standards lists under them update continuously. Its price is that compliance becomes a two-document question — what the regulation requires, and which standards currently deliver presumption — and the second half moves.

The recurring confusion is between the layers: citing a standard where the regulation is the legal obligation, or treating the regulation's general language as satisfiable without any recognised method at all. On cross-border projects, add a third confusion — assuming the layers divide the same way in every system. They do not.

See this workflow in practice.

Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work.