The code in force on the date of loss is not the code on your shelf.
A loss in 2019 is governed by the edition the jurisdiction adopted in 2019, and the draft on your desk quotes the one you happen to own.
Three places this work actually breaks
The wrong edition is a defect in an otherwise sound report
Your engineering is right, your reasoning is right, and you cited chapter and verse from an edition that did not exist on the date of loss. It is not an analytical error, which is exactly why it survives internal review.
“The code in force on the date of loss is not the code sitting on my shelf today.”
Adoption is local, and the record of it is scattered
A jurisdiction adopts on its own cycle, sometimes with amendments, and the evidence of which cycle applied is an ordinance in a municipal file rather than anything in the code book itself.
“If it will not survive cross-examination, it is worse than useless, it loses the case.”
Drawings, inspections and the code have to be read together
The as-built says one thing, the inspection report from the year before says another, and whether the difference matters depends on which edition governed. Three documents, one question, and they live in three places.
“Juniors cannot move without the principal, so the principal never gets out of the weeds.”
Three steps, and you approve the sources
Load the record
Drawings and as-builts, inspection and permit records, the adoption ordinances, and every code edition in play. You approve every source; nothing outside them is read.
Ask with the date attached
“What did chapter 16 require at this address on 11 August 2019?” The answer names the edition, the clause and the ordinance that made it apply.
Check the draft against it
Run the check to find every clause reference in a draft that belongs to the wrong edition, before it goes out.
Check the draft before it goes out
It establishes the governing edition from the adoption record, then finds every clause in the draft that belongs to a different one.
Input Loss date 11 Aug 2019, Ridgeline Plaza
- Two clause references in the draft need restating
- Adoption ordinance attached as the basis
Cited, or it tells you
No claim about whether the structure complied, that is engineering judgment and it stays yours. These are properties of the software, checkable on a loss you have already researched.
Cited to the clause and the ordinance
A code requirement arrives with the edition it is from and, where your file contains it, the adoption ordinance that made that edition the governing one. Which is the difference between citing a code and citing the code that applied.
It tells you rather than inferring adoption
If the record does not establish which edition a jurisdiction had adopted, or whether it amended it, the answer says so. It will not infer a jurisdiction’s adoption history from what neighbouring jurisdictions did.
Related: Fire & explosion investigation → · The forensics workbench →
Test it on a loss date you have already researched
Send the adoption ordinance and one draft, and ask which edition governed. Twenty minutes, and you will see whether it gets the edition right and shows you the ordinance.