Sender: |
|
Date: |
Tue, 31 Jul 2007 10:51:34 -0700 |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
8bit |
In-Reply-To: |
|
Content-Type: |
text/plain; charset="us-ascii" |
From: |
|
Parts/Attachments: |
|
|
We are a Fortune 500 and this is pretty much the way we do it --- well,
at least it's planned this way since our program is new and we haven't
actually done an annual destruction yet. Other than monitoring for
Litigation Holds, the records due for destruction WILL be destroyed
unless a business unit can give good cause for them not being destroyed.
And "just in case" is not a good reason, it must be a specific legal or
operational need.
I, as the Director of the program, am the only one (with a backup
person) who authorizes destruction, so all points in the destruction
process funnel through me so that I can make sure the process is being
done consistently and being properly documented. Since it's only the
exceptions that require any real work, it's not too burdensome.
Nolene
Nolene Sherman | Director of Records Management | Standard Pacific Homes
| 949-727-9360 | FAX 949-789-3379 | [log in to unmask]
-----Original Message-----
Subject: Re: [RM] Who gives final destruction approval in your company?
I think there is a misconception here.
Once the retention schedule has been approved and signed off, there is
no approval required for destruction. Notification that records are
about to be destroyed - yes, but no approval.
The procedures should state that destruction will take place if no
notice to the contrary is received within a certain period of time.
After all, these records do not belong to the individuals concerned.
They belong to the organization.
If one does not stick to the procedures consistently, a court would have
no trouble ruling against you. You must have a set documented plan for
each and every situation.
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]
|
|
|