Mandatory vs voluntary standard
No standard is mandatory by birth; mandatoriness is conferred. The mechanisms vary by system: incorporation by reference into law, inclusion in a government-maintained mandatory list, citation under a technical regulation as the route to presumed conformity, or — the mechanism that catches people — citation in a contract or project specification, which makes a voluntary standard as binding as any statute for the parties who signed.
The mapping also differs by jurisdiction for the same document. A standard voluntary at home may be mandatory where it has been adopted into another country's regulation; interstate and international standards carry different statuses in each adopting state. A project's compliance obligations are therefore a matrix — document by document, jurisdiction by jurisdiction — not a property of the standards themselves.
The operational failure is the word "voluntary" doing too much work: a designer treating a spec-cited standard as optional guidance, or a reviewer demanding a standard that is voluntary and uncited. Both arguments end the same way — by finding the document that does or does not confer the obligation.
Related reading
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.