Could we resolve the issue by creating two different record series
instead of one record series with two different retentions?

Gary Link, CRM
Astorino
Pittsburgh, PA

 

-----Original Message-----
From: Larry Medina [mailto:[log in to unmask]] 
Sent: Tuesday, August 12, 2008 5:14 PM
To: [log in to unmask]
Subject: Re: [RM] Are new retention periods retroactive?

>I have always gone with the decision the new, approved retention 
>schedule supersedes all previous ones.  In my previous position we had 
>a lot of litigation and never had to defend this position.

Interesting, I was thinking back specifically to my days in Utilities
when I made my initial post.  We had instances with a State PUC and with
the FERC and DOT where this became an issue.  We had extensive volumes
of records that were impacted by retention periods that changed and were
vacillating on whether or not we could shorten the periods based on new
regulations for existing intrastate facilities... fortunately we didn't.

>Also, if your
>disposition is being carried out by your RM software, having two 
>retention periods for the same record series might be difficult to
handle.

Actually, this would be the easiest condition I would think. It would be
based on generation/creation date and you could add an alpha character
or a "dash number" to the new retention period but retain the existing
record series code.  The system would simply calculate the date against
the various records and apply the appropriate schedule.

Larry Medina 

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]

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]