At first glance, the phrase standards publishing sounds straightforward: create a document that tells people how to do things consistently and share it with the world. But anyone who’s ever tried to access or compare technical standards knows it’s far more complicated. Why? Because standards publishing is not standard.
One of the root causes is the sheer number of independent organizations involved. Bodies like the International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and IEEE all produce standards, but each uses its own style, structure, numbering, and publishing workflow. This diversity reflects different industry needs. A hardware safety standard looks nothing like a management systems standard, and publication formats vary accordingly.
Another important reason standards publishing isn’t uniform is business model. Unlike open academic publishing, most technical standards are sold as proprietary documents to help fund standards development work. That leads to inconsistent pricing, variable access rights, and licensing arrangements that differ from one body to another.
Legal factors further complicate the picture. When a standard becomes part of regulation in one country but remains voluntary elsewhere, questions arise about copyright, public access, and distribution. Policies differ internationally, so the same standard may be freely available in one jurisdiction yet behind a paywall in another.
Recent developments discussed at the SPAB 2026 conference hosted by Accuris highlighted additional forces shaping standards publishing today. The annual SPAB gathering brings together standards development organizations, publishers, technology providers, and customers to collaborate on shared challenges and future directions. This year’s theme, “From Standards to Systems: Building the Interoperable Future”, underscored how the industry is transitioning from static documents to dynamic, connected data ecosystems.
Speakers at SPAB emphasized that standards are increasingly expected not just as PDF files but as data that can be integrated directly into engineering systems, compliance tools, and even artificial-intelligence workflows. This shift toward smart standards aims to improve discoverability, usability, and interoperability — but it also reveals why publishing hasn’t been “standardized” up to now. Organizations are operating at various levels of digital maturity, using different technical infrastructures and formats, from traditional text documents to machine-readable data structures.
The discussions also reinforced that collaboration matters. SPAB’s half-century of annual meetings has helped bridge gaps between standards creators and end users encouraging broad engagement, shared technologies, and harmonization efforts without mandating uniformity.
In short, standards publishing reflects a complex ecosystem of diverse stakeholders, funding models, legal frameworks, and technological transformations. It isn’t “standard” because it was never meant to be a single, monolithic process. It is the product of ongoing negotiation among communities, industries, and technologies.
If you are a standards publisher stuck in a PDF world and need help with your digital transformation initiatives, the team at Impelsys can help!
For over 25 years, we’ve helped organizations move from print to digital and who now leverage our AI to publish and distribute their content more efficiently than ever before. See for yourself why standards bodies and certification organizations leverage our mon’k adaptive learning platform to train and certify millions of professionals every day.
Authored by – Barry Bealer
