The situation
An organisation signs agreements over years, under different counsel, on different templates, with negotiated variations. Each was understood at the time by the people who negotiated it.
The question that arises later is portfolio-shaped: across everything we have signed, where are we exposed to this obligation, this notice period, this indexation mechanism, this change-of-control clause.
Why it is hard
The same obligation is drafted twenty ways
Searching for a phrase finds the contracts that happen to use that phrase, which is not the same as finding the obligation.
Variations live in side letters
The signed agreement may be amended by documents filed separately. Reading the base contract alone gives a confident wrong answer.
Dates are derived, not stated
A notice deadline is usually a function of a trigger date and a period, neither of which is a field in any system.
How we approach it
Agentix extracts obligations, parties, dates and financial values across the portfolio and resolves amendments against the agreements they modify, so a question about exposure is answered against the contract as it currently stands.
Each extraction cites the clause. Where a side letter changes the position, both the base clause and the amendment are returned.
What changes
- Obligations found by meaning rather than by phrase matching
- Side letters and amendments resolved against the base agreement
- Derived dates calculated from trigger and period, with both cited
- Every extraction traceable to its clause
Next
Is this your problem too?
Bring the version of it you actually have. We will tell you what it would take, including when the answer is that it is not worth doing.
N Catalyst.ai
Book a demo
