Production

internal software infrastructure

Optimizing Your Infrastructure for LAW & Explore eDiscovery

By: Joshua Tucker

It’s safe to say Microsoft isn’t going out of business anytime soon. Last year alone they grew 18 percent, reaching 168 billion dollars*. They are continuously making updates to their software, improving their products and functionality, and purchasing emerging software. They want to empower every person and organization on the planet to achieve more*, but the power you obtain from the software is up to you. Microsoft does not know your intended purpose or use of their software; all they can do is provide the software and the barebone requirements to make it run.

CloudNine software is no different. Let’s take a deep dive into your infrastructure and how you can optimize it with the CloudNine on-premise processing platforms.

We see that several of our clients run their environments with the most minimal recommended resources. Just like Microsoft can’t know how large your SQL server needs to be, we don’t know the level of demand your client’s data is putting on your workstation. What we DO know is that the number of files per case is growing, the complexity of files is growing, and resources are sparse.

We will cover the areas where we can make vast improvements in the efficiency in the way you are using your CloudNine software.

Your Local Area Network

Let’s use the common “business triangles” as a frame of reference. Examples would be “people, technology, and process” or “team, leadership, and mission”, or, my favorite, “price, speed, and quality”. The more your balanced business triangle, the better. Too much or not enough emphasis on one side and that balance will start to wane.

The eDiscovery version of the business triangle is called the ‘Local Area Network’. The first side of this ‘Local Area Network’ is the hardware or the backbone of your infrastructure. The second side would be the software, or the muscle needed to use that backbone. The third side is your network file server or the brain’s storage area, which will hold all the knowledge that our software is going to discover for you. And finally, the three sides are then connected, like sinew, with your local network speed.

You want to find the sweet spot that balances cost, throughput demands, speed to review, and hardware budget. Let us go ahead and call this the “Goldilocks Zone”.

Real-life case study: About 8 years ago, we were working with a client that had a few virtual machines and a few physical machines. The virtual machines were 4 core and 8GB of RAM. The physical machines were 8 core and 16GB of RAM.  IT wanted to get rid of the physical machines, but there was resistance to letting them go because they were able to process so much faster than the virtual machines. We conducted some testing to find the Goldilocks Zone between the amount of data being processed, the expected speed, and the cost. We created a few virtual machines with 4, 8, and 12 cores and ran tests to determine the correct core count for our company. We determined that an 8-core box with 16GB of RAM was able to process data much faster than a 4-core box with only 8GB of RAM.

After we completed optimizing the processing machines, we ventured forth into the other areas of our infrastructure.

Next, we reached out to our SQL team to see what would happen if we added more RAM and more SQL cores. We saw the same result. As we added more resources, we found that we were able to increase the speed on LAW’s communication with SQL. Faster communication equals a faster read/write, which equated to a faster processing speed. During this testing we also found that the more SQL cores, the more we could horizontally spread out the processing tasks on our LAW machines (i.e., we could have more machines writing to the same database).

Note: Today, I have a simple equation to determine the correct size of SQL:  Take the total number of read/write instances that can be communicating or interacting with SQL. Divide that number by three. The resulting number is the SQL cores needed. For RAM, take the same number of instances and multiply it by four.

After we completed this environment review, we had larger machines, faster read/write capability, and more machines to process on each matter. The Goldilocks Zone for SQL ensures that you have the right number of SQL cores and RAM per instances that have read/write work with SQL.

(For LAW workstations is highly suggested at 8 core and 16gb of RAM. For Explore that was 8 core and 32gb of RAM.)

Note: Your LAN does not have to be local to your office, but SQL, the LAW database folder structure and the workstations all need to be in close proximity to each other. The closer the better.

Software and Upgrades

Let’s go back to our Microsoft analogy. Microsoft keeps improving their product and each version of the operating system has the potential of changing the location or how certain files work. It is imperative that the operating system that is installed on your workstations is supported by the version of the product that you are going to use. If it isn’t, the software could act in a way that is completely unexpected – or worse.

