Project Management

Litigation Support Tools of the Trade – eDiscovery Best Practices

If you have worked in litigation support for a number of years like I have, you start to assemble a toolkit of applications that help you get your job done more quickly and efficiently.  In her excellent Litigation Support Guru blog, Amy Bowser-Rollins (who was previously profiled on THIS blog) has recently published a series of posts that describe tools of the trade that she recommends to litigation support “newbies”.  Let’s take a look.

The entire series of 18 Tools of the Trade is available here.  Here are the specific tools that she covers:

  1. TextPad
  2. Snagit
  3. Unstoppable Copier
  4. Concordance CPL to convert DAT to DCB
  5. Bulk Rename Utility
  6. TrueCrypt
  7. FileZilla
  8. Beyond Compare
  9. Dan Biemer Concordance CPLs
  10. Tableau
  11. Avery DesignPro
  12. UltraEdit
  13. FTK Imager (also previously discussed on our blog here, here, here, here and here)
  14. Directory Lister Pro
  15. iConvert
  16. Hard Drive SATA/IDE Adapter
  17. 7-Zip
  18. AutoCAD Viewer

Whether you need to edit large text files, perform screen captures, copy or rename files, manipulate data for Concordance, encrypt data for transfer, FTP data using an intuitive interface, capture data from a drive without spoliating evidence, create CD labels, convert load files, compress file collections or view engineering drawings, there is an application for you.  I personally use many of these frequently, including TextPad, Snagit, TrueCrypt, FileZilla, Beyond Compare, FTK Imager and iConvert.

Several of these applications are free.  Most are at least inexpensive.  They are vital “tools of the trade” for litigation support professionals.  Kudos to Amy for a terrific blog series!

So, what do you think?  What “tools of the trade” do you have in your litigation support “tool belt”?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Our 1,000th Post! – eDiscovery Milestones

When we launched nearly four years ago on September 20, 2010, our goal was to be a daily resource for eDiscovery news and analysis.  Now, after doing so each business day (except for one), I’m happy to announce that today is our 1,000th post on eDiscovery Daily!

We’ve covered the gamut in eDiscovery, from case law to industry trends to best practices.  Here are some of the categories that we’ve covered and the number of posts (to date) for each:

We’ve also covered every phase of the EDRM (177) life cycle, including:

Every post we have published is still available on the site for your reference, which has made eDiscovery Daily into quite a knowledgebase!  We’re quite proud of that.

Comparing our first three months of existence to now, we have seen traffic on our site grow an amazing 474%!  Our subscriber base has more than tripled in the last three years!  We want to take this time to thank you, our readers and subcribers, for making that happen.  Thanks for making the eDiscoveryDaily blog a regular resource for your eDiscovery news and analysis!  We really appreciate the support!

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan University, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, e-Discovery Team ® and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

I also want to extend a special thanks to Jane Gennarelli, who has provided some serial topics, ranging from project management to coordinating review teams to what litigation support and discovery used to be like back in the 80’s (to which some of us “old timers” can relate).  Her contributions are always well received and appreciated by the readers – and also especially by me, since I get a day off!

We always end each post with a request: “Please share any comments you might have or if you’d like to know more about a particular topic.”  And, we mean it.  We want to cover the topics you want to hear about, so please let us know.

Tomorrow, we’ll be back with a new, original post.  In the meantime, feel free to click on any of the links above and peruse some of our 999 previous posts.  Now is your chance to catch up!  😉

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

When Reviewing and Producing Documents, Don’t Forget the “Mother and Child Reunion” – eDiscovery Best Practices

I love Paul Simon’s music.  One of my favorite songs of his is Mother and Child Reunion.  Of course, I’m such an eDiscovery nerd that every time I think of that song, I think of keeping email and attachment families together.  If you don’t remember the Mother and Child Reunion, you might provide an incomplete production to opposing counsel.

BTW, here’s a little known fact: Paul Simon took the title of the song Mother and Child Reunion from the name of a chicken-and-egg dish he noticed on a Chinese restaurant’s menu.

