Third-Party Contract Review demo
Checks every vendor contract, with its amendments, against the clauses DORA Article 30, the US interagency guidance and group policy require, and drafts the fixes for counsel to approve. 1:29
What the demo shows
For vendor risk teams: each vendor contract checked for the clauses DORA and regulators require
Reads each contract family (agreement, amendments, schedules, DPA) and resolves which text governs today. It marks every required item for the chosen regime as covered, weak or missing, cited to the page. A challenger agent argues each mark before a person sees it. Each gap gets a drafted clause from the approved library, with fallbacks for the vendor's likely pushback. Counsel approves and signs, procurement sends, the vendor's redline is read and re-scored, and the register of information is fixed from the same citations before the renewal notice date.
Transcript
- Third-Party Contract Review Checks Vendor Contract for the clauses regulators require for vendor risk teams.
- DORA lists 15 terms for every contract behind a critical service.
- On Corvain Cloud's hosting agreement, agents read 4 documents.
- 11 clauses covered, 2 weak, 2 missing, each cited.
- Amendment 1 replaced the Old Location Clause.
- The rail shows the lineage.
- The exit clause is weak, 30 days of transition, where policy needs 12 months.
- A challenger said the data schedule covers subcontracting.
- It covers personal data only.
- Each fix comes from the approved library, with fallbacks for Corvain's pushback.
- Counsel Elena Rossi approves the amendment with a reason code and signs.
- Procurement sends it, and a register agent fixes the data location from the amendment.
- Cited, signed, and logged.
- 57 contracts with gaps.
- Every fix drafted before renewal.
- Built on bot mines.
- Agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.