The data we process can be a threat to our organization (and this does go for everyone!) and the best way to protect yourself is to be up to date on patches and virus software. I highly suggest that you first patch in a test environment, testing each part of the tool and making sure that the patching will not interfere with your work. The more up to date you can test, the more secure your, and your client’s, data will be.

One thing I like about the right test environment is that once your testing is done, you can make an image and deploy that image to the rest of your workstations. It is fast and efficient.

How your processing engine gets metadata to you matters. For instance, there are engines, like LAW, that will expand the files and harvest all the metadata. This type of processing is slower in getting the data in review, but much faster in the final export. There are also engines, like CloudNine Explore, that will hold off on expanding the data but harvest all the text and metadata extremely quickly. This workflow is great for ECA purposes.

How deep these tools dig into your data is also important. You never want a want privileged document produced because your processing engine did not discover it. Find out if your engine is collecting all the natives, text, and metadata that you need for these legal matters, and then come up with a workflow that will accentuate the strengths of your tool.

Having an Investment in your File Storage

The price of data storage has been coming down for years. Which is great news considering the fact that discoverable data keeps growing and will continue grow at an astounding pace. It is estimated that this past year, that each person on the planet created 1.7 megabytes of information each second. Every matter’s data size has increased and with it, the speed to review. All of this must run efficiently, all of it must be backed up, and all of it must be in your disaster recovery plans.

Network speeds matters. It ties your infrastructure together. If the processing machine can’t talk to the SQL machines quickly, or to the network storage efficiently, then it won’t perform at top speed, no matter how many cores you have. Network speed should be considered not only for the processing department, but for your whole company. We highly suggest a gigabit network, and if you are a firm or legal service provider, you might want to be looking at a 10-gigabit network.

Even with a gigabit network, your workstations, SQL server, and file server need to be local to each other. Having one data center or a or central location helps keep those resources working more effectively, getting you a higher return on investment on your machines.

Pro tip! There is a quick and easy way to test your network speed without having to contacted IT. Find a photo that is near 1mb and put it in the source location. Log into one of your workstations, open a window to that source location, and drag that image to your desktop. Then, drag it back. Both times that you move this image should be instantaneous to you. If either move takes a more than one second, then your network speed needs to be improved.

RECAP

It is our responsibility to figure out what we need to get full capacity out of outside tools. To run CloudNine’s LAW we need workstations that have at least an 8 core and 16gb RAM. For CloudNine Explore workstations, we need 8core and 32gb or RAM and SQL environment that adjusts to number of instances that are interacting with it.

Ensure that your software matches up with the recommended versions for your processing engine. If you are on or are working with an operating system that wasn’t on the list of that processing engine, we know that you could get unexpected results – or worse data. Line up the programs, test before you deploy, and stay up to date.

Know where your data is stored and the speed at which your systems talk to each other. Keep your environment in close proximity.

All in all, in order to get the top speed and performance out of CloudNine’s tools (or our third-party software your purchase), you must invest into the right resources.

Keep working towards your “Goldilocks Zone” – the sweet spot between speed, price, and quality.

If you are interested in having a CloudNine expert analyze your environment and provide recommendations for efficiencies, please contact us for a free Health Check.

 

*https://www.statista.com/statistics/267805/microsofts-global-revenue-since-2002/

* https://www.priceintelligently.com/blog/subscription-revenue-adobe-gopro-microsoft-gillette

* https://www.comparably.com/companies/microsoft/mission

* https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019?view=sql-server-ver15

 

BlueStar Accelerates Modern eDiscovery with ESI Analyst – CloudNine Podcasts

It’s a challenge to produce relevant evidence for large cases, especially when they feature non-traditional data types. JSON and PST formats simply don’t do modern data justice. The unwieldy files don’t possess threading or deduplication options. Instead, large amounts of irrelevant data are stretched across a multitude of pages and folders. Finding a team to manually review that data slows production speeds and raises discovery costs. It’s time to stop forcing a square peg into a round hole.

