The second-generation Eurocodes are coming
Every second-generation EN Eurocode carries a Date of Publication of 30 September 2027 (European Commission Joint Research Centre). It is a single, shared deadline — which means the whole profession starts recomputing against new and revised clauses at roughly the same moment.
That simultaneity is the point. When one firm updates a spreadsheet, it is an internal migration. When an entire discipline does it at once, the checking capacity that verifies those recomputes has to scale with it.
Why a shared date changes the checking problem
- No staggered rollout. There is no early-adopter phase to absorb the errors before everyone follows. Clause changes land across concrete (EC2) and steel (EC3) together.
- New clauses, old habits. The first calculations against a revised clause are where transcription and interpretation errors concentrate.
- Verification is the bottleneck.Recomputing to a new code is work a machine can do deterministically. Reviewing whether a human’s recompute matches the new clause is where independent checking earns its place.
What we are building toward
Support for the second-generation Eurocodes is being built against the 2027 publication timeline, alongside the current EC2 and EC3 checks with the UK National Annexes. The aim is simple: when the new clauses take effect, the recompute that checks your package already knows them.
Timeline as published by the European Commission JRC. Dates are cited, not paraphrased.