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:
Thu, 26 Apr 2007 06:02:22 -0700
Content-Disposition:
inline
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=ISO-8859-1; format=flowed
From:
Larry Medina <[log in to unmask]>
Parts/Attachments:
text/plain (30 lines)
Fred-

The first question I'd have to ask is how is the Agency's RRS designed?  Is
it organizational or functional?

Based on what you stated, it sounds as if it's organizational, and if so,
the first thing you may want to consider is eliminating much of the
duplication by realigning the schedule on a functional basis.  Every record
(and record series) supports a purpose, or function.  If the function is HR,
and there are a set number of series/types of records in HR, and EVERY
department in the Agency has these same records, you could potentially
eliminate one series from each department by establishing a functional
schedule and assigning a single series to each HR record type that all
departments commonly use.

One major benefit to this model is as/if/when there is a reorganization
within the Agency, there is no need to "shuffle" schedules to accommodate
it, whatever the new organization is, they will still be using the same
records and they will still serve to document the the same function.
Granted, they may begin to generate NEW record types, but that's evolution.

Larry
-- 
Larry Medina
Danville, CA
RIM Professional since 1972

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

ATOM RSS1 RSS2