In plain terms
Two kinds of vertical link make up most hierarchies, and a third extends them over time. The first runs from a framework agreement down to the statements of work that implement it: the framework fixes the general terms once, and each child sets out a specific piece of work, its price and its timetable. A master services agreement followed by a series of statements of work is the classic case, and the difference between an MSA and a statement of work is the difference between two levels of one hierarchy.
The second link runs from a contract to its amendments. An amendment does not stand on its own: it changes identified terms of the document above it and is read together with it. The third link, which the contract’s lineage records, runs over time, from a contract to the renewal or successor contract that takes over from it, and sometimes to a novation agreement when a new party steps in.
Positions in a hierarchy are relative, since the same document can sit below one contract and above another. That is why the useful way to draw a hierarchy is top-down, placing each document under the parent contract it depends on, rather than in the order the files were signed or saved.
A contract hierarchy is not to be confused with the order of precedence between contract documents. An order of precedence clause ranks the documents of one contractual set (special conditions, general terms, schedules, a purchase order) and states which one prevails if they conflict. The clause says which document wins; the hierarchy says who depends on whom. The two meet in practice, because a well-drafted framework states whether its own terms or those of a statement of work prevail.
Why it matters in a contract
A child contract is rarely complete on its own. The statement of work carries the scope and the price, but the liability cap, the governing law, the confidentiality terms and the termination rights usually sit in the framework above it. Reading a statement of work in isolation can therefore give a false picture of what was agreed, and the hierarchy tells you which documents must be read together, and in which direction.
French law gives the structure a clear basis. Article 1111 of the Civil Code defines the framework contract as an agreement by which the parties set the general characteristics of their future contractual relations, with implementing contracts specifying how they are performed. Article 1193 adds that contracts can be modified only by the mutual consent of the parties, or for causes the law authorises, which is the foundation of every amendment. In English private law, the same structure is built mainly through drafting: incorporation of the framework terms by reference, precedence clauses and variation clauses. Public sector frameworks and call-off contracts also follow their own procurement rules.
The hierarchy also matters at the edges of the relationship. When a framework expires or is terminated, the question is whether statements of work still in progress survive, and on which terms. When a successor contract takes over, the question is which earlier commitments it carries forward. Both are answered by reading down the hierarchy rather than by searching for a single file.
How hierarchies, families and their history fit together is explained in our reference on mapping contract lineage. In Pactolane, you link each document to the one it depends on, the platform displays the result as a tree view, and PactAI answers questions on the whole contract family, such as “What terms apply today after the amendments?” Linking and querying contract families are available on the Growth and Scale plans.
Example
A mid-sized engineering firm signs a master services agreement with an IT provider, followed by three statements of work: one for helpdesk support, one for a server migration and one for a security audit. Some months later the migration statement of work is amended to move its go-live date, and the framework itself is amended to raise the provider’s liability cap.
The hierarchy now has the framework at the top, three statements of work beneath it, one amendment attached to the framework and another attached to the migration work. When the finance director asks whether the helpdesk work benefits from the new cap, the structure shows where to look: the cap sits in the framework, so the framework amendment reaches the helpdesk work as well, provided that statement of work incorporates the framework terms and sets no cap of its own, and subject to what the amendment says about its scope and effective date.
When the framework reaches its term and a new agreement replaces it, the firm links the successor to its predecessor and records which statements of work move across.
General legal information, not legal advice.
Frequently asked questions
What is a contract hierarchy?
A contract hierarchy is the vertical structure of the contracts in one relationship: a parent contract sets the framework or initial terms, which child contracts implement and amendments change. It is a term of contract management practice rather than a legal category. Its purpose is to show, for every document in a relationship, which other document it depends on, so that nothing is read out of context.
What are the levels of a typical contract hierarchy?
A typical contract hierarchy starts with a parent contract, often a framework or master services agreement, beneath which sit the statements of work that implement it. Amendments then attach to whichever document they change, whether the framework itself or a single statement of work. Renewals and successor contracts are linked to the contract they replace, so the structure continues over time instead of starting again with each new signature.
What is the difference between a contract hierarchy and an order of precedence clause?
A contract hierarchy says which contract depends on which, whereas an order of precedence clause says which document prevails when two of them conflict. The clause ranks the documents of one contractual set, for instance special conditions above general terms and general terms above schedules. The hierarchy maps dependency between contracts across the whole relationship. A framework agreement usually needs both: a structure that ties each statement of work to it, and a precedence rule for the day a statement of work departs from the framework.
Does a contract hierarchy have legal effect?
A contract hierarchy has no legal effect of its own: it is a way of organising documents, and the legal consequences come from the contracts, the clauses that connect them and the rules of law that apply to them. Under Article 1186 of the French Civil Code, for instance, when the performance of several contracts is necessary to carry out one transaction and one of them disappears, the contracts whose performance is made impossible by that disappearance, and those for which performance of the vanished contract was a decisive condition of a party's consent, lapse, provided the party against whom the lapse is invoked knew of the overall transaction when it gave its consent. Whether a statement of work inherits the liability cap of its framework, for example, depends on the incorporation and precedence wording, not on where the document sits in a diagram. The hierarchy is still valuable because it shows which wording has to be read, and in which order.
How do you map the hierarchy of an existing set of contracts?
Mapping a contract hierarchy starts with finding, for each document, the contract it refers to, usually named by title, date and parties in the recitals or the first clause. Each document is then placed under the one it depends on, amendments are attached to the exact document they change, and renewals are recorded against their predecessor. In Pactolane, the user creates these links by hand, the result is displayed as a tree view, and PactAI can then answer questions about the whole family on the Growth and Scale plans.
Related terms
On the same topic
Other pages closely related to this one.