Like the rest of us, attorneys don’t like to feel shortchanged, especially in discovery.  While there are exceptions, in most cases these days when an email or attachment is deemed to be responsive, the receiving party expects to also receive any “family” members of the responsive file.  Attorneys like to have the complete family when reviewing the production from the other side, even if some of the individual files aren’t responsive themselves.  Receiving an email without its corresponding attachments or receiving some, but not all, of the attachments to an email tends to raise suspicions.  Most attorneys don’t want to give opposing counsel a reason to be suspicious of their production, so parties typically agree to produce the entire email “family” in these cases.  Here’s a scenario:

The case involves a dispute over negotiated gas rate agreements between energy companies and Federal Energy Regulatory Commission (FERC) approval of those rate agreements.  A supervisor at the company verbally requests a copy of a key contract from one of his employees, along with the latest FERC filings and the employee emails a copy of the contract and FERC filing summary attached to an email with the subject “Requested files” and the body stating “Here you go…” (or something to that effect).  A search for “negotiated w/2 (gas or rate or agreement)” retrieves the contract attachment, but not the email, which doesn’t really have any pertinent information on it, or the FERC filing summary.  Only part of the email “family” is responsive to the search.

If it’s important to produce all communications between parties at the company regarding negotiated gas agreements, this communication could be missed – unless your review protocol includes capturing the family members of responsive files and your review software provides an option to view the family members of responsive files and include them in search results.  I underlined “option” because there are still a few cases where parties agree to limit production to actual responsive files and not produce the families (though, in my recent experience, those cases are exceptions).

If your case isn’t one of the exceptions, make sure you have a well thought out protocol and robust software for including family members in your search results and in your document reviews for responsiveness, as well as automated and manual Quality Assurance (QA) and Quality Control (QC) checks to ensure your production contains complete family groups.

So, what came first, the chicken or the egg?  It doesn’t matter, as long as the family group is intact.  🙂

So, what do you think?  How do you handle family groups in discovery?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

It’s Friday at 5 and I Need Data Processed to Review this Weekend – eDiscovery Humor

We’ve referenced Ralph Losey’s excellent e-Discovery Team® blog several times before on this blog – it’s a great read and you won’t find a blog that gets more in depth than his does (he has also been gracious enough to participate in our thought leader interview series for the last three years).  And, as Ralph has demonstrated before, he has a sense of humor when it comes to electronic discovery.

In his latest post, Are You The Lit Support Tech?, Ralph takes a humorous look at “what it is like on a Friday afternoon in the Litigation Support Departments of most law firms”.  Or so it seems sometime.  Like before, Ralph used XtraNormal to make the video.  XtraNormal enables you to make an animated movie by selecting your animated “actors”, type or record your dialogue, and select a background.  The “actors” sound a bit robotic if you type the dialogue, but that just adds to the humor as the pronunciations and inflections are rather humorous.

Anyway, the video involves a law firm partner coming to the lit support tech on a Friday afternoon and asking for help to process data for ten custodians so that he can review over the weekend as the production is due Monday.  “When did you receive the request?”, asks the tech.  “30 days ago”, says the partner, “Why?”.  “No reason”, says the tech.

The video continues with the partner telling the tech not to worry “it’s only 15 gigabytes…not such a big number”.  When the tech says that it’s over a million pages and he will have to process it and load it into their review platform, the partner says “I don’t have time for all the processing and stuff, just print it out and load it in my car.”

OK, so part of the humor is that it’s a bit farfetched (hopefully).  Ralph notes that because he no longer has to supervise a litigation support department (because Jackson Lewis outsources all of its nonlegal electronic data discovery work), his “Friday afternoons are much nicer”.

It’s the vendor that has to deal with these last minute requests.  At CloudNine Discovery, we can relate to the lit support tech who receives 15 gigabytes (or even more) on a Friday afternoon to process for weekend review – we get those types of requests more often than you think and our staff often works late Fridays to get the client’s data ready.  It goes with the territory.  So, we don’t make big plans on Friday night so that you can enjoy yours!

So, what do you think?  Have you had to deal with last minute eDiscovery requests?  If so, how do you handle them?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Other Production Parameters from a Provider’s Point of View – eDiscovery Best Practices

