<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Illumination eDiscovery</title>
	<atom:link href="http://blog.lheDiscovery.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.lheDiscovery.com</link>
	<description>Lighthouse eDiscovery</description>
	<lastBuildDate>Wed, 09 May 2012 17:50:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Why is Privilege Review so Expensive and What Can We Do About It?</title>
		<link>http://blog.lheDiscovery.com/?p=708</link>
		<comments>http://blog.lheDiscovery.com/?p=708#comments</comments>
		<pubDate>Tue, 08 May 2012 20:06:22 +0000</pubDate>
		<dc:creator>Debora Motyka Jones</dc:creator>
				<category><![CDATA[Data Hosting and Review]]></category>
		<category><![CDATA[Data Production]]></category>
		<category><![CDATA[Electronic Data Processing]]></category>
		<category><![CDATA[Da Silva Moore]]></category>
		<category><![CDATA[attorney client]]></category>
		<category><![CDATA[document review]]></category>
		<category><![CDATA[ediscovery]]></category>
		<category><![CDATA[electronic discovery]]></category>
		<category><![CDATA[privilege]]></category>
		<category><![CDATA[work product]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=708</guid>
		<description><![CDATA[We all know that document review is generally very expensive.  In fact, in the often quoted Da Silva Moore case, the defendants stated that they expected their review costs to be about $5/document.  On a 500,000 document case, that’s $2.5 &#8230; <a href="http://blog.lheDiscovery.com/?p=708">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We all know that document review is generally very expensive.  In fact, in the often quoted <em>Da Silva Moore </em>case, the defendants stated that they expected their review costs to be about <a title="Peck Opinion" href="http://www.nylj.com/nylawyer/adgifs/decisions/022912peck.pdf">$5/document</a>.  On a 500,000 document case, that’s $2.5 million dollars!  With privilege review being one of the most expensive types of document review, it seems a likely target for cost reduction measures.  But, how do you do so without risking waiver?  There are technologies out there that can help.<span id="more-708"></span></p>
<p>Privilege review is expensive because it is more nuanced than straight responsiveness reivew.  In responsiveness review, the reviewer can make a quick decision about most documents from the content of the document.  In privilege review, however, the reviewer must consider the content, the context and the parties involved for <span style="text-decoration: underline;">each</span> document to determine whether the document should be marked as attorney client, work product, or both.  This leads to longer review times (i.e. less documents reviewed per hour) and makes the review more costly.</p>
<p>This cost is compounded by overbroad privilege search terms.  A party will typically want to cast a wide net to capture all privilege documents—understandably, as waiving privilege through a mistaken production can be costly.  Out of  an abundance of caution, parties end up supplementing attorney names with general search terms like “attorney” and “privilege*”.  These terms frequently capture a lot of non-privileged documents such as documents containing <a title="eDiscovery Daily Footers" href="http://www.ediscoverydaily.com/2011/06/ediscovery-trends-email-footers-give-privilege-searches-the-boot.html">footers </a>or “it was a privilege to meet you.”  This practice unnecessarily drives up the number of documents that are thoroughly, and expensively, reviewed for privilege.</p>
<p>But, there are products out there that can minimize this cost without sacrificing quality.  By leveraging experts and technology, you can isolate the most likely erroneous hits.  When we recently benchmarked our <a title="PrivSmart" href="http://lhediscovery.com/Lighthouse-Review-Preparation-Privilege-Document-Reduction.htm">PrivSmart product</a>, we found it was over 99% accurate in isolating those false hits which made up over 15% of the potentially privileged documents.  Recent studies have shown human review accuracy rates to be significantly lower than 99%! Whether you decide to QC those documents or remove them from privilege review entirely, you will still see a dramatic cost and time savings by applying this process.</p>
<p>What are you doing to reduce your privilege review costs?  What other products are out there attacking this issues?  I’d love to hear from you.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=708</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lighthouse Adds Zoom to its Offerings</title>
		<link>http://blog.lheDiscovery.com/?p=700</link>
		<comments>http://blog.lheDiscovery.com/?p=700#comments</comments>
		<pubDate>Wed, 02 May 2012 17:14:11 +0000</pubDate>
		<dc:creator>Debora Motyka Jones</dc:creator>
				<category><![CDATA[Company News]]></category>
		<category><![CDATA[Data Hosting and Review]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Equivio]]></category>
		<category><![CDATA[TAR]]></category>
		<category><![CDATA[predictive coding]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[technology assisted review]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=700</guid>
		<description><![CDATA[Last month we were among the first eDiscovery service providers to add Equivio&#8217;s Zoom to our service offerings. So far, it has been a fantastic augmentation to our ReviewSmart (Lighthouse&#8217;s proprietary Technology Assisted Review) product. Our internal experts, led by &#8230; <a href="http://blog.lheDiscovery.com/?p=700">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Last month we were among the first eDiscovery service providers to add Equivio&#8217;s Zoom to our service offerings. So far, it has been a fantastic augmentation to our ReviewSmart (Lighthouse&#8217;s proprietary Technology Assisted Review) product. Our internal experts, led by a lawyer with a Master of Science in Computational Linguistics, can leverage Zoom’s capabilities to dramatically reduce our clients’ review costs while maintaining defensibility. In fact, we are currently using it to reduce a client&#8217;s costs in a large multi-language matter.<span id="more-700"></span></p>
<p>For those of you not familiar with Zoom, it combines Equivio&#8217;s best-of-breed near-duplication, email threading and Relevance components with a robust data import and export function, as well as early case assessment capabilities and enriched analytics. These modules are seamlessly integrated on a unified web-based platform for easy access and use. The multi-faceted interface eliminates the need for moving data between applications, leading to shortened data handling cycles and reduced risk of errors.</p>
<p>Equivio was equally excited about our partnership. &#8220;Innovative e-discovery providers like Lighthouse have been quick to recognize the need for powerful predictive coding and analytics. It’s now clear that these analytical applications are the only effective way to cope with the continual growth in ESI volumes,” said Amir Milo, CEO of Equivio. “Equivio&#8217;s Zoom platform allows Lighthouse to reduce the risk and costs of discovery for<br />
its law firm and corporate clients.”</p>
<p>Check out the full <a href="http://lhediscovery.com/Lighthouse-News-2012-04-02.htm">press release </a>for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=700</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technology Assisted Review—The Great Equalizer</title>
		<link>http://blog.lheDiscovery.com/?p=689</link>
		<comments>http://blog.lheDiscovery.com/?p=689#comments</comments>
		<pubDate>Mon, 09 Apr 2012 15:00:02 +0000</pubDate>
		<dc:creator>Beau Holt</dc:creator>
				<category><![CDATA[Data Hosting and Review]]></category>
		<category><![CDATA[E-Discovery Software]]></category>
		<category><![CDATA[Flat Fee Pricing]]></category>
		<category><![CDATA[technology assisted review]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=689</guid>
		<description><![CDATA[With all the buzz about Technology Assisted Review (“TAR”) lately ( also known as predictive coding tools, such as ReviewSmart, Equivio’s Relevance and kCura’s Relativity Assisted Review), I noticed it’s often large companies and big law firms who are asking &#8230; <a href="http://blog.lheDiscovery.com/?p=689">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>With all the buzz about Technology Assisted Review (“TAR”) lately ( also known as predictive coding tools, such as ReviewSmart, Equivio’s Relevance and kCura’s Relativity Assisted Review), I noticed it’s often large companies and big law firms who are asking about it.  You may be saying, “well of course, they are the ones with the huge document productions.”  Small to medium size firms should take note &#8211; TAR can be an unbelievably useful tool for these firms, especially those who typically deal with multiple litigations in the 50k-150k document production range.  Why should small and medium firms pay attention to TAR?  Three big reasons:  time, capacity and price.<span id="more-689"></span></p>
<p><strong>Time </strong></p>
<p>Most small and medium firms don’t have a host of contract review attorneys available or an army of associates to press into document-review action.  With electronic data continuing to increase in volume at remarkable rates, even small cases can exceed 50k documents for review.  Medium size firms, much less, small firms or solo practitioners, are in danger of being overwhelmed or simply excluded from litigation involving document sets exceeding 50k documents because they don’t have the time or resources to review volumes of this size.  TAR can be a huge equalizer by reducing the eyes-on review total to less than 10k documents for cases involving document sets between 50k and 250k documents.  At 250k documents, a seed set of 1,500 documents and 4 validation rounds covering another roughly 6000 documents can reach the  95% confidence rating, with a  +/- 2.5% confidence interval.  Adding in another 2,500 documents from the non-responsive sample &#8211; to confirm the results of the machine coding &#8211; brings the total eyes-on review population to approximately 10k documents.  It’s true that additional review is likely necessary for privilege, confidentiality designations and issue coding, but with responsive rates often as low as 10% in linear or TAR reviews, this would add only another 20k documents to the eyes-on review population (assuming no use of privilege search terms or other technologies such as near-duplication or thread-suppression/identification).  And this was for the 250k document set…a 50k document set will require significantly less “eyes on” review, possibly less than 10k total documents.  Small to medium size firms and small businesses can manage a review volume of 20k-30k documents, especially if they have partnered with an e-discovery vendor that has significant TAR credentials and well-established TAR processes.</p>
<p><strong>Capacity</strong></p>
<p>Small to medium size firms who expect to handle only 1 matter a year totaling 50k+ documents may not need to spend the time and effort on TAR, but they should pause and ask themselves the following:</p>
<ul>
<li>Do they miss out on new clients or certain cases from existing clients because the perception is that a small or medium firm just can’t handle document intensive litigation?</li>
<li>Do they receive document productions exceeding 50k documents from opposing counsel?</li>
</ul>
<p>Small to medium size firms can take on cases or clients they might otherwise have to pass on by developing a working knowledge of TAR review workflows and best practices and becoming familiar with at least one of the platforms offering TAR.  As the small to medium size firms gain experience, knowledge and confidence in the TAR platforms, the tools and the available vendor-partners, they will be increasingly positioned and able to compete against much larger firms who doggedly hang on to the enormous billable hours associated with linear review (though clients are increasingly chafing at high linear review costs).</p>
<p>By incorporating TAR workflows and capabilities into their “litigation playbooks,” small to medium size firms can leverage their capacity in multiple ways.  How many times do small or medium firms face litigation where opposing counsel dumps huge volumes of supposedly “responsive” data on them?  Key word searches, file type analysis and other “traditional” solutions are often used to try to reduce things to a manageable size.  TAR offers a much more advanced and more capable solution, and is a truly low-risk option.  None of the current angst about whether courts will accept TAR or what level of transparency with the other side will be required.  There’s not likely to be procedure rules or case law dictating what confidence interval you have to use nor are you likely to be challenged by the other side about your use of TAR to organize documents you received from them.  If you can organize the materials along a handful of primary topics, you can use TAR to sift through large incoming productions from opposing counsel.</p>
<p>Adding TAR to your portfolio of tools can allow you to scale up without having to put all your available associates on month-long document reviews, hire temp review attorneys, or contract with review companies who are not as likely to offer “best” pricing to a small firm.</p>
<p><strong>Price</strong></p>
<p>TAR doesn’t make litigation cheap nor does it eliminate all review costs.  In fact, if not used correctly or if the small to medium firm works with the wrong e-discovery vendor, it can even result in higher review costs.  If you’re a small to medium firm and considering TAR (good for you if you are), ask the following questions:</p>
<ul>
<li>What pricing model are you using with your client?</li>
<li>What pricing model are you getting from your vendor?</li>
</ul>
<p>If the answer to these questions are “hourly” or “volume” or “volume plus hourly” (or  variations of volume based billing), I challenge you to consider other options such as flat fees, fixed fees or managed services agreements.  If your e-discovery vendor is unwilling to consider anything other than a volume based billing for TAR or other e-discovery work, a red flag should go up as TAR typically involves significant volumes of data.  Small to medium firms, through smart use of TAR and disciplined but flexible thinking on pricing models, can truly set themselves apart with existing and prospective clients.</p>
<p>How substantial a savings are we talking about?  Well, drawing on a recent experience, a client saved between $150k-$200k in review costs on a single document review through close consultation and use of TAR.</p>
<p><strong>THE GREAT EQUALIZER?</strong></p>
<p>I see TAR as one of the bigger potential game changers in litigation practices in my professional lifetime.  I started in the e-discovery industry 13+ years ago when Technology Assisted Review meant you could use Outlook to review PST files from your clients.  I spoke with many solo practitioners and small firms over the intervening 13 years and a common theme was that smaller firms and solo practitioners were the least equipped to deal with the explosion of ESI.  I believe TAR will eventually prove to be an extremely potent weapon in small to medium sized firms’ efforts to hold their own in the e-discovery arena.  What are you all seeing out there?  Any small to medium sized firms embracing TAR for their e-discovery needs?  I would love to hear from you about your experiences, questions and opinions with regard to TAR.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=689</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is Technology Assisted Review Dead?</title>
		<link>http://blog.lheDiscovery.com/?p=672</link>
		<comments>http://blog.lheDiscovery.com/?p=672#comments</comments>
		<pubDate>Tue, 03 Apr 2012 15:58:08 +0000</pubDate>
		<dc:creator>meisner</dc:creator>
				<category><![CDATA[Case Law]]></category>
		<category><![CDATA[Data Hosting and Review]]></category>
		<category><![CDATA[Da Silva Moore]]></category>
		<category><![CDATA[TAR]]></category>
		<category><![CDATA[predictive coding]]></category>
		<category><![CDATA[technology assisted review]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=672</guid>
		<description><![CDATA[Right on the heels of Judge Peck’s widely read and seemingly watershed ruling in Da Silva Moore is news that his ruling is being appealed.  Will a successful appeal mean the end of the using machine learning tools in e-discovery? &#8230; <a href="http://blog.lheDiscovery.com/?p=672">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Right on the heels of Judge Peck’s widely read and seemingly watershed ruling in <em>Da Silva Moore</em> is news that his ruling is being appealed.  Will a successful appeal mean the end of the using machine learning tools in e-discovery? While it is too early to tell whether the appeal will be successful, one thing does seem clear: even if the appeal is successful, it will not be a harbinger of the death of technology assisted review tools.<span id="more-672"></span></p>
<p>While the wave toward use of technology assisted review in e-discovery has certainly been building, there has been an undercurrent of reluctance until there has been clear judicial acceptance.  Judge Peck seemingly addressed this fact in an October 2011 Legal Technology News article, challenging litigants to cite that article as a sign of judicial approval, and then citing himself in the opening words of the <em>De Silva Moore </em>ruling.  In fact, it may be this rush to self-approve that ultimately causes the ruling to be overturned. However, the concepts that Judge Peck outlines in his opinion will survive and guide utilization of technology assisted review &#8211; regardless of the outcome of this case &#8211; and will lead eventually to wide judicial approval of the technology.</p>
<p>Judge Peck outlines several factors which can be influential in determining if technology assisted review is appropriate.  These factors include:</p>
<p>•         The volume of data</p>
<p>•         Proportionality under FRCP 26(b)(2)(C)</p>
<p>•         Having a well-designed, valid process implemented.</p>
<p>Even if Judge Peck’s ruling is overturned, these clearly delineated factors will likely persist, helping to move the ultimate acceptance of technology assisted review forward. A successful appeal of Judge Peck in <em>Da Silva Moore </em>is not the death of technology assisted review; <em>Da Silva Moore</em>’s principles will endure, and technology assisted review&#8217;s recognition as a valid and preferred review tool will continue.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=672</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Judge Peck’s Roadmap for Technology Assisted Review</title>
		<link>http://blog.lheDiscovery.com/?p=658</link>
		<comments>http://blog.lheDiscovery.com/?p=658#comments</comments>
		<pubDate>Wed, 29 Feb 2012 16:00:06 +0000</pubDate>
		<dc:creator>Nathaniel Byington</dc:creator>
				<category><![CDATA[Data Hosting and Review]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=658</guid>
		<description><![CDATA[Judge Peck&#8217;s recent opinion in Da Silva Moore highlights technology assisted review&#8217;s growing importance in the e-discovery toolkit, and offers a helpful roadmap for applying this process in future cases. In analyzing whether technology assisted review was appropriate in this &#8230; <a href="http://blog.lheDiscovery.com/?p=658">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Judge Peck&#8217;s recent opinion in Da Silva Moore highlights technology assisted review&#8217;s growing importance in the e-discovery toolkit, and offers a helpful roadmap for applying this process in future cases. </p>
<p>In analyzing whether technology assisted review was appropriate in this case, Judge Peck relied on scientific research and previous opinions to show the superiority of technology assisted review to alternatives like keyword searching and linear manual review. In fact, he challenged those who object to technology assisted review to come up with a better methodology. <span id="more-658"></span></p>
<p>One of my favorite aspects of this opinion is Judge Peck&#8217;s focus on process. Like everything else in e-discovery, the process surrounding technology assisted review is just as important as the underlying technology. Judge Peck explicitly recognizes this, writing that &#8220;&#8230;it is not a case of machine replacing humans: it is the process used and the interaction of man and machine that the court needs to examine.&#8221; </p>
<p>With process in mind, he describes how the parties constructed the seed set to train the system, how they used iterative review rounds to validate the system, and how they agreed to use statistical sampling to QC the results of the system&#8217;s classification. These details provide a helpful roadmap for successful use of technology assisted review.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=658</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lighthouse Launches New Brand, New Products For 2012</title>
		<link>http://blog.lheDiscovery.com/?p=651</link>
		<comments>http://blog.lheDiscovery.com/?p=651#comments</comments>
		<pubDate>Fri, 03 Feb 2012 16:00:00 +0000</pubDate>
		<dc:creator>Debora Motyka Jones</dc:creator>
				<category><![CDATA[Company News]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=651</guid>
		<description><![CDATA[After 16 years, Lighthouse Document Technologies will now be called Lighthouse eDiscovery. The updated brand also introduces the SmartSeries of services – a set of services designed to leverage technologies and expertise to eliminate up to half of a client’s &#8230; <a href="http://blog.lheDiscovery.com/?p=651">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>After 16 years, Lighthouse Document Technologies will now be called Lighthouse eDiscovery. The updated brand also introduces the SmartSeries of services – a set of services designed to leverage technologies and expertise to eliminate up to half of a client’s spend on eDiscovery.</p>
<p>“The updating of the Lighthouse brand is the culmination of months of work focused on the development of innovative solutions for our clients,” said Brian McManus, Lighthouse’s Managing Partner. “The industry is moving quickly to address the need to reduce the mountain of data being created by corporations to a manageable level for eDiscovery. The best innovations will be those that attack the most expensive and time-consuming aspects of the discovery process. The Lighthouse SmartSeries represent a large step forward in addressing this issue.”</p>
<p>Check out the new site: <a href="http://www.lhediscovery.com">www.lhediscovery.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=651</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technology Assisted Review: Five Tips on Getting the Most Out of TAR</title>
		<link>http://blog.lheDiscovery.com/?p=502</link>
		<comments>http://blog.lheDiscovery.com/?p=502#comments</comments>
		<pubDate>Fri, 27 Jan 2012 16:14:35 +0000</pubDate>
		<dc:creator>Nathaniel Byington</dc:creator>
				<category><![CDATA[Data Hosting and Review]]></category>
		<category><![CDATA[document review]]></category>
		<category><![CDATA[predictive coding]]></category>
		<category><![CDATA[technology assisted review]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=502</guid>
		<description><![CDATA[Although Technology Assisted Review (“TAR”) has been discussed at length over the last 14 months, many folks are still just getting started with the technology.  As a computational linguist with an eDiscovery background, I thought I would share my top &#8230; <a href="http://blog.lheDiscovery.com/?p=502">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Although Technology Assisted Review (“TAR”) has been discussed at length over the last 14 months, many folks are still just getting started with the technology.  As a computational linguist with an eDiscovery background, I thought I would share my top five tips on getting the most out of technology-assisted review.<span id="more-502"></span></p>
<p><strong>Tip #1. Know the Technology</strong></p>
<p>Having access to sophisticated review features won’t do you any good unless you understand how to use them. This was true for the previous generation of eDiscovery tools, and it’s even more critical with TAR. TAR software relies on behind-the-scenes statistical algorithms to evaluate and classify documents. Don’t worry, you don’t need to know these algorithms to use the software, but you do need a detailed understanding of the software’s options as well as the consequences of choosing those options. If you don’t have the time to develop this expertise yourself, it’s important to work with service<br />
providers who already have it.</p>
<h1><strong>Tip #2. Identify Good Training Documents</strong></h1>
<p>Before a TAR system can start classifying documents as responsive or non-responsive, it needs to be trained with human-selected sample documents. Choosing the right training documents increases the efficiency of the TAR process, so it’s worth some extra effort at the beginning of a project.</p>
<p>A good training document should fall within the proper date range, and should be clearly responsive on its face. If its responsiveness only comes from a broader context outside of the document, the training won’t work as well – computers haven’t yet mastered the art of implication. Try to find sample documents for each request or issue, but don’t be worried if you don’t have complete coverage at the start. TAR is an iterative process (as explained in Tip #3), so additional issues and sub-issues will be fleshed out over the<br />
course of review.</p>
<h1><strong>Tip #3. Take Advantage of the Knowledge Feedback-Loop</strong></h1>
<p>The iterative nature of TAR is like a continuing dialog between you and the computer, with each exchange adding to the accumulation of knowledge. The TAR system uses your initial training documents to find a batch of statistically significant documents for you to review. Your responsiveness choices on this batch will allow the system to find even more significant documents for you to review. This back-and-forth dialog continues until the system has classified the entire data set at an accuracy level acceptable to you. At each iteration you learn more about the documents, and this knowledge gets passed back to the system, rippling throughout the data set. The more you know, the better the system performs. The better the system performs, the more you know. It’s a beautiful thing.</p>
<p>This knowledge feedback-loop is one of TAR’s major advantages over manual review. Manual review is a linear process: reviewers work their way through batches of documents, learning more as they go, so by the end of review they have a fairly complete knowledge of the case. But this knowledge can’t be applied back to the documents they’ve already reviewed without a re-review of the entire data set, something prohibitively expensive in most circumstances. In contrast, by the end of the TAR process, both you and the system have a detailed knowledge of the documents, and it’s this detailed knowledge that gets applied automatically across the entire set of documents.</p>
<h1><strong>Tip #4. Log Everything</strong></h1>
<p>Two other big advantages TAR has over traditional review methods are repeatability and transparency. A TAR system is deterministic – if you feed it the same data, you get back the same output every time. Humans, on the other hand, are notoriously non-deterministic (which can be magical in some arenas, but not in document review). With TAR, every step of the process can be explained, defended, and repeated if necessary.</p>
<p>To take full advantage of TAR’s repeatability and transparency, you must ensure that a record of every step is recorded. Any good TAR system will have some sort of logging or audit functionality, but as I mentioned in Tip #1, this functionality won’t add value unless you know what it does and how to use it.</p>
<h1><strong>Tip #5. Post-Review Evaluation</strong></h1>
<p>A successful technology-assisted review depends upon three things: technology, human expertise, and a well-planned workflow. Unless you’re a software developer, the technology is outside of your control, so that means you’ll need to focus your efforts on improving expertise and workflow. Post-review evaluations are one of the best ways to do this.</p>
<p>After a review project is complete and you’ve had a few days to celebrate (and catch up on your sleep), it’s important to analyze the project while the details are still fresh in your mind. You’ll want to look for the things that went well and the things that didn’t. Was there an unexpected choke-point in the workflow? Do some of your team members need additional training? Answering these kinds of questions after every project leads to<br />
continual improvement, maximizing the effectiveness and efficiency of TAR.</p>
<p>I’d love to hear your TAR stories.  What would you tell new users to look out for before beginning a TAR project?  Leave a comment or email me to discuss.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=502</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Should Corporations Demand from eDiscovery Providers in 2012?</title>
		<link>http://blog.lheDiscovery.com/?p=544</link>
		<comments>http://blog.lheDiscovery.com/?p=544#comments</comments>
		<pubDate>Wed, 11 Jan 2012 00:16:03 +0000</pubDate>
		<dc:creator>Debora Motyka Jones</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=544</guid>
		<description><![CDATA[Many January blog postings focus on the 2012 predictions.  Rather than further opining on what several brilliant writers (here, here, and here) have already discussed—I thought I would skip the predictions this year.  I’m not sure that clairvoyance is my &#8230; <a href="http://blog.lheDiscovery.com/?p=544">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Many January blog postings focus on the 2012 predictions.  Rather than further opining<br />
on what several brilliant writers (<a href="http://www.clearwellsystems.com/e-discovery-blog/2011/12/08/top-ten-ediscovery-predictions-for-2012/">here, here</a>, and <a href="http://www.ediscoverydaily.com/2012/01/ediscovery-trends-2012-predictions-by-the-numbers.html">here</a>) have already discussed—I thought I would skip the predictions this year.  I’m not sure that clairvoyance is my strongest skill anyway.</p>
<p>Instead, this blog will focus on what clients should demand from their service providers in 2012.<span id="more-544"></span></p>
<h1><strong>Demand #1:  A Technology Assisted Review Differentiator.</strong></h1>
<div>We know almost all service providers have some sort of Technology Assisted Review offering.  And, clients generally understand what it does (that’s what 2011 was all about).  <a href="http://www.law.com/jsp/lawtechnologynews/PubArticleLTN.jsp?id=1202518919552&amp;slreturn=1">Judges are even starting to accept it</a>. But, to use the technology to its maximum capacity and in a defensible manner, service providers need to be true experts who fully understand the technology and the best process for implementing it.  For example, service providers need to know how to select appropriate training documents (because<br />
not all training sets are created equal).  It also helps to have computational linguists on staff to expertly train the computer on the nuances of the case (the devil is always in the details).</div>
<p><em>In 2012, clients should focus on the differences between service providers’ offerings and ask questions like</em></p>
<ul>
<li><em>What makes your TAR offering different?</em></li>
<li><em>How are you a qualified TAR expert?</em></li>
</ul>
<h1><strong>Demand #2:  An eDiscovery playbook.</strong></h1>
<p>Understandably, corporate counsel use different law firms for different types of cases—they want to top legal experts in a certain area of law.  This model doesn’t make a lot of sense in eDiscovery.</p>
<p>eDiscovery providers have eDiscovery expertise, that expertise doesn’t become obsolete when the subject matter of a case changes.  To the contrary, there are efficiencies to be had streamlining your eDiscovery and using one provider.  For example, it allows corporations to take advantage of volume discounts and to reuse data from case to case.  <em>In 2012, corporations should work with their vendors to create an eDiscovery playbook containing their streamlined repeatable eDiscovery workflow.</em></p>
<h1><strong>Demand #3:  Reuse of their data.</strong></h1>
<p>These days, even occasional litigants have data that is relevant to multiple cases.  And,<br />
there is no sense in paying to process, review and image the data twice if you don’t have to.  As my colleague, Chris Dahl, <a title="Same Data, Multiple Cases:  The Trouble with Data Reuse" href="http://blog.lheDiscovery.com/?p=495">points out</a>, there are some complications with reusing the data.  However, a smart service provider can figure out a way to do it.  <em>Clients should demand this service in 2012.</em></p>
<h1><strong>Demand #4:  Flat fees.</strong></h1>
<p>Much as the heyday of the hourly law firm rate has passed, so too has the height of the per GB service provider model.  These per unit models both still have their appropriate use but the shift has to be toward a more predictable model.  Data sizes are skyrocketing and nobody has the stomach for high and unpredictable litigation costs. Thus, clients should be demanding flat fee arrangements.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=544</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Same Data, Multiple Cases:  The Trouble with Data Reuse</title>
		<link>http://blog.lheDiscovery.com/?p=495</link>
		<comments>http://blog.lheDiscovery.com/?p=495#comments</comments>
		<pubDate>Mon, 02 Jan 2012 18:41:28 +0000</pubDate>
		<dc:creator>Chris Dahl</dc:creator>
				<category><![CDATA[Data Preservation and Litigation Holds]]></category>
		<category><![CDATA[E-Discovery Software]]></category>
		<category><![CDATA[Electronic Data Processing]]></category>
		<category><![CDATA[ReDiscovery]]></category>
		<category><![CDATA[litigation repository]]></category>
		<category><![CDATA[reuse data]]></category>
		<category><![CDATA[save money]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=495</guid>
		<description><![CDATA[Why Would I Reuse Data? Simply put—to save money. Reusing attorney decisions and other work across cases can lead to huge cost savings for corporations.  The three biggest cost savings involve leveraging privilege decisions, leveraging responsiveness decisions, and reusing production &#8230; <a href="http://blog.lheDiscovery.com/?p=495">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<h1><strong>Why Would I Reuse Data?</strong></h1>
<p><strong><em>Simply put—to save money.</em></strong> Reusing attorney decisions and other work across cases can lead to huge cost savings for corporations.  The three biggest cost savings involve leveraging privilege decisions, leveraging responsiveness decisions, and reusing production images. I will explain each in turn.<span id="more-495"></span></p>
<p>Leveraging privilege decisions carries the most savings potential.  When a law firm makes a privilege claim on a document for one case, that privilege claim should carry<br />
through to all cases.  Conversely, when a law firm reviews a document for privilege and produces it, deciding that the document is not privileged, generally, there should be no privilege claim for the document in other cases.  Thus, leveraging a document’s privilege review history from prior cases eliminates the need for another privilege review in the current case.  This saves corporations the time and money associated with the most expensive and slowest type of review—privilege review.</p>
<p>Other potential time and money savings opportunities arise in cases that have similar substance, for example, a series of cases in numerous jurisdictions regarding similar claims, or investigations regarding the same regulated subject matter.  Carrying from case to case decisions based on subject matter can either eliminate subsequent review, or provide context for subsequent review which can help lawyers arrive to review decisions more quickly.</p>
<p>Another potential savings lies with production images.  Linking documents between  cases allows an eDiscovery service provider to leverage imaging work between cases.  Because each document only needs to be imaged one time, corporations can see large reductions in imaging time and costs.</p>
<h1><strong>Sounds Easy, What’s the Catch?</strong></h1>
<p>In order to leverage work across cases, the data and the decisions about the data (i.e. work product) have to be in the same place.  In today’s eDiscovery market, this poses a<br />
challenge: no eDiscovery software handles the full end-to-end eDiscovery lifecycle, and no eDiscovery software handles a portfolio of cases on a client level (or at least no eDiscovery software handles these things well).  Tracking the work done across various tools, which don’t speak the same language, can be very difficult and time consuming.</p>
<p>This issue is often compounded when large corporations do not have a preferred  eDiscovery service provider.  Corporations often have many law firms managing their litigation portfolios and allow each law firm to manage processing, review, and production.  In that model, it is nearly impossible to leverage decisions across cases with documents scattered across many different law firms, service providers, and, consequently, eDiscovery processing tools.</p>
<h1><strong>So How Do I Leverage Data Across Multiple Cases?</strong></h1>
<p><strong><em>Get organized.</em></strong> Streamline your eDiscovery by developing a repeatable workflow and asking all your outside counsel to follow that workflow.   Work with your outside counsel and eDiscovery service provider(s) to determine what that workflow should be.</p>
<p><strong><em>Partner with someone with expertise.</em></strong> Sophisticated eDiscovery service providers create and utilize proprietary software to solve these problems.  This software links documents between various third party eDiscovery tools and enhances the current leading eDiscovery tools.  In addition, this proprietary software is platform-agnostic so it can adapt to new technology—a necessary characteristic in this constantly changing eDiscovery landscape.  A seamless integration between tools allows for clients to benefit from the latest and greatest eDiscovery software, and lays the groundwork for creating workflows and structure across cases.</p>
<p>Corporations which contract directly with a preferred eDiscovery service provider are in a much better place to leverage valuable decisions and processing work across cases.<br />
A single service provider can work with a corporation to create structure and workflows across the entire litigation portfolio, positioning the corporation for a successful and more efficient discovery period on every case.</p>
<p>I’d love to hear about your experiences with reusing data across cases.  Please leave a comment or contact me to hear more about how Lighthouse is attacking these challenges today.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=495</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Privilege and Confidentiality in the Electronic Age—Three Traps to Avoid Waiver of Privilege</title>
		<link>http://blog.lheDiscovery.com/?p=480</link>
		<comments>http://blog.lheDiscovery.com/?p=480#comments</comments>
		<pubDate>Thu, 15 Dec 2011 17:19:05 +0000</pubDate>
		<dc:creator>Beau Holt</dc:creator>
				<category><![CDATA[Case Law]]></category>
		<category><![CDATA[case law]]></category>
		<category><![CDATA[privilege]]></category>
		<category><![CDATA[waiver]]></category>

		<guid isPermaLink="false">http://blog.lheDiscovery.com/?p=480</guid>
		<description><![CDATA[Attorney client and work product privileges became much more complicated in the electronic age.  Not only was there significantly more data to review to determine whether privilege existed, but there were also a plethora of new ways to communicate—emails, text, &#8230; <a href="http://blog.lheDiscovery.com/?p=480">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Attorney client and work product privileges became much more complicated in the electronic age.  Not only was there significantly more data to review to determine whether privilege existed, but there were also a plethora of new ways to communicate—emails, text, social media, etc.  These “new” issues raised by the electronic age caused heartburn for many lawyers.  Following adoption of Federal Rule of Evidence 502, which expanded the protection provided by claw-back provisions, many lawyers breathed a sigh of relief, thinking they had a safety net that would allow them to avoid waiver issues associated with production of electronic data.  While it’s true that the claw-back protections, expanded in scope in Federal Rule of Evidence 502, afford greater protection against inadvertent waiver, there are other traps awaiting the “information age” attorneys.<span id="more-480"></span></p>
<div><strong>Trap 1: Work Email and Employer’s Electronic Communication Policies</strong></div>
<p>Given the explosion of email usage in the last 10 years, it’s become commonplace to send and receive personal email from business email accounts.  However, when you combine this with the widespread adoption of “employee electronic communications policies” (those pesky notifications along the lines of “all info placed on or set over this<br />
system may be monitored”), you can easily slip down the slope of privilege waiver due to failing the “made in confidence” requirement of attorney-client<br />
privilege claims.  The courts in <em>Alamar Ranch, LLC v. City of Boise</em> and <em>Holmes v. Petrovich Dev. Co., LLC<a href="#_ftn1">[1]</a> </em>ruled that communications between an attorney and client using the client’s employer-provided email system or via a company-issued computer were not protected by the attorney-client privilege because the person sending the email had no expectation of privacy/confidence.  Specifically, the regular electronic notifications to the employee regarding the employer’s electronic communication policies removed any expectation of privacy on the employee’s part.</p>
<div><strong>Trap 2: Accessing Personal Email Accounts on Employer Systems</strong></div>
<p>The courts have taken a similar stand where employees use or access web-based personal email accounts on employer computers or across employer systems to communicate with their attorneys.  In <em>Stengart v. Loving Care Agency<a href="#_ftn2">[2]</a><br />
</em>(a discrimination suit),<strong> </strong>the plaintiff (an employee) discussed the lawsuit with her attorney using a personal web-based email account on her work computer.  The trial court found that the emails were not covered by the attorney-client privilege because the employer’s electronic communications policy stated that the emails would be viewed as company<br />
property.  Although the trial court’s ruling was overturned on appeal, the lower court’s ruling was a warning shot across the bow to all attorneys regarding how, when and where you communicate with your clients.</p>
<div><strong>Trap 3: Loose Lips (and Laptops) Sink Ships</strong></div>
<p>The most obvious trap of the three is also the most prevalent.  How many of us use cell phones, smart phones or laptops in public places such as commuter trains, airplanes, on the street, in coffee shops, malls or even the public lobby of your office-building?  More than one attorney has fallen victim to talking about confidential information in a public location or having a “privileged email or memo” read by a seat-neighbor on a plane.  The experience of a Pillsbury partner’s discussion of layoffs within the firm on a commuter train in 2009 is famous enough to merit a mention on Wikipedia, Above the Law and the other legal blogs (if you’ve not heard of it, just run a search for “Pillsbury 2009 layoffs”).  Although not rising to the level of attorney-client privilege in the Pillsbury incident, how many of us have communicated with a client over a cell phone in a public location?  Are you sure you never discussed attorney-client confidences where<br />
members of the public could overhear details of the conversation?</p>
<p>Before you relax, having assured yourself that you never crossed that line, consider the following story.  I recently flew down to California on business.  During the flight, while working on my laptop, I noticed that the person sitting across the aisle from me was working on his laptop.  A few glances during the first half of the flight alerted me to the fact that he was an employee of one of my clients.  Fortunately, I had not been working on confidential materials on my laptop, but it was a tangible reminder of the potential for damaging a client or your relationship with the client by failing to consider your surroundings when working on confidential information.</p>
<div><strong>Constant Vigilance and Discretion Pay Off</strong></div>
<p>Remembering these three tips can save you from embarrassing and potentially costly discovery-related mistakes.</p>
<ul>
<li>Unless absolutely necessary, don’t email your non-corporate clients at their work email address or at least remember not to discuss attorney-client privileged information.</li>
<li>Remind your clients not to view or send emails containing privileged information via their personal email accounts on work computers.</li>
<li>Finally, be aware of your surroundings when conducting business in public places.  If in doubt don’t say it or write it where others can hear it or read it.</li>
</ul>
<div>
<hr size="1" />
<p><a href="#_ftnref1">[1]</a> <em>Alamar </em><em>Ranch, LLC v. City of Boise</em><em>,</em> 2009 WL 3669741 (D. Idaho Nov. 2, 2009)</p>
</div>
<div>
<div><a href="#_ftnref2">[2]</a> <em>Stengart v. Loving Care Agency</em>, 201 N.J.300, 990 A.2d 650<em> </em>(N.J. 2010)</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.lheDiscovery.com/?feed=rss2&#038;p=480</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

