Hi All, we have our retention schedules in a database.  There had been an 
older database that had some records in it (ISO 9000 records) and it has 
been combined in with the schedules database.  In the old ISO 9000 records 
database, they made changes whenever it was needed.  The ISO 9000 database 
has always been done like, the changes took place as needed, but there was 
version control, with notes on reasons for changes.  Some are asking that 
the retention schedule database be updated like the old ISO 9000 database, 
when needed and not on a schedule.  I want to do it on a schedule 
(monthly, quarterly, semi-annually, annually). 

I understand that changes to the schedules should be done 'as a normal 
course of business', but I always think of that as on a schedule (monthly, 
quarterly, semi-annual, annual, etc).  Plus, it's just easier, collect the 
changes, make them all at once. 

The question is, would it be alright to make chances to the retention 
schedule database whenever needed as long as there is version control and 
each change is explained, since it has been done that way for years?

What other risks are there besides the why the changes were made at a 
certain time and the documenting of that?  I would like some other points 
to use.

How often do other companies make changes to their retention schedules?  I 
suppose it partly depends on size (we are about 1500 employees).

We are a private manufacturing company.  Thanks for comments.  Susan 
www.selinc.com

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]