In general, "until superseded" is appropriate. A Disaster Recovery Plan is
an "action" plan. Once the plan is superseded it has no more value other
than for reference and comparison. The only exception is when the Disaster
Recovery Plan has been implemented. Then you need to keep that plan along
with all the actions implemented to document the incident. At that point
the Plan is now part of the incident report and will be kept in compliance
with that retention requirement.
Mary
Mary W. Haider, MBA, CRM
Records & Information Manager and Consultant
[log in to unmask]
865-983-1371
On Mon, Mar 26, 2012 at 9:43 AM, Kirk.Michelle
<[log in to unmask]>wrote:
> Hello folks,
>
>
>
> I'm hoping to solicit some input from anyone who may have experience
> scheduling Disaster Recovery Plan or Business Resumption Plan
> Documentation.
>
>
>
> I have looked in the archives and seen recommendations (or breadcrumbs
> to recommendations) including:
>
>
>
> * "until superseded"
>
> * "x time after superseded"
>
> * "2 years after superseded"
>
> * "1 year after system is superseded"
>
>
>
> Of course I would love to recommend the first retention length in that
> list, but am hoping to get a little more reasoning behind it to shore up
> my argument. This is especially since it has been explained to me that
> SunGard's LDRPS system does not keep audit trails of records once they
> are superseded.
>
>
>
> Is there anyone on the listserv who might have some experience in the
> realm that would be willing to share? If so, you can reply here or feel
> free to contact me directly.
>
>
>
> Many thanks in advance -
>
>
>
> Michelle Kirk, CRM |SunTrust ERIM | Atlanta, GA |404-588-8779 |
> [log in to unmask]
>
>
> LEGAL DISCLAIMER
> The information transmitted is intended solely for the individual or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other use
> of or taking action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited. If you have
> received this email in error please contact the sender and delete the
> material from any computer.
>
> By replying to this e-mail, you consent to SunTrust's monitoring
> activities of all communication that occurs on SunTrust's systems.
>
> SunTrust is a federally registered service mark of SunTrust Banks, Inc.
> Live Solid. Bank Solid. is a service mark of SunTrust Banks, Inc.
>
> [ST:XCL]
>
>
>
>
>
>
> 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]
>
--
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]
|