As much as possible you want to rely on interfaces with native systems that provide a termination date.  i.e. a contract system for your contracts/leases.  A pipeline information system that would capture closure and abandonment of the different p/l systems etc..
 
If your company is strong on process mapping and holding people accountable to following those processes, you may be able to rely on a department informing you of the events when they happen.  That is a pretty large "if" though.  
 
Long term retention records that may then have an event like a 50 year old pipeline and then it is retired and needs to be retained until complete depletion etc.. Can you see the issues relying on humans that just want to move on to the next project now they have laid the prior one to rest?
 
Sincerely,
 
Laura

--- On Tue, 9/28/10, Arnold, Rebecca <[log in to unmask]> wrote:


From: Arnold, Rebecca <[log in to unmask]>
Subject: Event-driven retention
To: [log in to unmask]
Date: Tuesday, September 28, 2010, 2:06 PM


Good afternoon everyone:

I am interested in hearing how other organizations are handling event-driven retention periods.  What different processes have been employed to notify RIM that the event has occurred for physical and/or electronic records and therefore start the retention clock ticking?  Thanks for your input!

Rebecca Arnold
RIM Advisor, Oklahoma City, OK




List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]