DiscoverAI

Contract Highlights

Whenever contracts are sent to CXOs, legal or finance teams for their approval or signatures, they are interested to know if a certain language is present or absent in the contract. This helps them to understand the nuances of the contracts, viewpoints of various stakeholders, etc. and they can quickly take an informed decision.

With this release,

• The DiscoverAI model can find the terms in documents and highlight them for business decision makers. Configurators can now specify the important words by the business so that the DiscoverAI model can find matching as well as similar terms in documents and highlight them for the intended audience.
• In case no phrases are specified, then ICI will identify the important sections in the contract based on learnings from historical data. The identified sections will also be ranked in order of importance.
• A configurator can also specify the maximum number of highlights to be extracted from the agreements. The AI algorithm would rank the findings and present only the top ranked highlights to the user.
• Configurators can configure the event to generate the contract highlight, for example agreement updated, etc. Using this configuration, when the specified event occurs, ICI will identify the important sections of the contract based on historical data and phrases specified by the configurator

To configure generating contract highlights from an agreement:

1. Create an Agreement Contract Type using Third Party Paper. You can use an existing Agreement Contract Type as well.

2. Click Next, the Attributes page opens.
3. To be able to generate contract highlights from an Agreement, include the following attributes in the Agreement Contract Type:

• Contract Highlight Terms: The Data Type must be selected as String. In the Default Value attribute, enter the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.
• Contract Highlights: Here the Data Type RichTextArea must be selected.

4. Create an Associated Document Contract Type, for example, ICILegalHighlights to generate contract highlights for your legal department.

5. To add contract highlights in an Associated Document, include the following attributes in the Associated Document Contract Type.

• Contract Highlight Terms: The Data Type must be selected as String. In the Default Value attribute, enter the different terms or keywords expected in the highlight, separated by a pipe symbol. For example, Legal|Confidentiality|Liability|NoOfRecords:10.
• Contract Highlights: Here the Data Type RichTextArea must be selected.

To add the created Associated Document Contract Type to the Agreement Contract Type:

6. On the Contract Types page, click the Agreement Contract Type created earlier. The Details page for that contract type opens.
7. Click the Edit button. The Edit Contract Type wizard opens.
8. Navigate to the Association tab by clicking Next.
9. Click the plus icon next to Association.
10. Create an Association for the Associated Document Contract Type.

• Select the created Associated Document Contract Type. You can set the Allow Multiple Instance option to Yes, to allow different contract highlight associated documents to be created for different departments, such as legal or finance.

11. Create a template for the Associated Document.

12. Create a Template Selection Rule for the Associated Document.

13. Create an Event Rule with the action AITriggerContractHighlights.

14. To get the contract highlights in the Associated Document, you need to create an Association with the Parent Agreement.

15. Click Next. The Meta Data page opens.
16. Enter the keywords in the Contract Highlight Terms. For example, CEO|Liabilities | Amount |Penalty |obligation| regulation| price| jurisdiction|NoOfRecords:10.
17. Add NoOfRecords:n where 'n' denotes the number of contract highlights to be extracted. The default is NoOfRecords:20, if the value of n is not specified in the keywords.
18. When an Agreement created using the selected Agreement Contract Type is published, the configured contract highlights will be extracted and compiled in the Associated Document.

Bulk Upload with Clause Discovery

To upload Agreements in bulk:

1. Click Agreement Management > Agreements on the dashboard. The Agreement Management page opens. Let us take an example of an Agreement Contract Type (CT1) that should have already been created and published.

2. Click Bulk Actions > Bulk Actions on the dashboard. The Bulk Action Management page opens.

3. Click Add Batch. The Add Batch pop up window opens. 

4. Click the Select Batch File button to select the file for a bulk upload. In this example, we are selecting the LegacyBulkUpload.zip file.

• The Meta.xlsx files contains data related to ContractType (CT1 in this case), CTTypeofContract (Agreement Contract Type), Technical Name of the Attributes present in the Contract and Display Name of the Attributes. 

• The Data.xlsx files contains all the Attributes in Contract Type (CT1) as a column name in which the data gets auto-populated from the PDF/docx file. User needs to add the Bulk Upload Business Status is Executed and the file name under File Path column in Data.xlsx file. 5. Click the Submit button. The File Uploaded Successfullymessage is displayed. 

