Aipedia: Structural and civil engineers

AI Eurocode checks and the second-generation codes

Aipedia, by the Apex broking team · Last reviewed 2026-10-27

AI code-checking tools must be validated against the code version a project actually uses, and IStructE says tools built for first-generation Eurocodes may need retiring when the second generation takes effect. An outdated checker can produce compliant-looking results against the wrong rules.

Part of: AI in structural and civil engineering

In short

Code-checking software, including AI-assisted tools that interpret clauses or automate checks, embeds a particular version of the Eurocodes and their National Annexes. IStructE's AI guidance asks firms to evaluate tools regularly against current standards and to plan their lifecycle, giving the example of retiring tools built for first-generation Eurocodes when the second generation takes effect. Without version control and validation records, a firm may not be able to show which rules a design was checked against. PI usually responds to negligent design, but disputes about the applicable code can be costly to defend.

How engineers use AI for code compliance

Engineers use analysis packages with built-in Eurocode checks, AI assistants that explain clauses or locate the governing check, plug-ins that automate member and connection verification, and LLMs asked to summarise what a code requires. Each sits on top of a specific edition of the code and, for UK work, the UK National Annex values. As the second-generation Eurocodes are introduced, firms will run both generations side by side for a period, which raises the risk of mixing them.

AI layers add another variable. A general chatbot may have been trained on a mix of code editions, draft documents and commentary, and will not necessarily say which one it is drawing on. A specialist plug-in may be updated by its supplier without the engineer noticing that a clause interpretation has changed.

The duties that apply

IStructE AI guidance: evaluate tools regularly against current standards; keep an AI risk checklist or matrix; plan the tool lifecycle, including retiring first-generation Eurocode tools when the second generation takes effect. Implementing AI in structural engineering.
IStructE Code of Conduct: Article 4 (maintain and broaden competence) and Article 6 (skill and judgement within a quality management system). Code of Conduct.
Part 2A reg 11K: the designer must take reasonable steps so the design would comply with relevant requirements if built.

The IStructE and Engineering Council guidance explainer covers the wider expectations.

What can go wrong

Version drift is the obvious risk: a tool updated to new clauses while the project specification still references the old code, or the reverse. AI assistants can also quote clause numbers or formulae that do not exist in the edition being used, or blend National Annex values with recommended values. More generally, CROSS-UK's Report 1554 warned that AI-written structural content can look robust to a non-engineer while being fundamentally wrong.

Illustrative scenario: a firm upgrades its checking plug-in mid-project. Some members are checked under the new rules and some under the old, and partial factors differ between them. A later independent review cannot reconstruct which checks were done under which version, and the client alleges the design is non-compliant and claims for a full re-check and delay.

How PI usually responds

PI usually responds to a claim that a design was negligently checked against the wrong or outdated rules. Defending it, though, depends on evidence: tool versions, validation runs and the code edition agreed with the client. Poor records can turn a defensible claim into a costly one. Our guides on PI for structural engineers and what to document about AI use explain why. Cover is subject to the policy wording and accurate disclosure of how the firm works.

Practical controls

Keep a tool register listing each checker, its version and the code edition it implements.
Fix the code edition for each project in the appointment and design basis.
Validate new tool versions against benchmark hand calculations before live use.
Do not upgrade tools mid-project without a recorded decision and re-check.
Verify any clause quoted by an AI assistant against the published code.
Plan retirement dates for first-generation tools, as IStructE suggests.
Train staff on the differences between code generations before they use updated tools, so they can spot a result that looks wrong.
Name an owner, such as the AI lead IStructE suggests for smaller firms, to approve tool changes and keep the register current.

How Apex helps

Apex arranges PI for structural engineers. A broker reviews your cover and how your policy and proposal form deal with AI-assisted code checking.

Sources

Frequently asked

Do I have to stop using first-generation Eurocode tools?

IStructE's guidance gives retirement of first-generation Eurocode tools, once the second generation takes effect, as an example of lifecycle planning. The practical point is to use tools that match the code edition each project is designed to and to plan the changeover.

Can I rely on an AI assistant to tell me what a Eurocode clause says?

Use it as a pointer only. AI tools can misquote or invent clauses and mix National Annex values. Always check the published code edition that applies to the project before relying on any clause or value.

Who is responsible if a supplier update changes how a tool checks the code?

The engineer issuing the design remains responsible to the client. Whether you can recover anything from the supplier depends on the licence terms. Controlling updates and re-validating after them is the practical protection, and IStructE expects tools to be evaluated regularly.

What records help if a code compliance claim is made?

The agreed code edition, the tool versions used, validation runs against benchmark calculations, and notes of any mid-project upgrade. These let you show what the design was checked against and help your insurer defend the claim.

Check your PI covers how you use AI

Tell us about your firm and the work you do. A broker will review how your current PI treats AI-assisted work, or arrange new cover. No fee for a quote. Or call 0117 325 0027.

Start a PI quote Request a callback

Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority. Registered in England and Wales, company number 07014570. This page is general information about how AI is used in the profession and how insurance may respond. It is not legal, regulatory or insurance advice on your circumstances, and it does not guarantee that cover will be available or on what terms.