Module 20 · Lesson 20.2
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.
Why 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 Queensferry 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)
The position, stated plainly
For most of its life this course could not consult the UK National Annexes, and said so on every page. The documents were then obtained in two stages: most in July 2026, and BS EN 1993-1-8 and BS EN 1090-2 with their National Annexes shortly after. All 47 design values have now been read from their published source, and each one carries the clause it came from.
The position taken while the documents were out of reach is the point of this lesson, and it does not stop being the point now that they have been read. There were three possible responses, and only one of them was honest.
Use plausible values quietly. Many of the numbers in general UK circulation are almost certainly right. Using them without saying so would have produced a course that looked complete and could not be audited — and a reader would have had no way of telling which numbers were checked.
Omit the topics entirely. This would teach less than is teachable. The mechanics is unaffected by a national choice: the buckling behaviour of a column does not depend on which partial factor a National Annex adopts.
Teach the behaviour and refuse the number. Which is what the course did. Where a design value could not be verified, it was recorded as requiring verification, and any calculation depending on it was marked teachable but not usable.
That discipline paid, and this is the argument for it. Reading the documents found four errors, one of them unconservative. It found them because every value had a clause reference against it to check. A course that had quietly used plausible numbers would have had the same four errors and no way to discover them.
One thing has not changed. Verified means each number can be traced to a clause. It does not mean this course is fit for producing design values for construction: none of the work here has had independent design review, and Module 19 is about exactly why that distinction matters.
What the verification found
Reading the documents was not a formality. It found four things.
η was wrong, and unconservatively. The course held the recommended European value of 1.20 for the shear-area factor. The UK National Annex to EN 1993-1-5, NA.2.4, sets it to 1.0 for all steels. The course had been overstating the shear resistance of a stocky web by 20%.
Two different factors are both called γM2, and they had been conflated. EN 1993-1-8 gives 1.25 for bolts and welds. EN 1993-1-1 §6.1 gives one for a cross-section in tension to fracture, and the UK sets that to 1.10. The course was using the bolt factor in a member check — which is why Module 6 now spends a paragraph on the distinction, and why its allowance moved from 3% of area to 15%.
The plastic sway threshold was 15; the UK gives 10, and 5 for portals under gravity loads only. Module 4 was rewritten around it.
Steel density is a range, 77.0 to 78.5 kN/m³, and the course held the lower bound without saying so.
None of these was found by re-reading the calculations. They were found by opening the source — which is the last lesson's point about independence, applied to this course.
The register, and why it is generated
The register that follows is produced by reading the design-standard profile at the moment the page is built. Nothing in it is written by hand.
That is deliberate, and the reason is worth stating: a hand-written register drifts. The first time a value is added to the profile without the document being updated, the register becomes wrong — and a register that has drifted is worse than no register at all, because it is believed.
Generating it means the two cannot disagree. If a value's status changes in the code, the register changes with it; if the course ever verifies the National Annexes, the register empties itself without anybody editing this page.
That is now the best evidence this page can offer, because it is exactly what happened. An earlier version of this lesson made that claim as a prediction, with eight entries still outstanding — seven from BS EN 1993-1-8 and one from BS EN 1090-2, the two documents not then in the set. Those documents were obtained and read. Nobody edited the register. It is empty because the profile changed underneath it.
As it stands: 0 of 47 design values require verification. Read the denominator, not the zero. A register that reports only its outstanding entries becomes meaningless at the moment it succeeds — "nothing outstanding" tells you nothing about whether the profile holds four values or four hundred, or whether anyone ever populated it at all.
The register is the weaker claim of the two on this page, and it is worth being clear about which is which. It says every number is traceable to a clause. It does not say the numbers are right for your project, that the clause was the applicable one, or that anyone independent has looked. Those are different questions, and Module 19 is about them.
A cleared register is not a finished job. It is the point at which the interesting question changes from do we know where these numbers came from? to did we choose the right ones?
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, a buckling problem wants restraint, a fatigue problem wants a better detail, and none of them cares what the yield strength is.
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
- 46 values require verification; 7 are nationally determined and cannot be reasoned to
- EN 1993-1-1 carries 33 of them — 72% of the register
- 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
This is educational material. It uses simplified examples to teach principles, and must not be relied on for real design or safety-critical decisions. Module overview and checkpoint