5. Click the Submit button. The File Uploaded Successfully message is displayed.

6. Click OK. The file is now displayed in the Grid view with the status Not Started. 

7. Click Refresh icon twice. On first Refresh, the Status changes to In Progress and then to Needs Validation.

8. Select an Actions radio button for the file that you want to finalize. The Validate and Finalize buttons are enabled.

9. Click the Validate button to download the PopulatedData.xlsx file. The values of the Attributes can be edited in this file. 

Note: The data in the Excel sheet that is marked green signifies the highest confidence level, data in yellow indicates medium confidence level and data in red indicates lowest confidence level. You can then make any changes to the Attribute values. (In this example, you can make changes to the Attribute value from the downloaded PopulatedData.xlsx file). 

10. Click Save to save the changes.

11. Click the Finalize button, the PopulatedData.xlsx file can be uploaded. The Finalized File Uploaded Successfully message is displayed.

12. The Needs Validation status changes to Completed. 

13. Click the Agreements tile to view the Agreements which will be in the Draft state.

Table Discovery

Along with clauses and metadata, ICI also extracts tables (including information such as SLAs, price list, etc.) in Agreements and displays them on the Tables tab (on the Details page). ICI tries to match the discovered table(s) with the Associated Contract Types of the Agreement. If a strong match is found, then the table is tagged with that Associated Contract Type, and the table columns are also matched with the Attributes of that Associated Contract Type.

You can then take relevant action such as creating new instances of the Associations. Automatically recognizing table data inside the Agreements saves a lot of manual labor of identifying and tagging the data correctly.

The table discovery allows you to:

• Identify and discover the table(s) in the Agreement Document
• Update the data in the discovered table as required
• Create new instances of the Associations for the uploaded Agreement

The table discovery in PDF agreements works well with:

• Tables with well-defined borders in text PDFs and high-quality scanned PDFs
• Tables that may be slightly skewed or tilted
• Table cells with light-colored backgrounds

The table discovery in PDF agreements may not work well with:

• Tables in low-quality scanned PDFs and those without borders
• Tables without well-defined borders or characters overlapping the table border, etc., due to certain OCR limitations
• Certain non-table elements, such as flowcharts and diagrams
• Tables with merged columns and rows
• Nested tables, which may be discovered as multiple tables

Discovering Tables in an Agreement

To discover tables in an Agreement:

1. Create an Agreement (Third Party Type Of Paper). 

2. Ensure that the Clause Discovery functionality is turned On and the Contract Type is enabled for table discovery.

3. Create and Publish the Agreement. ICI automatically queues the Agreement for table discovery.

Viewing Discovered Tables in an Agreement

You can view all the discovered tables in an Agreement, so that you can review them and take actions as needed (based on whether they meet the criteria for creating an associated document or not).

1. Click the Tables tab on the uploaded Agreement Details page.
2. ICI displays a list of the Discovered Tables for that Agreement Document.

Editing Table Data

1. Click the Edit Table Name icon next the table that you want to edit. For example, Table 2.

2. Toggle the Has Header button toYes if you want the table to have a header.

3. Click inside the header box to add the header name. For example, PSE Workers, Term, etc.

4. Click inside each of the boxes to add data in the columns. For example, 3.0 (Version), 09 Sep, 2019 (Date Released), etc.

5. Click Save Changes to save changes if you want to review or edit them later. The Table data saved message is displayed.

6. Select the Association for which you want to create this data from the Select Association drop-down. For example, Payment Details.

7. A validation message is displayed to check if you want to save the updated data. Click Save to update the data in the table, else click Discard.

8. Select the checkbox for the rows and columns that you want to update.

9. Click Finish. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.

10. Click Yes if you are sure that you want to update the table and proceed.

11. A message is displayed indicating that the table data is saved and the Associations are being created. Click Yes if you are sure that you want to update the table and proceed, else click No.

12. You can view the associations on the Associations tab.

13. Click View Record to view the details of the individual records.

14. You can take further action as needed. For example, send it for Approval.

