Contract lineage: linking parent contracts, amendments and SOWs

Why a contract is never read alone

Over a multi-year relationship, a contract gathers amendments, statements of work and renewals, often signed by different teams. Read alone, the original may no longer tell the truth. Five situations show why the family is the unit that matters.

Amendments only carry the changes

An amendment rarely restates the whole agreement. It says that clause 7.2 is replaced, that the price is indexed from a given date or that the term is extended by a year, and nothing more. A procurement manager at a regional logistics company who reads amendment No. 3 alone sees a new price but not the service levels it applies to; whoever reads the original alone sees the service levels at the old price. The terms in force only appear when both are read together, in order.

Cumulative caps under a framework agreement

Framework agreements often cap total value, while the commitments build up through successive amendments, each with its own amount. Picture a mid-sized food manufacturer buying packaging under a three-year framework agreement capped at 600,000 euros. Four amendments, negotiated by different sites, extend the scope and raise unit prices along the way. Each amendment looks reasonable on its own; the cumulative amount of the amendments against the cap only appears if someone links every amendment back to the framework and reads them together.

Contradictions between the framework and what depends on it

The master agreement sets the rules, and each SOW applies them to a project. Under time pressure, terms drift: the master agreement provides payment at 45 days, the fourth SOW says 30; the master caps liability, a later amendment sets a different figure. Spotting these gaps means reading each SOW and amendment against its parent, as our page on contradictions between a master agreement and the documents that depend on it shows in detail.

Interdependent contracts that fall together

Some contracts only make sense together. An IT services company may sell a client a software licence, an integration contract and a maintenance contract as a single project. If the licence ends, the maintenance contract loses its purpose.

For contracts governed by French law, article 1186 of the Civil Code provides that when several contracts are needed to carry out one operation 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. Lapse only applies if the party against whom it is invoked knew of the overall operation when it gave its consent. Knowing which contracts form one operation is a lineage question.

Audits, transfers and due diligence

Lineage becomes urgent when someone outside the contract team asks for it. An auditor wants the terms that applied during the financial year. A buyer conducting due diligence on a business unit wants every customer contract with its amendments, and needs to know which transfers require the counterparty’s consent. A group reorganising its subsidiaries needs to know which entity is party to what, a topic covered in our page on multi-entity hierarchies and scope.

The relationships to map

Lineage is built from a few relationship types, each with its own points to watch. These five matter most in a commercial portfolio.

Relationship	Example	What to track
Framework agreement and statements of work	A master service agreement with an IT provider, executed project by project through statements of work	Cumulative value against any cap, the framework’s end date, which framework terms each SOW applies or departs from
Contract and amendments	A software licence amended three times: price indexation, extra users, extended term	The order of the amendments, the clause each one replaces, the terms that apply today
Renewal and successor contract	A cleaning contract renewed tacitly twice, then replaced by a new contract after a tender	Renewal dates and notice periods, which terms carried over, where the predecessor stops and the successor starts
Novation and assignment	A supplier sells its business and its customer contracts move to the buyer	The current counterparty, the transfer date, the consents obtained, which obligations moved
Interdependent contracts	A licence, an integration contract and a maintenance contract sold as one project	The overall operation, the contracts within it, the effect on the others if one ends

For contracts governed by French law, each relationship has a statutory anchor in the Civil Code:

• article 1111: the framework agreement, and the implementing contracts that specify how it is performed;
• article 1193: modification by mutual consent of the parties, the basis of an amendment;
• article 1215: tacit renewal;
• articles 1216 and following: assignment of a contract;
• articles 1329 and following: novation;
• article 1186: the lapse of interdependent contracts.

Under another governing law, check the equivalent rules with counsel; the mapping discipline stays the same.

