- eLessons Learned
- Press and Publicity
- About Our Team
- Contact eLL Blog
In McCann v. Kennedy Univ. Hosp., Inc., the plaintiff Robert McCann sued Kennedy University Hospital, asking the court to sanction the hospital for intentionally or inadvertently destroying necessary videotapes. The plaintiff contended that the videotapes contained an account of the defendant’s emergency room lobby on the night the plaintiff claims to have been mistreated by the defendant’s staff. The plaintiff argued that the defendant knew or should have known that the video tapes were discoverable material and that there was actual withholding or suppression of the videotapes, which constituted spoliation. On December 21, 2011, the plaintiff was transported to the hospital after suffering extreme rectal pain and trouble breathing. The Plaintiff claims to have been in excruciating pain while he was waiting to be seen by the hospital staff. He states that he was ignored and neglected for at least seven hours. During the time that he was at the hospital, the plaintiff claimed to have collapsed on the floor and was left lying on the floor for over ten minutes, while staff walked over him without offering assistance. McCann also claimed that when he was eventually seen by the hospital staff, they treated him in ways that made him feel humiliated and uncomfortable. The hospital allegedly refused to treat McCann because he did not have insurance. On December 23, 2011, the plaintiff sent an e-mail to Renae Alesczk, the assistant to the Senior Vice President of the Kennedy Health System, complaining about his experience at the hospital while also threatening to sue. A few hours after the email was received, Aron Berman, formerly employed as the defendant’s Director of Guest Relations and Service Improvement, forwarded the McCann’s e-mail to Kim Hoffman, the Corporate Director of Patient Safety. The defendant claimed to have conducted an internal investigation of the complaints at that time, and notified the plaintiff that his complaints were being addressed. The hospital staff then stated that the investigation showed that the hospital staff acted appropriately and managed the patient’s clinical care in a professional manner. So far, so good. However, the plaintiff’s attorneys requested videotapes of the emergency room lobby, which showed the plaintiff waiting without being treated by staff. The defendants claimed that there was no videotape footage because they did not have enough disc drive space to keep all their video footage and had already erased the footage from the night in question. The plaintiff argued that the defendants knew or should have known that the videotapes would be requested in discovery, and that the defendants should not have destroyed the videotapes. The plaintiff claimed such activity as obstruction of justice and an intentional spoliation of evidence. The defendants argued that the tapes only show the time period during which the patient was in the waiting room, and are irrelevant to the plaintiff’s complaints about the treatment by staff when he was seen in the hospital. The Third Circuit has adopted a four-factor test for evaluating spoliation claims, finding that spoliation occurs where: “(1) the evidence was in the party's control; (2) the evidence is relevant to the claims or defenses in the case; (3) there has been actual suppression or withholding of evidence; and (4) the duty to preserve the evidence was reasonably foreseeable to the party.” Here, there is no argument that the tapes were in the party’s control. The court found that the tapes were not relevant to the plaintiff’s claims and that the defendant did not have a duty to preserve the video tapes at issue. Therefore, there had not been actual suppression or withholding of the evidence. The takeaway from this case is that the court found it was reasonable for the hospital to destroy the videotapes because the plaintiff’s claim was specifically in regard to his being treated while at the facility, NOT his experience while waiting in the lobby. However, to be safe, videotapes of the night in question should be preserved to avoid this kind of confusion. 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
In Freedman v. Weatherford Int'l Ltd., a putative class action alleging securities fraud, the plaintiff moved for reconsideration of the court’s denial of a motion to compel discovery. The plaintiff sought to compare a document that had been produced by defendant Weatherford International during discovery with documents from two internal investigations conducted by defendant, which had not been produced during discovery. Specifically, the plaintiff secured 18 emails from “‘critical custodians at Weatherford’ that were produced (after briefing on the original motion to compel was complete) . . . by third-party KPMG.” KPMG worked with the defendant on its remediation efforts. The defendant never produced these emails during discovery, thereby—according to the plaintiff—demonstrating significant deficiencies in the defendant’s discovery production. The United States District Court for the Southern District of New York acknowledged that discovery on discovery is proper “where a party makes some showing that a producing party’s production has been incomplete . . . in order to test the sufficient of that party’s discovery efforts.” However, these meta-discovery requests must be “closely scrutinized” to avoid unnecessarily prolonging the “costly and time-consuming discovery process.” The plaintiff argued that KPMG’s production of the 18 emails proved that the defendant’s production was deficient and that providing the plaintiff with the documents of the two internal investigations would lead to the discovery of “additional relevant documents that had not been produced.” Thus, the district court noted that the plaintiff did seek to test the defendant’s discovery efforts. Rather the plaintiff sought to ‘identify the documents missing from [the defendant’s] production.” The district court held that the documents the plaintiff sought would not lead to additional documents not previously produced. The plaintiff admitted that only three of the 18 emails would have been identified had it been able to compare initially produced documents with documents of the two internal investigation. Additionally, the plaintiff never argued that other documents produced by third parties, but not by the defendant, would have been identified by requested document comparison. Moreover, the court stated “the Federal Rules of Civil Procedure do not require perfection.” Further, “it [was] unsurprising that some relevant documents may have fallen through the cracks,” when the defendant “reviewed million of documents and produced hundreds of thousands.” In conclusion, the plaintiff’s requested remedy was not best suited to cure the alleged discovery deficiencies. In order to win a motion to compel discovery on discovery, the plaintiff needed to “proffer an adequate factual basis for their belief that the current production [was] deficient.” Given that a party is not subjected to sanctions for failing to produce minimal amounts of documents during a massive discovery production when its production was otherwise lawful, the plaintiff in this case should never have filed the motion for reconsideration of its previous motion to compel discovery. Furthermore, the plaintiff should have assessed the usefulness of the relief they sought. In this case, the motion to compel discovery was unnecessary because only three of the 18 emails were relevant and the proposed document comparison would not have yielded any other documents not produced by the defendant. Aaron Cohen, a Seton Hall University School of Law student (Class of 2015), focuses 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, Aaron 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.
Employers should take note: erasing and taping over messages that relate to a fired employee is never a good idea. Employers who engage in this type of practice will never escape the wrath of a judge when the fired employee inevitably brings a wrongful termination. Eventually, such action catches up with the defending company and they will have to pay a steep price. Take, for instance, the case Novick v. AXA Network, LLC. The plaintiff was asking the judge for sanctions to be imposed on the defendants because he claimed that the defendants spoliated audio recordings and emails from an eight-week stretch, which ran from late August until early November 2006. The defendants admitted that recordings from this time period were likely erased and taped over. The problem here is that this stretch of time covers the time directly before and directly after Novick’s termination. It should seem obvious to anyone that a company’s failing to preserve any recordings regarding a former employee’s termination is a terrible idea and will likely hurt one’s case in court. It should instead be common sense that when an employee is terminated, and certainly when that termination is contentious, a lawsuit is foreseeable. Thus, the employer should take care to preserve anything that might come into play at trial. Novick asked the judge to sanction the defendants for the spoliation of emails. The defendants could not produce any emails between the two employees at AXA Network, who took over Novick’s accounts, and Novick’s former clients. If these employees were involved with Novick’s clients after Novick was fired, it is only logical that there would have been emails taking place between these employees and those clients! Nevertheless, the defendants could not produce a single e-mail. Sanctions can be imposed on a party for spoliation in violation of a court order under Rule 37(b) of the Federal Rules of Civil Procedure or, where there has been no violation of a court order, a judge can impose sanctions for spoliation under the court’s “inherent power to control litigation.” West v. Goodyear Tire & Rubber Co., 167 F.3d 776, 779 (2d Cir. 1999) (emphasis added). For the court to exercise its inherent power, there must have been a showing of bad faith. United States v. Int’l Bhd. of Teamsters, 948 F.2d 1338, 1345 (2d Cir. 1991). The Novick court in this case found that the defendants did spoliate the audio recordings because they were notified in October 2006 to preserve the recordings for future litigation and to produce those recordings to the plaintiff. In addition, the defendants provided no reason for why or how these recordings were missing. Unsurprisingly, the court suggested that such behavior indicates that the company acted deliberately and therefore possessed a culpable state of mind. The defendants acted in bad faith. The court did not find that the defendants spoliated the email messages, but it still believes they acted in bad faith with respect to the production of the emails because the company failed to search one of their email archives for months due to what was claimed as “human error.” This was clearly a delay tactic, further warranting sanctions. The court invoked its inherent power to control litigation because the defendants acted in bad faith, employed delay tactics, caused substantial costs to be incurred by the plaintiff, and wasted the court’s time. The court imposed an adverse inference jury instruction. Adverse inference instructions can be imposed against a party who had an obligation to preserve evidence at the time it was destroyed, who destroyed the evidence with a culpable state of mind, and who destroyed evidence that was relevant to the opposing party’s claim or defense. Residential Funding Corp. v. DeGeorge Fin. Corp., 306 F.3d 99, 107 (2d Cir. 2002). The clear takeaway from this case is that it is better to be safe than sorry; if it is reasonable that a lawsuit may be brought against you, take all measures to preserve any evidence that might have anything to do with that future case. Preserving the evidence will not hurt, but failing to do so will. Logan Teisch received his B.A. in Government and Politics from the University of Maryland, College Park in 2012. He is now a student at Seton Hall University School of Law (Class of 2015), focusing his studies in the area of criminal law. Logan’s prior experiences include interning with the Honorable Verna G. Leath in Essex County Superior Court as well as interning with the Essex County Prosecutor’s Office. Want to read more articles like this? Sign up for our post notification newsletter, here.
Companies issue laptops to their employees to be used for business purposes both in the office and at home. A company’s distributing laptops is joined with the company’s responsibility to preserve the electronically stored information (ESI) when litigation is reasonably anticipated. Every company has its own “ordinary business protocol” to be used in relation to these laptops when a situation requires it, but sometimes these protocols lead to bigger issues. In Hawley v. Mphasis Corp., the United States District Court for the Southern District of New York granted an adverse inference instruction regarding a supervisor’s laptop, but not for the employee laptop. In Hawley, an employee of the defendant company brought an employment discrimination claim and moved for sanctions against the defendant for alleged discovery violations; those of which, in particular, were violations regarding spoliation of information on two company laptops. The employee alleged that the company deleted all information from his work laptop, as well as his supervisor’s information, and did not produce records vital to the defendant’s case. The company countered, arguing that clearing the hard drive of a former employee’s laptop was the business protocol. In evaluating the request for an adverse inference sanction, the district court explained that the plaintiff must demonstrate: “(1) that the party having control over the evidence had an obligation to preserve it at the time it was destroyed; (2) that the records were destroyed with a culpable state of mind; and (3) that the destroyed evidence was relevant to the party’s claim or defense such that a reasonable trier of fact could find that it would support that claim or defense.” Hawley v. Mphasis Corp., No. 12 Civ. 592 (DAB) (JLC), 2014 WL 3610946, at *7 (S.D.N.Y. July 22, 2014) (quoting Residential Funding Corp. v. DeGeorge Fin. Corp., 306 F.3d 99, 107 (2d Cir. 2002)). As to the supervisor’s computer, the court held for an adverse inference sanction because the company had a duty to preserve the supervisor’s data from the time of the EEOC filing. Furthermore, the company negligently destroyed the records on the laptop , which were found to be highly relevant to the employee’s case. In regards to the employee’s computer, the court found both a duty and the requisite culpability; however, the court did not believe that the employee sufficiently proved how relevant the information was to his case. The lesson to extract from this case is that the courts do not care if your company’s protocol requires one procedure to be followed (i.e., wiping a hard drive) when it comes to the spoliation of relevant evidence. The company’s wiping the hard drives is trumped by a duty to preserve data when a lawsuit is reasonably anticipated. The ruling in Hawley demonstrates that, in an employment case, the receipt of an EEOC charge triggers the obligation to preserve all data, but it could arise earlier depending on the circumstances. Be aware of when a lawsuit is reasonably anticipated and do not hesitate to act and preserve. Such awareness will help your company in the long run. With that, be on top of the individuals responsible for preserving company data and ensure those individuals are complying with company policy. One does not want to need a hard drive that has no data saved on it. Evidence must be preserved until litigation is resolved or no longer reasonably anticipated, and as courts become stricter with this rule of law, so should every company. A look at the circumstances and a possible deviation from ordinary protocols may be needed. For more information on the case used as precedent, Residential Funding Corp. v. DeGeorge Fin. Corp., click here: http://caselaw.findlaw.com/us-2nd-circuit/1003010.html. 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.
In a case dealing with gender discrimination between female employees and a large advertising conglomerate, the plaintiffs filed claims against the defendants under Title VII of the Family and Medical Leave Act, the Equal Pay Act, the Fair Labor Standards Act, and similar New York labor laws. After the plaintiffs objectioned to the defendants’ use of computer-assisted review and search method, United States Magistrate Judge Andrew J. Peck opined that computer-assisted review is an acceptable search method for relevant ESI in appropriate cases. Throughout his opinion, Judge Peck referred to articles and public statements he had made prior to the case on his beliefs of the value of computer-assisted review. Judge Peck explains his interactions with the two parties involved started at the first discovery conference, which took place on December 11, 2011. While, both parties had discussed ESI protocol, the plaintiffs were reluctant to accept the defendant’s utilization of predictive coding to gather the relevant documents among the three million electronic documents from the agreed-upon custodians. In a later discovery conference, the court refuted the defendants’ proposal to cutoff production at the most relevant 40,000 documents due to expense, explaining that proportionality must consider cost and results in gathering the most likely highly responsive documents. The court went on to agree with the defendants on other factors concerning document production and custodians due to the fact that the plaintiffs could not give meaningful reasons for the inclusion of other custodians and emails or assert a likelihood that the information could be found through other reasonable discovery procedures. On February 8, 2012, after going through the main issues that were holding up the discovery process, Judge Peck acknowledged that the defendants agreed to provide the plaintiffs with all seed documents and protocol in determining relevant ESI throughout the computer-assisted review process. With that knowledge, Judge Peck accepted the proposal that defendants submitted to the plaintiffs and the court for producing relevant ESI, and acknowledged that computer-assisted review was an efficient and officially judicially approved method for ESI protocol and production when given the appropriate case. On February 8, 2012, the plaintiffs filed an objection to the court’s ruling.
Facts of the Case The employee in this case was not some floozy with limited knowledge of how the world works. Rather, he was a veteran sergeant of the Ontario, California, police force and a member of its S.W.A.T. team. In 2001, the Ontario Police Department (OPD) issued alpha-numeric pagers to his team in order to facilitate communications between members, which, as you can imagine, would be extremely useful in the field and efficient at the office. OPD then put in place a “Computer Usage, Internet and E–Mail Policy” which the employee signed a statement that said he had read and understood the policy. It expressly reserved the right to monitor all of the network activity, which included e-mail and Internet use. Additionally, the policy said that there should be no expectation of privacy when using the network. The problem was that the computer policy did not cover text messaging, at least expressly, since the pagers were contracted out to a company called Arch Wireless. Therefore, all communication passed through their network, and a copy of all communications was retained on their servers after delivery. However, the OPD made it clear to all of its employees, in a meeting that the employee attended, that the messages sent on the pagers were to be treated as e-mails, meaning that they were subject to the same computer policy. As it turned out, the employee exceeded his monthly text character allotment, almost immediately, and for a period of a few months. He paid for those overages, but the OPD decided that enough was enough. The police chief launched an investigation, ostensibly in order to determine whether the employees were being forced to pay out of pocket for overages on work-related messages due to an overly-restrictive character limit, or if the messages were personal. Transcripts of the messages from the previous 2 months were obtained, and revealed material that was personal, and some sexually explicit, in nature. The employee was then disciplined. Claims by the Employee The employee essentially brought two claims: 1) that the OPD violated the Stored Communications Act (SCA) and 2) his Fourth Amendment privacy rights, by obtaining and reviewing the transcripts of the messages. The first claims was not before the Supreme Court on its merits, since the lower court decided that Arch Wireless was forbidden to turn over the transcripts, and this was not contested. However, the Fourth Amendment claim was alive and well. As with most Fourth Amendment claims, the crux of the issue is whether there is a reasonable expectation of privacy that was violated. The Fourth Amendment guarantees the right of people to secure against unreasonable searches and seizures by the government of their stuff. This has been applied to the government acting as an employer as well. The analysis of such claims, however, was the subject of dispute among the Supreme Court justices in a case called O’Connor v. Ortega. In that case, the plurality opinion of the Court said that the question of whether an employee has a reasonable expectation of privacy is to be decided on a case-by-case basis. If there is an expectation of privacy, is an intrusion on that reasonable under the circumstances. Justice Scalia said that there is a blanket expectation of privacy for government employees, but the employers can search to retrieve work-related materials, etc. Here, the Court expressly punted the issue of whether there was, or is, an expectation of privacy for communications made on electronic equipment owned by a government employer. The Court cited the difficulty in predicting how the expectation of privacy will be shaped by the rapid changes in the dynamics of communication and information transmission. Instead, the Court cautioned “prudence” to avoid deciding this important issue, and instead decided the case without it. The Court stated that even if the employee had a reasonable expectation of privacy in his messages, and therefore protected by the Fourth Amendment, the “search” done by OPD didn’t necessarily violate it. The “special needs” of the workplace were said to be an exception to the rule that all warrantless searches are automatically unreasonable. There was a reasonable ground for assuming that the search was necessary for a work-related purpose, not just to invade the employee’s privacy. Rather, their interest was to ensure the employees were not paying out of pocket for work-related expenses. Therefore the review of the transcripts was reasonable. Also, the employee should not have expected that his messages were going to remain private under all circumstances, since he was told that the messages were subject to auditing. Additionally, the scope of the search was reasonable as well, since it did not reveal the details of the employee’s life, since the private messages in the search sample were redacted. Ultimately, the sergeant should have known better than to air his dirty laundry on a government-issued communications device. Although the Court avoided deciding whether there is an expectation of privacy, they made it pretty clear that if there was a well-distributed policy, and if the review of the messages is ostensibly for work-related issues, that such a “search” will be permissible. Akiva Shepard received his J.D. from Seton Hall University School of Law in 2014. Akiva has worked for a New York State Supreme Court Judge in Kings County and for a NJ real estate firm.
On July 31, 1996, plaintiff Omega Engineering Corp. ("Omega"), a New Jersey based company, lost its computer programs relating to design and production permanently from its system. Omega manufactured “highly specialized and sophisticated industrial process measurement devices and control equipment” for NASA and the United States Navy. The deletion of these programs debilitated their ability for manufacturing as well as costed the company millions of dollars in contracts and sales. From 1985 to July 10, 1996, defendant Timothy Lloyd worked as the computer system administrator at Omega. He trained with the Novell computer network and installed it to Omega’s computer system. The program worked to ensure that all of Omega’s documents could be kept on a central file server. Lloyd was the only Omega employee to maintain the Novell client and have “top-level security access” to it; however, the defense asserted that others at the company had access. According to a government expert, access "means that ... [an] account has full access to everything on the server." Lloyd was also the only employee in charge of backing up the information to the server. In 1994 or 1995, Lloyd became difficult. The company moved him laterally in hopes of improving his behavior. A government witness testified that even though it was a lateral move, it was in fact, considered a demotion by the company. Lloyd’s new supervisor asked him about the back-up system and wanted him to loop a couple more people in but he never did. Moreover, he instituted a company-wide policy that employees were no longer allowed to make personal backups of their files. On top of the above issues, there was also a “substandard performance review and raise.” The combination of the two factors, according to the government, showed Lloyd that his employment with the company would soon be terminated. This established Lloyd’s motive to sabotage the Omega computer system. On July 10, 1006, Lloyd was terminated. On July 31, 1996, Omega’s file server would not start up. On July 31, “Lloyd told a third party, that "everybody's job at Omega is in jeopardy.” days later it was realized that all of the information contained on it were permanently lost. More than 1,200 of Omega’s programs were deleted and, as per Lloyd’s policy, none of the employees had their own personal backups. There was no way for any of these programs to be recovered. A search warrant conducted on Lloyd’s house turned up some backup tapes and a file server master hard drive. Experts hired by Omega found that the deletion of information was “intentional and only someone with supervisory-level access to the network could have accomplished such a feat.” The commands necessary to pull off such a purge were characterized as a “time bomb” set to go off on July 31st when an employee logged into the system. There was evidence found by these experts of Lloyd testing these specific commands three different times. This string of commands was further found on the hard drive that was in Lloyd’s home. Lloyd was convicted of a federal count of computer sabotage. It was remanded due to a jury member’s claimed use of outside knowledge during deliberations. Julie received her J.D. from Seton Hall University School of Law in 2014. Prior to law school, she was a 2008 magna cum laude graduate of Syracuse University, where she earned a B.A. in History and a minor in Religion and Society. After law school, Julie will serve as a law clerk to a judge of the Superior Court of New Jersey.
Background Omega Engineering Corporation, an international company based in New Jersey, was once the employer of Timothy Lloyd. To put Omega’s importance into perspective, the U.S. Navy and NASA were two of their clients for highly specialized and sophisticated industrial process measurement devices. According to testimony during the trial, Lloyd worked at Omega as its sole system administrator from 1985 through 1996. In 1995, Lloyd had undergone Novell network training and installed Novell software on Omega’s computer system. Additionally, Lloyd was the only person who maintained and had top-level access to the Omega network. Between 1994 and 1995, Lloyd became belligerent and increasingly truculent. Due to his poor interpersonal skills, he was demoted in May 1995 from manufacturing to support engineer. A woman who had once been Lloyd’s subordinate and had engaged in a romantic relationship with Lloyd, was the individual responsible for replacing Lloyd as manufacturing supervisor. In June 1996, Lloyd instituted a policy to “clean up” all of the individual computers in Omega’s manufacturing department. It was unclear as to why Lloyd was implementing company policies after his demotion. Nonetheless, the policy required employees to save their files to the company’s file server and prohibited them from making their own backups. Lloyd’s manager became suspicious of this policy and requested from Lloyd access to the file server. Lloyd never complied. By the end of June, upper management had enough of Lloyd’s behavior and terminated him in early July 1996. On July 31, Omega’s file server would not boot up. All of Omega’s manufacturing programs on the server, which contained instructions for operating the machines, were gone. Multiple computer experts were brought in to recover the files, but to no avail. The files had not only been deleted, but also had been “purged,” meaning that they were rendered unrecoverable. A leading expert on Novell networking testified at trial that this could only have been done intentionally and by someone with supervisory-level access. The government’s theory included that on July 30, anyone who would log on to the server at any time after that date would “detonate” a program installed by Lloyd that would destroy the information on the Omega file server. The government’s theory was bolstered by the fact that the Secret Service recovered missing Omega backup tapes that had been reformatted as well as a master hard drive from the file server. This had the same string of commands that had functioned as the time bomb program found on the Omega file server. The Decision Ultimately, Lloyd was found guilty of computer sabotage. The jury had deliberated for over twelve hours over the span of three days and had requested testimony in the jury room before they reached their verdict. However, three days after the verdict, one juror said that she had seen on the news, during the trial, about a computer virus called the Philippine “love bug” which allowed the perpetrator to cause great harm by flooding the victim computers and causing them to crash. Whether this affected her decision is unclear; however, the defendant claimed that his 6th Amendment rights had been violated. The district court agreed, granting a new trial. On review, the Court of Appeals reversed the district court’s holding. After a lengthy discussion, the court said that there were significant dissimilarities between the “love bug” and the “time bomb” and most jurors would not confuse the two. Therefore, the appellate court found, the defendant was not prejudiced. Lloyd’s managers should never have allowed a single employee hold as much power as they did. This case highlights the vulnerabilities the company subjects itself to if that is allowed to happen. For example, Omega lost over 1,200 programs and many current and potential clients as well. Akiva Shepard received his J.D. from Seton Hall University School of Law in 2014. Akiva has worked for a New York State Supreme Court Judge in Kings County, and for a NJ real estate firm.
In Haskins v. First Am. Title Ins. Co., the court was asked whether a title insurance company (the "Insurer") is in "control" of documents that are in not in the Insurer's possession, but where the Insurer has the contractual right to direct those with possession to produce the documents. The district court found in the affirmative, demonstrating that in some circumstances, the more extensive one's contractual rights, the more extensive its obligations in discovery. The plaintiffs sought class certification, which defined the class as all New Jersey consumers who paid premiums in excess of regulated title insurance refinance rates during the class period. The plaintiffs alleged that the Insurer had overcharged for title insurance over a period of several years. During discovery, plaintiffs sought certain documents in the possession of certain independent title agents, who were not employees of the Insurer, but with whom the Insurer had a contractual relationship. The representative contracts made all documents "available for inspection and examination by [the Insurer] at any reasonable time." The court inquired as to whether such documents are in the "control" of the Insurer, because pursuant to Fed. R. Civ. P. 34(a), a party may request another party to produce documents within that party's "possession, custody, or control." Thus, if such documents were in the "control" of the Insurer, the plaintiffs could properly request that they be produced in discovery. The Insurer argued that it should not be required to produce documents in the physical possession of its agents because it does not possess or control the requested documents. However, the court did not struggle to conclude that the Insurer's agency contracts plainly indicate that it has control over and access to the documents. It drew this conclusion based on the premise that there is control if a party “has the legal right or ability to obtain the documents from another source upon demand.” Haskins demonstrates the potential for increased discovery obligations for those that have negotiated extensive rights in contract. That is, the greater rights in contract, the potential for broader obligations in discovery. While this factor may not drive the decision making for those negotiating contracts, contract parties should at least be aware of this consequence Adam L. Peterson 2014 graduate of Seton Hall University School of Law. While at Seton Hall, Adam was a member of the Seton Hall Law Review and prior to law school Adam was an Environmental Analyst with the New York State Department of Environmental Conservation.
Richard Fraser was an independent contractor working for Nationwide Mutual Insurance Company when he was fired in 1998. Although Fraser argued that he was fired for reporting illegal policies that Nationwide had implemented, Nationwide stated he was fired because he was disloyal to the company. Nationwide found that plaintiff had drafted (but not sent) two letters to two Nationwide competitors, Erie Insurance Company and Zurich American Insurance, expressing Contractors Association members' dissatisfaction with Nationwide and seeking to determine whether Erie and Zurich would be interested in acquiring the policyholders of the agents in the Contractors Association. After discovering the letters, Nationwide also searched its mail file server and found e-mails revealing company trade secrets. Fraser filed a wrongful termination suit against Nationwide, arguing that Nationwide’s accessing Fraser’s e-mail account without permission violated the Electronic Communication Privacy Act and a parallel Pennsylvania statute. The trial court granted Nationwide’s motion for summary judgment and Fraser appealed. The Third Circuit Court of Appeals affirmed the trial court’s ruling that Nationwide had access to the independent contractor’s emails. Nationwide was found to not have violated the ECPA because Nationwide had provided the independent contractor with the e-mail account, the e-mail was hosted on Nationwide’s servers, and the e-mails were acquired after transmission of the e-mails. Therefore, the court held that the e-mails were not intercepted by Nationwide. Title 1 of the ECPA prohibits the interception of e-mails, but Nationwide argued that since the e-mails were reviewed after the transmission of the e-mail, that no interception had occurred. The court agreed and found that for one to intercept e-mail, he must occur contemporaneously, at the time of the transmission. Therefore, as long as the seizure of e-mail occurs after the e-mail is transmitted, a company does not need permission to access the independent contractor’s e-mails. Salim received his B.A. in Applied Communications, with a minor in Legal Studies, from Monmouth University. He received his J.D. from Seton Hall University School of Law in 2014. Salim’s past experiences include interning for a personal injury law firm prior to attending law school, as well as judicial internships in the Civil and Family Divisions.