As the CTO and Managing Partner at BlueStar, Jeremy Schaper has seen an uptick of non-traditional data in the last five years. He and his team found CloudNine’s ESI Analyst while searching for an eDiscovery solution to process both traditional and modern data types. Jeremy joined Rick Clark for our CloudNine 360 Innovate Podcast to discuss how BlueStar leveraged ESI Analyst in large cases involving SMS, Slack, and Microsoft Teams data.
Click here to listen to the podcast and learn more.

Perin Discovery Streamlines Workflow Through ESI Analyst: CloudNine Podcasts

For legal teams, the race to production may seem never-ending. The journey begins with some data mapping to discern who owns the data and where it is located. Once the identification process is successful, legal teams are often stopped by the first roadblock. They need to find a vendor that can collect modern data types such as text messages, tweets, and videos. After the data is collected, another roadblock stands in the way. A second vendor is needed to carry out review and production. Stopping and restarting between each step is frustrating and time-consuming, yet few LSPs offer means for a continuous workflow.

Recognizing this issue, Peter Smith and Erin Perczak launched Perin Discovery to provide a one-stop shop for both digital forensics and eDiscovery. The co-founders joined Rick Clark for our 360 Innovate Podcast to explain how they leverage ESI Analyst to engage their clients in a smooth workflow. To learn how our platform has improved their data and case strategies, visit this link: https://cloudnine.com/webcasts/perin-discovery-podcast/?pg=ediscoverydaily/collection/perin-discovery-streamlines-workflow-through-esi-analyst-cloudnine-podcasts

Do’s and Don’ts of Text Message Discovery

Discovery requests of the past had little reason to include text messages as a form of evidence. Emails were the primary concern since they held the bulk (if not all) of business communications. Finding relevant corporate emails was rather simple. Corporate servers stored the data, regardless of how the email was sent or received (via mobile device or work computer). Consequently, companies were able to locate ESI without the assistance of forensic experts. As text messages became the preferred method for informal communications, their usage in the business world also grew. [1] In 2015, research showed that 80% of professionals conducted business communications through texts. This percentage has likely skyrocketed in recent years due to the shift to remote work during the pandemic. Today, some industry experts refer to texts as the new email, citing them as the main source of relevant information. Litigants, however, must remember that phone carriers aren’t obligated to permanently preserve message records. Unless subpoenaed, they may refuse to participate in discovery investigations. Instead of depending on carriers, text messages must be preserved and obtained from the device itself. [2]

Text Message Spoliation Sanctions

  • Stinson v. New York City: The plaintiffs in this suit alleged that the NYPD was issuing summonses without probable cause. The court imposed an adverse inference sanction against New York City for failing to preserve and collect relevant text evidence.
  • Timms v. LZM, LLC: Plaintiff Heather Timms sued her employer for failing to compensate her overtime hours, but she removed text messages and a messaging app before submitting her cell phone as evidence. Consequently, attorney fees were issued, and the case was terminated.
  • First Fin. Sec. Inc. v. Lee: FFS, an insurance broker, requested the production of all written communication after the defendants violated their contract by sharing company information after termination. After failing to produce text message evidence, the Court arranged attorney fees and an adverse inference sanction against the defendant. [3]

Text Message Do’s

  • Develop policies about business messaging. Some companies may go as far as banning all employees from discussing work affairs over text. Others companies may impose regulations on who and how work messages are sent. If your company permits any kind of text-based business communications, set up retention policies and collection plans. Through the policies, ensure that the data is preserved if needed for litigation.
  • Once your retention policies are established, consistently enforce them. Update your employees on any changes that the policies undergo. Poorly enforced policies are no better (and sometimes worse) than having no policy at all.
  • Train employees on how to appropriately send work texts. Also, inform them of the risks associated with deleting potentially relevant information.
  • Issue litigation holds when anticipating litigation. In the litigation hold letter, remind employees to disable any automated deletion features. Companies should also specify if message preservation is required for company devices, personal devices, or both. [4]

