Thursday, September 30, 2010

E-discovery moves in-house

More companies are seeing the wisdom of putting the function under internal IT control

When Jonathan Chow, chief information security officer at NBC Universal, found his department's services in increasing demand, that wasn't necessarily a good thing.

He says demand for e-discovery services was increasing 30% to 50% annually in the early and middle parts of the past decade, and he was seeing a dramatic rise in the hours spent supporting e-discovery as his department collected and culled through some of the electronically stored data needed by the company's legal staff.

The information security department, part of corporate IT, owns the e-discovery function and uses it not just for litigation support, Chow explains, but also for M&A activities and internal investigations generated by HR or corporate security, for example.

"We used to handle those occasional queries on an ad hoc basis, but as the number of e-discovery requests grew, this became a much larger and much more time-/resource-intensive process to manage," he said via e-mail. "It was obvious that we could more affordably conduct our e-discovery in-house, assuming we could find the best solutions to support our process."

So Chow moved e-discovery in-house in 2007.

Others are following a similar course. Analyst firm Enterprise Strategy Group (ESG) and Clearwell Systems Inc., an e-discovery software company in Mountain View, Calif., surveyed about 100 Fortune 2,000 enterprises and government agencies late last year and found that some 73% plan to bring e-discovery in-house.

Discovery is the part of the pretrial process in which both sides request information, data and documents from each other as each tries to find, or discover, facts pertinent to the case. Electronic discovery is the part of this longstanding legal process that refers to any information stored electronically.


To Continue Reading: Click Here
-----------------------------------------------------------
Source: Computerworld
By: Mary K. Pratt

0 comments: