** This blog series is intended to introduce new eDiscovery professionals to the litigation process and litigation terminology. Click here, here, here, here, here, here, here, here, here, here, here, here, here and here to go to the first fourteen posts in the series.**
In this blog series, we’ve talked quite a bit about discovery, and we’ve covered the first steps involved in handling documents – steps that lead up to the document review. As a litigation technology professional, you’ve probably assisted litigation teams in the review process. You might have helped to select, set up, and maintain review technology applications, or to supervise document review activities. Your focus has probably been on technology and monitoring project status. It’s important, however, that you don’t lose sight of the objectives of the document review, and that you understand the challenges that come with the territory. Keeping these things in mind will better enable you to make valuable contributions to the document review effort.
Objectives: The primary objective of a document review is to select documents that are responsive and must be produced, and at the same time to ensure that privileged documents are not produced. The litigation team might establish secondary objectives as well. For example, they may choose to identify hot documents during the review and assign issue or topic codes to documents. On one hand, it makes sense to do as much as possible in the review to get the biggest bang for your buck. On the other hand, if you ask people to do too much, you increase the likelihood of errors and extend the time it will take to complete the review. Suggest to the litigation team that they consider the size of the collection, the review team’s familiarity with the case, the complexity of the issues, and production deadlines when determining the scope of what you’ll ask a review team to do.
Challenges: The litigation team wants document review work to be high quality and consistent. And of course, they want it to cost as little as possible. These requirements can be difficult to meet because of the typical challenges that are inevitable, especially on a big project. Two of the biggest challenges are:
In next week’s post, we’ll stark covering what happens after discovery. Please let us know if there are specific litigation topics that you’d like to see covered in this blog series.
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.
Browse eDiscovery Daily Blog