Text Message Don’ts

  • Rely on screenshots alone as a way to create records. Text messages can be easily manipulated, so screenshots are not enough to validate their authenticity. Find additional means of proof such as witness or expert testimony. As a better alternative, companies can find a discovery solution to produce the evidence through native or near-native files.
  • Rely on phone carriers to preserve the messages. As stated above, carriers will only store the data for short periods of time. Take ownership of your preservation duties by establishing retention policies in advance.
  • Delete messages or conversation histories when anticipating litigation.
  • Manually preserve text messages by copying and pasting them into other sources. Manual efforts include forwarding text messages to email and exporting texts to Excel files. These methods are time-consuming and harder to authenticate in court. [5]

 

[1] Nicole Allen, “Text Messages: Preservation Lessons for Mobile E-discovery,” LitSmart E-Discovery, December 20, 2017.

[2] Bill Kammer, “In eDiscovery, Texts are the New Email,” SDCBA Blawg 401, January 7, 2020.

[3] Zac Muir, “Failure to Produce Text Messages in eDiscovery,” Microfocus, October 16, 2012.

[4] Anthony J. Diana, Catherine Bernard, and Therese Craparo, “Managing The Risks And Costs Of Text Messaging (Electronic Discovery & Records Management – Tip Of The Month),” April 3, 2013.

[5] “How Federal Agencies Can Capture Text Messages for E-Discovery,” February 4, 2021.

TIFFs, PDFs, or Neither: How to Select the Best Production Format

Through Rule 34(b) of the FRCP, the requesting party may select the form(s) of production based on the needs of the case. Though this flexibility better serves the client, it also begs a few important questions: What is the best form of production? Is there one right answer? Since there are multiple types of ESI, it’s hard to definitively say that one format type is superior. Arguably, any form is acceptable so long as it facilitates “orderly, efficient, and cost-effective discovery.” Requesting parties may ask for ESI to be produced in native, PDF, TIFF, or paper files. Determinations typically consider the production software’s capabilities as well as the resources accessible to the responding party. [1] The purpose of this article is to weigh the advantages and disadvantages of each type so that legal teams can make informed decisions in the future.

Production Options

  1. Native – As the often-preferred option, native files are produced in the same format in which the ESI was created. Since native files require no conversions, they save litigants time and money. True natives also contain metadata and other information that TIFF and PDF files may lack. Litigants may also be interested in native files for their clear insights into dynamic content (such as comments and animations). TIFFs and PDFs can only process dynamic content through overlapping static images. This cluttered format is often confusing and hard to decipher. Though useful, litigants must be careful with the metadata and dynamic content because they may contain sensitive or privileged information. [2] Native files may seem like the superior choice, but they aren’t always an option. Unfortunately, some ESI types cannot be reviewed unless they are converted into a different form. Additionally, reviewers utilizing this format are unable to add labels or redactions to the individual pages.
  2. TIFF – TIFFs (tagged image format files) are black and white, single-paged conversions of native files. Controllable metadata fields, document-level text, and an image load file are included in this format. Though TIFFs are more expensive to produce than native files, they offer security in the fact that they cannot be manipulated. Other abilities that differentiate TIFFs include branding, numbering, and redacting information. [3] To be searchable, TIFFs must undergo Optical Character Recognition (OCR). OCR simply creates a text version of the TIFF document for searching purposes.
  3. PDFs – Similar to TIFFs, PDFs also produce ESI through static images. PDFs can become searchable in two ways. The reviewer may choose to simply save the file as a searchable document, or they can create an OCR to accompany the PDF. However, OCR cannot guarantee accurate search results for TIFFs or PDFs. [1] Advocates for PDFs cite the format’s universal compatibility, small file size, quick download speeds, clear imaging, and separate pages. [4]
  4. Paper – As the least expensive option, paper production may be used for physical documents or printing digital documents. Many litigants prefer to avoid paper productions because they don’t permit electronic review methods. All redactions and bates stamps must be completed manually. This may be okay for a case that involves a small amount of ESI. However, manually sorting and searching through thousands of documents is time-consuming and exhausting. Litigants who opt for this format also miss out on potentially relevant metadata. [3]

 

[1] Clinton P. Sanko and Cheryl Proctor, “The New E-Discovery Battle of the Forms,” For The Defense, 2007.

[2] “Native File,” Thomas Reuters Practical Law.