Yesterday, we began to discuss some of the production parameters that CloudNine Discovery collects from our clients in order to ensure that the production includes the correct documents in the required format.  But, wait – there’s more!  Let’s take a look at some other examples of information we collect from our clients.

  • Naming Structure for Files: Files that are produced follow some sort of naming convention and structure, typically either the original file name or some sort of naming convention that involves a unique identifying prefix followed by a zero-filled number (e.g., ABC000001.{file extension}).
  • Image Endorsements: Of course, images that are produced typically include a Bates number on each page that involves a unique identifying prefix followed by a zero-filled number (see example above), but endorsements can also include special endorsements such as a confidential stamp, so we provide a place on our questionnaire for clients to provide additional endorsement instructions for text and placement.
  • Metadata Fields and/or Tags to Be Produced: If the client is producing metadata, it’s obviously important to know the fields to be produced and the desired order.  We also ask them to specify the delivery format – the typical formats are CSV (comma separated values, which can be loaded into Excel) or DAT (data) file.
  • Populate Production Numbers Back into Database: When clients produce documents, they typically want to track the production numbers, so we give them the option for us to create new fields in their (OnDemand®) database with those production numbers.
  • Branded Images Back into Database: We also offer the same option for putting images branded with the Bates numbers and other endorsements back into the database, so that the client can easily reference the production number when looking at the page.
  • Load File: Often parties agree to produce load files to make it easy for opposing counsel to load the documents and metadata into their own eDiscovery platform, so we will create load files in several industry standard formats to support that requirement.
  • Delivery Method for Production: There are several options for delivering documents and data including CD or DVD, portable hard drive or electronically via File Transfer Protocol (FTP).
  • Where to Send Production: If the client selects CD, DVD or Portable Hard Drive, we require the Name, Street Address and Phone Number where the media is being delivered, if they select FTP, we need an FTP address (and any credentials, if necessary, to access it).
  • Name of Production Set: We request that each production set be uniquely named for later reference purposes, which is especially useful when there are multiple productions to track.
  • Other Instructions: Believe it or not, all of the parameters that we’ve identified over the past two days don’t cover every scenario, so we provide a place on the questionnaire to provide any other instructions.  Those can range from special handling for other file types, extra copies requested, etc.

As you can see, we collect a lot of information from our clients at production time to ensure a proper production.  There are a lot of variables to consider, so it’s important to be consider those variables not just when producing, but WAY back at the beginning of the case, to ensure that you will be able to fulfill your discovery obligations to opposing counsel.  Hope this list of parameters was helpful.

So, what do you think?  How do you ensure proper productions?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Production from a Provider’s Point of View – eDiscovery Best Practices

 

We sometimes forget that the end goal of the discovery process is production: to produce responsive electronically stored information (ESI) to opposing counsel.  But, do you realize how many parameters and potential permutations there can be to the production process?  Let’s take a look.

eDiscovery providers like (shameless plus warning!) CloudNine Discovery handle productions for our clients routinely, (in our case, often out of our eDiscovery review application, OnDemand®).  When a client asks for a production, there are a series of questions to ask to ensure that the production includes the correct documents in the required format.  To ensure that and avoid potential confusion, we provide a questionnaire to the client to complete to define the parameters of that production.  Examples of information we collect from our clients:

  • Documents to be produced: Typically, we expect the client to identify a tag that was applied to the documents (especially when the documents are in OnDemand) to be used to identify the documents to be produced (e.g., To Be Produced, Responsive-Produce, etc.) and confirm the count of documents that are included in that tag.  If the count doesn’t match the tag, we resolve with the client before proceeding.
  • Output Formats to Include: Productions can be native or image, may or may not include Optical Character Recognition (OCR) or extracted text and may or may not include metadata.  It’s important to confirm the formats to be produced, which can include all or just some of the available formats.
  • Format of Images: If images are to be produced, we confirm whether they single or multi-page TIFF, or in Adobe PDF.
  • Format of OCR/Extracted Text Files: OCR files can also be produced either in single or multi-page files, so we enable the client to specify the format.
  • Handling of Excel Files: Because they are often not formatted for printing, Excel files often don’t image well and generate a high number of image pages.  So, we provide options for producing a placeholder image along with the native Excel file (which is the default option), or TIFFing all or part of the Excel document.
  • Handing of AutoCad Files: Though less common, AutoCad DWG files can also be problematic to convert to TIFF, so we provide a placeholder and native option for this file type as well.
  • Handling of Redactions: If redactions are present, we confirm the production of documents with the redactions present.  We also recommend that (and assist clients with) removal of redacted text from OCR files of the redacted images to ensure that there are no inadvertent disclosures of privileged or confidential information via those text files.

