The Period field describes the time for which the records must be kept (applicable only events that specify destruction), for example, 7 years, 2 months, 40 days and so on, whereas the Retention Date Field describes the reference point or trigger, for example, document creation date, matter close date, email received date, and so on.

The value provided in the Retention Date Field must be mapped in the Metadata Mapping for it to be displayed here. Also, the value should exactly match the name provided in the metadata mapping for that library, that is they're case-sensitive.

The two components combine to define when a record becomes eligible for declaration or disposition. Refer to the following examples for more information:

Example 1:

• Type: Declare All Versions

• Retention Date Field: Matter Close Date (The value picked from iManage Work, that is this is mapped metadata value with this name)

• Period: 7 Years

• Result: Content is kept for 7 years after the matter closes and all versions of the records within the workspace or folder for which a schedule is applied to as well as the contents of all the subfolders that don’t have different schedules applied are declared 7 years after the matter close date.

Example 2:

• Type: Destroy All Versions

• Destruction timing: Exact Date

• Retention Date Field: Matter Close Date

• Retention Period: 2 months

• Result: Content is retained for 2 months after the matter closes and all versions of the records with the workspace or folder for which a schedule is applied to as well as the contents of the all the subfolders that don’t have different schedules applied are destroyed 2 months after matter close date.

This flexibility allows organizations to account for different business events or document lifecycle triggers.