[3] Farrell Pritz P.C. “In What Format Should I Make My Production? And, Does Format Matter?” All About eDiscovery, May 30, 2019.

[4] “PDF vs. TIFF,” eDiscovery Navigator, February 13, 2007.

Increasing Your Technological Competence, Part 1

From the CloudNine family to yours, we wish you a wonderful holiday season! As a gift of knowledge, this article will focus on defining and maintaining high levels of technological competence. To effectively represent their clients, a lawyer must actively update their knowledge on legislative changes. The American Bar Association referred to this skill in Rule 1.1 as “competence.” The rule originally called for lawyers to possess the “legal knowledge, skill, thoroughness and preparation reasonably necessary for the representation.” [1] In 2012, the ABA expanded the definition through an amendment concerning technological competence. According to Matthew Knouff from ESI Survival Guide, 39 states adopted this rule in some form by March 2021. South Dakota, Rhode Island, Oregon, New Jersey, Nevada, Mississippi, Maryland, Maine, Hawaii, Georgia, and Alabama are the main exceptions to this trend. [2] Though Rule 1.1’s amendment laid out the framework, it didn’t provide instructions on how lawyers should build their technological competence. To achieve this duty, the California Bar committee issued an opinion, outlining 9 necessary skills. Since this opinion was crafted through examinations of federal cases, these skills could be applicable to various states.

Explanations of the First Five Skills

  1. Initially assess e-discovery needs and issues, if any.

In fear of the cost and rules of e-discovery, some lawyers try to avoid the practice altogether. By doing so, lawyers disadvantage their clients by missing out on relevant ESI. Instead of yielding to eDiscovery trepidation, conduct an initial assessment to determine the cost, timeframe, and data types needed for the investigation. Consider the value of the claims in comparison with the costs of processing and production. Determining which data types must be collected and how much time is allotted for the process. These examinations can act as a starting point in assessing the proportionality of the production request.

  1. Implement or cause to implement appropriate ESI preservation procedures.

To accomplish this skill, lawyers should acquaint themselves with their client’s IT setup. Once the preservation responsibilities have been established, clients and custodians should be informed with clear, written instructions. It’s important to follow up with clients and custodians to ensure that they are complying with the preservation requirements to avoid spoliation sanctions. If requesting ESI from opposing counsel, send a preservation letter that identifies what data should be preserved and where it can be found.

  1. Analyze and understand a client’s systems and storage.

Get familiar with your client’s IT environment and staff. It’s beneficial to request data maps of complex systems and speak directly to the IT staff. Through this knowledge and ease in communication, lawyers will gain a better sense of where relevant ESI may lie. After determining the location of the data, one can access how difficult and/or expensive it will be to access the information.

  1. Advise the client about available options for collection and preservation of ESI.

The scope and cost of preservation might be huge when dealing with larger companies due to their larger volumes of data and longer lists of custodians. However, lawyers should not concern themselves with burdensome collections unless the information is proportional to the case. During Rule 26(f) conferences, consult opposing counsel on the scope of discovery in relation to the costs of collection and production. If the parties determine that the discovery request is disproportional, seek guidance from the court.

  1. Identify custodians of relevant ESI.

After identifying the custodians who possess relevant data, categorize the list into two categories: primary custodians and secondary custodians. As the terms suggest, primary custodians have more direct involvement with the information than secondary custodians. To save money, counsel can decide to initially search for primary custodians within a limited time frame. If necessary and proportional, the search can be expanded to encompass secondary custodians. [3]

 

[1] Model Rules of Professional Conduct Rule 1.1

[2] Matthew Knouff, “How to Gain & Maintain Technology Competence — Element 1: Education — Part 1 of 3,” March 30, 2021.

[3] Hon. Joy Flowers Conti and Richard N. Lettieri, “E-Discovery Ethics: Emerging Standards of Technological Competence,” The Federal Lawyer, 2015.

Assessing the Proportionality of Modern Data Types

The Costs of eDiscovery

