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
Content-Transfer-Encoding:
quoted-printable
Sender:
Records Management Program <[log in to unmask]>
Subject:
From:
Kelly Hamilton <[log in to unmask]>
Date:
Thu, 7 Jun 2007 10:27:25 -0600
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Reply-To:
Records Management Program <[log in to unmask]>
Parts/Attachments:
text/plain (86 lines)
Thanks, Chris...this subject line works a lot better!

 

I'm looking at all the feedback, and to Barb Wyton's question about the
5 separate retention schedules, we have one policy that governs them, so
I guess it would be 5 sections of the same retention schedule.  I just
always think of them as separate, but now that I'm really thinking about
it, since there's one policy, then it would be one retention schedule.

 

Back to Chris' Gaines' email...

>Create a way to initiate a suggested change such as a controlled form. 

 

We have a web form on our Intranet that we use...we like the
standardization, and we want people to go to our Intranet more, now that
our users aren't just local, but are enterprise-wide.  Even when it was
just local users, the free-texting of requests just gets a little
crazy...we always had to ask for more information!

 

>Create a change control log for the retention schedule. 

 

Creating the change control log for the retention schedule really
answers my (b) question about saving versions.  Someone else (looking
back, it looks like Charmaine Brooks) suggested a database to track the
changes, which I can't believe that I never thought of before.  I've
been saving the emails, but there's getting to be a few of them, so I
think that database idea is great.

 

>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. 

 

We're working on creating written procedures now (we had some, but
they're from the last records management software system, and so are
outdated), and all this is really something for me to think about when I
write that one.

 

 

Kelly Hamilton

Records Specialist  

 

Safeway, Inc.

20427 North 27th Avenue

MS-7011

Phoenix, AZ 85027

623.869.3848 Tel

623.869.6175 Fax

 


"Email Firewall" made the following annotations.
------------------------------------------------------------------------------

Warning: 
All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient.  This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s).  If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited.  If you have received this message in error, please notify the sender immediately.   
 
==============================================================================

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

ATOM RSS1 RSS2