Novation and assignment both move a contract position to a new party but work differently, as our comparison of assignment and novation explains: under English law, an assignment generally transfers only the benefit of the contract, whereas a novation replaces a party with the consent of all; under French law, an assignment of contract (articles 1216 and following of the Civil Code) transfers the status of party with the other party’s consent. In every case, record the transfer date. A framework agreement and the individual contracts made under it also play distinct roles, set out in our page on framework agreements and the contracts made under them.

Contract hierarchy, contract family and parent contract

Three related terms describe the structure that lineage maps, each answering a slightly different question.

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. The hierarchy answers the question “who depends on whom?”.

A parent contract is the contract that other contract documents depend on: it sets the framework or initial terms that child contracts implement or that amendments change. It sits at the top of the hierarchy: a master service agreement, a framework agreement or simply the original contract.

A contract family is the set formed by a parent contract and every contract document linked to it (amendments, statements of work, renewals), read together to know which commitments actually apply. The family is the unit you read, audit and query.

Lineage connects the three. The hierarchy gives the structure, the parent contract the starting point and the family the full set, while lineage records the chain that ties each document to the others, including across time, from a predecessor contract to its successor.

Lineage is not an order of precedence

An order-of-precedence clause answers a different question: which document prevails when two documents in the same contractual set conflict, for example the master agreement over a SOW on legal terms. Our comparison of MSAs and SOWs explains what such a clause usually provides.

The two work together: lineage tells you which documents belong to the family, and the precedence clause, read within that family, resolves a clash between them. An entire agreement clause is a neighbouring tool again: it fixes which documents form the agreement and sets aside earlier negotiations, without ranking them.

How to map the lineage of a contract portfolio

Mapping lineage is a structured exercise rather than an IT project. The five steps below can be carried out in stages, starting with the relationships that carry the most value or risk.

1. Take an inventory. Gather the contracts and every document that changes or depends on them: amendments, side letters, SOWs, renewal letters, transfer agreements. Bring documents scattered across email and shared drives into one place.
2. Identify the parent contracts. For each relationship, find the document that sets the framework or initial terms: usually the master agreement, the framework agreement or the original contract. Where two documents could play that role, choose the one the others refer to.
3. Link each document to its parent. Attach every amendment to the contract it modifies, every SOW or implementing contract to its framework, every renewal or successor to its predecessor, and connect interdependent contracts. Record the type of link, not just its existence.
4. Check consistency. Look for amendments that refer to a contract you cannot find, gaps in amendment numbering, SOWs signed after the framework expired and transfers with no record of consent. Each gap is a missing document or a question for the business owner.
5. Query the family. Read each family as a whole: the terms in force today, the next deadline, the cumulative amount of the amendments against the framework agreement’s cap and any contradiction between the parent and its children.

Step 3 calls for judgement, and it makes everything else reliable: a link drawn by someone who knows the relationship is a fact the team can build on.

What Pactolane does for contract lineage

Pactolane keeps your contracts in a single searchable repository, imported from PDF and DOCX files, and lets you link them into families. You link each document manually, and every type of relationship is covered: an amendment to the contract it modifies; a statement of work or an implementing contract to its framework agreement; a renewal or successor contract to its predecessor; and interdependent contracts to one another.

The linked family is displayed as a tree. Each document sits under the contract it depends on, so you see the structure of a relationship at a glance, from the parent contract to the latest amendment, instead of piecing it together from file names.

Once the family is linked, PactAI analyses it as a whole and answers any question you ask about it, for example:

• “What terms apply today after the amendments?”
• “What is the family’s next deadline?”
• “Are there contradictions between the framework agreement and its amendments?”
• “What is the cumulative amount of the amendments against the framework agreement’s cap?”
• “Do the new amendments affect the parent contract’s risk score?”

The division of work is deliberate. You link your contracts, PactAI analyses the family. The people who know each relationship build the tree reliably, and the AI draws the reading from it. The PactAI product page presents the assistant in more detail.

