SES Annual Conference 2026: the new life of a standard

For most of their history, standards have had a clear destination: the PDF. Write the content, reach consensus, and publish the document. Job done.

But the world that consumes standards has changed. Compliance is no longer primarily a human reading a document and making a judgment call. It is engineers’ querying requirements across a portfolio. It is procurement systems checking conformance at scale. It is AI assistants in regulated industries answering questions that used to require a specialist and half a day. It is regulators expecting to integrate standards into digital frameworks rather than print them out.

In that world, the PDF is not the end product. It is a rendering, one output among many. The real end product is something more valuable: structured, queryable, reusable knowledge that can flow into the systems and processes where decisions actually get made.

This is what the shift to structured standards development is really about. And at this year’s SES Annual Conference in Ottawa, session after session circled back to the same underlying tension: the gap between how standards are created and how they are actually used is widening, and the costs of that gap are growing.

The gap between creation and use

One of the sharpest observations at SES came from a session on digital transformation: standards creation and standards consumption have become disconnected, even though the value of a standard depends entirely on linking them end-to-end.

Think about what happens today. A committee spends months, sometimes years, reaching careful consensus on the meaning of a requirement. The intent is precise. The nuance is deliberate. That meaning is then encoded in prose and published as a PDF.

Downstream, an engineer in a regulated industry tries to extract what applies to their product. A compliance system tries to map requirements to controls. An AI assistant tries to answer a question about applicability. Each of them is now in the business of interpreting the document, because the document is all there is.

If the committee did not govern interpretation explicitly, others will do it for them. The consensus that took months to build starts to dissolve at the point of use.

The opportunity is to change this. Not by producing better PDFs, but by making the knowledge inside a standard directly operational. Available to the people and systems that need it, in the form they need it, without requiring each user to re-interpret prose from scratch.

Standards as operational intelligence

When a standard is built as structured knowledge rather than a formatted document, something shifts fundamentally. Requirements become individually addressable. Terms can be reused and queried across a portfolio. A single source of content can flow to a website, a PDF, an API, a compliance tool, or an AI system. Simultaneously, consistently, from the same authoritative source.

The committee’s intent travels with the content. The meaning does not have to be reconstructed at every point of use.

This is what “operational intelligence” means in practice. It means a procurement manager can ask which requirements apply to a specific product category and get a governed answer. It means a regulatory body can integrate standard requirements into a digital framework without manually re-entering text. It means an SME entering a new market can find what applies to their situation without needing to hire a specialist to read the document for them.

At SES, this was framed precisely: the goal is not machine readability for its own sake. The goal is ensuring that the meaning the committee created reaches the people and systems that need to act on it. Intact, without distortion, without requiring each consumer to start interpretation from scratch.

Who gets Included when standards become more usable

There is an inclusion dimension to this shift that deserves more attention than it typically gets.

Document-centric standards development is, structurally, a system that favours the well-resourced. Large organizations can afford specialists who know how to read and navigate complex technical documents. National bodies with small secretariats cannot always provide the same level of support. Companies entering new markets for the first time face a steep barrier just to understand what applies to them. Non-English-speaking experts face additional friction at every stage.

When standards become structured operational knowledge, many of these barriers fall.

Guidance that is queryable and searchable is more accessible than a 200-page PDF. Content that can be translated reliably, because it was written precisely and structured consistently, reaches more language communities. Requirements that can be delivered through familiar digital interfaces, without requiring a reader to know how a standards document is organized, open the door to participants who were previously excluded not by lack of expertise but by lack of access.

Multiple SES sessions touched on this. The challenge of SME participation, companies representing 95% of global businesses but often unable to engage with the standards system because of complexity and cost, is partly a usability problem. Online tools and digital delivery reduce barriers. Structured content makes those tools far more effective.

The accessibility session made a related point about representation in standards development: the process itself needs to be accessible, not just the final document. When authoring environments are browser-based, collaborative, and designed to guide rather than assume expertise, more people can contribute. When a committee member no longer needs to master the formatting conventions of a Word template to participate effectively, the threshold for meaningful contribution drops.

This is not incidental to the transition. It is one of the strongest arguments for it.

The transition is already underway

ISO and IEC have made governance decisions that signal where this is heading. New deliverables default to structured authoring from January 2025, with more than 75,000 committee experts expected to work in these environments during the year. The question for every standards organization is not whether this transition is happening, but how to navigate it in a way that captures the full opportunity.

The organizations that do this well will treat it as what it is: a shift in how knowledge is produced, governed, and delivered, not a software upgrade. The technology is the enabler. The real work is understanding what it means to build standards that are not just authoritative, but useful: findable, queryable, integratable, and accessible to the full range of people and systems that need to act on them.

Standards bodies have always existed to serve the public interest. In a world where decisions are increasingly made by systems rather than people reading documents, the question is whether the knowledge those standards contain can reach that world in a form it can actually use.

That is what the shift from documents to decisions is really about.