Selecting the Type of Table to be able to create Associations for it

You can create Associated Documents using the data in the discovered tables. You are basically discovering the Associated Document type and the columns associated with that document type.

To do so:

1. Click the Tables tab on the uploaded Agreement Details page.
2. In the Discovered Tables window when matching data is present, the exact Associations with that table are discovered. For example, the Payment Details are discovered. These are associated and the names of the header are also discovered. 

3. You can select whether the table should have a header or not by enabling the Has Header flag to Yes. 
By doing this, the first row of the table will be marked as the header and Associations will not be created for it. If there are 2 rows other than the header, then 2 Associations will be created. A green tick mark will be displayed next to them which means that they are successfully created in the Tables tab. 
4. In the Discovered Tables window, make changes in the table as required. For example, select 3 rows and columns.

Saving the changes of the Table Discovery for the Agreement

You can save the interim progress of the Table Discovery for an Agreement, so that you can review it later by:

1. Click Save Changes. The Table data saved message is displayed.

Finishing the Table Identification for an Agreement

You can complete the Table identification for an Agreement, so that the identified tables become part of the Agreement. 
1. Click Finish. A message will be displayed indicating that you will not be able to make any changes to the table data.

2. Click Yes if you are certain that you want to make the changes, else you can save changes and review them later. 
3. Click the Associations tab to see the Associations that are discovered, as shown in the screenshot below: 

4. Click the Payment Details association to view the details and send for approval.
5. Click Export to Excel if you want to export the table that has been discovered. 

Note:

• Once the Associations are created, you cannot make any changes to the table. The table is disabled and the status changes to Review Completed.
• It is not necessary to match every table to one of the association contract type. You can still make changes to such tables and download them using ‘Export to excel’ functionality.

DiscoverAI - Support for Own Paper

ICI already leverages the DiscoverAI app to discover attributes, clauses, tables and obligations in agreements created using third party paper type.

Now, ICI has extended the support to discover attributes, clauses, tables and obligations in agreements created using own paper type, and tagging the attributes and clauses to the original agreement document. This helps convert unstructured documents into structured agreements, making it easier to manage and also increase compliance.

Note:

• Tagging is supported only in Word documents.
• The attributes and clauses that have been confirmed in ICI (even on the web UI) are tagged back in the agreement document.

Discovering Attributes, Clauses, Tables and Obligations

To discover attributes, clauses, tables and obligations using own type of paper:

1. Create an agreement using Own Type of Paper.

2. Click Next. The Attributes page opens.

3. Select Discover AI from the Clause Discovery Type drop-down and ML based from the Obligation Discovery Type drop-down.

4. Click Next. The Select Template page opens.

5. Select a template or upload a file.

6. Click Next.

7. Click Create and Publish. The agreement Details page opens.

All non-tagged attributes, clauses, tables (if present in the agreement document) and obligations (if you select the value in the Obligation Discovery Type drop-down) are discovered.

Tagging Discovered Attributes

1. Click the Attributes tab.

2. Click Save to confirm the attributes. You can also modify the discovered attribute values by clicking the View potential matching values icon and then click Save.

3. The Metadata Save Confirmation message is displayed.

4. Click the Versions tab.

5. Download the latest version of the agreement in Word format. The discovered attributes are tagged as ICI attributes in the agreement document, as shown in the screenshot below:

Tagging Discovered Clauses

1. Click the Clauses tab. The discovered clauses are displayed.

2. Take actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.

3. Click Finish to complete the review process, as shown in the screenshot below:

4. Click the Versions tab. A new version of the agreement is created in both Word and PDF formats. 

5. Download the latest version. The confirmed clauses are tagged as ICI clauses in the agreement document.

Note:

• If you create a new agreement and upload the Word document that was downloaded in Step 5, the discovery will be triggered, however the clauses that were already confirmed and tagged as ICI clauses are not displayed.
• Only when the agreement is published, the clauses that you confirm on clicking Finish will be saved as ICI clauses and displayed in the Agreement Clauses tab on the Details page.
• A new agreement version is created each time you save the discovered attributes and confirm the clauses by clicking Finish.

Inbuilt Discovery of Attributes and Clauses

