RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Records Management Program <[log in to unmask]>
Date:
Wed, 23 Jul 2008 09:45:33 -0400
Reply-To:
Records Management Program <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=us-ascii
From:
Stephen Cohen <[log in to unmask]>
Parts/Attachments:
text/plain (63 lines)
A delayed response, but Dwight is right on the money. Looking at the 
records in terms of series and not individual documents is the way to go 
if you don't want to go insane managing at the item/document level. 
looking at the series of records with regard to function again bolsters 
the same type of thinking that works extremely well with managing large 
volumes of records in a diverse organization. personally, I have been 
involved in developing and or implementing a variety of schedules and the 
best one that are easiest to apply / enforce is exactly what Dwight has 
described.

Stephen Cohen
Records Manager
MetLife \ Legal Affairs
27-01 Queens Plaza North
Long Island City NY 11101
212-578-2373



...retentions are generally applied through record series, which
describe a collection of documents which serve a common function, and
can be described as a unit. Its not uncommon to have a situation as you
describe. You've already considered the impact on records integrity and
completeness. Also to take into consideration is whether separating
specific documents by retention is more costly than simply keeping them
together, as such separation may entail more cost and labor. 

I would suggest thinking of the retention schedule as less of a specific
document based system, and more of a system based on functional record
series describing aggregates of documents serving that particular
function (such as accounts payable records, recruitment and selection
records, personnel records, etc....). Another thing you want to avoid is
creating too complicated a record series structure, which tends to
happen with document specific systems. How to aggregate into more
generalized series relates to a proper balance of cost, customer
perceptions, and what meets traditional records retention values of
operational, fiscal, legal, and historic needs. Its not uncommon, for
example, to see a separate retention for supporting documents, and one
for documents which meet key milestones, in a single records series
description describing a particular function (for example, construction
project records). These can then be used as weeding guidelines.

...

Dwight Wallis, CRM
Records Administrator
Multnomah County Fleet, Records, Electronics, Distribution and Stores
(FREDS)
1620 S.E. 190th Avenue
Portland, OR 97233
Phone: (503)988-3741
Fax: (503)988-3754
[log in to unmask]



The information contained in this message may be CONFIDENTIAL and is for the intended addressee only.  Any unauthorized use, dissemination of the information, or copying of this message is prohibited.  If you are not the intended addressee, please notify the sender immediately and delete 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]

ATOM RSS1 RSS2