This does result in the desired behavior, however, getting rid of the event entirely doesn't make much sense to me. It would make more sense to keep a history of cutoff and uncuttoff events. In our process we may terminate and rehire an employee multiple times and it would be nice to keep a record of the full lifecycle of the document. 

When I think of Uncutting off a document, I would assume the behavior would be to keep the cuttoff event and allow the document to be cuttoff again immediately.  

Also, if the record has not been cutoff yet, this does not work. This might happen in a case where records are reviewed on January first and a seasonal employee is terminated on February 28 and re-hired December 1.

Hi Justin,

It sounds like you have two possible approaches here for dealing with the re-hired temp worker scenario. Either their original records remain the master records (in which case you perform uncutoff on them and reset their active status) or they now get a new set of master records (in which case the original ones continue on to their normal retention resolution and now you're working with a new set). Based on your questions, it sounds like you're going with option 1, in which case - for the purposes of calculating future retention rules and eligibility - the original events are no longer relevant. Everything will be re-calculated based on new future events, and that's why they are no longer displayed when specifically looking at retention definitions and life-cycle. However, you can still see a record of all events and modifications on that entry in Audit Trail for a full life-cycle view.

If you feel that it's critical to keep the original termination for purposes of retention, you may want to consider the second approach instead.

This makes sense, keep the RME tab clean by only having information relative to the current retention cycle, but keep a full history of the documents life cycle in the audit logs. 

Thank you!

"Also, if the record has not been cutoff yet, this does not work. This might happen in a case where records are reviewed on January first and a seasonal employee is terminated on February 28 and re-hired December 1."

This is now the issue we are running into. We run a search yearly on December 31 to check for records that can be cutoff. We have seasonal employees that work from Nov 1 - Jan 31. Their records never get officially cut off and therefore whenever we try to refile their docs it just throws warnings and doesn't remove events.