As time passes, the definition of electronically stored information (ESI) must expand to accommodate emerging data types. As discussed in our recent article, (Don’t Get Spooked by Communication Applications!), these changes can be intimidating and uncomfortable for some legal teams. Since modern data types are unavoidable in eDiscovery, litigators must adapt and address any subsequent challenges. Financing the production of newer ESI types is a looming concern for many firms. From a financial perspective, each gigabyte of reviewed data costs about $18,000. [1] Meanwhile, 300 million photos are posted to social media every day, and 16 million texts are sent every minute. [2] In addition to paying for production, responding parties must  have adequate access and resources to manage the information. If responding parties cannot juggle these duties, they should speak with the judge and requesting party about the proportionality of the evidence.

Proportionality and Amendments to Rule 26(b)(1)

Before requesting the production of digital evidence in a legal trial, the proportionality of said evidence must be evaluated. In other words, the costs and benefits of production must be weighed. Proportionality is far from a new concept in eDiscovery. Most of its factors and considerations were first added to Rule 26(b)(1) of the FRCP in 1983. On December 1, 2015, the rule was amended slightly to require that the scope of discovery be “proportional to the needs of the case.” [3] Six factors should be considered when evaluating the proportionality of ESI:

  • The importance of the issues at stake in the action – This guideline measures the importance of the non-monetary losses or gains that a party might acquire due to a case (i.e. time, resources).
  • The amount of controversy – This guideline focuses on the money that a party may gain or lose.
  • The parties’ access to relevant information – The need for a formal discovery is determined based on a party’s access (or lack thereof) to relevant information.
  • The parties’ resources – A party’s technological, administrative, and human resources are assessed to determine if they are capable of handling the discovery process.
  • The importance of the discovery in resolving the issues – This guideline relates to the discovery’s importance in resolving the case.
  • Whether the burden or expense of the proposed discovery outweighs its likely benefit – The burdens and benefits of discovery are compared. There is no fixed ratio to determine the proportionality. [4]

Proportionality Best Practices

  • Parties should engage in discovery planning early on. Discussions on the relevance and proportionality of the request should be held as soon as possible.
  • Prior to Rule 26(f), meet in person (or over the phone) to develop a discovery management plan.
  • Ask the judge to hold Rule 16(b) case-management conferences.
  • If you anticipate proportionality disputes or the production of voluminous data, start the discovery process by producing the most accessible and relevant information . [4]

 

[1] Patrick E. Gaas and Tiffany Harrod, “How to Proactively Control E-discovery Costs,” Tech Brief, AGC of America.

[2] Bernard Marr, “How Much Data Do We Create Every Day? The Mind-blowing Stats Everyone Should Read,” Forbes, May 21, 2018.

[3]Rule 26. Duty to Disclose; General Provisions Governing Discovery,” Legal Information Institute, Cornell Law School,

[4] Bolch Judicial Institute, “Guidelines and Best Practices for Implementing the 2015 Discovery Amendments Concerning Proportionality,” Third Edition, 2021.

Investing in the Future: Release Highlights for CloudNine LAW & Explore 7.6

As a dedicated eDiscovery provider, CloudNine is committed to providing our network partners and legal clients with efficient software solutions. Advancements to our innovative technologies are largely due to client feedback and support.

After hearing your feedback on the need to expedite document conversion while also reducing cost and dependency on 3rd party applications, we are eager to announce the latest updates to CloudNine LAW and Explore 7.6.  With more than 200 feature updates and enhancements, the leading applications for early case assessment and processing are equipped to process today’s prodigious volumes of data and accelerate your review and production speeds.

By utilizing a robust ingestion engine, LAW and Explore maximize the processing power of a single computer.

As the primary highlight of LAW 7.6, the new Turbo Imager produces static images of native files up to eight times faster than the traditional imaging module.  By reducing client dependency on native applications, Turbo Imager provides on-demand scalability and workflow efficiency. If available, the tool will utilize multiple processing cores to expedite document conversion time. Turbo Imager will be offered together with Turbo Import licenses. For each license of Turbo Import, CloudNine clients will also receive a license of Turbo Imager or vice versa.

