Collection

eDiscovery Project Management: Data Gathering Plan, Identify Data Sources

 

One of the first electronic discovery tasks you’ll do for a case is to collect potentially responsive electronic documents from your client.  Before you start that collection effort, you should prepare a data-gathering plan to ensure that you are covering all the bases.  That plan should identify the locations from which data will be collected, who will collect the data, and a schedule for the collection effort.

Learn about Your Client

First, you need information from your client that is aimed at identifying all the possible locations and custodians of responsive data.  Some of this information may be available in written form, and some is best gleaned by interviewing client employees.   

Start by looking at:

  • Organization charts to identify potential custodians.
  • Organization charts for the IT and Records Management departments so you’ll know what individuals have knowledge of the technology that is used and how and where data is stored.
  • Written policies on computer use, back-ups, record-retention, disaster recovery, and so on.

To identify all locations of potentially relevant data, interview client employees to find out about:

  • The computer systems that are used, including hardware, software, operating systems and email programs.
  • Central databases and central electronic filing systems.
  • Devices and secondary computers that are used by employees.
  • Methods that employees use for communicating including cell phones, instant messaging, and social networking.
  • Legacy programs and how and where legacy data is stored.
  • What happens to the email and documents of employees that have left the organization.
  • Third party providers that store company information.

Once you’ve done your homework and learned what you can from your client, compile a list of data sources of potentially relevant materials.  To compile that list, you should get input from:

  • Attorneys who are familiar with the issues in the case and the rules of civil procedure.
  • Technical staff who understand how data is accessed and how and where data is stored
  • Records management staff who are familiar with the organization’s record retention policies
  • Client representatives who are experts in the subject matter of the litigation and familiar with the operations and business units at issue. 

Once you’ve got your list of data sources, you’re ready to put together the data-gathering plan. 

So, what do you think?  Do you routinely prepare a data-gathering plan?  Have you had problems when you didn’t?  Please share any comments you might have or tell us if you’d like to know more about a particular topic.

Announcing eDiscovery Thought Leader Q&A Series!

 

eDiscovery Daily is excited to announce a new blog series of Q&A interviews with various eDiscovery thought leaders.  Over the next three weeks, we will publish interviews conducted with six individuals with unique and informative perspectives on various eDiscovery topics.  Mark your calendars for these industry experts!

Christine Musil is Director of Marketing for Informative Graphics Corporation, a viewing, annotation and content management software company based in Arizona.  Christine will be discussing issues associated with native redaction and redaction of Adobe PDF files.  Her interview will be published this Thursday, October 14.

Jim McGann is Vice President of Information Discovery for Index Engines. Jim has extensive experience with the eDiscovery and Information Management.  Jim will be discussing issues associated with tape backup and retrieval.  His interview will be published this Friday, October 15.

Alon Israely is a Senior Advisor in BIA’s Advisory Services group and currently oversees BIA’s product development for its core technology products.  Alon will be discussing best practices associated with “left side of the EDRM model” processes such as preservation and collection.  His interview will be published next Thursday, October 21.

Chris Jurkiewicz is Co-Founder of Venio Systems, which provides Venio FPR™ allowing legal teams to analyze data, provide an early case assessment and a first pass review of any size data set.  Chris will be discussing current trends associated with early case assessment and first pass review tools.  His interview will be published next Friday, October 22.

Kirke Snyder is Owner of Legal Information Consultants, a consulting firm specializing in eDiscovery Process Audits to help organizations lower the risk and cost of e-discovery.  Kirke will be discussing best practices associated with records and information management.  His interview will be published on Monday, October 25.

Brad Jenkins is President and CEO for Trial Solutions, which is an electronic discovery software and services company that assists litigators in the collection, processing and review of electronic information.  Brad will be discussing trends associated with SaaS eDiscovery solutions.  His interview will be published on Tuesday, October 26.

We thank all of our guests for participating!

So, what do you think?  Is there someone you would like to see interviewed for the blog?  Are you an industry expert with some information to share from your “soapbox”?  If so, please share any comments or contact me at daustin@trialsolutions.net.  We’re looking to assemble our next group of interviews now!

eDiscovery Best Practices: Cost of Data Storage is Declining – Or Is It?

Recently, I was gathering information on the cost of data storage and ran across this ad from the early 1980s for a 10 MB disk drive – for $3,398! That’s MB (megabytes), not GB (gigabytes) or TB (terabytes). What a deal!

Even in 2000, storage costs were around $20 per GB, so an 8 GB drive would cost about $160.

Today, 1 TB is available for $100 or less. HP has a 2 TB external drive available at Best Buy for $140 (prices subject to change of course). That’s 7 cents per GB. Network storage drives are more expensive, but still available for around $100 per TB.

At these prices, it’s natural for online, accessible data in corporations to rise exponentially. It’s great to have more and more data readily available to you, until you are hit with litigation or regulatory requests. Then, you potentially have to go through all that data for discovery to determine what to preserve, collect, process, analyze, review and produce.

