After a document is uploaded or saved and checked into iManage Work, iManage AI Enrichment analyzes its content and assigns a Category: Agreement, Court Document, or Undetermined. This value is stored as an AI-enriched metadata property in iManage Work.
If the document is categorized as an Agreement, iManage AI Enrichment extracts the agreement-specific information from the document content and automatically populates additional AI-enriched metadata properties (for example, Agreement Date and Heading). Documents categorized as Court Document or Undetermined don’t receive this agreement-specific metadata; only the Category property and the administrative properties are populated for these documents.
Before extraction, iManage AI Enrichment identifies the agreement’s specific sub-type (66 supported sub-classes). This step runs automatically and doesn’t produce a separate visible property.
For documents categorized as Agreement, iManage AI Enrichment populates six additional AI-enriched metadata properties, based on document content. The three remaining properties (Enrichment Date, Enrichment Status Code, and Enrichment Version) are administrative properties that are updated regardless of category, including for documents that are only categorized as Court Document or Undetermined.
The generated metadata falls into two groups:
Editable properties: Properties populated with agreement-specific information. Users with appropriate permissions can update these values.
Administrative properties: Read-only properties used to record enrichment status, timing, and the model version applied to the document.
All enriched metadata properties are stored within the iManage platform and inherit its existing compliance, security, and governance controls.
In this section:
Editable properties
There are seven editable properties.
Taxonomy properties:
Category (single-value taxonomy)
Jurisdiction (multi-value taxonomy)
Lookup properties:
Governing Law (multi-value lookup)
Text properties:
Date properties:
Boolean properties:
Administrative properties
There are three administrative properties.
Display and consistency considerations
For consistent display across iManage Work, particularly in Grid view, List view, and search results, metadata values may appear differently if they’re configured inconsistently across libraries.
Property visibility
Property visibility depends on your administrator’s settings. If iManage AI Enrichment isn't configured for your library, the enriched metadata properties won’t appear.
Knowledge library behavior
The visibility of metadata fields depends on whether a library is designated as a knowledge library.
In knowledge libraries (for example, Japan, designated as a knowledge library), users see curation fields, which are used for manual review and tagging.
In non-knowledge libraries (for example, U.S., a non-knowledge library), users see enrichment fields, which are automatically populated by the AI enrichment service.
By design, iManage AI Enrichment doesn’t run on knowledge libraries, since these libraries are often curated manually (sometimes over several years) and enrichment could override that work. Customers with a knowledge library will see curation fields. Customers without a knowledge library may see enrichment fields, provided the enrichment application is enabled and configured.
Required properties
Enriched metadata properties are always optional. These properties can't be set as required or mandatory in your library.
Change tracking and data handling
For taxonomy and lookup properties, only the most recent value is retained.