The rest of the platform supports the same families: seven access roles per contract, an audit trail, multi-level approval workflows for new amendments and statements of work, a simple electronic signature (SES) compliant with eIDAS, and connectors to DocuSign and Yousign. Contract data is hosted in France and Belgium on Google Cloud and encrypted with AES-256-GCM, and personal data is removed before any AI processing.

Family linking, the tree view and PactAI’s analysis of each family are available on the Growth plan, at 499 euros per month, and on the Scale plan, from 2,500 euros per month, as listed on the Pactolane pricing page.

Who builds the family, who reads it, who decides

Pactolane prepares two things: the tree view of each family you have linked, and a reading of that family on demand, through PactAI. The machine prepares, you decide.

Everything that commits the company stays with you. You decide which document is the parent and how each one is linked; Pactolane displays the links you create. You decide how to interpret a contradiction that comes up in PactAI’s answer, which term prevails under your precedence clause, and whether to renegotiate, amend or let a contract run to its end. PactAI answers when you ask it, so the questions, and their timing, stay with your team.

For questions that turn on the law, such as whether interdependent contracts lapse together or whether a transfer needed consent, the analysis gives your lawyer a clear starting point. Legal advice remains the role of your counsel.

Choosing a CLM for contract hierarchies

If you are comparing tools, our buying guide on which CLM can manage contract hierarchies and dependencies sets out the criteria to test: how links are created and by whom, how the family is displayed, what the AI can answer about it and which plans include it. For contracts that accumulate changes over time, see also managing multiple contract amendments.

Frequently asked questions

What is contract lineage? Contract lineage is the mapped chain of relationships between a contract and the documents that derive from it or change it: the parent contract, statements of work, amendments, renewals and successor contracts. It shows, for each contract, where it comes from, what changes it and what depends on it. It is a term of contract practice rather than a legal term, resting on notions such as framework agreements, amendments and novation. In Pactolane, it takes the form of contract families that you link and view as a tree.

How does contract lineage differ from an order-of-precedence clause? Contract lineage says which documents depend on which, while an order-of-precedence clause says which document prevails when two of them conflict. Lineage is a map of the relationships in a contract family, built by linking each amendment or SOW to its parent. A precedence clause is a term of the contract that ranks the documents. You need both: lineage to know which documents are in play, precedence to resolve a conflict between them.

Does Pactolane link amendments to their contract automatically? In Pactolane, you link each amendment and related document to its contract yourself, then PactAI analyses the linked family as a whole: every link is a deliberate choice by your team rather than an automatic match. This keeps the tree reliable, because each link reflects the knowledge of someone who understands the relationship. Every type of link is available: amendments, SOWs and implementing contracts, renewals and successor contracts, and interdependent contracts.

What can PactAI answer about a contract family? PactAI analyses a linked contract family as a whole and answers any question you ask about it. Examples include “What terms apply today after the amendments?”, “What is the family’s next deadline?” and “What is the cumulative amount of the amendments against the framework agreement’s cap?”. PactAI answers when asked; the interpretation and the decisions that follow remain with your team and, where needed, your lawyer.

Which Pactolane plans include contract family linking and analysis? Contract lineage in Pactolane, meaning family linking, the tree view and PactAI’s analysis of each family, is available on the Growth plan at 499 euros per month and on the Scale plan from 2,500 euros per month. Teams on the Team plan, at 149 euros per month, can move up to Growth when they need to link and analyse contract families.

Do you have to link the whole contract history at once? No, contract lineage in Pactolane can be mapped in stages, starting with the families that carry the most value or risk. A sensible first pass covers active framework agreements with their current statements of work, and contracts with several amendments, since that is where the terms in force are hardest to read. Older relationships can be linked later, as audits, renewals or transfers bring them back into view.

Start with one contract family

Contract lineage turns a pile of separate documents into families you can read, check and query. To see how linking and family analysis work on your own portfolio, book a Pactolane demo and bring a framework agreement with its statements of work, or a contract with its amendments.

Updated 13 October 2026

General information, not legal advice.