Here is what each additional GB can cost to review (based on typical industry averages):

  • 1 GB = 20,000 documents (can vary widely, depending on file formats)
  • Review attorneys typically average 60 documents reviewed per hour (for simple relevancy determinations)
  • That equals an average of 333 review hours per GB (20,000 / 60)
  • If you’re using contract reviewers at $50 per hour – each extra GB just cost you $16,650 to review (333×50)

That’s expensive storage! And, that doesn’t even take into consideration the costs to identify, preserve, collect, and process each additional GB.

Managing Storage Costs Effectively

One way to manage those costs is to limit the data retained in the first place through an effective records management program that calls for regular destruction of data not subject to a litigation hold. If you’re eliminating expired data on a regular basis, there is less data to go through the EDRM discovery “funnel” to production.

Sophisticated collection tools or first pass review tools (like FirstPass™, powered by Venio FPR™) can also help cull data for attorney review to reduce those costs, which is the most expensive component of eDiscovery.

So, what do you think? Do you track GB metrics for your eDiscovery cases? Please share any comments you might have or if you’d like to know more about a particular topic.

Social Tech eDiscovery: Twitter Guidelines for Law Enforcement

Tuesday, I provided information regarding Facebook’s Law Enforcement page with information about serving civil subpoenas. Facebook provides quite a bit of useful information regarding serving subpoenas, including the address for registered agent (to process requests), information required to identify users, fee for processing, turnaround time, and fee to expedite responses. Facebook is very informative with regard to how subpoenas are handled in terms of cost and time to process.

So, it makes sense to look at other popular social media sites to see how they are handling this issue. Twitter is probably right behind Facebook in terms of popularity in the social media world and they have a “Guidelines for Law Enforcement” page to address requests for non-public information for Twitter users.

As the Twitter policy notes, most Twitter profile information is public, so anyone can see it. A Twitter profile contains a profile image, background image, as well as the status updates, which, of course, they call “tweets”. In addition, the user has the option to fill out location, a URL, and a short “bio” section about themselves for display on their public profile. Non-public information includes “log data” such as IP address, browser type, the referring domain, pages visited, search terms and interactions with advertisements (as noted in their Privacy Policy page).

Twitter doesn’t provide any cost information regarding processing subpoena requests, nor do they address standard turnaround times or fees to expedite processing. Their policy is to notify users of requests for their information prior to disclosure unless they are prohibited from doing so by statute or court order and they do require the URL of the Twitter profile in question to process any subpoena requests. They do provide email, fax and physical address contact information to address user information requests. FYI, only email from law enforcement domains will be accepted via the email address. Preservation requests must be signed with a valid return email address, and sent on law enforcement letterhead. Non-law enforcement requests should be sent through regular support methods (via their main support page).

So, what do you think? Have you ever needed to file a subpoena on Twitter? Please share, or let us know or if you’d like to know more about a particular topic.

Social Tech eDiscovery: Facebook Subpoena Policy

As President and CEO of Trial Solutions, I’ve noted and embraced the explosion in use of social technology over the past few years (Trial Solutions has a Facebook, Twitter and LinkedIn page, and this blog, with more to come soon). According to new statistics from Nielsen, social network sites now account for 22.7% of time spent on the web, a 43% jump in one year (by contrast, email only accounts for 8.3%). With that explosion in social tech use, companies have had to address social media as another form of media to collect for eDiscovery. It seems there’s a new article or blog post online every week on the subject and there is a social media webinar at Virtual Legal Tech this Thursday.

As probably the most popular social media site, Facebook is one of the most likely sites for relevant ESI. There are already a number of stories online about people who have lost their jobs due to Facebook postings, such as these. There is even a Facebook group to post stories about Facebook firings. Oh, the irony!

Naturally, cases related to Facebook eDiscovery issues have become more prevalent. One case, EEOC v. Simply Storage Management, resulted in a May ruling that “SNS (social networking site) content is not shielded from discovery simply because it is ‘locked’ or ‘private’”. So, request away!

If the employee resists or no longer has access to responsive content (or you need to request from their online friends through “Wall” posts), you may have to request content directly from Facebook through a subpoena. Facebook has a Law Enforcement page with information about serving civil subpoenas, including:

  • Address for Registered Agent (to process requests)
  • Information Required to Identify Users – Facebook user ID (“UID”) or email address
  • Fee for Processing ($500, plus an additional $100 if you want a notarized declaration)
  • Turnaround Time (minimum of 30 days)
  • Fee to Expedite Responses ($200)

Obviously, fees are subject to change, so check the page for the latest before serving your subpoena.

So, what do you think? Have you ever needed to file a subpoena on Facebook? Aware of other case law related to Facebook eDiscovery? Please share, or let us know or if you’d like to know more about a particular topic.