How do you set the cutoff and disposition trigger for a record series?

Setting retention for a record series comes down to answering two questions: when does the clock start (the cutoff) and what has to be true before destruction or transfer happens (the disposition trigger). Getting both right is what makes a retention schedule enforceable rather than aspirational.

Define the cutoff

The cutoff is the point at which a group of records is closed off so the retention period can begin to run. Records are rarely measured from the date each individual item was created; instead they are grouped and “cut off” at a logical break, and the retention clock starts after that break.

Common cutoff approaches include:

• Periodic (calendar or fiscal year): close the series at the end of the year, then begin counting. This is the most common method for ongoing administrative records.
• Event-driven: cut off when a defining event occurs, such as a case being closed, a contract expiring, an employee separating, or a system being decommissioned.

Document the cutoff rule precisely in the schedule so different staff apply it the same way. Ambiguous cutoffs are a leading cause of records being kept too long or destroyed too early.

Define the disposition trigger

The disposition trigger combines the cutoff with the approved retention period to determine the eligibility date. In practice it reads as: retain for X years (or until an event) after cutoff, then [destroy / transfer to archives / review].

A sound trigger has three parts:

• The base point — the cutoff or event that starts the clock.
• The duration — the time the series must be kept to meet legal, fiscal, operational, and historical needs.
• The action — destruction, permanent transfer, or further review when eligibility is reached.

Validate before you finalize

Confirm the period satisfies every applicable obligation (statutory, regulatory, litigation, and business use), and add a legal hold override so eligible records under hold are never destroyed. Then apply the trigger consistently and log each disposition action so the process is auditable.

For more foundational guidance, see the retention and disposition topic hub.