Previously, discovering attributes and clauses in customers’ agreement documents was time consuming as it required retraining of the algorithms from scratch, causing delay in deployment of services.

Now, ICI has an inbuilt discovery model that helps to automatically extract and discover the most common attributes and clauses in agreements besides enhancing clause delineation in third party contracts. This facilitates the prediction of accurate clause categories and capturing the right metadata within clauses. This improves contract turnaround time and quality of results, thus leading to improved user experience.

The inbuilt discovery model supports the discovery of the following predefined attributes and clauses in any MSA, NDA and SOW third party paper contract types:

• Attributes: Party Name, Party Address, Effective Date, Expiry Date, Contract Value, Contract Duration, Renewal, EverGreen, PaymentTerms, Jurisdiction, Governing Law, Notice Period For Termination, LiabilityType and ComplianceType

Note: The Contract Value attribute supports the following currencies - USD, CAD, EUR, INR and CAN

• Clauses: Amendment, Assignment, Audit, Confidential Information, Conflicts, Counterparts, Definitions, Dispute Resolution, Entire Agreement, Force Majeure, Governing Law, Indemnification, Insurance, Intellectual Property Rights, Limitation Of Liability, Non-Compete, Non-Solicitation, Notices, Payment Terms, Penalties/Remedies, Personnel, Preamble, Publicity, Relationship Of Parties, Representations, Warranties and Compliances, Severability, Signature, Survival, Taxes, Term, Termination, Waiver, Deemed Acceptance, Acceptance Criteria, Rejection Remedy, Cost of Living Adjustments, Most Favored Customer, Use of Third Party Software, Exclusivity, Subcontract, Technology Escrow, Governance Schedules, Termination Assistance, Change Control, Non Circumvention, Rebates and discounts, Fixed Liability, No Liability and Uncapped

The discovery support has been further extended for URL datatype attributes. DiscoverAI  would be able to discover the URLs in contract and associate them with URL datatype attribute. Also, users now would be able to select and save multi-choice attributes as well as multi-choice lookup datatypes on the Attributes Discovery page.

With this release, identification of the following attributes in the document has additionally been introduced: City, State, Zip code, Country, Point of contact – Name, Point of contact – Title, Point of contact – Address, Point of contact – Email and Point of contact – Phone.

Users can manually trigger the attribute discovery on the Attributes page itself, while uploading a third-party document, during the agreement creation process. Discovered values will then be auto-filled in empty attributes and users can view additional potential options for the discovered attributes. 
Users can: 
•    View the progress of the attribute discovery. 
•    Identify AI discoverable attributes on the “Attributes” page of the agreement creation wizard.
•    View the values recommended by AI for discoverable attributes.
•    View the agreement document on the “Attributes” page itself, for quick validation of AI recommended values for discoverable attributes as well as attributes values already tagged in the agreement document.

Discovering Common Attributes and Clauses

1. Create an agreement using Third Party Type of Paper.

2. Click Next. The Attributes page opens.

3. Select a document in the File Path field. For example, ICMMasterServiecesAgreement.pdf. The Discover Attribute button will be displayed, using which user can trigger attribute discovery manually.

4. Click Discover Attributes. 

The discovery process starts in the background and the details are displayed on the Attributes page.

• The Document is displayed in a side by side view in a pdf format.
• The two-column attributes layout is converted to the single column layout to accommodate the agreement document view.
• The Discoverable Attributes are indicated with a grey bar as the Discovery confidence indicator and are disabled, notifying users that they don’t need to enter the values for these attributes. For example, attribute Effective Date.
• The discovery process progress bar is displayed at the bottom indicating the progress in percentage with a Stop button.
• The Attribute discovery is in progress is indicated for each discoverable attribute by three dots icon.

Once the discovery process is complete, the document presents the discovered attributes with all potential matching values as suggestions. 

5.Click the View potential matching values icon corresponding to the discovered attribute to take actions on them such as Accept or Keep Selected Text. For example, TerminationPeriod has two suggestions.

The first value in the suggestions will be selected by default. For example, 8 years. Users can select any value from the presented suggestions.

The attribute values are normalized and displayed based on the defined rules. For example, the Effective Date is displayed in the ICI-supported format, as shown in the screenshot below:

