Request for Documents
The Request for Documents
Recent developments concerning mutual disclosure of documents
Rule 26(a)(1) of the Federal Rules of Civil Procedure (FRCP) requires mutual disclosure of all documents, electronically stored information (ESI), and tangible things that the disclosing party has in its possession, custody, or control, without waiting for a discovery request.
This includes information that the disclosing party may use to support its claims or defenses.
"Possession, custody, or control" signifies that the party either physically holds the items or has the legal right to obtain them from a third party.
These initial disclosures must be made within 14 days after the initial conference between the parties (often referred to as the Rule 26(f) conference or "meet and confer").
The primary purpose of these early disclosures is to streamline the discovery process by ensuring parties exchange fundamental information at the outset of the litigation.
Mutual Disclosures and ESI
Mutual disclosures under Rule 26(a)(1) specifically encompass electronically stored information (ESI).
ESI refers to data that is created, stored, and retrieved in electronic format. Its scope is extremely broad and includes:
All relevant items of ESI found in any electronic device, not just those commonly thought of as traditional computers (e.g., desktops, laptops).
This may include data from personal devices like smartphones, tablets, external hard drives, USB drives, and cloud storage accounts.
Examples of ESI include emails, text messages, voicemails, instant messages, social media posts, website data, databases, spreadsheets, word processing documents, presentation files, and even metadata embedded within these files.
The intent is to ensure that all relevant digital information is exchanged without waiting for a specific discovery request, streamlining the litigation process by revealing fundamental digital evidence early on.
The sheer volume and diverse formats of ESI present significant challenges in discovery, often necessitating specialized expertise for identification, preservation, collection, review, and production.
Alternative methods of requesting documents
Deposition duces tecum
A deposition that requires a witness (deponent) to bring specified documents, ESI, or other tangible evidence to the deposition, in addition to providing oral testimony.
Subpoena duces tecum for a nonparty to produce documents: This is used to compel a non-party to produce documents or ESI for inspection and copying, often without requiring their oral testimony in a deposition.
Interrogatories
Written questions sent by one party to another, which must be answered under oath.
While primarily for eliciting factual information, interrogatories can be used to identify the existence, location, and custodians of relevant documents and ESI, paving the way for targeted document requests.
Requests for documents is the most effective and efficient way to obtain documents directly from an opposing party, specifically designed for document production under Rule 34 FRCP.
Legal holds and the duty to preserve evidence including ESI
A "legal hold" (also known as a "litigation hold" or "preservation order") is a directive issued by a party's legal counsel to relevant employees, instructing them to preserve all potentially relevant documents and ESI generated, received, or stored by them.
This duty arises when a party anticipates litigation and is crucial to prevent spoliation of evidence.
What triggers a litigation hold?
The duty to preserve evidence is triggered when a party knows or reasonably should know that evidence may be relevant to anticipated litigation. This is a crucial threshold issue in discovery.
Common trigger events include receiving a demand letter, filing a lawsuit, public announcements of regulatory investigations, or even a credible threat of litigation.
Managing the litigation hold process
This involves identifying key custodians of information, specifying the scope of documents and ESI to be preserved, communicating the hold effectively, monitoring compliance, and releasing the hold once litigation concludes or is definitively averted.
Trigger events and adverse inferences
Standard: When a party knew or should have known litigation is imminent.
Failure to implement or properly manage a legal hold after a trigger event can lead to spoliation of evidence, which may result in severe sanctions, including adverse inference instructions (i.e., the jury is told to assume the destroyed evidence was unfavorable to the party), monetary fines, or even dismissal of claims or defenses.
Preliminary Decisions Regarding Requests for Documents
Timing of the request
Before deposition: Requesting documents before a deposition allows the examining attorney to review pertinent evidence and prepare more focused questions. This can help to identify key issues, assess the deponent's credibility, and uncover additional lines of inquiry based on the produced documents. It ensures the attorney is fully informed about the documentary evidence related to the deponent's expected testimony.
After deposition: Requesting documents after a deposition might occur when new information or potential document custodians are identified during the testimony. This approach can be useful for following up on specific statements made by the deponent or for seeking documents that were previously unknown or deemed irrelevant until the deposition revealed their significance. It allows for targeted discovery based on sworn testimony.
The decision often depends on the strategy of the requesting party, the nature of the case, and the anticipated scope of the deponent's knowledge regarding documents.
Approaches to Document Production
Organizing and formatting documents
Warehouse approach: This method involves producing all documents in their original disorganized state, often in large batches, without specific sorting or indexing. It can be cost-effective for the producing party in the short term, but may place a significant burden on the requesting party to sort through potentially millions of documents to find relevant information. This approach is often used when there is a very large volume of documents and the producing party wants to shift the organizational burden to the requesting party.
Comprehensive approach: In this approach, the producing party undertakes a detailed review, organization, and indexing of all relevant documents before production. Documents are typically Bates-stamped, categorized, and often accompanied by a privilege log and an index. This method is more time-consuming and expensive for the producing party but provides a more streamlined and usable production for the requesting party, often facilitating easier review and use in litigation.
Limited approach: This approach involves producing only a select subset of documents that are clearly and narrowly responsive to specific requests, often after a contested negotiation regarding the scope of discovery. The producing party aims to minimize disclosure to only what is absolutely necessary, which can lead to disputes and motions to compel if the requesting party believes broader discovery is warranted.
Number of documents: The sheer volume of documents involved in a case significantly influences the chosen approach. Cases with a small number of documents might allow for more focused, manual review, while cases with millions of documents often necessitate the use of technology-assisted review (TAR) and a more strategic approach to production, such as sampling or phased discovery.
Volume of ESI: The amount of electronically stored information (ESI) presents unique challenges due to its diverse formats, location across various devices and systems, and the potential for metadata. High volumes of ESI often require specialized forensic experts, e-discovery platforms, and advanced analytical tools like predictive coding to effectively manage the review and production process while ensuring data integrity and compliance with discovery obligations.
ESI and the Document Request
Three types of discoverable ESI
ESI based on the configuration of the computer system: This refers to data whose discoverability is influenced by the software and hardware setup, operating systems, applications, and network configurations. Understanding these configurations helps in identifying where relevant ESI might reside and how it can be accessed.
ESI based on the nature of the evidence itself: This category focuses on the intrinsic characteristics of the data, such as its format (e.g., text document, spreadsheet, email, video, audio), its content, and its potential relevance to the legal matter. Different data types require different preservation and review strategies.
ESI based on its storage status: This classifications depends on how and where the ESI is stored, which directly impacts its accessibility and the cost of retrieval.
Active data: Information readily available and regularly used by a system or user (e.g., current files on a hard drive, live database entries). This is generally the easiest and least expensive to access.
Inactive data: Data that is no longer actively used but remains on a system and is still relatively accessible (e.g., old project files, archived documents on a server).
Back-up data: Copies of data made for disaster recovery or archival purposes, often stored on tapes, external drives, or in the cloud. Retrieving ESI from backups can be complex, time-consuming, and costly, as it often requires restoration to an operational system.
Legacy data: Data stored on outdated systems, in obsolete formats, or on old media (e.g., floppy disks, older operating systems). Accessing legacy data can present significant technical challenges and expense due to hardware and software obsolescence.
Ephemeral data: Data designed to exist only for a short period, such as instant messages, temporary files, or data in RAM. Preserving ephemeral data for discovery is particularly challenging and often requires immediate action or specialized forensic techniques.
Document production requests and computer systems
When requesting ESI, understanding the opposing party's computer systems (e.g., operating systems, enterprise software, network topology, data retention policies) is crucial. This knowledge informs targeted requests and helps identify potential sources of relevant ESI, including custodian-specific devices, shared network drives, and application-specific data stores.
Want ESI produced?
Hire an expert! Due to the technical complexities of ESI, including its diverse formats, storage locations, and the need for proper preservation and collection, e-discovery experts or forensic specialists are often indispensable. They can assist in identifying relevant ESI, managing data integrity, ensuring defensible collection, and navigating technical hurdles.
Document production requests and storage of ESI
Cloud storage, ESI owners, and ESI centers: ESI stored in cloud services (e.g., Dropbox, Google Drive, Microsoft 365, AWS) presents unique challenges. Identifying the actual 'owner' of the data in the cloud, understanding the terms of service, and knowing the location of the data centers (which may be in different legal jurisdictions) are critical. Requesting parties must address how to access data from third-party cloud providers, often requiring cooperation from the ESI owner.
The chain of custody and e-forensics: Maintaining a strict chain of custody for ESI is vital to ensure its authenticity and integrity. E-forensics involves the systematic collection, preservation, analysis, and presentation of ESI in a manner that adheres to legal standards, ensuring that data has not been altered or compromised from the time it was collected until its presentation in court.
The expense involved in the retrieval of ESI
The retrieval of ESI can be significantly expensive due to several factors: the sheer volume of data, the need for specialized software and hardware, the involvement of forensic experts, the costs associated with data processing (e.g., de-duplication, de-NISTing, indexing), review by legal teams, and the challenges of managing proprietary or legacy systems.
Predictive coding and the ESI production revolution
Predictive coding (also known as Technology-Assisted Review or TAR) utilizes machine learning algorithms to assist in the review of large volumes of ESI. Attorneys train the system by coding a sample set of documents as relevant or irrelevant, and the system
Protection of Documents
The attorney-client privilege
Protects confidential communications between an attorney and their client made for the purpose of obtaining or providing legal advice.
Key elements include: a communication, made between privileged persons (attorney, client, or their representatives), in confidence, for the purpose of rendering or obtaining legal assistance.
The privilege belongs to the client and can only be waived by the client.
The work product privilege
Protects materials prepared by an attorney (or their agent) in anticipation of litigation or for trial.
Distinct from attorney-client privilege, it aims to prevent one party from free-riding on the investigative efforts of the opposing party's attorney.
It distinguishes between "ordinary" work product (which may be discoverable upon a showing of substantial need and inability to obtain equivalent without undue hardship) and "opinion" work product (mental impressions, conclusions, opinions, or legal theories of an attorney, which receive heightened protection and are rarely discoverable).
Federal Rules of Evidence—Rule 502
Addresses the inadvertent disclosure of privileged or work product protected information.
Rule 502(b) states that an inadvertent disclosure does not operate as a waiver 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 (e.g., requesting return of the material).
Rule 502(d) allows federal courts to enter an order that the privilege or protection is not waived by disclosure in the litigation, which is binding on all persons and federal and state proceedings.
Additional privileges:
Common interest
Allows parties with a shared legal interest to share privileged information without waiving applicable privileges, even if they are not co-parties in litigation.
The common interest must be legal in nature, not merely commercial or financial.
Medical privilege
Protects confidential communications between a patient and their healthcare provider (e.g., doctor, psychologist) for the purpose of diagnosis or treatment.
The scope and existence of this privilege can vary significantly by jurisdiction.
Confessor-penitent privilege
Protects confidential communications made by an individual to a clergy member in their professional character or role as a spiritual advisor.
The communication must be made in confidence and for the purpose of seeking spiritual counsel or absolution.
Protection of Documents/Objections
Overbroad and duplicate requests
These are common objections raised when a document request seeks information that is excessively broad in scope, unduly burdensome, or has already been produced. An overbroad request may not be reasonably calculated to lead to the discovery of admissible evidence, while duplicate requests can be harassing and inefficient, leading to unnecessary effort and expense for the responding party.
Inadmissible and irrelevant evidence
Parties may object to requests for documents or ESI that are irrelevant to the claims or defenses in the litigation or are clearly inadmissible under the Federal Rules of Evidence. Discovery is limited to non-privileged matter that is relevant to any party's claim or defense and proportional to the needs of the case.
Confidentiality agreements and protective orders
To address concerns about sensitive or proprietary information, parties often enter into confidentiality agreements or seek protective orders from the court. These legal mechanisms establish rules for how confidential documents and ESI will be handled, produced, and used during litigation, preventing their disclosure to unauthorized third parties and mitigating potential harm.
Format objections to document requests
Objections may arise concerning the specific format in which documents or ESI are requested (e.g., native format, TIFF, PDF, searchable text). Rule 34(b)(2)(E) of the FRCP allows a requesting party to specify the format for ESI, but the responding party can object if the requested format is unduly burdensome or not reasonably usable. If no format is specified, ESI must be produced in a form in which it is ordinarily maintained or in a reasonably usable form.
Inadvertent production of documents
This refers to the accidental disclosure of privileged or work product protected documents during discovery. As outlined in Federal Rule of Evidence 502(b), such an inadvertent disclosure does not operate as a waiver if: (1) the disclosure is inadvertent; (2) the holder of the privilege took reasonable steps to prevent disclosure; and (3) the holder promptly took reasonable steps to rectify the error.
Inadvertent production of electronically stored information
Similar to physical documents, ESI can also be inadvertently produced. Given the volume and complexity of ESI, the risk of inadvertent disclosure is high. Rule 502 is particularly relevant here, providing a safeguard against waiver of privilege or protection for ESI that is accidentally disclosed, provided the specified conditions are met. Courts can also issue Rule 502(d) orders to prevent waiver for disclosed ESI in future proceedings.
Requesting the Production of Documents
Form and Content of the Request
Title of the document and introductory paragraph: The request should begin with a clear title identifying it (e.g., "Plaintiff's First Request for Production of Documents to Defendant John Doe"), followed by an introductory paragraph. This paragraph typically cites the relevant rule (e.g., Federal Rule of Civil Procedure 34) and states the general purpose of the request, which is to obtain discoverable documents, ESI, or tangible things in the responding party's possession, custody, or control.
Definitions: It is crucial to include a section defining key terms used throughout the request (e.g., "document," "electronically stored information" or "ESI," "communication," "you/your," "identify"). These definitions ensure clarity and prevent ambiguity, ensuring both parties understand the scope and meaning of the terms uniformly. This helps avoid later disputes over interpretation.
Instructions: This section provides specific guidelines on how the responding party should produce the requested items. Instructions might cover aspects such as:
The deadline for response (usually 30 days from service, per Rule 34(b)(2)(A)).
The required format for ESI production (e.g., native format, TIFF with searchable text).
Requirements for organizing documents (e.g., produced as they are kept in the usual course of business or organized to correspond to the requests).
The need for a privilege log for any withheld documents.
Procedures for addressing objections.
Documents requested: This comprises the specific, enumerated requests for documents or ESI. Each request should be drafted with sufficient particularity to enable the responding party to identify what is being sought. The requests should be relevant to the claims or defenses in the litigation and proportional to the needs of the case. Examples include requests for contracts, correspondence, financial records, emails, text messages, and internal memos related to specific issues.
Final responsibility in drafting the request
Attorney: While legal support staff (like paralegals) often assist in drafting discovery requests, the attorney bears the ultimate legal and ethical responsibility for ensuring that the request complies with all applicable rules (e.g., FRCP), is legally sound, is reasonable in scope, and is strategically appropriate for the case. The attorney must review, approve, and sign the discovery requests.
Motion to compel
A motion to compel is a formal application to the court requesting an order that an opposing party must either respond to outstanding discovery requests (like document requests) or provide more complete or appropriate responses. It is typically filed when a party fails to comply with discovery obligations, provides evasive or incomplete answers, or raises improper objections. Before filing, the moving party usually must certify that they have conferred or attempted to confer in good faith with the opposing party to resolve the dispute without court intervention, as required by Rule 37(a)(1).
Reviewing the documents of the opposing party
Once documents, ESI, and other tangible things are produced by the opposing party, a thorough review process is undertaken. This often involves:
Initial sorting and categorization: Organizing documents by date, custodian, document type, or subject matter.
Relevance determination: Identifying documents that are directly relevant to the claims, defenses, or specific issues in the case.
Privilege review: Ensuring that no privileged or work product protected information was inadvertently produced by the opposing party or identifying any such materials that might give rise to a clawback request.
Indexing and coding: For large productions, documents may be indexed and coded in review platforms to facilitate searchability, categorize responsiveness, and identify key documents.
Analysis: Identifying critical evidence that supports or refutes claims, preparing for depositions by cross-referencing testimony with documents, and using documents to support motions or trial exhibits. This systematic review is crucial for building the case and preparing for trial.
Responding to a Request for Documents
Determining a target date
Establishing a target date for document production is critical for managing timelines and ensuring compliance with discovery deadlines set by court rules (e.g., days from service under Federal Rule of Civil Procedure 34(b)(2)(A)) or by the court itself. This date must account for the volume and complexity of the ESI and physical documents, the time needed for collection, review, and privilege assertions, and the resources available (personnel, technology, experts). Setting a realistic target date prevents last-minute rushes and potential sanctions.
Categorizing the documents
Effective categorization is essential for managing the potentially vast array of documents and ESI. This involves initial sorting based on various criteria:
Custodian: Grouping documents by the individual(s) who possessed or created them.
Date range: Organizing documents chronologically.
Document type: Separating emails, spreadsheets, contracts, presentations, etc.
Subject matter: Grouping by topic or specific issues in the litigation.
Relevance: Identifying documents directly related to claims or defenses.
Privilege: Segregating potentially privileged documents for further attorney review and logging.
This systematic sorting aids in streamlining the review process, identifying key evidence, and preparing logs for privileged materials.
Involving the client in document production
Client cooperation is paramount for efficient and accurate document production, as they are the primary source of the information.
Requirements imposed by the Sarbanes-Oxley Act (SOX): Although primarily impacting public companies, SOX emphasizes the importance of robust internal controls and accurate record-keeping. In the context of document production, this means companies are often more prepared with organized data and established retention policies, facilitating the litigation process. Non-compliance with SOX can result in severe penalties, underscoring the need for meticulous document management.
Making document production a joint effort with the client: The legal team and client must collaborate closely. The client provides institutional knowledge of where relevant information resides (data custodians, systems, physical files), while the legal team guides them on legal obligations (preservation, scope of discovery, privilege). This partnership ensures comprehensive collection and accurate responses to discovery requests.
Selecting a client’s representative for document production: Designating a dedicated client representative (e.g., a paralegal, IT manager, or in-house counsel) who understands the company's data architecture and is knowledgeable about the litigation's issues is crucial. This representative acts as the primary liaison between the legal team and relevant client departments, coordinating data collection, answering questions, and ensuring internal compliance with legal hold directives.
Organizing the Document Production
After collection, documents and ESI must be meticulously organized for review and production:
Controlling the documents: Maintaining a strict chain of custody and secure storage for all collected documents and ESI is vital. This prevents spoliation (loss or alteration of evidence), ensures data integrity, and safeguards against unauthorized access. Digital files should be stored on secure servers with audit trails, and physical documents in locked facilities.
Copying and printing the documents: For physical documents, copies are often made for working sets, while originals are carefully preserved. When ESI is converted to static formats (e.g., TIFF or PDF), the process must ensure accuracy and completeness, capturing all data (including metadata) as required.
Scanning the documents: Physical documents are often scanned and converted into searchable digital formats. This enhances accessibility, reduces physical storage needs, and allows for efficient electronic review and searching using e-discovery tools. High-quality scanning with Optical Character Recognition (OCR) is essential for full-text searchability.
Numbering the documents: Bates numbering (a unique, sequential numbering system) is applied to every page of every document produced. This ensures each document has an indelible, identifiable mark, facilitating easy reference in pleadings, depositions, and trial exhibits. It also helps track documents if they are inadvertently separated from their original sets.
Reviewing, labeling, and filing documents before removal: Before being produced, all documents undergo a thorough review for relevance, responsiveness, and privilege. Documents are labeled according to their status (e.g., relevant, privileged, confidential, non-responsive). A privilege log is created for all withheld documents, detailing the basis for the claim of privilege. Finally, documents are filed or organized for production in the agreed-upon format, often electronically via a secure e-discovery platform, ensuring a defensible and organized production.
Organizing and Indexing the Documents After Production
Indexing the documents after production is a crucial step after documents have been collected, reviewed, and produced. This process enhances the usability and retrievability of the documents throughout the litigation, from depositions to trial. Key indexing fields include:
Document number: This refers to the unique identifier assigned to each document, typically through Bates numbering. Bates numbers ensure every page of every produced document has an indelible, sequential identifier, which is invaluable for referential accuracy in pleadings, motions, depositions, and trial exhibits. It helps in tracking, citing, and distinguishing documents systematically.
Date: The date of the document’s creation, modification, or transmission is fundamental for establishing timelines and understanding the chronological development of events. This can include precise timestamps for ESI.
Author: Identifying the individual or entity who created or originated the document helps in understanding the source of information, assessing credibility, and connecting documents to specific custodians and their roles in the case.
Recipient: Listing the individuals or entities to whom the document was sent or distributed is vital for tracing the flow of information, establishing knowledge, and identifying all parties aware of particular facts or events. For emails, this includes 'To,' 'Cc,' and 'Bcc' fields where available.
Document type: Categorizing documents by their inherent nature (e.g., email, memorandum, contract, spreadsheet, presentation, text message, voicemail, internal report) aids in organizing and filtering large datasets, allowing legal teams to quickly locate specific kinds of information.
Brief summary of content: A concise overview of the document's subject matter or key points. This summary is invaluable for quick triage and recall, especially when dealing with hundreds or thousands of documents, enabling legal professionals to rapidly determine a document's relevance without a full re-read.
Key Issues/Topics: Indexing documents by the specific legal or factual issues they relate to (e.g., contract breach, product defect, specific date range of dispute, witness testimony topic) allows for granular searching and the creation of focused sets for different aspects of the case or for specific lines of inquiry during depositions.
Responsiveness/Privilege Status: Indicating whether a document is responsive to a request, non-responsive, or withheld based on privilege (e.g., attorney-client privilege, work product) or other protections (e.g., confidential, proprietary) is essential for compliance and strategically managing document review.
Inspection of Property
Rule 34—Inspection of Property
Federal Rule of Civil Procedure 34 governs requests for inspection of documents, electronically stored information (ESI), and tangible things. It specifically allows a party to request another party to:
Produce and permit the requesting party or its representative to inspect, copy, test, or sample the following items in the responding party’s possession, custody, or control:
Any designated documents or ESI, including writings, drawings, graphs, charts, photographs, sound recordings, images, and other data or data compilations stored in any medium from which information can be obtained either directly or, if necessary, after translation by the responding party into a reasonably usable form.
Any designated tangible things.
Permit entry onto designated land or other property possessed or controlled by the responding party, so that the requesting party may inspect, measure, survey, photograph, test, or sample the property or any designated object or operation on it.
The scope of Rule 34 is broad, covering not only physical documents and ESI but also real property, making it a powerful tool for obtaining non-testimonial evidence.
Obtaining an inspection
Informally by letter
Often, parties will first attempt to arrange an inspection informally through a letter or other communication between counsel. This approach can be more flexible, less adversarial, and potentially more efficient and cost-effective than formal discovery requests.
An informal request might outline the items or property to be inspected, propose dates and times, and discuss any specific conditions (e.g., presence of experts, methods of inspection).
Informal agreements can avoid the formalities and strict deadlines of Rule 34, provided both parties are willing to cooperate.
#### Demand for inspection
If informal attempts fail or if a party prefers a formal approach, a Request for Production of Documents, ESI, or Tangible Things, or for Entry Upon Land is served under Rule 34.
This formal demand must:
Describe with reasonable particularity each item or category of items to be inspected.
Specify a reasonable time, place, and manner for the inspection and any related acts.
For ESI, specify the form or forms in which ESI is to be produced.
The demand ensures that the requesting party's rights are legally enforceable and establishes a clear legal obligation for the responding party.
Responding to demand for inspection
The party receiving a Rule 34 request must respond in writing within days after being served, unless the parties agree to a different timeline or the court orders otherwise.
The response must state for each item or category:
That inspection and related activities will be permitted as requested; or
An objection to the request, including the reasons for the objection. Common objections include overbreadth, undue burden, privilege (e.g., attorney-client privilege, work product), or irrelevance.
A statement that the party will produce documents or ESI in a specific alternative form. If an objection is raised to the requested form of ESI production, the responding party must state the form or forms in which it intends to produce the ESI.
When producing documents, the responding party must either:
Produce them as they are kept in the usual course of business; or
Organize and label them to correspond to the categories in the request.
A party objecting to an inspection must clearly articulate the basis for the objection, and if only part of a request is objectionable, the unobjectionable part must still be produced.
Failure to respond or provide a proper response can lead to a motion to compel under Rule 37.
ESI and On-Site Inspections
Goals of the on-site inspection protocol for ESI
Retrieve and preserve all ESI relevant to the case: The primary goal is to ensure that potentially discoverable electronically stored information, regardless of its storage location or format, is identified, collected, and preserved in an forensically sound manner to prevent alteration or loss, which could lead to spoliation claims.
Regulate the extent of the production process so that unnecessary or repetitious ESI is not revealed or compromised in any way: This involves setting clear boundaries for the scope of the inspection to avoid over-production of irrelevant data, protect non-responsive information, and prevent the disclosure of data that is duplicative or falls outside the agreed-upon discovery parameters.
Minimize the inconvenience, intrusiveness, and expense of an on-site visit: On-site ESI inspections can be highly disruptive, costly, and technically complex. Protocols aim to streamline the process, limiting access to only necessary systems and data, using efficient collection methods, and often negotiating the terms to reduce the burden on the responding party.
Preserve the privacy of certain business records: Many organizations hold sensitive business information (e.g., customer data, financial records, proprietary operational details) that is not relevant to the litigation. The protocol protects this information from being broadly exposed during the search.
Protect the privileged nature of trade secrets and professional confidences: Beyond general privacy, specific legal protections exist for trade secrets, attorney-client privileged communications, and attorney work product. The protocol must include mechanisms (e.g., privilege logs, review by the owner's counsel, clawback agreements) to prevent the waiver of these crucial protections during an on-site inspection.
Prevent the unnecessary and costly loss of ESI stored in a computer system: Improper or amateurish handling of ESI during an on-site inspection can lead to accidental deletion, corruption, or destruction of data, which could be critical to the case or the responding party's operations. The protocol emphasizes using qualified experts and defensible methodologies.
Hire an expert: Due to the inherent technical complexities and legal implications of ESI on-site inspections, it is almost always essential to hire an e-discovery expert, forensic IT specialist, or a vendor with proven experience. These experts ensure the collection is forensically sound, maintain the chain of custody, navigate complex systems without causing data loss, and provide defensible certifications of their work, which can be critical if data collection methods are later challenged in court.
Steps in the on-site inspection protocol for ESI
Set procedural restrictions: Before any inspection begins, the parties must agree on specific procedural rules. These may include limiting access to certain servers or devices, restricting the use of external storage devices, setting clear parameters for the search terms and methodologies, delineating who can be present during the inspection (e.g., only experts from both sides, without legal counsel directly observing data content), and establishing guidelines for creating forensic images or copies of data.
Determine which party will be responsible for covering the expense of the on-site production process: ESI collection can be very costly. The parties typically negotiate whether the requesting party, the responding party, or a combination will bear the costs associated with the expert, equipment, labor, and potential business disruption. Courts may also shift costs if the requested discovery is unduly burdensome.
Decide which parties will be accountable for the expense that might be involved in recovering any lost or destroyed ESI that results from the search: If ESI is inadvertently lost, altered, or destroyed during the inspection, the protocol should clearly assign responsibility for the costs of recovery (if possible) or any sanctions that might arise from such spoliation. This incentivizes careful conduct and the use of qualified professionals.
Specify status of the ESI subject to the search: It's crucial to define what types of ESI will be targeted. This includes active data (readily available files), inactive data (archived but accessible), backup data (used for disaster recovery), legacy data (on older systems), and ephemeral data (short-lived data like RAM contents or temporary files). Each type requires a different approach for preservation and collection, impacting feasibility and cost.
Specify whether any backup paper copies of the ESI will be included in the on-site search: While the focus is often on electronic data, some ESI might have been printed to paper. The protocol should address whether these physical copies or hybrid documents (portions electronic, portions physical) are within scope and how they will be handled to ensure a comprehensive collection.
Establish a time frame in which the ESI will be gathered: A clear timeline for the inspection and collection activities must be agreed upon. This includes start and end dates for the on-site work, deadlines for forensic imaging, and a schedule for the producing party to review and produce the collected data. This ensures efficiency and avoids indefinite disruption.
An independent, objective IT specialist conducts the search for ESI: To ensure impartiality, technical competence, and defensibility, an IT specialist who is neutral and respected by both sides often conducts the technical aspects of the search. This expert's role is to forensically collect data according to the agreed protocol, without making judgments on its relevance or privilege in the field.
The IT specialist makes copies that are turned over to the owner of the ESI; the owner of the ESI examines the copy to preserve any confidential or private data: After forensic collection, the initial copies of the ESI are typically provided to the responding party (the 'owner'). The owner's legal team then reviews this raw data for responsiveness, relevance, confidentiality, and privilege before it is ever disclosed to the requesting party. This step is crucial for protecting sensitive information.
After all private and confidential data is expunged (redacted or segregated), it is turned over to the party that filed the document request: Once the owner has completed their review, all non-responsive, privileged, or unduly confidential information is either redacted or segregated from the responsive data. Only the properly vetted and responsive ESI is then produced to the requesting party, usually accompanied by a privilege log for any withheld documents.