- eLessons Learned
- Press and Publicity
- About Our Team
- Contact eLL Blog
Arthur Lawrence’s attorneys must have thought that he had struck gold because among the 15,000 documents turned over as discovery from Dependable Medical Transportation Services, LLC, there were a number of e-mails between the Dependable Medical and their attorney. Lawrence immediately jumped at the opportunity to use these e-mails to his advantage. The e-mails were the Holy Grail, the promised land; they would surely bolster his case against the defendant and they might even give him the leverage to win a motion for partial summary judgment. Without a moment’s hesitation, Lawrence filed that motion for partial summary judgment; however, he was in for a rude awakening. The surprising part of this story is the fact that Lawrence was represented by counsel. He had retained the Phillips Deyes Law Group to represent him in this matter. Therefore, the ignorance of the court rules when dealing with such a matter is inexcusable; these attorneys should have known that not following the proper procedure in such a matter would result in an impending detriment to their client. When the defendant learned that the plaintiff had these e-mails in their possession they requested that they be returned in accordance with Arizona Rule of Professional Conduct 4.4 which provides that "[a] lawyer who receives a document and knows or reasonably should know that the document was inadvertently sent shall promptly notify the sender and preserve the status quo for a reasonable period of time in order to permit the sender to take protective measures." Further the comment on this rule state, [i]f a lawyer knows or reasonably should know that a document was sent inadvertently, then this Rule requires the lawyer to stop reading the document, to make no use of the document, and to promptly notify the sender in order to permit that person to take protective measures." Nevertheless, the plaintiff ignored this rule and the defendant’s requests, did not return the documents, and utilized the e-mails in their motion for partial summary judgment. This was a mistake, which would ultimately cost them any chance to use the e-mails at all. In their ruling denying the motion for partial summary judgment, the court referenced a rule that the plaintiff’s should have already known Rule 26(b)(5)(B). The court stated, "The requirements in Rule 26(b)(5)(B) are straight forward. Once a party is notified that a claim of privilege is being made, the party must either return or destroy the document or the party may turn the document over to the court for determination of the claim." Piasa Commercial Interiors, Inc. v. J.P. Murray Co., 2010 WL 1241563 *2 (S.D. Ill. Mar. 23, 2010). Therefore, since the plaintiffs had not followed the rule they not only lost their motion, but also lost any chance to argue tor their right to use the e-mails in any capacity. A.S. Mitchell received his B.A. in Political Science from the University of Central Florida (2008). He will receive his J.D. from Seton Hall University School of Law in 2015. Want to read more articles like this? Sign up for our post notification newsletter, here.
A party has been burdened with manually reviewing 565,000 potentially relevant documents for search term hits. This manual method of review was agreed on by both parties and memorialized in a court order at the start. Shortly into the review process, the plaintiff realized this method would be costly and time consuming, and took it upon themselves to apply a predictive coding method using the agreed upon search terms. They then moved before the court to be able to use these predictive coding techniques, and not human manual review, to review the documents. The plaintiff argued that the modification to predictive coding should be utilized because it would achieve a more accurate measure of relevant documents, in addition to saving time and money. The defendant argued the opposite, believing that the predictive coding protocol was complicated and had various other issues involved. They argued that other courts, which have allowed predictive coding, have stressed the need for transparent and cooperative behavior by all parties, a manner of which plaintiff in this case has not acted. They even went as far as to say that the predictive coding protocol utilized by the plaintiffs did not comply with the “best practices” for the chosen software. The court, although in support of predictive coding, ordered the plaintiff to produce all documents in the agreed upon manner (Human review wins!). “If the parties had worked with their E-discovery consultants and agreed at the onset of this case to a predictive coding based ESI protocol, the court would not hesitate to approve a transparent mutually agreed upon ESI protocol.” But here, their hands were tied by the earlier court order. The court also stated that, and agreeing with the defendant’s argument, predictive coding requires a heightened degree of transparent cooperation among parties. “In the few cases that have approved technology assisted review of ESI, courts have consistently required the producing parties to provide the requesting parties with full disclosures about the technology being used, processes, methodology and documents used to “train” computers.” Here, the court found that the Plaintiff has been unwilling to engage in the level of transparency necessary, which they believed would “only result in more disputes and delays.” TAKEAWAY: The parties, especially the moving party, should have prepared a electronic discovery strategy from the beginning, as the main problem here was that the plaintiff sought to modify an already agreed upon order and the court thought it was too late in the game. Additionally, the parties must be open and transparent about the methodology being used with the technology if predictive coding is the agreed upon ESI method. Amanda is a third-year student at Seton Hall University School of Law, where she is pursuing a J.D. with a certificate in Health Law. Prior to law school, she was a 2011 magna cum laude graduate of Seton Hall University, where she earned Bachelor of Arts in Political Science and a minor in Philosophy. Presently, she is a law clerk at a small firm handling real estate and bankruptcy matters. After graduation this native New Yorker hopes to work at a mid-sized firm in the Big Apple. Want to read more articles like this? Sign up for our post notification newsletter, here.
This case involves ACT, a career guidance service firm that assists job seekers throughout their job search, suing Daniel Drasin, the administrator of a blog known as Random Convergence. According to ACT, Drasin exercises editorial control over the blog. ACT complains that the blog disparage ACT's services and damages ACT's business and reputation. On March 11, 2013, Magistrate Judge Kristin Mix granted ACT's motion to serve third party subpoenas on Drasin, demanding that he produce the name and contact information for each of the people who posted disparaging remarks on Drasin’s blog. On April 18, 2013, Drasin, then self-represented, filed a third-party motion to quash the subpoenas, stating that they violated the bloggers’ rights to First Amendment right to anonymous speech. He also argued that most individuals who posted comments on the Blog did so anonymously, and he explained that he had no records of those who chose to remain anonymous. The court sided with Drasin and quashed the subpoena. The court found that the Subpoena imposes two types of burden on Drasin. First, in order to comply with the subpoena, Drasin must surrender his personal hard drives to ACT for up to thirty days. Personal computers generally cannot function without their hard drives, so this requirement would force Drasin to spend up to thirty days without the use of his personal computer. Second, forcing Drasin to surrender his hard drives to ACT would give ACT access to Drasin's personal files. Moreover, ACT has alternative means to obtain the information it seeks, such as serving a subpoena on Google. The court also found persuasive that the benefits of the Subpoena appear to be minimal, as there is no indication in the record that Drasin possesses any information that would be relevant in the Colorado Action beyond that which he has already provided. The takeaway message is that subpoenas can be quashed if discovery imposes an undue burden, if the information is irrelevant to the action, and if there are other avenues from which the information can be obtained. Rebecca Hsu, a Seton Hall University School of Law student (Class of 2015), focuses her studies in the area of Patent Law, with a concentration in Intellectual Property. She is also certified in Healthcare Compliance, and has worked in Compliance at Otsuka America Pharmaceuticals, Inc. Prior to law school, she graduated cum laude from UCLA and completed graduate work in Biomedical Science. She has co-authored two medical science research articles, as well as completed fellowships through UCLA Medicine and the Medical College of Wisconsin. In addition to awards for her academic achievements, Rebecca has been honored by awards for her community service with disadvantaged communities. In her spare time, Rebecca regularly practices outdoor rock climbing, and can be found camping in the Adirondacks. Want to read more articles like this? Sign up for our post notification newsletter, here
Executive Mgmt. Services, Inc. v. Fifth Third Bank is not a riveting case to read. It involves a rather mundane breach of contract claim by the plaintiff alleging wrongdoing by the defendant. Namely, Executive Management Services brought suit against Fifth Third Bank alleging that the bank had made misleading statements regarding interest-rate swaps. While the subject matter of the claim would fail to interest anyone, the procedural elements and motion practice offer a far more interesting and educational prospect. In building their defense, Fifth Third Bank sent Executive Management Services multiple discovery requests, which included tax returns, financial statements, and documents referring or relating to their (EMS) loan applications. However, Executive Management Services refused to produce the requested discovery on three grounds. First, EMS argued that the requested as they have "not claimed to be unsophisticated regarding standard commercial banking," only that they "did not understand the risks of the swap transactions." Second, the EMS argued that the defendant’s discovery requests were "overly board and unduly burdensome." Third, EMS claimed privilege regarding the requested documents under both attorney-client privilege and the work product doctrine. The court rejected EMS’s first argument right out of the gate. EMS claimed that the documents sought were not relevant to the issue at bar and therefore did not need to be turned over to their adversary. EMS claimed these documents were irrelevant because they had "not claimed to be unsophisticated regarding standard commercial banking," but rather that "did not understand the risks of the swap transactions." However, the court was not persuaded by this argument because even though this was a new area of investment banking, it remained the same procedure and protocol as any form of investment banking. Therefore, EMS’s past actions in commercial banking provided them with a foundation by which to understand this new field of investment and thus the documents proving this foundation were relevant. The court also rejected EMS’s argument that the documents were privileged under attorney-client privilege and the work product doctrine. While there may have been concerns regarding the confidentiality of these documents the court stated that the protective order in place addressed and negated all of the concerns posed by this argument. EMS’s second argument seems like it could have had the most impact out of the three; however, hardly any effort at all was put forth in crafting it. The plaintiffs simply stated that the production of such documents was unduly burdensome and overbroad and left it at that. There was no further development of this argument and therefore the court rejected it on its face. If the plaintiffs had put forth any evidence regarding why the request was overbroad or unduly burdensome the court may have limited the requested discovery. The plaintiffs should have offered evidence regarding why this request was unduly burdensome and overbroad; their failure to do so resulted in the court rejecting this argument on its face. A.S. Mitchell received his B.A. in Political Science from the University of Central Florida (2008). He will receive his J.D. from Seton Hall University School of Law in 2015. Want to read more articles like this? Sign up for our post notification newsletter, here.
The District Court for Massachusetts held that “the use of broad terms such as ‘relate to’ or ‘relating to’ provides no basis upon which an individual or entity can reasonably determine what documents may or may not be responsive.” In doing so, the court ordered the defendants to produce documents responsive to a request and that request calls for documents “related to” a topic, the court modified the requests to strike the language “related to” and replacing it with “concerning.” This holding comes in response to the plaintiff’s Motion to Compel defendants Reposes to Document Requests and Production of all documents. The plaintiff in this case is the previous employer of the two defendants, husband and wife. The defendants were both employed by the plaintiff in different sectors for several years. The company now disputes that trade secrets developed by both parties were the sole property of them. Keep in mind, one of the defendants now works with a competitor company, so you can see the importance of these trade secrets. The plaintiffs brought claims alleging violation of the Computer Fraud and Abuse Act (“CFAA”), conversion, misappropriation of trade secrets, and breach of fiduciary duty. Soon thereafter, the defendants offered responses to the first set of Requests for Document Production. In summary, there are limits to the scope of discovery under Rule 26(b). They are: (1) unreasonably cumulative or duplicative, or is obtainable from some other source that is more convenient, less burdensome, or less expensive; (2) the party seeking discovery has had ample opportunity by discovery in the action to obtain the information sought; or (3) the burden or expense of the proposed discovery outweighs its likely benefit, taking into account the needs of the case, the amount in controversy, the parties’ resources, the importance of the issues at stake in the litigation, and the importance of the projected discovery in resolving the issues. See Fed. R. Civ. P. 26(b)(2)(C). The defendant former employees objected to discovery on the grounds that the requests were overly broad and unduly burdensome. The court agreed in the finding that the requests were overly broad, specifically because they call for documents “related to” a topic. Use of the word “concerning” would be the correct qualifying language. To see video of the morning session at court on this case, click here. Amanda is a third-year student at Seton Hall University School of Law, where she is pursuing a J.D. with a certificate in Health Law. Prior to law school, she was a 2011 magna cum laude graduate of Seton Hall University, where she earned Bachelor of Arts in Political Science and a minor in Philosophy. Presently, she is a law clerk at a small firm handling real estate and bankruptcy matters. After graduation this native New Yorker hopes to work at a mid-sized firm in the Big Apple. Want to read more articles like this? Sign up for our post notification newsletter, here.
Last spring the District Court for the District of Colorado heard argument on Galena St. Fund, LP v. Wells Fargo Bank, N.A. Plaintiff Galena specifically appealed to the court to compel discovery with respect to 8,327 documents that defendant Wells Fargo claimed were privileged. Magistrate Judge Boyd N. Boland was asked to consider whether Wells Fargo was allowed to claim privilege from trust beneficiaries, or in the alternative, if Wells Fargo waived the attorney-client privilege in its entirety. Plaintiff’s motion consisted of the kitchen-sink brief: first, Wells Fargo could claim no privilege exists to prevent disclosure of records to a beneficiary of a trust; second, when Wells Fargo named a non-party at fault, they effectively waived privilege by making the documents at-issue in the case; third, Wells Fargo waived privilege by having an overbroad privilege log; and fourth, Wells Fargo waived simply by inadvertently disclosing during the course of discovery. In short, Judge Boland was not convinced. Only one exhibit in the universe of disclosure was deemed to be a waiver of privilege, based on the at-issue waiver rule. That document was an email chain discussing defendant’s non-party claim and deciding how to remit proceeds from federally insured RMBS loans. The court recognized that Wells Fargo “cannot use the attorney-client privilege as a shield to hide communications that indicate that Wells Fargo directed [the non-party] on how to remit those proceeds.” Galena, 2014 WL 943115 at *12-13. Unfortunately for Galena, that was the only point for plaintiffs on the scoreboard. The court went on to explain that Wells Fargo’s contact with outside counsel did not waive privilege for Galena as a beneficiary of the trust, essentially because Wells Fargo’s reaching out to outside counsel was inspired by Galena’s threat of litigation. Furthermore, Judge Boland did not find defendants assertion of privilege to be overbroad, and recognized that inadvertent disclosure does not waive privilege in any meaningful sense. Rule 26 of the Federal Rules of Civil Procedure works in conjunction with Rule 502 of the Federal Rules of Evidence to provide a solution to this very situation. So long as the disclosure was truly inadvertent and the holder of the privilege took reasonable steps to remedy the problem, privilege is still maintained. In this situation, the “burden of showing that the privilege has not been waived remains with the party claiming the privilege.” Silverstein v. Federal Bureau of Prisons, 2009 WL 4949959 *10 (D. Colo. Dec. 14, 2009). In the other situations in which the court analyzed potential waiver here, the burden of establishing a waiver of the attorney-client privilege “rests with the party seeking to overcome the privilege.” People v. Madera, 112 P.3d 688, 690 (Colo. 2005). Galena couldn’t possibly meet that burden, for all 8,327 documents. Hopefully, Galena’s counsel can make some hay with the one record in which privilege was waived. Kevin received a B.S. in Political Science from the University of Scranton (2009), and will receive his J.D. from Seton Hall University School of Law in 2015. Prior to joining the Seton Hall community, Kevin worked as an eDiscovery professional at two large “white-shoe” law firms in Manhattan. Want to read more articles like this? Sign up for our post notification newsletter, here.
Why is clawing back digital data any more dangerous than clawing back physical documents? Imagine making physical copies of one thousand documents. That would take a long time, right? Now, imagine making digital copies of the same one thousand documents. This takes a fraction of the time. Giving up too much information in a digital form is incredibly dangerous because duplicating the data is as simple as “copy” and “paste.” In the case of Crissen v. Gupta, the party producing documents gave the receiving party a CD with all the documents requested; however, they mistakenly included over 600 pages of documents that were not supposed to be produced. Thankfully, for the producing party, a protective order was in place which mandated that documents could be “clawed back” if they had been mistakenly produced. A claw back provision essentially will undo a document production. In theory, this is a great way to increase the flow of information between opposing parties, decrease discovery costs, and limit the amount of time spent combing through documents before they are produced. See 2006 Advisory Committee Note to Fed.R.Civ.P. 26(f). However, this only works if opposing counsel plays by the rules of the “claw back” game. Here, instead of just returning the CD as requested by the producing party, the receiving party copied and pasted all the documents from the CD onto the law firm’s server. The CD was eventually returned to the producing party, but the damage had already been done. The receiving party had an unblemished, unrestricted view of all the documents saved right on their servers. The producing party promptly asked the court to interject and enforce the claw back protection order; however, the receiving party had already reviewed the recalled documents via the copies on their servers. The court ordered that the recalled documents be deleted, forbade the use of the documents unless they were properly produced, and required the receiving party to submit confirmation of the same. However, as the saying goes, the cat was already out of the bag. Judge Magnus-Stinson admitted in his opinion that he could not bar the receiving party from using the recalled documents because the documents still may be properly requested and produced. In other words, the receiving party now had the upper hand because they knew what documents to specifically request based upon their review of the recalled documents. The moral of the story in this case is do not rely solely upon claw back protective orders when going through the discovery process, especially when producing digital information. Even if the protective order is enforced and a party is able to claw back specific data, there is some damage that just cannot be undone. Victoria O’Connor Blazeski (formerly Victoria L. O’Connor) received her B.S. form Stevens Institute of Technology, and she will receive her J.D. from Seton Hall University School of Law in 2015. Prior to law school, she worked as an account manager in the Corporate Tax Provision department of Thomson Reuters, Tax & Accounting. Victoria is a former D3 college basketball player, and she has an interest in tax law and civil litigation. After graduating, she will clerk for the Hon. Joseph M. Andresini, J.T.C. in the Tax Courts of New Jersey. Want to read more articles like this? Sign up for our post notification newsletter, here.
The court began its opinion by reciting the quote that “[d]iscovery relevance is minimal relevance,” leading most readers to presume the court was going to rule in favor of Plaintiff’s motion to compel. However, after learning that Plaintiff sought “the entire claims file” of Defendant, that presumption slowly dissipates. The motion before the court involved Plaintiff’s request for an order compelling Defendant to produce documents that are responsive to certain of Plaintiff’s second, third and fourth sets of Requests for Production of Documents. The Plaintiff alleged that Defendant’s objections are premised on unsupported claims of privilege and that the documents Defendant did turn over were excessively redacted. After a back and forth regarding the concept of “privileged” the court rules that the real crux of the issue is the “point at which Defendant was reasonably anticipating litigation.” It is at this point that a privilege is created for the documents at issue based on the work product doctrine as outlined in Fed. R. Civ. P. 26(b)(3)(A) at which point a privilege for the documents at issue based on the work product doctrine. Because insurance claims are of such sensitive and proprietary nature, the court holds that the question of whether insurer documents were created in anticipation of litigation “depends on whether the party seeking protection can point to a definite shift made by the insurer from acting in its ordinary course of business to acting in anticipating of litigation.” Colloquially known as a “trigger” for document preservation, the burden is on the Defendant to establish the existence of such privilege in the face of litigation. The court ultimately held that the relevant date was December 28, 2012, when Defendant sent a letter regarding a settlement check. Thus, the court ordered that any information withheld on the basis of work product doctrine after that time must be produced. After serving its second set of discovery requests, the Plaintiff subsequently asked for the documents to be produced in native electronic format. However, the Defendant had already produced documents in paper and PDF form, which Plaintiff alleged was not the form maintained by the Defendant “or in any reasonably usable form.” Citing Fed. R. Civ. P. 34(b)(2)(D) and (E), the court noted that the rule allows, but does not require, the requesting party to specify the form in which it is requesting electronic data. The court also noted there is nothing in the rule that prohibits a party from requesting different formats from one set of discovery requests to the next. Ruling in favor of the objecting Defendant, however, the court considered the “proprietary nature of certain software used by Defendant” and “Defendant’s right to withhold privileged information” as well as the “added costs of re-producing information already submitted to Plaintiff.” Because the Defendant endured the time, effort, and expense of producing documents in PDF form as initially requested by Plaintiff, the court denied Plaintiff’s request to compel the native electronic forms of such documents. The Plaintiff’s motion to compel also sought all files containing “similar” claims. While disregarding the Plaintiff’s motivations for requesting such documents, the court opined that the effect of requiring this production would be to “subject [Defendant] to undue burden in light of topics which, at best, have limited evidentiary value in this case given the broadly worded nature of the information requested.” Adding insult to injury, the court makes it a point to criticize Plaintiff’s complaint. The cause of action was premised on a breach of the covenant of good faith and fair dealing yet Plaintiff’s motion “continually” refers to this as a claim for “bad faith.” Succinctly and sharply, the court imparts some legal education by bluntly stating that the two are not interchangeable. After making its criticism of Plaintiff’s mischaracterization, the court writes that “even if such information were to be considered relevant, the requests, as written, are facially over broad.” The court broadly cites a “lack of specificity” before denying more than 25 of Plaintiff’s discovery requests. Because Plaintiff “failed to provide a sufficient, substantive limitation,” the court ruled that these “generalized discovery requests” were “facially over broad as well as irrelevant.” Lastly, seemingly as a concession to the largely defeated Plaintiff, the court partially grants Plaintiff’s final discovery request. Plaintiff sought the “complete personnel files” for certain claims handling supervising personnel involved in the claim. As with the other requests, Defendant objected citing the “personal, confidential, private information” that these files held. Significantly, the court recited that “‘confidential’ does not equate to ‘nondiscoverable’ or privileged.” Thus, the court granted Plaintiff’s motion to compel such personnel files, although it concluded this grant by limiting it to information from the files that specifically pertains to the employees’ “background, qualifications, training and job performance” and explicitly excluded any “sensitive personal or medical information” regarding these individuals. By the end of its succinct seven-page opinion, the District Court for the District of Kansas handed down many valuable lessons for future parties engaged in discovery-based litigation. Among them: (1) The work product doctrine will not prevent production if litigation is reasonably anticipated; (2) Request documents in the form desired or risk a landslide of “unusable” documents; (3) Be careful, diligent, and precise in your word choice – both in your pleadings and your document requests; (4) Private/Confidential does not mean Privileged/Nondiscoverable. Nicole was a 2010 magna cum laude graduate of Northeastern University located in Boston, Massachusetts where she earned her B.A. in English and Political Science. She will receive her J.D. from Seton Hall University School of Law in 2015. After graduation, Nicole will serve as a clerk to a trial judge of the Superior court of New Jersey in the Morris-Sussex Vicinage. Want to read more articles like this? Sign up for our post notification newsletter, here.
This matter came before the court upon Plaintiff Black & Veatch’s Motion for Protective Order and Request for Discovery Conference. B&V entered into a series of agreements wit American Electric Power Services (“AEP”) and other companies (collectively, the “Owners”) to engineer, procure material, and construct wet flue gas desulfurization systems (also known as JBRs). The Owners claimed the JBRs were defective. B&V paid several millions of dollars to repair and replace the JBRs. To recover some of the incurred costs, B&V filed a claim with its professional liability carriers, filed suit against a subcontractor, and filed a breach of contract and declaratory judgment action against various insurance providers relating to the relevant insurance policies. B&V alleged it maintained Electronically Stored Information (“ESI”) relating to the JBRs on Documentum—an electronic document management program, custodian hard drives, and Accounting and Field Management System. B&V produced 448.7 gigabytes of data to the Defendant. However, B&V withheld additional relevant ESI, arguing that the Defendants’ proposed search terms were too board and producing discovery pursuant to those search terms would be unreasonable and excessively expensive. B&V was unable to estimate the cost of producing the ESI. B&V sought a protection from producing this additional relevant information. In the alternative, B&V proposed to shift some of the cost in producing the ESI to the Defendants. Fed. R. Civ. P. 26(c) states, “a court may, for good cause, issue an order to protect a party or person from annoyance, embarrassment, oppression, or undue burden or expense. The movant bears the burden of establishing good cause by making a particular and specific demonstration of fact. A mere conclusory statement that ESI production would cost a party tens or hundreds of thousands of dollars does satisfy a movants burden to make a specific demonstration of fact in support of a protective order. The court held that B&V’s undue burden and expensive argument to be unsupported and conclusory. B&V failed to provide any hour or cost estimate. Thus, the court denied B&V’s Motion for Protective Order. Additionally, the court refused to grant the protective order because the Defendants’ search terms were overbroad, noting that Fed. R. Civ. P. 26(c) only allows protective orders when the movant proves the order is necessary to protect the party from annoyance, embarrassment, oppression, or undue burden. Over breadth is not an enumerated category. The court also denied B&V cost shifting proposal. Fed. R. Civ. P. 26(b)(2)(C)(iii) allows the court to impose cost shifting measures when the party from whom discovery is sought demonstrates that the information is reasonably accessible because of undue burden or cost. B&V failed to show that the ESI production was inaccessible because of undue burden or cost because B&V’s only mention of cost to produce ESI was conclusory and unsubstantiated. Furthermore, the court stated that the parties were free to enter into a clawback agreement, which would compel the parties to return inadvertently produced privileged documents. B&V also sought protection from producing ESI from the custodian hard drive, arguing that that data produced pursuant to Defendants’ search terms would be unrelated or duplicative. Moreover, B&V argued that a Defendant’s proposed list of custodians was overly broad. Defendant argues that the proposed list is reasonable on its face given that the case involves a $70 million coverage dispute. The court again denied B&V’s Motion for Protective Order because B&V failed to substantiate its claim that the production of ESI from the custodian hard drives pursuant to proposed search terms will yield unrelated or duplicative data. B&V also failed to substantiate its claim that Defendant’s proposed list of custodian hard drives was unduly burdensome because it was without any information regarding the custodians’ job duties, their involvement with the facts at issue, or whether they had potentially relevant information on their hard drives Finally, B&V sought protection from producing electronic interim accounting reports regarding the cost of the JBR projects, arguing that such production would be wasteful, expensive, and burdensome. B&V stated that only the final accounting costs were necessary to determining damages, and a final cost accounting report was previously produced to the Defendants. The electronic interim accounting reports requested by the Defendants are adjusted monthly, and do not represent final costs needed to determine damages. Defendants argued that the report produced did not include the final cost documents, and the lack of information prevents them from properly assessing damages. The court again denied B&V’s Motion for Protective Order because B&V did not substantiate how producing the electronic interim accounting reports would be unduly burdensome or expensive. B&V’s assertion that monthly-adjusted accounting reports will not provide final cost information was conclusory. Aaron Cohen, a Seton Hall University School of Law student (Class of 2015), focused his studies in the area of Family Law. He participated in the Seton Hall Center for Social Justice’s Family Law Clinic. After graduation, he will clerk for a judge in the Superior Court of New Jersey, Family Division. Prior to law school, he was a 2011 cum laude graduate of The George Washington University Columbian College of Arts and Sciences, where he earned a B.A. in Psychology. Want to read more articles like this? Sign up for our post notification newsletter, here.
The attorney-client privilege is not as inclusive as some may think. The privilege protects confidential communications between attorney and client in order to “encourage full and frank communication between attorneys and their clients.” The attorney-client privilege only applies if the following conditions are met. The asserted holder of the privilege is or sought to become a client; The person to whom the communication was made is an attorney; The communication relates to a fact of which the attorney was informed; (a) By the client, (b) Without the presence of strangers, (c) For the purpose of securing an opinion of law or legal services; and The privilege has been claimed and not subsequently waived. Commonly, disclosure of confidential information functions as an abdication of attorney-client privilege. Unintentional disclosure, however, does not constitute a waiver of the attorney-client privilege if: (1) the disclosure is inadvertent; (2) the holder of the privilege or protection took reasonable steps to prevent disclosure; and (3) the holder promptly took reasonable steps to rectify the error. Courts also look to factors such as the quantity of the disclosure and the overriding interests of justice when determining whether the attorney-client privilege was inadvertently waived. In this case, a discovery dispute arose because the defendant unintentionally disclosed two privileged documents to the plaintiff. The first document was a letter from the defendant to an attorney for the purpose of soliciting legal advice. The second document was a response letter from the attorney providing counsel to the defendant. The court here found that these two documents are clearly covered by attorney-client privilege. So, the issue then became whether or not the defense waived attorney-client privilege when the party unintentionally disclosed the privileged documents. The court first considered the precautions taken by the defense to prevent accidental disclosures and discovered that there were none. For one, the defendant did not maintain a privilege log. Additionally, the defense did not even mark or designate the letters as confidential. For purposes of maintaining privilege, this factor weighed heavily against the defendant. The next factor the court looked to was the number of inadvertently disclosed documents. These documents were a mere three pages among a total of 3,500 pages of discovery documents. This factor weighed in favor of maintaining privilege. The third factor considered was the extent of privileged information disclosed. This factor weighed in favor of waiver because the information contained on the letters was clearly privileged. The court reasoned that the extent of the defendant’s carelessness weighed against maintenance of attorney-client privilege. The fourth factor considered was the extent of any delay in correcting the inadvertent disclosure. Since the defense took more than three months to attempt to rectify their mistake, this factor was found to be in favor of waiver. As to the last factor, the court stated that the defense did not offer any explanation as to why, in the overriding interest of justice, the letters should still be privileged. Since the majority of factors were found to be in favor of the waiver of attorney-client privilege, the court held that the defense has waived attorney-client privilege with respect to the letters. It is imperative to keep in mind that the attorney-client privilege can be waived unintentionally. One of the most effective ways to prevent an inadvertent disclosure is to maintain a preventative mechanism. Mark all privileged documents as privileged, keep a detailed privilege log, and constantly double check all disclosed documents so any mistake can be corrected quickly. If these steps are followed, a party will likely be able to maintain privilege even if the party inadvertently discloses privileged documents. Daniel received a B.A. in Criminology and Criminal Justice from The University of Maryland. He will receive his J.D. from Seton Hall University School of Law in 2015. Presently Daniel is serving as a legal intern in the Juvenile Justice Clinic. After graduation Daniel will clerk for a trial judge in the Superior Court of New Jersey. Want to read more articles like this? Sign up for our post notification newsletter, here