The Automated and Requires Review options let you select the right balance between operational efficiency (Automated) and human oversight (Requires review) based on the sensitivity and criticality of the content to be governed.

NOTE: The Requires review option isn't available for the following event types:

  • Declare All Versions

  • Declare Latest Version

When Automated is:

  • Selected: Eligible tasks are run once per day at 3:00 PM UTC.

  • Not selected: Tasks must be processed individually and manually by Records Managers before they're run.

When Requires Review is:

  • Selected: The tasks must be reviewed by a mapped Disposition reviewer, if an active Disposition reviewer is available, before the records can be destroyed. Records Managers can also review and approve records on behalf of Disposition reviewers.

  • Not selected: Records are destroyed without review when the retention is met. The processing requirement is still enforced, if the Automated option is selected.

IMPORTANT: When records are destroyed, they're deleted from iManage Work at cloudimanage.com and can't be retrieved or restored.

Records aren't destroyed immediately when events to destroy records are created, or added to a schedule, or applied to workspaces, folders, or subfolders. Records are destroyed when tasks defined by these destroy events are executed manually or automatically.

The following table describes what happens to events when a combination of Automated and Requires Review options are selected or not selected.

Table: Combination of Automated and Requires Review options

Event type

Is Automated selected?

Is Requires Review selected?

Description

  • Declare All Versions

  • Declare Latest Version

Yes

Not available

This event type is automated, meaning it declares documents when its criteria are met.

For example, if the period defined is 30 days and the retention date field is the close date and the close date defined is April 20,2026. Then, either all versions of the record are declared or the latest version of the record after 90 days from April 20, 2026.

The automation runs at 3:00 PM UTC.

No

Not available

The event type isn't automated, meaning Records Managers have to manually process the tasks before they are run.

  • Declare Latest Version Destroy Undeclared

  • Destroy All Undeclared Versions of a Declared Document

  • Destroy All Declared Versions

No

No

The tasks have to be manually processed by Records Managers, but don’t require any review by disposition reviewers even when they are mapped reviewers.

No

Yes

The event type isn’t automated and requires review from a mapped reviewer and manual processing from disposition reviewers.

Yes

No

Doesn't require manual processing from Records Managers and no review from other users, even when there are mapped reviewers.

Yes

Yes

The event is automated but requires review from a mapped Disposition reviewer (for example, an attorney), if an active Disposition reviewer is available, before the records can be destroyed. Records Managers can also review and approve or deny records on behalf of disposition reviewers.

The destruction task is triggered when:

  • At least one reviewer or Records Managers have approved the task.

  • Eligibility date is reached.

  • Time is 3:00 PM UTC.

Make workspace/folder read-only

No

No

The tasks have to be manually processed but doesn’t require any review by Records Managers or disposition reviewers.

No

Yes

The event type isn’t automated and requires review and manual processing from a mapped reviewers. An email is not triggered for these events, but is available in the list of tasks that require approval.

Yes

No

The event is automated and doesn’t require any manual processing or review from mapped reviewer.

The task is triggered at 3:00 PM UTC when the eligibility criteria is met.

Yes

Yes

The event is automated but requires review from a mapped Disposition reviewer. An email is not triggered for these events, but is available in the list of tasks that require approval.

After approval, the task is triggered at 3:00 PM UTC when the eligibility criteria is met.

Additionally, Records Managers can also transfer ownership using the Transfer Workspace/Folder Ownership field and select the new owner in the New owner field when using the Make workspace/folder read-only event.

When ownership is transferred to the selected user, the previous owner’s access is changed to read-only.

NOTE: The tasks aren't executed if:

  • Holds are applied and the hold is still active and not expired.

  • Records Managers or mapped Disposition Reviewers, if still active, have denied the tasks.