This is just the beginning of what we ask clients.  Tomorrow, we will cover other information we collect to ensure a proper production.

So, what do you think?  How do you ensure proper productions?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

The Pitfalls of Self-Culling and Image Files – eDiscovery Best Practices

This topic came up with a recent client, so I thought I would revisit it here on this blog.

There’s a common mistake that organizations make when collecting their own files to turn over for discovery purposes.  Many attorneys turn over the collection of potentially responsive files to the individual custodians of those files, or to someone in the organization responsible for collecting those files (typically, an IT person) and the self-collection involves “self-culling” through the use of search terms.  When this happens, important files can be missed.

Self-culling by custodians, unless managed closely, can be a wildly inconsistent process (at best).  You’re expecting each custodian to apply the same search terms consistently and, even if IT performs the self-culling, the process may have to be repeated if additional search terms are identified later on.  Even worse, potentially responsive image-only files will be missed with self-culling.

It’s common to have a number of image-only files within any collection, especially if the custodians frequently scan executed documents or use fax software to receive documents from other parties.  In those cases, image-only PDF or TIFF files can often make up as much as 20% of the collection.  When custodians are asked to perform “self-culling” by performing their own searches of their data, these files, which could contain information responsive to the case, will certainly be missed.

With the possibility of inconsistent self-culling, the possibility of additional search terms identified later and the (almost certain) presence of image-only files, I usually advise against self-culling by custodians.  I also don’t recommend that IT perform culling on behalf of the custodians, unless they have the ability to process that data to identify image-only files and perform Optical Character Recognition (OCR) to capture text from them.  If your IT department has the capabilities and experience to do so (and the process and chain of custody is well documented), then that’s great.  However, most internal IT departments either don’t have the capabilities or expertise (or both), in which case it’s best to collect all potentially responsive files from the custodians and turn them over to a qualified eDiscovery provider to perform the culling (performing OCR as needed to include responsive image-only files in the resulting responsive document set).  Unless the case requires supplemental productions, there is also no need to go back to the custodians to collect additional data with the full data set available.

So, what do you think?  Do you self-collect data for discovery purposes?  If so, how do you account for image-only files?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Government Attorneys Have eDiscovery Issues Too – eDiscovery Trends

 

When many eDiscovery professionals talk about their clients, they’re usually talking about law firms and corporations.  However, government agencies have their own eDiscovery challenges.  According to findings from Deloitte’s 7th Annual Benchmarking Study of e-Discovery Practices for Government Agencies, attorneys and other professionals in government agencies have their own problems and concerns when it comes to eDiscovery.

One hundred twenty three (123) professionals from various government agencies participated in the survey, with attorneys comprising 80% of the respondents.  Depending on the area, the respondents showed different levels of confidence in their preparedness regarding discovery and handling of discovery matters:

  • When it comes to challenges with regard to handling, processing, reviewing, or producing ESI, the respondents ranked the most significant challenges as follows: 1) Internal systems and processes, 2) Buy-In from senior management, 3) Communicating with IT, 4) Budgetary issues/constraints;
  • When asked if they felt adequately prepared to discuss matters regarding eDiscovery with opposing counsel, 53% of the respondents said ‘Yes’;
  • However, when asked if they feel that you have adequate technical support when dealing with opposing counsel regarding electronic discovery, only 25% of the respondents said ‘Yes’;
  • From a confidence standpoint, 73% of respondents feel as confident or more confident in their ability to manage eDiscovery in their cases.  But, 84% of respondents feel somewhat or not at all effective in their agency’s ability to deal with the challenges of eDiscovery and 80% of respondents feel somewhat or not at all confident that if challenged their agency could demonstrate that their ESI was “accurate, accessible, complete and trustworthy;
  • Predictive coding may be the wave of the future, but only 17% of survey respondents indicated that they had used it in any of their cases;
  • When asked what issues are driving upper management to explore more advanced electronic discovery solutions, the most commonly identified issue was ‘respond to increasing amounts of data’ (20% of respondents).  However, 19% of respondents indicated that their upper management is not actively looking for an eDiscovery solution;
  • Top three challenges in identifying ESI identified by respondents were: 1) Volume of data, 2) obsolete or proprietary data and 3) insufficient manpower.

