⚠️ RESTRICTED ACCESS — This feature is exclusively available to certain clients under a specific contractual agreement. If you believe you should have access and cannot see this feature, please contact your Customer Success Manager.

The Contract Relationships module in DiliTrust CLM enables you to create, visualise, and manage complex contractual structures by linking related documents together into contract bundles (called "liasses contractuelles"). Attributes can be shared across documents within a bundle, and the full relationship tree can be visualised in the platform. Features are being progressively delivered across multiple lots.

⭐ Introduction

Modern contracts rarely exist in isolation. A master agreement may be supported by amendments, annexes, purchase orders, or sub-contracts — all forming a structured contractual chain. The Contract Relationships module formalises these links in DiliTrust CLM, allowing teams to navigate between related documents, share key data points across the bundle, and visualise the full contractual hierarchy at a glance.

Below you will find a chapter per capability with its current delivery status and planned availability date.

View the full feature prototype on Figma (internal access required)

✅ Attribute Sharing Between Linked Documents — Delivered: April 22, 2026

A key value of contract bundles is the ability to propagate information from one document to related documents — automatically. When an attribute (a field in the summary sheet, or "fiche de synthèse") is shared from one document to another within the same bundle, its value is automatically populated in the destination document.

How attribute sharing works

1. Open the source document (e.g., the master agreement) in CLM.
2. In the summary sheet (fiche de synthèse), locate the attribute you want to share.
3. Click the Share attribute option on that field.
4. Select the target document(s) within the same bundle to receive the attribute value.
5. Confirm. The value is immediately reflected in the destination document's summary sheet.

This eliminates manual data re-entry across related contracts and ensures consistency throughout the bundle.

See attribute sharing in the Figma prototype

✅ Attribute Origin & Destination Traceability — Delivered: April 22, 2026

When an attribute value is shared across documents, CLM tracks and displays the full chain: which document is the source of the value, and which documents have received it. This traceability ensures auditability and clarity for contract teams.

How to view attribute traceability

1. Open any document that is part of a bundle.
2. In the summary sheet, look for attributes that display a shared indicator.
3. Click on the indicator to view the origin (source document) and all destinations (documents receiving the value).
4. Click on any linked document to navigate directly to it.

⏳ New Inter-Document Link Type — Planned: June 3, 2026

Currently, CLM supports a standard set of document relationship types. With this upcoming feature, a new Parent / Child link type will be added to the list of available relationship natures. This allows teams to formally express hierarchical relationships between contracts — for example, a framework agreement (parent) and its individual purchase orders or amendments (children).

How the new link type will work

• When linking two documents, select Parent / Child as the relationship type.
• The parent document becomes the root of the bundle; children appear beneath it in the hierarchy.
• This link type enables the n-level cascading view (see below).

⏳ N-Level Contract Bundle Visualisation — Planned: June 3, 2026

As contractual structures grow more complex, with multi-level hierarchies (framework → contract → amendment → order), a flat list view is insufficient. This feature introduces a cascading, indented view of the full bundle — showing all levels of the contractual tree within the folder and document views.

What you will see

• In the Documents or Folder view, related contracts will appear indented under their parent document.
• You can expand or collapse each branch of the tree to navigate deep contractual structures.
• The hierarchy can go to any depth — n levels — reflecting the real-world complexity of your contracts.

See the bundle visualisation design in the Figma prototype

✨ Tips & Best Practices

• Define your bundle structure (which document is the parent, which are children) before linking documents — this will make the hierarchy intuitive for all team members.
• Use attribute sharing for key fields that must remain consistent across a bundle: contract value, counterparty name, governing law, etc.
• Always check the traceability view when editing a shared attribute, to understand which other documents will be affected.
• Once the n-level view is available (June 2026), review your existing document relationships to leverage the new cascading visualisation.
• Coordinate with your administrator to set up the Parent / Child link type before rolling it out to users.

◾ Limitations & Known Constraints

• The new Parent / Child link type is planned for June 3, 2026 — until then, only existing relationship types are available.
• The n-level cascading bundle visualisation is also planned for June 3, 2026; current views show linked documents but without deep hierarchical indentation.
• Attribute sharing only applies to documents within the same bundle — cross-bundle sharing is not supported.
• When a shared attribute value is updated at the source, the change propagates automatically; however, users should verify that all destination documents have been refreshed after an update.

❓ Frequently Asked Questions

What is a contract bundle (liasse contractuelle)?

A contract bundle is a group of related documents formally linked together in CLM — for example, a master agreement and all its amendments, annexes, and purchase orders. The bundle reflects the real-world structure of a contractual relationship.

Can I share any attribute from one document to another?

Attribute sharing is available for fields configured in the summary sheet (fiche de synthèse). Not all fields may be eligible — your administrator can define which attributes are shareable based on the document type configuration.

What happens to a shared attribute if I change the value at the source?

The updated value propagates automatically to all destination documents within the bundle. The traceability view will reflect the change and show the updated origin.

How many levels of hierarchy can the bundle support?

The upcoming n-level visualisation (June 2026) supports unlimited depth — reflecting any real-world contractual structure, however complex.

Can I remove a link between two documents?

Yes. Document links can be removed by users with the appropriate permissions. Removing a link will also stop attribute propagation between the previously linked documents.