The argument · How precedence works
Which standard takes precedence? The order you set decides. It is a contractual question before it is a technical one, and it determines whether a review is right or merely thorough.
The clause
An order of precedence clause sits in the conditions of most engineering contracts. It exists because the parties knew the documents would disagree, and agreed in advance which one would win.
It is read once at contract award and rarely again. The reviewer checking a datasheet eighteen months later is usually working from memory of what normally applies.
The hierarchy
A hierarchy of codes and standards is not arbitrary. Each level is more specific to the job than the one below it, and specificity is what earns precedence.
← MORE SPECIFIC TO THIS JOBMORE GENERAL →
Owner standard vs industry code
A code sets a minimum the industry agreed was safe. An owner standard says how this owner requires things built, which is usually stricter and always more specific.
A deliverable that satisfies the code and misses the owner standard is compliant with the wrong document. It will pass a code check and fail at handover.
Checking against a code is a defensible instinct and the wrong one. The code is the lowest ranked document in the chain.
Engineering specification hierarchy exists precisely so the most specific agreement wins, not the most familiar one.
Where it breaks
Nobody disputes the hierarchy. The difficulty is that it has to be applied to a single value on a single sheet, by someone who would have to open five documents to be certain which one speaks to it.
So it gets applied from memory, and memory defaults to whichever document the reviewer knows best.
What follows from it
standrdX does not decide which standard wins. It applies the order your team configures and shows its working on every finding.
FAQ
It is a contract provision stating which document prevails when the documents forming an agreement conflict. It establishes a ranking in advance, so a disagreement between a specification and a standard has a contractual answer rather than a negotiated one.
The one your contract ranks highest for that parameter. In most arrangements an approved deviation prevails over a project addendum, which prevails over the project specification, then the owner standard, then the code. The exact order is set by the contract, not by convention.
Because it is more specific to the work. A code sets a minimum the industry agreed is safe; an owner standard states how that owner requires things built, which is usually stricter.
That is its purpose. An addendum is issued to change what was already agreed, so it ranks above the document it modifies for the matters it addresses.
No, and assuming so is a common source of error. Contract terms and client standards change the ranking, which is why it is established per project rather than carried over.
Your team, from the contract. The platform applies the order you configure and records which clause governed each finding; it does not infer the hierarchy from the documents.
Next step
Pick a value that appears in your specification, your owner standard and an addendum, and see which one your current review would have used.