Preservation Guide

This entry is part of a series, EDRM Framework Guides»

[Introduction]

Preservation

Aim: When duty to preserve is triggered, promptly isolate and protect potentially relevant data in ways that are: legally defensible; reasonable; proportionate; efficient; auditable; broad but tailored; mitigate risks.

Goal: Mitigate risks.

* Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity.

3 comments to Preservation Guide

  • 2

    [...] assist it in developing possible recommendations on whether a rule should be developed addressing Preservation of relevant electronically-stored information (ESI), as well as sanctions for a failure to [...]

  • 1
    Tom Coleman says:

    I would think, if at all, “Suspend Destruction” would come FIRST- but only in the first iteration, immediately, once an organization admits there should BE a strategy for data preservation. Perhaps it doesn’t really belong in the chart.

    After the initial “suspense of destruction”, it should be represented more as an on-going, planned scheduling and pre-determined identification process than some unplanned panic response, which is how I see the label “Suspend Destruction.” Certainly this entire section would need reiteration upon (scheduled or other) occasion, to re-evaluate the Plans in the current and foreseen environments.

    • 1.1
      Michael Gray says:

      I gather, Tom, that it should be implicit in any firm’s IT plan to have a data retention policy. I know personally that 7 years is common, however many cases in our system (government system) have been going on for 8+ years. In order to mitigate the risk of the data being destroyed if it falls outside of the firm’s data retention timeframe, this step must be included.

      Also, firms often have differing levels of retention policies – I used to work in an office about 2 years ago that only allowed you to have 10mb of email per employee on the exchange server – data retention wasn’t about length of time – it was about space. If you wanted more than that, you had to individually archive to your c drive… not good practice, however that was the firm’s policy.

Add Comment Register



Leave a Reply