The code hierarchy
Design documents stack in layers. Higher layers are mandatory; lower layers fill in the detail. Click a layer to see what lives there and how it is used.
Authority navigator
Pick a region and a discipline. The card shows who approves the design, the main documents they enforce and what you normally submit. Names are current to the best of our knowledge; editions change, so check before you rely on one.
Region
Discipline
Which code answers it?
Real design questions. Pick the document you would open first.
Order of precedence
Documents disagree more often than you would think. Decide which requirement governs in each case.
A typical contract order of precedence
Your contract's conditions define the actual order. Authority regulations sit above all of it because they are law.
Design compliance checker
Enter a few values from your design. Each check shows the reference value, where it comes from, and lets you override it with the local authority or specification value.
3D code map and 4D approval route
Tap any system in the building to see the codes that govern it for the selected region. Play the 4D timeline to follow a typical approval route from design to completion certificate.
Engineer's notes
Lessons from real design reviews.