Click to view related learning resources:
- Plan Your Data in Ironclad: This article will walk you through how to create a data schema plan before you begin using Data Manager. This will help you create a solid foundation for you to build your future workflow configurations around.
- Clean Up Data Schema Models in Ironclad: This article will walk you through how to clean up your data schema models in Ironclad. This includes how to merge new and existing data, remove invalid data, and manage default data.
- Manage and Optimize Data Schemas: This article will provide an overview of data schema management and provide a list of relevant resources for further data management.
- Improve Data Discoverability: This article will walk you through how to improve your data’s discoverability.
- Use Metadata Import to Clean Up Stored Contract Data in the Repository: This article will provide you with best practices on how to use metadata import to clean up your stored contract data in the Repository.
-
We highly recommend taking our Manage Data in Ironclad course in Ironclad Academy. After you complete this course, you will be able to:
- Explain Ironclad’s data structure and its relationships to your contracts.
- Identify system-generated properties within the Lifecycle Preset.
- Define and manage the data you track in Ironclad with Data Manager and Workflow Designer.
- Add and configure the Lifecycle Preset in your workflows.
- Align your data structure to Ironclad’s standard, system-generated properties.
This article will provide you with definitions of some key Ironclad data concepts and terms related to Data Manager.
Ironclad Data Manager uses a combination of data schemas, properties, clauses, and record types associated with your contracts and users. Review the table below to learn more about each term:
Term | Definition | Relevant Articles |
---|---|---|
Data Schema | The structure and organization of data within a database or system, including the definition of data events, properties, and their relationships. | |
Properties |
Data properties are attributes or characteristics of a contract, workflow, or other data objects in Ironclad, such as the contract type or the signing date. At a high level:
Ironclad Data Tip: Standardize your data property naming conventions to make your data schema easier to read and manage. Avoid multiple properties with similar names but different meanings or data sources. |
|
Clauses | A clause or clause type, also known as a provision, is an attribute describing a section, phrase, paragraph, or segment of a legal document, such as a contract, deed, will, or constitution, that pertains to a specific point. Clauses generally consist of eight or more words and can be described in one or more sentences. | |
Record Types | A category or classification of a document or artifact created, negotiated or stored in Ironclad, such as a Non-Disclosure Agreement (NDA) or a Master Service Agreement (MSA). | |
Date Events |
A data event is a generic term that refers to any significant occurrence, action, or state change within a system or application that is worth tracking and analyzing. In the context of Ironclad, data events can represent various data objects, user actions, system events, and updates to the structured data model. Examples of data events include:
Data events help track and analyze the usage, performance, and effectiveness of different aspects of the Ironclad platform. |
|
Data Quality | The accuracy, completeness, consistency, and reliability of data. High-quality data is essential for making informed decisions and driving business value. |
Related Terms
While these concepts and terms are not directly included in Ironclad Data Manager, you may see these related terms as you learn more about how Ironclad Data Manager functions.
Term | Definition |
---|---|
Workflow Configuration | A workflow configuration is the setup and structure of an automated process in Ironclad, defining the steps, approvals, and data requirements for a specific contract type or business process. |
Workflow | A workflow is an automated process in Ironclad that defines a series of steps, tasks, and approvals required to complete a specific business process, such as contract creation, negotiations or approvals. |
Repository | A centralized storage area in Ironclad where all contract documents and related artifacts are stored and managed. |
Integrations | You can integrate Ironclad Data with your existing tools to streamline data management. To integrate a platform, navigate to Company Settings > Integrations and link the new/modified data property. To learn more, refer to Manage Integrations. |
Related Records | The most general record is a related record - a simple one-to-one relationship between two contracts. This is most useful when representing the relationship between contracts that don’t directly modify each other, but you might want to reference together. An example of this might be a Non-Disclosure Agreement(NDA) and a Statement of Work(SOW).To learn more, refer to Manage Related Records in Workflow Designer. |
Contract Families |
Parent and child records represent a more specific type of contract relationship where the contracts directly reference or modify each other and must be evaluated as a group. Child records are usually sub-agreements or amendments of the parent record. Each parent record can have multiple child records, but each child record can only have one parent record. Child records can also be parent records themselves. If you build multiple levels of parent/child relationships, you create a contract family. When a record is a part of a contract family, in addition to the record’s direct parent and child records, you can see the entire contract family. |