eDiscovery using AI

With this release, we are now introducing a framework using Artificial Intelligence to automatically identify and analyze clauses in the legacy contract. This will help contract owners to leverage existing documented clauses and derive insights from them.

With eDiscovery using AI:

• ICI can automatically confirms certain discovered clauses, so that users do not have to confirmed them manually
• Auto confirmed clauses can be searched same as any other agreement clauses.
• Contract owners can distinguish between automatically confirmed clauses and those that have been manually confirmed. This helps contract owners to treat automatically confirmed clauses with extra precaution as compared to standard clauses.
• Configurators can now specify list of clauses by the agreement contract types which should be discovered and confirmed automatically.
• While auto confirming, ICI compares the discovered clause text with the clauses in the clause library. If the clause text matches more than a threshold value (say 70%) with clause in clause library, then discovered clause is identified as the clause library clause. If the match percentage is lesser than the threshold then clause is identified as one of the standard ICI AI clause category.

This feature is available in ICI through a technical configuration. To configure the eDiscovery of clauses:

1. Configure an Agreement Contract Type specific to eDiscovery. While configuring the attributes for the agreement contract type, the eDiscovery Mode and Clause Discovery Type attributes must be added.

2. Configure a Masterdata Contract Type named EDiscoveryAutoConfirmList. It should contain two attributes:

• Contract Type (Datatype: String)
• Clauses (Datatype: String)

3. Create Masterdata using the newly created Masterdata Contract Type. While configuring the Masterdata:

• Specify the Contract Type name for eDiscovery (created in Step 1).
• Specify the Clauses that need to be auto-confirmed post eDiscovery, for example preamble, payment terms andsignature.

4. Create an Agreement using a contract type configured for eDiscovery.

5. Click Next, the Attributes page opens.
6. Select an Agreement file.
7. Select the Clause Discovery Type as Discover AI.

8. Select the eDiscovery Mode.

The eDiscovery Mode attribute has 3 options: None, Auto andManual Review.

• Auto: By selecting this option, the clauses will get auto-confirmed and added as agreement clauses. The user will not have an option to review the discovered clauses.
• Manual Review: By selecting this option, the clauses will only be confirmed, and the user still has the option to go to each clause and ignore or confirm these clauses. These clauses will be added as agreement clauses only when the user clicks the Finish button.
• None: By selecting this option, the user can opt out of eDiscovering clauses in the agreements.

9. Click Create and Publish.
10. Go to the Agreement Details page.
11. In the AI Discovery tab, click Clauses to trigger the Clause Discovery.

12. Once the discovery of the clauses is complete, the AI model will try to match the discovered clause with the clauses in the clause library. If a match score is greater than the set threshold, then the discovered clause is identified as a clause from the clause library. Otherwise it will be identified as one of the default AIML clause categories.

Support for additional languages in AI apps

The discovery models have now been enhanced to support clause and obligation discovery for the following additional languages – German, Spanish and Portuguese, to meet the needs of our customers.

With this release:

• Additional language support is available in NegotiateAI and DiscoverAI for legacy migration.
• Discovered clauses and obligations are displayed and then linked back to the matching text in original document.
• Identified clause and obligation categories/ sub-categories are displayed in user preferred language on the UI.
• While discovering or matching the clause from clause library, document language is taken into consideration.
• The additional languages are supported while discovering similar clauses.

Supporting clause hierarchy in agreements in .docx format

Previously, clauses discovered through DiscoverAI followed a flat structure in which every paragraph was identified as a clause and assigned a clause category. However, in a contract each paragraph could be part of a typical hierarchy where, for example, a clause might be a combination of multiple paragraphs forming one section.
With this release, DiscoverAI is being considerably enhanced to identify the different levels within a clause. Users now have a distinct visual representation of clauses with sub-sections of clauses displayed in a delineated view, during the clause discovery process. The hierarchical representation of clauses helps users to compare clause sections, sub-sections and so on.
Further, any document objects which are in the agreement document but not necessarily a part of the clause language will now be identified separately and will be excluded from the actual clause discovery process.

Recommendation

