Skip to content
Building & transportation forensics

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.

As-builts Permits Ordinances IBC editions your archive Code in force on the date of loss
Cited to the page, or it tells you it isn’t thereYour documents onlyWe do not train on your archive
Why firms call us

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.”

What it changes The substitution is caught before it ships

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.”

What it changes The ordinance sits beside the answer

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.”

What it changes One question across all three
On your own file

Three steps, and you approve the sources

Step 01

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.

Step 02

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.

Step 03

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.

The app for this work

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

Edition in force: 2015 IBC, not 2021
  • Two clause references in the draft need restating
  • Adoption ordinance attached as the basis
Adoption ordinance §22015 IBC 1607.12
Click a step to jump to it

Changing a clause reference in a report you will sign is not something software should do unattended, so the app shows the substitution and its basis and waits for the engineer to confirm it.
What the system commits to

Cited, or it tells you

No claim about whether the structure complied, that is engineering judgement 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.

Cites IBC editionsASCE 7Local amendments
Questions we get first

Before you send us a document

Does it know which code my jurisdiction had adopted?

It knows what is in the sources you loaded. If the adoption ordinance is in your file, it will find it and cite it; if it is not, it will tell you it cannot establish the edition rather than guessing. On this question specifically, a guess is worse than nothing.

What about local amendments?

Same answer, and it is the honest one: if the amendment is in your sources it is findable and cited. If the record does not establish one, it says the record does not establish one. It will not infer that a jurisdiction did or did not amend.

Can it tell me whether the structure complied?

No. It puts the governing clause, the drawing and the inspection record in front of you with the sources attached. Whether the condition met the requirement is your engineering judgement.

Can it assemble the exhibit set for a loss date?

It pulls the candidates together with their sources attached: the clause from the edition your file establishes as governing, the drawing it refers to, the inspection record from around that date. What you get is a cited index of what your own record contains, not an exhibit list somebody else decided on. Which items go in front of a trier of fact is yours.

Bring one you already know the answer to

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.