I looked at press release and realized and what actually come to my attention is the next part:
"To meet the needs of the variety of firms exposed to spoliation torts – including architects, engineers, land surveyors, landscape architects and agency construction managers, as well as engineering companies that provide testing and forensic analysis"
In my archives and records management practise, I worked with records of some big construction companies.
After seeing the records, it is no mo secret for me when I here about.... collapsing of structure, let say.
Very often when it happened, investigator are looking for documents, and very often they don't exist somehow.
I think you remember than now we have set of records from designer, architect , engineer, and set called "as build" .
Before, before...
it was common that the changes in the material used were not saved, or somehow, "forgotten" on the field.
When investigators look at original records - plans, engineering calculations, and..., and compare them with analysis of what left over from the structure....Hairs go up. I think you know these stories.
Now, may be this Insurance is talking also about cases like this?
Contractor, sub-contractor, sub-sub-contractor???
Another issue. I worked with records related to "licencing' the foreign colleges and universities, mostly from US, and was surprised how well the part related to keeping Records was worded.
Let say the University??? from some American state. In case the University decides to close its activity completely, the all records regarding programs, staff, and graduates, will transfer to State Archives, or another University ( with real name).
Also, the document says who will control the safety of the records of this university.
For me it was example how it should be, on the paper at least.
Another side of this insurance:
what will be cheaper -to establish proper records management program, or to pay the annual insurance premium, that could be equal potential fine?
Regards,
Alex Babin
[log in to unmask]
--- On Tue, 12/7/10, Todd Johnson <[log in to unmask]> wrote:
From: Todd Johnson <[log in to unmask]>
Subject: Re: [RM] Lexington Insurance Company Introduces Spoliation Insurance
To: [log in to unmask]
Received: Tuesday, December 7, 2010, 6:17 AM
I thought this was interesting and wondered if anyone has seriously looked
at this. At first glance it appears companies could buy spoliation
insurance, spend less money on RIM/eDiscovery and take their chances that if
information assets relating to litigation were lost or destroyed, the
spoliation insurance would cover them...
Any thoughts are appreciated.
Todd Johnson, CRM, ermm
Analyst - Records & Information Management
Southern Star Central Gas Pipeline
4700 Hwy 56
Owensboro, KY 42301
Direct: (270) 852-4512
On Sat, Dec 4, 2010 at 8:24 AM, PeterK <[log in to unmask]> wrote:
> Lexington Insurance Company Introduces Spoliation Insurance
>
> http://bit.ly/hCEqTA
>
> Source:
> http://www.businesswire.com/news/home/20101202005980/en/Lexington-Insurance-Company-Introduces-Spoliation-Insurance
> See if people are clicking on this link:http://bit.ly/hCEqTA+
> Try the bit.ly sidebar to see who is talking about a page on the web:
> http://bit.ly/pages/sidebar
>
> 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]
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]
|
