Susan wrote: "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."

I think one difficulty would be communicating each change to the company every time one happens and making sure that people are using the most current retention schedule for their destruction decisions.  The other difficulty I would have (and maybe not everyone requires these kinds of approvals) is that my Steering Committee needs to approve each change, so I'm only doing annual revisions right now.  I just save up all of the requested changes throughout the year to use at revision time.

Thank you,
Deanna L. Brouillette, CRM
Records Manager
Chesapeake Energy Corporation
Phone: (405) 767-4747
Mobile:  (405) 706-2745
Email: [log in to unmask]



This email (and attachments if any) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law.  If the reader of this email is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by return email and destroy all copies of the email (and attachments if any).

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]