Improved reporting capabilities in  Explore 7.6 provide greater visibility into case metrics, such as original source file counts and sizes, as well as filtered file counts and sizes.. Rather than creating additional copies of data during ingestion, Explore reads and extracts metadata and text from the source, leaving it in place.  After searching and culling, clients may create copies when they are ready to export the information for review. This improvement reduces security risks by minimizing the number of identical files that need to be managed. The reduction in data volumes also decreases review time and expenses by as much as 70%. Additionally, Explore’s Import Library has improved its analysis abilities by recognizing more file types and email components.

To learn more and see a live demonstration, register to view the webinar:  Investing in the Future:  LAW and Explore ver. 7.6 Release or click to request a demonstration.

 

Investing in the Future: Release Highlights for CloudNine LAW & Explore 7.6
Investing in the Future: Release Highlights for CloudNine LAW & Explore 7.6 150 150 CloudNine

Don’t Get Spooked by Communication Applications!

Since Halloween is approaching, it’s time to reflect on a scary part of the discovery process: handling communication applications. As a newer form of digital evidence, communication apps can be a legal team’s worst nightmare. Ephemeral messaging apps like Wickr and Signal make conversations disappear like ghosts in the night. Slack and Microsoft Teams have sunk their teeth into the communications of most corporations. Social media apps have entranced us with a spell, prompting our fingers to type a new DM or tweet every other hour. It’s easy to view these applications as monsters in the discovery process. They have revolutionized the world of e-discovery, expanding it to more than just emails and electronic files.  Whether you love them or hate them, communication apps aren’t going anywhere. In fact, their popularity is only rising. Approximately 2.5 billion people use at least one messaging app on their mobile devices. This number is expected to reach 3 billion by the end of next year. [1] Here’s another chilling statistic: in 2020, 41 million application messages were sent every minute. The volume of communication app data is frighteningly large, but its relevance is undeniable. Regardless of case type, (criminal, personal injury, defamation, etc.) litigants should consider its production. Within each channel and group chat lies a plethora of information that could make or break a case. Still afraid? Here’s a list of challenges and solutions for managing communication applications.

Understanding the missing context:

Messages sent on communication applications are often short and sent with little context. Bits and pieces of conversations might be spread out across multiple platforms and group chats. When handling a case, legal teams should identify all relevant communication platforms to connect the missing dots. Litigants should also consider deriving context from atypical sources such as emojis, liked messages, images, and GIFS. [2] These humorous icons and features can reflect the sender’s tone, a difficult thing to gather over text. Remember, images and emojis aren’t supported in all native file types, so it’s important to find an eDiscovery provider that will reconstruct the conversations. [3]

Managing large volumes of data:

Producing and reviewing voluminous data is stressful, time-consuming, and expensive. By creating comprehensive retention policies, businesses can proactively determine which data types and channels should be preserved. Within the policies, companies should outline the procedures for labeling, storing, and deleting records. [4] The deletion of unneeded data lowers the risk of massive data accumulation.

Remembering each application’s retention policies:

Applications like Slack and Microsoft Teams will retain all messages unless configured otherwise. Similarly, Facebook, Instagram, and Messenger store data until the account has been deleted. [5] If the account owner deletes or unsends a message, the data will still show on the recipient’s phone. Some of these platforms contain “Recently Deleted” features that make recovery much easier. The policies for collaboration and social media applications are rather straightforward. Ephemeral messaging apps are a bit different; however, the auto-deletion features can be adjusted to the user’s discretion. Auto-deletion settings should be turned off during or in anticipation of litigation.

 

[1] Damjan Jugovic Spajic, “Text, Don’t Call: Messaging Apps Statistics for 2020,” Komando Tech, December 11, 2019.

[2] Erin Tomine, “Chat Messages and eDiscovery: How to Ease the Burden and Get the Full Picture,” Conduent, July 7, 2021.

[3] Matthew Verga, “Discovery from Slack: It’s Complicated,” Xact Data Discovery, June 19, 2020.

[4] Law Offices of Salar Atrizadeh, “Electronic Discovery and Data Retention Policies,” Internet Lawyer Blog, May 18, 2020.

[5] “Data Policy,” Instagram Help Center, 2021.