The Order of Precedence Clause Explained (2026)

What is an order of precedence clause? An order of precedence clause ranks the documents that make up a contract, so that everyone knows which one wins if two of them say different things. It is also called a priority of documents clause or a conflict clause. Most real contracts are not a single document. A deal is often a main agreement plus schedules, an order form, a statement of work, technical specifications, service levels, policies and sometimes the other side's standard terms. These are written at different times by different people, and they do not always agree. The order of precedence clause decides the winner in advance, instead of leaving a court to guess later. In one line: it sets the pecking order of the contract's parts so that an inconsistency has a clear answer. ## What does an order of precedence clause do? The clause performs three jobs. 1. It lists the documents that form the contract. This itself matters, because it confirms what is in and what is out. A document that is not named is usually not part of the agreement.

2. It ranks them. It states which document prevails over which, from highest to lowest, so a conflict resolves top-down.
3. It explains how conflicts are handled. Good clauses say that the higher-ranked document controls only to the extent of the inconsistency, so the lower document still applies everywhere it does not clash. Without the clause, a conflict is resolved by general rules of contract interpretation, which are slower, less predictable and more expensive to argue. ## Why the order of precedence clause matters Complex deals bundle many files, and the more files there are, the easier it is to introduce an inconsistency. Construction, IT, outsourcing and procurement contracts can run to hundreds of pages across many annexes, and a figure or a definition in a schedule may quietly contradict the main terms. The clause matters because it converts that risk into a rule. When a dispute arises over, say, whether the service level in the SOW or the one in the master agreement applies, the parties do not have to litigate which was meant to govern. They read the ranking. It also protects the commercial deal. Negotiated terms usually sit in the main agreement or order form, while standard terms and third-party schedules sit lower down. A sensible ranking stops a buried standard term from overriding something the parties actually negotiated. One caution worth stating plainly: the clause is not a cure-all. A court will usually try to read the contract as a whole first, and will only fall back on the ranking if a genuine inconsistency remains. The clause is a tie-breaker, not a licence to leave documents contradicting each other. ## A sample order of precedence clause The example below is a neutral, general-purpose starting point to adapt with legal advice. > Order of Precedence. This Agreement is made up of the following documents. If there is any conflict or inconsistency between them, the document higher in the following list prevails over the document lower in the list, but only to the extent of the conflict: (a) this master agreement; (b) any Order Form signed by both parties; (c) the Statement of Work; (d) the Service Level Agreement; (e) the technical specifications; and (f) any policy incorporated by reference. A document lower in the list applies in full except where it conflicts with a higher document. Some contracts add a fallback for the case the ranking does not resolve, for example that the interpretation giving effect to the parties' commercial intent, or the one most favourable to a named party, applies. Use such fallbacks carefully, because they can reintroduce uncertainty. ## Drafting and negotiation points The ranking is a commercial decision, not boilerplate. A few points decide whether it helps you or hurts you. - Rank by where the real deal lives. Put the documents containing the negotiated, deal-specific terms (usually the order form and main agreement) above the standardised ones. If the vendor's standard terms sit at the top, your negotiated concessions may be overridden.

• Decide whether schedules count as part of the main document. Be explicit about whether appendices, annexes and schedules rank separately or are read as part of the agreement they attach to. Silence here is a common source of argument.
• Limit the override to the conflict. Say that a higher document prevails "only to the extent of the inconsistency," so you do not accidentally switch off whole sections of a lower document.
• Allow deliberate exceptions. Sometimes a lower-ranked document should win on a specific point, for example a special condition in a schedule. If so, allow an express override such as "except where a Schedule states that it prevails over clause X."
• Keep the list current. When documents are added during the deal (a change order, a new SOW), update the ranking so new files are placed, not orphaned.
• Match the document names exactly. Use the same defined names for each document throughout, so there is no doubt which file a rank refers to. ## How the clause works across jurisdictions The mechanics of an order of precedence clause are broadly similar across common-law jurisdictions, but the way courts approach it varies, and it interacts with local rules of interpretation. - In India, the UK and other common-law systems, courts generally give effect to a clear precedence clause, but they read the contract as a whole first and apply the ranking only to a true inconsistency. Verify the current approach with local counsel for high-value contracts.
• In civil-law systems, interpretation leans more on the parties' common intention and good faith, so a rigid ranking may be weighed against that context.
• Standard form contracts, such as FIDIC in construction or public-procurement frameworks, often set their own precedence order, which you should align with rather than contradict. Where the governing law's interpretation rules matter, name them in the contract. This explainer is general information, not legal advice. ## Common mistakes to avoid - Treating the clause as a reason not to fix contradictions. Resolve the inconsistency where you can; use the ranking only for what is left.
• Leaving a document off the list, which can put its status in doubt.
• Ranking incorporated policies, which the provider can change, above negotiated terms.
• Copying a precedence order from an unrelated template without checking it matches where your deal's real terms sit. ## Bringing the whole contract into one view The reason an order of precedence clause exists is that a contract is really a stack of documents that have to agree with each other. Keeping that stack consistent, spotting a schedule that contradicts the main terms, tracking which version of each document is current, and seeing the whole agreement as one structured thing, is work that is hard to do by eye across separate files. An AI contract workspace models a contract as a structured clause tree rather than flat, separate documents, which makes cross-document conflicts easier to see and precise edits easier to make. If you want to see that idea in practice, Adira is one example of a single workspace for drafting, reviewing, tracking and governing contracts. ## Key takeaways - An order of precedence clause ranks the documents in a contract so a conflict has a clear winner.
• It is a tie-breaker, used only after reading the contract as a whole; it does not excuse leaving contradictions in place.
• Rank the documents by where the negotiated deal actually lives, and limit each override to the extent of the conflict.
• Courts generally honour a clear clause, but the approach varies by jurisdiction, so name the governing law and get advice for high-value deals.