In plain terms
A family turns a stack of files into one object of analysis. No single member gives the full answer: the framework holds the general terms, each statement of work its scope and price, each amendment the changes agreed since, and the renewal the period now running. The commitments that actually apply result from reading all of them together, in the right order, with a later change prevailing over earlier text where the parties intended it to.
A family is a tree in principle and often a network in practice. A statement of work under which the supplier processes personal data on your behalf may also depend on a separate data processing agreement: Article 28(3) of the UK GDPR and of the EU GDPR requires processing by a processor to be governed by a contract or other legal act binding the processor, and many organisations put those terms in a standalone agreement that can serve several statements of work at once. A maintenance contract may rely on a software licence that also supports a hosting contract. Recording these cross-links matters, because a change to the shared document reaches every family that leans on it.
French law can give such networks legal weight. Under Article 1186 of the Civil Code, 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. That lapse applies only if the party against whom it is invoked knew of the overall transaction when it gave its consent. Whether a given set of contracts forms one transaction is a question of fact.
A contract family is not to be confused with a counterparty file: two unrelated contracts signed with the same supplier do not form a family unless one depends on the other. Nor should the family be confused with the documents that a single contract declares to be the whole agreement. An entire agreement clause states that the documents it identifies form the entire agreement between the parties, so a statement of work carrying its own clause should list or expressly incorporate the framework; otherwise, how the documents fit together becomes a question of construction, and the family may be read more narrowly than intended.
Why it matters in a contract
Treating the family as the unit of analysis changes the questions you can answer. What is the cumulative amount of the amendments against the cap in the framework? Which date comes next: a notice period in the parent, a delivery deadline in a statement of work, an end date moved by an amendment? Does any amendment contradict a term the framework still shows? Each answer combines several documents, and finding contradictions between a master agreement and the contracts beneath it is rarely possible one file at a time.
The family is also what a risk review should cover. A liability cap raised by one amendment, a price index changed by another and a renewal on new terms can together shift the balance of the relationship, even though each document looked reasonable on the day it was signed.
Pactolane sums up this approach in one sentence: you link your contracts, PactAI analyses the family. You attach each amendment, statement of work or renewal to its parent by hand, and the family appears as a tree view. PactAI can then answer any question about it, such as “What is the cumulative amount of the amendments against the framework agreement’s cap?” The machine prepares the reading; you decide.
Linking and querying a family are available on the Growth and Scale plans. The wider method, from the first contract to its successors, is set out in our reference on contract lineage across a relationship.
Example
A retail group’s marketing department works with a digital agency under a master services agreement that caps annual spend. Three statements of work run beneath it: a website redesign, a customer loyalty email programme and an analytics project. The analytics and email work both involve the agency processing customer data on the group’s behalf, so both rely on a data processing agreement signed separately with the agency. During the year, one amendment extends the redesign deadline and adds a paid second phase, and another changes the payment terms of the framework.
Before approving a fourth statement of work, the finance team needs three answers: how much of the cap is already committed, which deadline comes next, and whether the new payment terms apply to work already under way. None of the documents answers alone. Read as one family, with the data processing agreement linked to both statements of work that depend on it, each answer has a source: the committed amount is the total of the three statements of work plus the cumulative amount of the amendments, the next deadline is the earliest date across the framework, the statements of work and the extended redesign date, and the payment question turns on whether the framework amendment states that it applies to work already under way.
The same reading shows the network behind the tree. Any change to the data processing agreement will reach two branches of the family at once, so the team reviews both statements of work before signing it.
General legal information, not legal advice.
Frequently asked questions
What is a contract family?
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. It is the unit to read when the question is what the parties owe each other today, rather than what a single document says. The term comes from contract management practice and has no statutory definition.
What is the difference between a contract family and a contract hierarchy?
A contract hierarchy describes how related contracts are structured, while a contract family is the set those contracts form when they are read as one unit. The hierarchy answers who depends on whom: the statement of work on the framework, the amendment on the statement of work. The family answers what applies once all those documents are combined, which is the question finance, procurement and legal teams usually need settled.
Can a contract belong to more than one family?
A contract can belong to more than one family when it supports several parent contracts that are otherwise independent of each other. A data processing agreement signed once with a supplier may cover both a software subscription and a separate consulting framework, so it sits in two families at the same time. Recording that link matters, because any change to the shared agreement has to be checked against every family that relies on it before it is signed.
Why read a contract family as a whole?
Reading a contract family as a whole is how you find out which commitments apply, because each document holds only part of the answer. The cumulative amount of the amendments against a framework cap, the next date that requires action and any conflict between a framework and its amendments all depend on combining several documents. Reviewing them one by one tends to miss the interaction between them, such as an amendment that overrides a term the framework still displays.
Can Pactolane analyse a contract family?
Pactolane lets you analyse a contract family once you have linked its documents: PactAI then reads the family as a whole and answers any question about it. Examples include “What terms apply today after the amendments?”, “What is the family's next deadline?” and “Are there contradictions between the framework agreement and its amendments?” You link your contracts, PactAI analyses the family, and the decision stays with you. The feature is available on the Growth and Scale plans.
Related terms
On the same topic
Other pages closely related to this one.