Currently support for clause delineation is provided for documents in well-structured format. Hence, it is recommended to use documents in which:

• Lists, headers, footers, tables and table of contents have been added by using MS Word functions. 
• All the items added in the list are linked to each other. Appropriate MS Word styles must be used for creating lists like numbering and so on.
• List of the entire clause block are created at the same time. No changes should be made manually. 
• Appropriate indentation has been given as per level while designing the layout. Indentation of parent clauses must be lower than child clauses.
• Document lists have been added using MS Word functions and should be updated automatically if there is any deletion / addition. 
• Document should not have any field which is not linked to other MS Word fields using Word functionality. 

Note:

• Manually added lists are currently not supported. 
• Numbering format must be uniform across a clause. If there is any change in the numbering style, then it will be treated as a different clause even though MS Word styles have been used. 
• Free text added without linking it to a parent list level, will not be considered for hierarchy.
• Headers edited manually are currently not supported, they will be treated as blank.

A few examples:

List Levels added from the MS Word List Library are supported.

UX revamp to display discovered entities and original document side-by-side

Previously, contract negotiators had to periodically visit the AI discovery section to check for discovery completion. Then, they had to switch to the Document View in order to review the recommendations given by the AI algorithm.
With this release, when contract negotiators trigger the discovery process, they can readily view the progress of AI discovery within the agreement details page. 
When the discovery for one of the entities is complete, contract negotiators will now have an option to launch an interface in a new window where the discovered clauses, attributes, tables and obligations are displayed alongside the agreement document. On clicking any of the discovered entities, the system automatically scrolls to the page where that entity is present in the document. 

1. Create an agreement in ICI. The discovery process is automatically triggered for the agreement and the agreement Details page is displayed. The AI Discovery tab shows an hourglass icon to indicate that the discovery is in progress.

Note: Discovery process for an agreement is triggered only for users with the AI license if the discovery is configured for a contract type.

The discovered clauses are displayed in a delineated view to indicate the main section, sub-sections and so on, of each identified clause by default.

You can filter clauses based on Action Status, Clause categories and Confidence.
The level of confidence associated with Discovered Clauses is displayed using different color indicators to depict High (green), Medium (orange), Low (pink), Revised Manually (blue) and Library Clause (grey) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the     icon next to them. You can click the icon to view the obligations.

4. Click on the clause which you want to review, for example License/Grant of License. The Document View section displays the page of the document where this clause is present.

5. Click Review on the clause you want to review, for example License. The Library clause comparison with discovered clause window opens.

 

You can review an entire section as a clause or review each sub-section separately and confirm each as a separate clause. 

6. Take actions (such as Confirm, Confirm with Deviation, Ignore, Review Later) on the discovered clauses.

To enable or disable clause hierarchy view:

10.  Uncheck the Clause hierarchy checkbox to view only the parent level clauses.

To rearrange discovered clause boundaries:

11.  Click Rearrange clauses link if you want to rearrange clause boundaries. The discovered clauses open in an edit mode.

Users can take following actions on the discovered clauses from the Rearrange clauses page.

• Manage category: Users can change the category of discovered clauses using the Category drop down at the top of each discovered clause. For example, change the category of a clause from definition to confidential information. 

Users can keep the clause category as blank if a text which is not part of any clause has been miscategorized as discovered clause.
 

• Merge: Users can merge two or more clauses using the Merge action.

i. Select the text you want to merge as a single clause. For example, recitals sub clauses- 2.1.1 (from Purpose of…), 2.1.2 and 2.1.3. The Merge button will be enabled.
 

ii. Click Merge. The selected text spanning across multiple discovered clauses will be merged into a single clause.

Users can select clauses from same or different categories to merge by selecting the text.

• Split from existing: Users can split a clause into two or more clauses using Split from existing action.

i. Select the text in a clause you want to split into separate clause. For example, a section starting from ““Defect(s)” means significant to for the Program. The Split from existing button will be enabled.

ii.    Click Split from existing. The clause will be split into three parts- The selected text as one clause and previous and later unselected texts as two separate clauses. 
For example, three separate clauses are created for texts as:
“Agreement” means to and addenda.
““Defect(s)” means significant to for the Program.
”Derivative Work(s)” means to of the Programs.
 

