Subject: | |
From: | |
Reply To: | |
Date: | Wed, 15 May 2013 14:26:32 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Larry:
And to make the waters even murkier in some instances in the public realm
that I have seen, some agencies consider the background material
non-records/working files once the policy/schedule is approved, and subject
to faster disposition - eliminating background material some may consider
important. One current public client keeps this type of material
(transfer/disposition lists as well) for three years after approval/action.
The other public client conforms to GRS 16/2.
Tod Chernikoff, CRM, CIP
Silver Spring MD
[log in to unmask]
www.twitter.com/tchernik
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On Behalf
Of Larry Medina
We save all background information for changes (Permanent) and we save a
table of changes that reflects WHAT was changed (Permanent) but we replace
the schedule itself when it becomes superseded by a new revision.
If a question ever comes up about WHAT changed and WHY it changed, we can go
to the above items and justify any changes that took place and show when it
happened. As for retention periods applied to electronic records, the
system logs changes made and retains that information as part of the
metadata.
Larry
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]
|
|
|