Deanna wrote "....I just save up all of the requested changes throughout the year to use at revision time."
I think this is the right approach to retention management. If an organization is having to making more frequent periodic updates that perhaps one may consider looking at the overall retention schedule/file plan to see it is in synch with the RM requirements. By nature of records retention, most of the retention periods are typically in years hence an annual or perhaps even a semi-annual update schedule should work for most retention schedules. This is more true for retention schedules that have passed the intial 2-3 year "bake-in" period.
Also the idea of a steering committe is right on - changes to retention schedule cannot and should not be made a "normal" business process rather it is to be done on an exception basis either due to legal or regulatory changes or new record types and/or things that were missed during the initial retention schedule development.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this message.
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]