The second generation of Eurocodes is the biggest change to European structural design standards in almost twenty years. Most of the conversation about it has focused on what changes in the codes themselves: new shear rules in Eurocode 2, consolidated parts, clearer layouts.
That conversation matters. It is also only half the story for a structural practice.
Commercial analysis and design software will be updated by its vendors. What will not update itself is everything a practice has built in-house over the last fifteen years: the Excel spreadsheets, the Mathcad sheets, the custom Tedds calculations, the macros and templates that sit at the centre of daily design work. Every one of those was written against first-generation clauses, and every one of them needs to be checked, updated or retired before the first-generation codes are withdrawn.
This guide covers the timeline, what changes, and a practical approach to migrating a practice's calculation library without disrupting live projects.
The Transition Timeline
The key date for UK practices is fixed. According to the Institution of Structural Engineers, BSI will withdraw the UK adoptions of the first-generation EN Eurocodes on 30 March 2028. Until then, the first-generation documents remain the applicable standards unless a relevant authority or project specification says otherwise.
Across Europe, the timeline follows a similar shape. Final versions of the new standards were due with national standards bodies by March 2026, national implementation is required by September 2027, and the withdrawal of the existing standards is expected by March 2028. Between those dates, first- and second-generation Eurocodes may be used in parallel.
Some parts are already available. The second-generation Eurocode 2, EN 1992-1-1:2023, has been published, along with its UK National Annex. Other parts follow through the transition period.
IStructE's guidance to designers is clear on two points: familiarise yourself with the second-generation codes as soon as possible, and avoid mixing first- and second-generation Eurocodes on the same design.
For a practice, that means a little over two years in which every new project has to make a deliberate choice about which generation it uses, and in which the tools supporting that choice have to be ready.
What Changes in the Second Generation
The second generation is not a rewrite of the underlying engineering. It is a substantial revision of how the rules are organised, expressed and applied.
Taking Eurocode 2 as the example, EN 1992-1-1:2023 updates the rules for shear, torsion and several other checks to give more accurate designs. It also absorbs material that previously sat in separate parts. Bridges, liquid-retaining and containment structures, CFRP strengthening and steel-fibre reinforced concrete now sit within EN 1992-1-1, which reduces the need for separate parts such as EN 1992-2 and EN 1992-3. New annexes cover the assessment and strengthening of existing structures.
Across the suite, the stated aims are clearer layouts, better suitability for digital use, and more consistent rules between disciplines.
For a practice, the practical consequences are that clause numbers change, formula structures change, some checks move between documents, and some results change. A calculation that was correct under the first generation may give a different answer under the second, and a template that references "EN 1992-1-1 clause 6.2.2" may now point to something that no longer exists in that form.
The Problem Nobody Is Talking About: In-House Calculation Templates
Most structural practices run on a mix of commercial software and in-house tools. The commercial software handles analysis and a large share of member design. The in-house tools handle everything else: connection checks, padstone designs, lintel checks, retaining wall calculations, foundation sizing, bespoke elements, and the countless small checks that make up a calculation pack.
Those in-house tools share some common characteristics:
They were written by individual engineers, often years ago, sometimes by people who have since left.
Clause references and formulas are embedded directly in cells or worksheets.
Verification records, if they exist, are rarely kept alongside the template.
Several versions of the same template often circulate on shared drives.
Under normal conditions, this is a manageable risk. During a code transition, it becomes a significant one. Every template needs to be identified, checked against the new clauses, updated, verified and re-issued. Every one that is missed becomes a source of non-compliant calculations after the withdrawal date.
The vendor articles on the transition warn that spreadsheet-based workflows may become obsolete. For most practices, the more accurate statement is that spreadsheet-based workflows will need to be rebuilt, and the question is whether they are rebuilt the same way or better.
What the Migration Actually Costs
The effort depends on the size and state of the template library, but the scale is easy to underestimate.
Consider a mid-sized practice with 150 in-house calculation templates in active use. Updating a template to second-generation clauses, checking it against hand calculations or benchmark examples, and documenting the verification typically takes somewhere between 6 and 10 hours for a straightforward template, and considerably more for complex ones.
As an illustrative example:
150 templates × 8 hours × £85/hr = £102,000
That figure covers the direct work only. It does not include the time engineers spend locating the current version of each template, working out what each one is actually used for, or resolving the inconsistencies between copies. It also assumes the work is planned. Practices that leave it until late 2027 will be doing the same work under deadline pressure, alongside live projects that have started to specify second-generation codes.
The cost of not doing it is harder to put a number on and more serious: calculations issued against withdrawn standards, and the professional liability that follows.
How to Migrate Your Calculation Library
A structured approach turns an open-ended risk into a defined project.
1. Audit the library
Start by finding out what exists. Search shared drives, project folders and personal directories for calculation templates. For each one, record what it does, which code clauses it references, who maintains it, and how often it was used on recent projects.
Most practices discover two things during this step. The library is larger than anyone thought, and a large share of it is rarely or never used.
2. Prioritise by use and risk
Rank templates on two axes: how often they are used, and how much the relevant clauses change in the second generation. High-use templates with significant clause changes go first. Low-use templates with minor changes can wait. Templates that are rarely used at all are candidates for retirement.
This step usually reduces the migration scope considerably. A library of 150 templates often comes down to 40 or 50 that genuinely need migrating, with the rest retired or consolidated.
3. Decide whether to update, rewrite or retire
For each template that survives prioritisation, decide whether a direct update is enough or whether the template should be rebuilt. A template that is well structured and clearly documented can be updated in place. A template with hard-coded values, undocumented logic and no verification record is usually faster to rebuild than to repair.
Where commercial software now covers a check that used to need an in-house template, retiring the template is often the right answer.
4. Rebuild for traceability
When a template is rebuilt, build it so the next transition is easier. Separate the code clauses and parameters from the calculation logic, so a future amendment changes one reference rather than dozens of cells. Show every clause reference in the output, so a checker can see exactly which provision each step relies on. Keep inputs, intermediate values and results visible rather than buried in hidden sheets. We cover why this matters in more detail in our article on why structural engineering software shouldn't be a black box.
5. Verify and document
Every migrated template needs verification: comparison against hand calculations, published worked examples or results from independent software. Record the verification alongside the template, with the date, the checker and the cases tested. This record is what makes the template defensible in a review or a dispute.
6. Run both generations safely
During the transition, some projects will run on first-generation codes and some on second. The practice needs a clear way to make sure the right template version is used on the right project. That means clear version labelling, a single controlled location for released templates, and a project-level record of which generation applies. Mixing the two generations within one design is exactly what IStructE advises against, and an uncontrolled template library is the easiest way for it to happen by accident.
How Does Structural Software Ensure Code Compliance?
Structural software ensures code compliance by implementing the provisions of a specific code edition, and its national annex, as explicit calculation rules, then reporting each check against the clause it comes from. Good compliance software makes three things visible: which code edition and national annex it applies, which clause governs each check, and what the intermediate values were.
Software does not guarantee compliance on its own. It guarantees that the rules it implements are applied consistently. Compliance still depends on the engineer choosing the right code edition, the right inputs and the right checks for the structure, and on the software being kept up to date as codes change.
That last point is why the Eurocode transition matters for in-house tools. A commercial package gets a vendor update. An in-house spreadsheet only complies with the edition it was written against, and only until someone changes it.
Using the Transition to Fix the Underlying Problem
A code transition forces a practice to touch every calculation template it relies on. That makes it the best opportunity in a generation to change how calculation templates are built and managed.
The practices that come out of the transition in the best position will not just have updated their spreadsheets. They will have consolidated duplicate templates, retired unused ones, separated code parameters from calculation logic, and moved their most-used checks into tools that connect directly to their analysis and modelling environments rather than relying on manual re-entry.
That last step is where the long-term return sits. A migrated spreadsheet still needs an engineer to copy forces out of ETABS and section sizes out of Revit. A rebuilt calculation connected to those tools does not. We cover the options for that in our guides to structural calculation automation software and Revit, Tekla and ETABS integration.
The work has to be done either way. The difference is whether the practice ends up with the same fragile library written to new clauses, or a smaller, verified, connected set of calculations that will handle the next amendment in hours instead of months.
The Starting Point
The 30 March 2028 withdrawal date is fixed, and every structural practice in the UK will reach it. The commercial software will be ready. The question for each practice is whether its own calculation library will be.
The most useful first step costs very little: an audit of what templates exist, what they do and how often they are used. That audit turns an undefined risk into a scoped project, and in most practices it reveals that the real migration is smaller and more manageable than it first appears.
If you want help scoping that audit, or rebuilding your most-used calculations so they are traceable and connected to your analysis tools, get in touch. It is usually a short conversation to work out where the effort sits and what can be automated along the way.
Transition dates sourced from the Institution of Structural Engineers: Second-generation Eurocodes, when should I start using them? and IDEA StatiCa: Ready to transition to the 2nd generation of Eurocodes. UK National Annex details from BSI. Further background from the European Commission Joint Research Centre.