A retention schedule is a collection of triggers and retention events used to control the activity and status of a record throughout its life cycle. Retention Schedules can be started automatically by giving a retention date from an outside database (like a Matter Close Date from a Practice Management System). They can also be started manually by processing a Trigger-type event.

Retention schedules may be:

• Time-based: An item is archived 5 years after its creation date.

• Event-based: An item is archived after it is closed.

• Time-event based: An item is archived 5 years after it's closed.

Event-based and time-event-based retention schedules are activated using a trigger.

Default Schedule

When a new file part is created, the application applies a default retention schedule in the following order:

1. Template: If the file part is created from a template, the retention schedule defined in the template is applied to the new file part.

2. Record Type: If the template doesn't specify a retention schedule, or if there is no available template, the retention schedule is based on the record type assigned to this file part. When you create new record types, you have the option of defining the default retention schedule.

3. Parent Container: Finally, the application tries to apply a retention policy based on the parent's retention schedule. If the parent has no retention schedule applied, then no retention policy is applied to the new file part.

The default retention schedule can be manually overridden. 

This section includes the following topics: 

• Create Retention Schedules
• Share Events Across Schedules
• Apply Retention Schedules
• Select a Retention Schedule
• Modify Retention Schedules
• Delete Retention Schedules