• Create Sub Clause: Users can create a sub clause within a clause using Create Sub Clause action.

i. Select the text in a clause you want to make as a sub clause. For example, “”Defect(s)” means to of the programs. The Create Sub Clause button will be enabled. 

ii. Click Create Sub Clause. The clause will be split into two clauses with the selected text as a child clause.
For example, text from “Agreement” means to and addenda, will be marked as a parent clause and text from “”Defect(s)” means to of the programs, will be marked as a sub clause.
 

• Change Hierarchy: Users can change the hierarchy levels of clauses using the Decrease Indent and Increase Indent actions.

i. Click Increase Indent button corresponding the clause you want to change level of. For example, Use of proceeds clause.

The clause will move to a higher hierarchy.

ii. Click Decrease Indent button corresponding the clause you want to change level of. For example, Use of proceeds clause.
 
The clause will move to a lower hierarchy.

The Confidence Indicator will change to blue for any change in a clause.
12. Click Undo if you want to discard the changes.
13. Click Save. The changes will be saved to the discovered clauses.

8. Click Ok.

To export discovered clauses:

8. Click Export Clause Data if you want to export the clause which has been discovered.

6. Click Finish to complete the review process. The Clause discovery progress saved message is displayed and the Discovered Clauses Status changes to Review Completed.

 

14. Click Ok.

15. Click Review button corresponding to the Tables. The Review button will be enabled when there is at least one discovered Table.

Similar to clauses, the discovered tables and document are displayed in a parallel view. The Document View section displays the page of the document where the table is present.  

 

17. Click the Edit Table Name icon next the table that you want to edit. For example, Table 1.
18. Toggle the Has Header flag to Yes if you want the table to have a header.

 

19. Click inside the header box to add the header name. For example, SKU Name, Service Name, etc.
20. Click inside each of the boxes to add data in the columns. For example, HCM (SKU), Human Capital Management (Service), etc.

 

21. Select the checkbox for the rows and columns that you want to update.
22. Click Save Changes to save changes if you want to review or edit them later. 
23. Click Finish. A validation message is displayed informing you that you will not be able to make any changes to the table data after this.    

 

24. Click Yes if you are sure that you want to update the table and proceed.    
25. Click the Obligations tab. Similar to tables, the discovered obligations and document are displayed in a parallel view. The Document View section displays the page of the document where the obligations are present.

 

26. Click Review on the obligation you want to review. The Library Obligation comparison with discovered Obligation window opens.

 

27. The following actions can be taken on selected Obligation:

• Click Confirm to confirm the Obligation.
• Click Review Later if you are unsure and want to review the Obligation later.
• Click Ignore to ignore the Obligation.

28. Click Metadata to view all the discovered metadata. The number (for example, 10.10) indicates the number of Attributes that are discovered such as Email, Numbers, Date and Time, and so on. 
29. Click Parent Clause to see the parent Clause that the Obligation is linked to.
30. Click Export Obligation Data to export the Obligation information to an Excel file.
31. Click Finish to complete the review and continue with the workflow as expected. The Obligation Save Confirmation window opens.

 

32. Click Mark Confirmed, Mark Ignored or Cancel as required. The obligations are marked as Review Completed and the Obligation discovery progress saved message is displayed.

 

33. Click Ok.
34. Click Export Obligation Data to export the Obligation information to an Excel file.

 

Using Filters

 

• You can filter clauses as well as obligations based on Clause/Obligation categories, Confidence and Review Status.
• The level of confidence associated with Discovered Clauses/Obligations is displayed using different color indicators to depict High (green), Medium (orange) and Low (pink) confidence. All discovered clauses have the Review link next to them until you click it to take an action (such as Confirm, Confirm with Deviation, Ignore or Review Later). In addition, clauses with obligations have the     icon next to them. You can click the icon to view the obligations.
• Click the Finish button to complete the review process.

35. Click the link above the tabs to go back to the agreement Details page.

 
 

Related Topics: Agreement Management | Obligation Management | Managing US Federal Contracts using ICI  | Contract Digitalization | NegotiateAI | ObligationAI | VisualizeAI