35 Years in Digital Construction with John Benstead

The first decade of BIM in Australia was largely spent arguing about geometry. Model sizes, LOD thresholds, hardware that couldn't keep up. Those were real constraints, but they were the wrong conversation. The right one was always about information: what decisions does it need to support, who will use it, and when?

John Benstead, Digital Engineering Manager at School Infrastructure New South Wales, has spent more than 45 years working through every major shift in digital construction, from toolmaking precision in the UK, to GIS implementation across nine European countries, to BIM leadership on large projects, to now leading digital engineering for a government agency delivering schools to over 800,000 students. His perspective on where the industry is, and where it's stalling, is worth paying attention to.

CAD Was About Drawings. BIM Was Supposed to Be About Decisions.

Here's the distinction that still trips up most organisations.

CAD management was about files, drawings, and deliverables. Information management is about outcomes: which decisions are enabled, which assets are operated more effectively, which costs are avoided. Those are fundamentally different jobs.

John puts it plainly: a BIM model delivered at the wrong level of information isn't a solution. It's a deliverable. And a project information requirements document that nobody reads isn't information management. It's documentation.

The organisations that have genuinely made the shift ask three questions before specifying anything: who will use this model, for what decision, and at what point in the asset lifecycle? Most teams skip these questions entirely and go straight to the template.

That reframe is still underway across much of the industry. Frameworks like ISO 19650 and, more recently, the NSW Infrastructure Digitalisation and Data Policy are forcing the conversation. But knowing the framework and internalising the mindset are different things.

Standards That Arrive as Policy Documents Get Filed

In the late 1990s, John was tasked with developing CAD and GIS standards across nine countries for a fibre optic cable network in Europe: 18,000 kilometres, nine regulatory environments, multiple languages.

The lesson he took from that project has shaped how he approaches standards ever since.

You cannot write standards in isolation and expect adoption. The effort on that project was a large stakeholder engagement exercise across all nine country teams before a single standard was published. People follow workflows they helped build. They work around workflows handed down to them.

This is now how School Infrastructure NSW approaches its digital standards. The goal isn't compliance documentation. It's design workflows that build capability as teams use them. Following the workflow teaches people why the information is needed, not just what to produce.

The technical document and the operational practice have to be the same thing.

The Government Advantage: Information That Doesn't Die at Handover

Most project clients treat digital engineering as a delivery tool. Information gets created, the project completes, and the data sits in an archive.

School Infrastructure NSW sits in a different position. It is simultaneously a major capital works client, a long-term asset owner, and a direct service deliverer to communities. That combination means information created during design and construction has genuine operational value from day one.

A school built today will serve three or four generations of students. The outdoor facilities are often the primary open space for the surrounding community. Getting the asset information right isn't about compliance. It's about 40 years of maintenance decisions that follow.

That changes how you specify information requirements. And it changes who you need to involve when you write them.

Standardisation at Scale Is Not a Compromise on Design Quality

Treating every school as a bespoke project developed from scratch is not viable across 2,200 buildings. School Infrastructure NSW's response is a pattern book: pre-engineered, digitally defined components developed with industry, aligned to education facility standards, and made available to delivery partners as a validated library.

This is not a cost-cutting measure dressed up as innovation. It's a precondition for delivering quality at scale.

When components are pre-specified and manufactured off-site using DfMA approaches, the as-built reality more closely matches the design model. That matters for operations. It also means the BIM model for a new school can be largely assembled from validated library content, reducing design time and creating a more consistent foundation for the asset information model.

SI has demonstrated that DfMA can reduce on-site construction assembly time and material waste by up to 30%. The delivery window for many projects is constrained to school holiday periods. That 30% isn't an efficiency statistic. It's what makes the project possible.

Moving Sectors Requires More Than Technical Competence

John's transition from consultant to government client in 2021 changed how he thinks about digital engineering's purpose. It also surfaced a gap he sees consistently in people making the same move.

Technical skills transfer directly. Cultural skills require deliberate recalibration.

In private practice, pace and decisiveness are valued. In government, thoroughness, consultation, accountability, and documentation carry equal weight. Neither is wrong. They serve different governance requirements.

The skill most worth developing before a sector transition is stakeholder management at the political and executive level. In consultancy, the key stakeholder is usually a project manager. In government, the landscape includes ministers, directors-general, Treasury, the audit office, industry bodies, and community groups. Five years in, John describes it as still learning.

That's contextual intelligence: the ability to read the incentive structures, risk frameworks, and decision-making cultures of the environment you're in, and adapt accordingly.

Where The Most Important Conversations Happen

Technical credibility matters in digital engineering. Practitioners can quickly identify leaders who are speaking theoretically rather than from experience.

But technical credibility alone isn't enough.

The professionals who create lasting change are those who can translate technical capability into organisational value. Who can explain to a CEO why ISO 19650 compliance is an organisational capability investment, not a technical exercise. Who can explain the community impact of DfMA to a local councillor as clearly as they can configure the common data environment.

The most technically capable digital engineers John has worked with are often not the most influential, because they can't translate their knowledge into language that resonates with non-technical stakeholders.

That communication skill is not a soft extra. It's the job.

Key Takeaways

• Start every digital engagement by asking who will use the information, for what decision, and when in the asset lifecycle, before specifying what models should contain.
• Involve the people who will use your standards in writing them. Co-design produces adoption; top-down mandates produce workarounds.
• Information management is about outcomes: decisions enabled, assets operated, costs avoided. If your BIM practice is still focused on files and deliverables, the mindset shift hasn't happened yet.
• A validated component library is not a shortcut on quality. It is what makes consistent quality possible at scale.
• Technical skills travel between sectors. Understanding the governance culture, incentive structures, and stakeholder landscape of a new environment takes deliberate investment before and after the move.
• ISO 19650 certification is the professional common language of the field. It differentiates practitioners in the labour market and underpins every serious digital engineering programme.
• The professionals who will lead digital construction in 10 years are actively engaging with AI, digital twins, and automated compliance tools now, not waiting for the industry to settle.
• Structured information only has value if someone is using it to make better decisions. Design for the user, not the standard.