Codes and standards: AISC, Eurocode, British, Australian, ISO.

The code changes the drawing, not only the calculation

It is easy to think of a design code as something that happens before detailing starts. In practice the code reaches all the way into the sheet. Standard hole clearances differ. Minimum bend diameters for reinforcement differ. Fabrication tolerances and execution classes differ, and they change what has to be stated on the drawing. Welding symbols follow different standards. Even the question of who is responsible for designing a connection is answered by a code of practice rather than by the contract in some jurisdictions.

So a detailing package is not code-agnostic work that gets a stamp at the end. It is produced against a standard from the first decision, and it should be checked against that standard automatically rather than by a checker remembering which country the job is in.

The five families we work to

• AISC — the American steel framework: AISC 360 for design, AISC 303 as the code of standard practice that governs detailing responsibility and tolerances, and AISC 341 where seismic provisions apply.
• Eurocode — EN 1990 through EN 1999 with the National Annex of the country of construction, executed under EN 1090-2 for steel and EN 13670 for concrete.
• British standards — BS EN Eurocodes with the UK National Annex, plus the British standards that remain the working documents on site, notably BS 8666 for reinforcement scheduling.
• Australian standards — AS 4100 and AS/NZS 5131 for steel, AS 3600 and AS/NZS 4671 for concrete and reinforcement, with AS 1100 drawing conventions.
• ISO standards — ISO 19650 for information management, ISO 16739 for IFC exchange, and the ISO drawing standards that govern presentation and title block data.

Voluntary documents, mandatory projects

Almost none of these standards is a law in itself. AISC, BSI, Standards Australia and the ISO committees publish consensus documents. What makes a document binding is one of two things, and it is worth knowing which one a project is relying on.

The first is adoption by reference. A statutory building regulation names a standard, and from that moment the named edition of that standard carries the force of the regulation behind it. The International Building Code references AISC 360 and AISC 341 for structural steel. The National Construction Code calls up Australian Standards inside its Deemed-to-Satisfy provisions. National building regulation across Europe adopts the Eurocodes together with the country's own National Annex. What was a voluntary document becomes mandatory the moment the jurisdiction adopts the code that names it.

The second is the contract. A specification saying work shall comply with a standard makes that standard an obligation whether or not any regulation mentions it. That is how most British Standards operate: voluntary as documents, binding the moment they are cited, and cited constantly.

So the question of which code applies is really two questions — what the jurisdiction requires, and what the contract requires — and they do not always return the same answer. Both are recorded at intake, because a package that satisfies one and not the other is still a package that gets rejected.

National annexes and mixed-code programmes

Eurocode is not one code. A frame in Germany, France, Poland and the United Kingdom is designed to four different sets of nationally determined parameters, and detailing follows. Programmes that span regions are common — an operator building the same facility in three countries, or a fabricator supplying across a border — and they are the easiest place to make an expensive assumption.

We fix the governing standard per package at intake, record it, and configure the checks to match. A mixed-code programme is set up as a mixed-code programme, rather than being detailed to whichever standard the first package happened to use.

Which edition governs

A standard is not one document forever. AISC 360 has been reissued on a roughly five-to-six-year cycle. The Eurocodes are in the middle of a generational revision, with new parts published progressively and each country's National Annexes following behind them. AS 4100 stood unchanged from 1998 until its 2020 edition. British Standards are reviewed, amended, superseded and withdrawn on their own schedule.

The edition a regulation enforces usually lags the newest edition the standards body has published, sometimes by years, and adoption can differ between states or regions inside one country. A connection drawn to the current edition of a specification is not automatically acceptable on a project whose building regulation still names the previous one. A specification that cites a standard with no year leaves that ambiguity sitting in the documents for somebody to discover at approval stage.

We record the standard, its edition, and its National Annex or state variation as one identifier rather than three loose facts, and configure the checks against that identifier. It is dull administration that removes a whole category of argument later.

How checks are configured per code

The automated quality control is not a fixed rulebook. It is a configuration: bolt edge distances and hole clearances from the governing steel specification, minimum bend diameters and lap lengths from the governing concrete code, tolerance and execution class requirements reflected on the drawing, welding symbol conventions, and drawing presentation rules from the applicable ISO or national standard.

The check record is issued with the package, so what you receive states which standard the work was checked against — not just that it was checked.