https://embed.notionlytics.com/wt/ZXlKd1lXZGxTV1FpT2lJek5URmlOalV5TURRek5UQTBObUU0WVRJNE16VXdNRGhrT1dGbU0ySXdPQ0lzSW5kdmNtdHpjR0ZqWlZSeVlXTnJaWEpKWkNJNklrWlpTMHBYVWsxM1VteERUWEk1YlhobFNrUklJbjA9
A contract has metadata — agreement date, address, contract value, term length, you name it.
<aside> 🔄 Contract metadata is dynamic. It changes as the contract and its terms change during the negotiation process.
</aside>
This project aimed to build more integrity and maintain contract accuracy through an experience powered by a merge algorithm that integrates metadata and contracts in Ironclad.
While concurrently working on the Editor Redesign project, I led the design for this project and took it from ideation through usability testing, and shipped an MVP as part of a beta program run for selected customers between Jun—Oct 2020. Based on feedback from the program which ran for ~1.5 years, I also worked on subsequent iterations. In addition, I also collaborated with a Product Manager and a couple of engineers.
Ironclad's Workflow Designer lets users embed fields in document templates for capturing metadata. A form collects data at workflow launch and generates a document from the template. Updating and versioning a document can occur via the same form during the workflow, or even via an integration with a system like Salesforce, but it has limitations as it relies on the template to generate a new version.
Non-standard contract changes made outside Ironclad or in Ironclad Editor result in a version that deviates from the template. So when the metadata is updated, the document is no longer automatically updated with the new metadata.