Revolutionising access to construction standards

Why construction is the last industry to digitize

Chris opened by noting that construction ranks among the least digitized industries globally. The reason it has lagged behind is not a shortage of tools - it is that the stakes of getting it wrong are different. As he put it during the fireside chat: "we're literally in an industry where you cannot move fast and break things." In sectors where errors are reversible, rapid iteration is viable. In construction, mistakes in standards compliance can have safety consequences, which means digitization has to happen through partnerships and careful validation rather than unilateral disruption.

Standards Australia faces a parallel challenge on the content side. Daniel described users now expecting rapid access similar to "Google or YouTube" rather than scrolling through PDFs. A one-size-fits-all standard, he noted, does not meet diverse industry needs in the digital age. For fast-moving areas like cybersecurity and digital connectivity, Standards Australia cannot wait twelve to eighteen months for traditional committee processes. The organisation is exploring technical specifications and alternative pathways to get standards content into the field faster.

The PDF problem and the cost barrier it created

Before the Calcs.com integration, engineers who needed to reference a standard they did not own faced a binary choice: purchase the document or skip the check. Chris described this as a "risk and confidence gap." Obscure or specialist standards were particularly affected: engineers could not justify buying an entire PDF for a single clause in an edge-case project.

Calcs.com addressed this by treating standards as interconnected components rather than isolated documents, offering all National Construction Code referenced standards with hyperlinked access under a single platform subscription. New materials like cold-formed steel were added by user request - engineers signalled what they needed, and the cost barrier that had previously held them back was removed. Standards that previously sat behind a per-document paywall became part of the daily workflow.

Turning standards from documents into structured data

Daniel described a fundamental shift required in how Standards Australia develops content. Historically, standards were "developed to be read" - designed as narrative documents for sequential human reading. Treating that same content as a database requires structural changes that cannot easily be retrofitted after the fact.

He used a direct analogy: "trying to turn a hamburger back into a cow" is difficult. It is far more practical to approach digitization from the start of a standards development cycle than to convert finished documents. For Standards Australia this means rethinking how committees structure content from the outset, not just changing the delivery format at the end of the process.

How easy access changes what engineers actually do

Chris described a straightforward behavioural observation: "if you put a bag of potato chips at eye level, you're more likely to have it. So hopefully the potato chips are standards." When access requires a context switch - opening a separate viewer, searching a PDF, locating the right clause - it introduces friction that makes shortcuts more likely. When the relevant clause is embedded alongside the calculation that depends on it, engineers read it.

The user feedback Chris reported reflected this. Senior engineers were enthusiastic specifically about training junior staff: accessible standards meant juniors could see the underlying code reference rather than treating a tool's output as a black box. Engineers who had previously been copying, pasting, and building personal standards compilations found that bookmarking, hyperlinking, and natural language search addressed those workarounds more directly.

Institutional knowledge, feedback loops, and the decade ahead

Daniel pointed to a gap that Standards Australia committees typically lack: data on how standards are used in practice. Engineers build up marked-up personal copies over years, capturing edge cases, interpretations, and field knowledge. That institutional knowledge has historically been trapped in individual annotated PDFs, invisible to the committees writing the next edition.

The platform integration creates a feedback channel that did not previously exist: real-world usage patterns, compliance challenges, and implementation questions can surface from the platform back to the committee. Daniel predicted "nine thousand new standards over the next decade" - a volume that makes that feedback loop increasingly important.

Both speakers noted the potential for AI-assisted standards navigation, while acknowledging that current tools still get technical details wrong often enough to warrant care. Daniel framed it as a genuine opportunity if approached carefully: "AI powered assistance that might provide trusted accurate insights using the standards." Chris grounded the near-term ambition more simply - standards integration should reduce the lookup and procedural work so engineers spend more time thinking than searching, freeing capacity for the parts of the job that actually require engineering judgement.