You can download Deloitte’s 4 page report here.  If you’re not in a mood to read and you like your findings condensed USA Today infographic style, you can open up their one page infographic here.

So, what do you think? Do you work for, or with, government agencies?  If so, do any of these findings surprise you? Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Planning for the Unexpected: Changing eDiscovery Providers on Short Notice – eDiscovery Best Practices

 

Editor’s note: From time to time, we get the opportunity to host a “guest blogger” which not only provides a different perspective to our readers, but also gives me a break from writing for a day!  🙂  Formerly the Vice President of eDiscovery and Information Governance at one of largest biopharmaceutical companies in the world, Ronke Ekwensi is now a Managing Director at Huron Legal, where she helps clients overcome information lifecycle challenges to meet immediate and long-term information governance and eDiscovery goals.  Ronke has written a terrific article about her challenge in having to switch eDiscovery providers right after taking over as head of eDiscovery and how she and her team addressed that challenge.  Enjoy!

_________________________________

About a month after assuming my role as head of eDiscovery for one of the world’s largest biopharmaceutical companies, I was suddenly forced to change eDiscovery vendors.

The day began with what I thought was a routine business meeting with our existing eDiscovery vendor, a relationship which, until that moment, had been blissful. Five minutes into the meeting, bliss was replaced with shock when I learned that the company’s owners had decided to “get out of the eDiscovery business.”

The experience forcefully taught me the importance of carefully choosing an eDiscovery vendor. Savvy practitioners typically look at vendors’ substantive qualifications such as analytics expertise, review capacity, processing and hosting technology, but do not necessarily look at their underlying stability and are often unprepared to deal with an eventuality like the one I faced. 

Following are some lessons I learned from the experience:

1.  Communicate internally

The first order of business should be internal communication. Your approach to communication could possibly make or break the success of the transition.

a. With management

It is critical to keep upper management informed. Their data and their litigation are at issue and you do not want them to learn of the situation elsewhere. The communication should be direct and focused; while tempting, this is not the time to be alarmist or adversarial. I chose to simply state the facts and make assurances that my team and I had the situation under control. I committed to deliver to management a fully executable plan within a few days.

b. With affected stakeholders

It is also important to make sure that those affected by the change are kept informed of the situation, including internal stakeholders and outside counsel.

2.  Assemble a transition team

Bring together the key team members who will be involved in the transition. I kicked off a small internal team from the law department (both eDiscovery and litigation) and our IT organization.

3.  Assess the current state

The transition team’s first order of business should be to assess the full state of affairs.  In our case, the team was charged with answering the following questions:

  • What data is in the vendor’s possession? 
  • In what phases of the Electronic Discovery Reference Model (EDRM) is the data?
  • Which matters are affected?
  • In what stage in the litigation are these matters?
  • What is the implication of switching providers mid-matter?
  • What are the technical options available for data transfer?
  • What are the risks inherent in each option and are they defensible?

Each component of these answers can require technical expertise and legal advice to ensure defensibility.

4.  Identify a new eDiscovery partner

“Vendor going out of business” is a very uncomfortable feeling, and it highlighted for me the importance of looking beyond technical and EDRM capabilities in the vendor selection process. A critical part of our selection was the potential vendors’ financial stability, based on a strong balance sheet, diversified products or services, and a diversified client base. We elected not to consider providers for whom a single “anchor client” accounted for more than 50% of their revenue. 

