Structural Steel Design / Checking, review and knowing what you do not know
What this course does not know
The last lesson, and the one that turns the method back on the course itself. Every value it could not verify is listed — by the code, not by hand.
Lesson review: expert verification remains open
This lesson has received a full-context editorial review and a check of its technical explanations. Selected arithmetic has been checked separately. This is not independent engineering sign-off.
Corrections checked in this pass
- Historical SC/PC escalation and fixed NDT/cost claims removed from lessons; public execution-class calculator already withheld. Current first-generation selection basis and EN1090-2 amendment identified; traceability distinguished from sign-off.
Checks needed for project use
- A steel-design reviewer must check the first-generation calculation profiles, second-order analysis assumptions, connection rules and execution references against the applicable standards and amendments.
- Project execution specification, applicable edition/National Annex, weld-specific inspection/tolerance requirements and actual fabrication controls. Legacy executionClass function remains in library but is not imported by the public lab; do not restore it as a current recommendation engine. Full independent engineering sign-off remains open.
These are educational models and exercises. Check their assumptions before using the results. The full technical content and every diagram have not yet been independently verified.
Concrete and steel calculations retain their stated first-generation Eurocode teaching basis. Use the standards and amendments specified for your project; do not mix generations without an appropriate design basis.
Read the lesson register and outstanding review notesWhy this matters
A design that cannot say what it does not know is not more reliable than one that can. It is less reliable, because nobody can see where the gaps are.
That applies to this course as much as to anything it teaches. So this final lesson does to The Chartership Forum what the previous one asked you to do to a design: it states, precisely and without softening, what has not been verified and what follows from that.
By the end of this lesson you should be able to
- Read the register of values this course has not verified
- Say why it is generated rather than written
- Distinguish a nationally determined parameter from other unverified values
- State what this course is and is not fit for
What you should already know
- The distinction between derived, calibrated and nationally determined rules (Module 1)
- Levels of independence and what each can find (this module, lesson 1)
Verification status
Use the live register to inspect each parameter’s source, edition, clause and review status. A recorded source check does not establish that the parameter applies to a particular project, or that the model using it is complete.
The technical review has also identified model and example defects that a parameter register alone cannot detect. Keep separate records for source verification, arithmetic checks, model applicability and independent engineering review. This course is educational material and has not received independent design certification.
Reading the register
The register is generated from the design-standard profile, so its displayed entries follow the recorded data. That reduces manual duplication; it cannot guarantee the data, clause interpretation or calculation is correct.
Read the total number of entries, outstanding items, source editions and review dates. Do not infer that an empty outstanding list means the whole course has been verified. Parameter verification, diagram review, model validation and independent professional review are different tasks.
Where a standard, National Annex or interpretation changes, review the dependent equations, examples, figures and exercises as well as the parameter value.
Try it
What this course does not know
This register is generated from the design-standard profile every time the page is built. Nothing in it is written by hand, so it cannot drift from the code — and it cannot be quietly allowed to lapse.
Show
- Profile
- BS EN 1993 (first generation) with UK National Annexes
- Values requiring verification
- 0
- Nationally determined parameters
- 0
- Standards affected
- 0
- Register is clear
- yes
- — showing —
- 0 entries
All 47 design values in UK EC3 gen 1 have been verified against their published source, and each one carries the clause it was read from. This register is GENERATED from the profile every time it is read, so it cannot drift from the code — an empty register is worth reading precisely because nobody had to remember to empty it. Verified is not the same as fit for construction: none of this work has had independent design review.
Things worth trying
- Read the total first. 8 design values in this course still require verification against their published source. It was 46 until the standards were read in July 2026.
- Filter to the nationally determined parameters. There are 2, and they are a different kind of unknown: no amount of engineering reasoning can settle them, because a National Annex chooses them.
- Both are joint factors. gamma-M0 and gamma-M1 used to be on this list; they were read from NA.2.15 and confirmed at 1.00, so they have left it.
- Filter to EN 1993-1-8. It carries 7 of the 8 — because that document was not among the ones obtained. The remaining entry needs BS EN 1090-2.
- That is the shape a good register has. It is not a list of things nobody got round to; it is a list of things nobody could reach, and it names the reason.
- Note what the register does NOT do: it does not guess. Where a value cannot be verified, the course teaches the behaviour and refuses the number rather than substituting a plausible one.
- The reason it is generated rather than written: a hand-written register drifts from the code the first time a value is added, and a register that has drifted is worse than none — because it is believed.
- Every entry carries its standard and clause reference, so anybody with access can check the course rather than take its word.
Practice
The profile holds 47 design values and 9 of them are nationally determined parameters — values a UK National Annex chooses rather than the base Eurocode. What percentage of the profile is nationally determined?
Predict first
If the National Annexes were consulted and every value confirmed, what would happen to the register on this page?
The end of the course
Twenty modules, and the argument they add up to is smaller than the material.
Steel is a material whose failures are mostly about stability, and stability is a question about geometry and restraint rather than about strength. That is why so few of the remedies in this course involve a stronger steel: a deflection problem wants depth, buckling requires section and restraint checks, while fatigue requires the correct detail and stress history. Yield strength can affect buckling resistance even though it does not change elastic stiffness.
The rules are a mixture — some derived, some calibrated, some chosen by a national committee — and telling them apart is not pedantry. It tells you which ones you can reason from and which you have to look up.
And the decisions that matter most are taken earliest, with the least information, and then stand. Which is an argument for spending real effort at the beginning, and for writing down why — including what you did not know at the time.
The last of those is the one this course has tried hardest to practise, and the register is the evidence.
Summary
- A design that cannot say what it does not know is less reliable, not more
- This course teaches the behaviour and refuses the number where a value is unverified
- Check the live register for outstanding values and nationally determined parameters
- Check each parameter against its stated standard, edition and applicable National Annex
- The register is GENERATED from the profile, so it cannot drift from the code
- The course is fit for understanding behaviour, and not for producing design values
- Agreement with common practice is not verification