Sender: |
|
Date: |
Mon, 19 May 2008 09:52:24 -0400 |
Content-Disposition: |
inline |
Reply-To: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Content-Type: |
text/plain; charset=ISO-8859-1 |
From: |
|
Parts/Attachments: |
|
|
my two cents worth on this subject. The audit like a litigation hold. The
problem I've found is that the vast majority of users have no idea when an
audit has taken place or is currently being done or when it was completed..
In some cases the audit may take place in only one group, but not another.
I think the better solution would be to state the retention period as
Termination + x years
If an audit takes place you notify the relevant departments that the records
are subject to an audit and that destruction is put on hold. Use the same
process you use for a litigation hold
On Mon, May 19, 2008 at 8:40 AM, Mullen, James L (SN) <
[log in to unmask]> wrote:
> Last week Laurie Carpenter wrote "I'm looking at retention periods and
> how to make them more usable and user friendly...
>
> I've not discovered a good way to do this. As I think other have
> pointed out, your always looking for a moving target AND the trigger
> event isn't always common knowledge. Here's a couple of ideas...
>
> Scenario A: Retain until the tax department has closed their
> audit/releases
> the tax year, but a minimum of 7 years.
> How about:
> 7 years or until audit is closed, whichever is longer
>
--
Peter Kurilecz CRM CA
[log in to unmask]
Richmond, Va
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]
|
|
|