Working with our procurement organization, we developed a robust set of objective and subjective criteria with which to evaluate potential providers on their likely longevity. The criteria included:

  • Annual eDiscovery services revenue above $25 million.
  • Fully verifiable multi-year financial statements (particularly privately held companies)
  • At least three favorable client references within our industry

Through the partner selection process, I was skeptical of low priced vendors, privately held companies without financial transparency, and the “new kid in town.” I was not enamoured by flashy presentations of the latest, greatest technology.  We ultimately selected a partner that was financially stable and did quality work at a good price point.

5.  Transfer active matters

I once worked with a facilities manager who quipped, “the way to get people to reduce the paper in their offices is to move them frequently.” That was certainly true in the digital equivalent of our transition plan.  The cost, complexity, and risk of moving over 40 terabytes relating to hundreds of matters necessitated that we develop a strategic approach to data transition. We therefore archived as much data as was practical, based on the direction of the lawyers overseeing the matter and the opportunity to reduce cost. The rest of the data we transitioned to our new platform.

6.  Create defensible documentation

My team and I entered this situation at a disadvantage. I was new to the position and my team was completely new. The vendor relationship had been established and most of the data had been transferred before I joined the company. The data related to multi-year matters that had gone through a phased collection process. I was determined that, going forward, we would document our process, both for defensibility and to preserve organizational history. Each action taken for each matter was fully documented and the documentation was preserved as a business record.

Conclusion

While not pleasant at the time, the experience resulted in tremendous benefits in the end. We were able to improve our existing processes, seek opportunities to reduce costs, “clean house,” and select an eDiscovery partner, not just another vendor. I am happy to report that the relationship lasted a long time.

_________________________________

So, what do you think? Have you been forced to suddenly switch eDiscovery providers?  If so, how did you handle it?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

ASU-Arkfeld eDiscovery and Digital Evidence Conference – eDiscovery Trends

Apparently, next week is the week for eDiscovery conferences.

Last week, I told you about a two-day program being hosted next week in my hometown of Houston by The Sedona Conference®.  Then, on Tuesday, I told you about the Second Annual Electronic Discovery Conference for the Small and Medium Case, hosted by the Levin College of Law at the University of Florida and EDRM also next week.  Now, here is another conference alternative for next week – the Third Annual ASU-Arkfeld eDiscovery and Digital Evidence Conference, hosted by Arizona State University and noted eDiscovery expert Michael Arkfeld.

The conference will be held next week, March 12-14 at the Sandra Day O’Connor College of Law / Armstrong Hall at Arizona State University in Tempe, Arizona.  As the downloadable brochure states, the conference will be “[f]ocusing on the practical issues affecting the discovery and admission of electronic information.  Attendees will be participating with thought leaders and practitioners of eDiscovery on issues impacting legal professionals locally, nationally, and globally.”

The conference will include:

  • noted eDiscovery judges, including Shira A. Scheindlin (who will be giving the keynote address on the first morning), John Facciola, and Craig Shaffer;
  • knowledgeable in-house counsel and eDiscovery specialists, including Robert Amicone from Office Depot, Tom Morrissey from Purdue Pharma and Kit Goetz from Qualcomm;
  • distinguished outside counsel, including Robert Singleton from Squire Sanders, Mark Sidoti from Gibbons, Joy Woller from Lewis Roca Rothgerber, Maura Grossman from Wachtell, and Ariana Tadler from Milberg and;
  • dedicated litigation support professionals including Tom O’Connor, Steven Goldstein, and Anne Kershaw.

Topics run the full range of the eDiscovery life cycle – from information management strategies to dispose of “zombie data” (I like that term) to meet and confer, preservation, collection, data analytics and technology assisted review, production formats, eDiscovery for criminal cases and cross-border issues and eDiscovery project management best practices.  You can earn up to 15 hours of CLE credit for attending.

It’s too late for early bird pricing, but regular attendees can still register prior to the show for $595.  Government, non-profit and paralegal registrants can do so for $345; if you’re a student, it only costs $95 to attend.  Those rates are $695/$395/$115, respectively, if you wait until the day the show starts.  Discounted group rates are also available.  You can register for the conference online here.

So, what do you think? Do you plan to attend the program, or perhaps one of the other programs next week? Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.