RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chris Gaines <[log in to unmask]>
Reply To:
Records Management Program <[log in to unmask]>
Date:
Thu, 7 Jun 2007 10:35:27 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Kelly,

In addition to the database, you might consider a structured change 
control process:

Create a way to initiate a suggested change such as a controlled form. 
Evaluate the change and accept, reject, or accept with modifications, as 
appropriate.  Note that this implies the existence of an approval process.
Create a change control log for the retention schedule. 
Bundle the approved changes and hold for the next revision to the schedule 
- it typically is not necessary to revise the schedule for each individual 
change. 
Use the bundle of approved changes as source materials for periodic 
refresher training for staff.

In fact, you could capture these steps in a procedure and use it for any 
form of governance, all of which should be approved for use and, 
therefore, should be subject to revision control. 

Chris Gaines, CRM





List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
 

ATOM RSS1 RSS2