Corporate groups sign document stacks. Disputes rarely respect document boundaries.
Shareholder agreements, SPAs, guarantees, supply agreements, licences and project documents can create one commercial conflict across several contracts and parties. Clause compatibility should be designed before consolidation becomes urgent.
The Clause Compatibility Matrix
The point is to make hidden drafting decisions visible before they become procedural disputes.
The Clause Compatibility Matrix
Clause decision architectureSeat, rules, parties and scope.
May contain a different clause.
Parent, subsidiary, guarantor, JV or affiliate.
Article 35 addresses multi-party / multi-contract proceedings.
Compatibility and common issues can support one process.
What the drafting is actually trying to control.
This is drafting intelligence, not a substitute for transaction-specific legal advice.
Same institution
Use compatible institutional rules across related agreements.
Alignment
Avoid conflicting supervisory legal systems where consolidation is expected.
Related claims
Ensure clauses capture connected disputes.
Affiliate logic
Do not assume non-signatories are automatically bound.
Mechanism
Align clauses with Article 35 possibilities.
Parallel relief
Coordinate emergency / interim options across documents.
Where sophisticated-looking clauses break.
Most drafting defects only become expensive when the parties need the clause urgently.
| Failure mode | What happens | Why it matters |
|---|---|---|
| Different institutions | Fragmentation | Related claims may have to proceed separately. |
| Different seats | Conflict | Consolidation can become legally / procedurally difficult. |
| Incompatible wording | Consent problem | Related agreements may not support one proceeding. |
| Affiliate assumption | Jurisdiction fight | Corporate relationship alone does not equal arbitral consent. |
| Guarantee carved out | Split remedy | Debt and guarantee claims may travel separately. |
The clause can activate an institutional lifecycle, not merely a hearing.
Article 35 expressly authorises proceedings involving relevant parties and contracts where consent / compatible agreements permit, and allows consolidation in specified related-dispute circumstances.
The clause becomes important only after breach.
Clause language is treated as boilerplate until the dispute makes every word operational.
The clause manages the relationship from uncertainty to outcome.
The clause is designed as an operating system for the full dispute lifecycle.
Turn the clause into a controlled decision.
The same workflow can be used by outside counsel, in-house legal teams and procurement / contracting functions.
Find the exact commercial / legal problem.
Separate parties, contracts, seat and assets.
Choose the minimum architecture that solves the problem.
Run DPC / CIS™ checkpoints where appropriate.
Sign the reviewed version and govern deviations.