Glossary
Order of precedence
Loonar · Updated 12 November 2026
An order of precedence clause ranks the documents that form a tender or contract, so that when two of them conflict, the higher-ranked one prevails. It decides between documents, not within one. It does not make the prevailing requirement technically right, and some contracts add or substitute a rule that the more stringent requirement applies.
Also called: priority of documents, precedence clause, hierarchy of contract documents.
How an order of precedence clause works
The clause lists the documents that form the contract and ranks them. When two documents say different things, the one higher in the list prevails.
The World Bank's standard contract for goods is an example. The contract agreement "shall prevail over all other contract documents" and lists the others: the letter of acceptance, the letter of bid, the addenda, the special conditions, the general conditions, the specification, and the completed schedules, including the price schedules. The general conditions then refer to "the order of precedence set forth in the Contract Agreement" (World Bank, Contract Agreement and GCC 2). FIDIC contracts set a document hierarchy in Sub-Clause 1.5, Priority of Documents. The documents are meant to be mutually explanatory; the priority applies where a conflict, ambiguity or discrepancy arises, and the contract procedure then provides for a clarification or instruction.
Industrial purchase orders often follow a similar pattern, set by each buyer. One common order, for illustration only:
- Purchase order or contract agreement
- Agreed list of deviations and clarifications
- Special or particular conditions
- General purchase conditions
- Datasheets
- Project specification
- Company or client standards
- Codes and international standards
Many buyers rank the specification above the datasheets instead. Read the clause in each package: the order is a decision of the buyer, not a convention.
Three ways contracts resolve conflicts
| Rule | How it works | Watch for |
|---|---|---|
| Order of precedence | The higher-ranked document prevails | The prevailing requirement may be the weaker or the wrong one |
| More stringent requirement applies | The stricter requirement prevails, whatever its document | "Stricter" is not always defined, and it can change dimensions, not only cost |
| Refer to the buyer | The supplier must report the conflict and wait for an instruction | A conflict found and not reported can become the supplier's risk |
Many specifications combine the three: a hierarchy between documents, the more stringent requirement for technical conflicts, and a duty to report any conflict found.
Where the order of precedence stops
- Inside one document. Two clauses of the same specification that contradict each other are not ranked by the clause.
- When the answer is technically wrong. A hierarchy can give an answer no engineer would build. A supplier who sees it and stays silent takes the risk.
- Documents that are not ranked separately. A client standard, an international code or a vendor document referenced in a contract document may still be part of the contract, incorporated by reference. Check how it is referenced, whether it forms part of the contract, and which precedence rule applies to it. If that is unclear, ask.
- The offer itself. Supplier offers often rank low or are not listed at all. A technical deviation accepted at evaluation holds only if the contract carries it.
Example: a pressure class conflict
A valve datasheet gives Class 300 for a line. The piping class for the same line gives Class 600. The purchase order ranks datasheets above the piping class.
On paper, Class 300 prevails. But the piping class sets the rating for the line, and a Class 300 valve may be rated below the line's design conditions. Whether it is inadequate has to be checked against the actual design pressure, design temperature and material: a piping class sometimes specifies a higher class for standardisation, so the class designation alone is not the engineering assessment. A Class 600 valve also has a different face-to-face length under ASME B16.10 and, in most sizes, different flange dimensions, so it does not drop into a Class 300 line either (see pressure class).
The supplier asks, even though the clause gives an answer: "The order of precedence gives Class 300 from the datasheet. The piping class gives Class 600 for the same line. Please confirm which applies." The question goes in the clarification log, with the basis of the offer stated if no answer comes.
Objections, and what holds up
"The clause settles every conflict." It settles conflicts between listed documents. It does not settle conflicts inside a document, conflicts with unlisted documents, or answers that are technically wrong.
"We always price the most stringent requirement." Do not assume it applies. A stricter requirement can mean a different material, configuration, interface, performance or test procedure, not only a higher cost. Check whether the contract has a specific rule for technical conflicts. If the requirements lead to different designs, materials or interfaces, raise the issue before committing to the offer, and state the basis of the offer if no answer comes.
"Our offer is the latest document, so it prevails." Often the opposite. Many contracts rank the offer last or exclude it. What the supplier wants to keep, such as accepted deviations and stated assumptions, has to be listed in the contract.
How Loonar helps
RFQ Analysis extracts the requirements from the tender package and cross-checks them across documents. When two documents conflict, it puts both statements side by side, each traced to its source page.
Your team finds the inconsistencies between datasheets, specifications, piping classes and other technical documents before the offer goes out. Your engineers then read each conflict against the order of precedence and raise a clarification with the buyer when needed.
Frequently asked questions
What happens if a contract has no order of precedence clause?
The conflict is resolved by the rules of interpretation of the law that governs the contract, which vary between countries. The outcome is harder to predict. In a tender, raise the conflict as a clarification before the deadline for questions.
Does an order of precedence apply during the tender?
Usually yes. Tender documents often rank their own parts. In World Bank bidding documents, the bid data sheet prevails over the instructions to bidders, and in the contract the special conditions prevail over the general conditions.
Is "the more stringent requirement applies" an order of precedence?
No. It is a different rule: it compares the requirements, not the documents. Some specifications use it for technical conflicts and keep a document hierarchy for everything else. The more stringent requirement is not always the right one, for example when two pressure classes give different flange dimensions.
Where does an accepted deviation list sit in the order of precedence?
Where the contract puts it. If the purchase order lists the agreed deviations above the specification, they prevail. If it does not list them, or ranks them below the specification, the original specification may prevail over a deviation the buyer accepted at evaluation.
Who decides when the order of precedence does not settle a conflict?
Before award, the buyer, through an answer to a clarification. After award, the party the contract designates. Under the FIDIC Red and Yellow Books, the Engineer issues the necessary clarification or instruction; under the Silver Book, which has no Engineer, the Employer does.