Electronic Discovery Procedures: A Guide to E-Discovery in Law

Electronic discovery procedures govern how parties identify, preserve, collect, review, and produce electronically stored information in a legal case. Because relevant evidence may reside in emails, messaging platforms, cloud services, and mobile devices, early planning can help protect its integrity and address discovery obligations.

The process typically begins with preservation measures, including legal holds and steps to prevent routine deletion or alteration. Collection and review must then be managed carefully, while disputes over scope, costs, or production may require meet-and-confer discussions or court intervention under applicable rules.

How Electronic Discovery Procedures Begin in a Legal Case

Electronic discovery procedures generally begin when a party reasonably anticipates litigation or receives a claim that may lead to a lawsuit. At that point, counsel assesses whether relevant electronically stored information (ESI) may exist and identifies the people, systems, and records connected to the dispute.

The parties’ claims and defenses help define the likely scope of discovery. Relevant ESI may include emails, text messages, documents, databases, and information stored in cloud services or business applications. The applicable rules and any court orders guide what must be preserved and may later be requested.

Early communication between counsel can clarify the issues, likely sources of ESI, and practical limits on collecting it. These initial steps establish a basis for the electronic discovery procedures that follow, while helping prevent avoidable disputes over preservation and scope.

Preserving Electronically Stored Information

Preservation begins when a party reasonably anticipates litigation, not only when a lawsuit is filed. At that point, counsel should identify potentially relevant electronically stored information (ESI), the people and systems likely to hold it, and the applicable preservation duties under governing law and court rules.

A legal hold communicates those duties to relevant employees and other custodians. It should describe the information to preserve, explain how to suspend deletion, and provide a way to ask questions. Counsel should distribute it to appropriate custodians and follow up to confirm that they understand and comply.

The organization must also take reasonable steps to prevent routine processes from deleting or altering relevant ESI. Depending on the systems involved, this may require suspending email or messaging auto-deletion, backup rotation, device wiping, or other retention settings. Preservation measures should reflect the data’s relevance and the systems’ capabilities.

Because electronic discovery procedures may later be scrutinized, counsel should document the hold’s scope, distribution, acknowledgments, and any updates. Preservation duties can continue as the case develops, so the hold should be reviewed when new custodians, data sources, or issues are identified.

Issuing and implementing a legal hold

A legal hold should be issued when litigation is pending or reasonably anticipated and relevant electronically stored information may need to be preserved. The responsible legal team identifies the matter, the likely date range, and the people or systems that may hold relevant records.

The notice should explain, in clear terms, what information must be retained and why. It may cover email, messages, documents, business applications, and data on mobile devices, depending on the case. Recipients should know how to ask questions and whom to contact.

Implementation requires more than sending a notice. Counsel or designated staff should confirm that recipients received and understand it, notify relevant custodians and IT personnel, and suspend deletion settings or other routine processes that could affect covered data.

The organization should track acknowledgments and follow up when roles, custodians, or systems change. As electronic discovery procedures progress, the hold should be reviewed and updated so its scope remains tied to the dispute and preservation obligations.

Preventing routine deletion or alteration

Once a legal hold is in effect, relevant data must be protected from ordinary systems that delete or overwrite it. This may include pausing email-retention rules, auto-delete settings, backup rotation, and scheduled deletion of messages or files in collaboration platforms.

The preservation steps should match the information at risk. For example, custodians may need instructions not to delete relevant texts or documents, while IT staff may need to suspend deletion settings for identified accounts, devices, or repositories. The scope should be limited to potentially relevant data and consistent with applicable legal obligations.

Organizations should also guard against alteration. Restricting access, preserving original files, and using system logs or other records to track changes can help maintain data integrity. Because routine processes vary by system, counsel and technical staff should verify that the measures work as intended.

Document what was suspended, when, by whom, and for which data sources. These records help show that electronic discovery procedures addressed routine deletion and alteration risks, and can support later explanations of how the information was preserved.

Planning the Collection of Digital Evidence

Before collection begins, counsel should identify the relevant issues, date range, custodians, and categories of electronically stored information (ESI). Potential sources may include email, messaging platforms, shared drives, mobile devices, and cloud services. The scope should be proportionate to the needs of the case and consistent with applicable rules.

The collection plan should specify who will gather the data, which systems or devices will be searched, and what methods will be used. Counsel and technical personnel should consider access restrictions, encryption, file formats, and whether collection could alter metadata or other relevant information.

Reliable procedures help preserve data integrity and support later verification. Depending on the source and circumstances, teams may use forensic imaging or targeted exports, while recording the tools, settings, dates, and steps involved. The chosen method should reflect the evidence sought and the risks of changing or omitting data.

A documented plan also helps identify practical issues, such as inaccessible sources, duplication, or collection costs, before work proceeds. These decisions guide the next stages of electronic discovery procedures without expanding collection beyond a reasonable, defensible scope.

Processing and Reviewing Collected Information

After collection, electronically stored information is processed to make it suitable for review. This may include extracting text and metadata, converting files to searchable formats, removing exact duplicates, and organizing records while preserving their original content and relevant context.

Reviewers then assess the material for relevance, responsiveness to discovery requests, privilege, and confidentiality. Search terms, date ranges, and technology-assisted review may help manage large data volumes, but their use should be tested and documented to support a reasonable, defensible process.

Potentially privileged documents should be identified and withheld or redacted as appropriate under applicable rules and agreements. Review protocols should also address access controls and quality checks, reducing the risk of disclosure errors or inconsistent decisions.

Careful processing and review create an organized record for production and help parties identify issues before information is exchanged. The methods used should reflect the data’s nature, the case’s needs, and any court orders or agreements.

Producing Electronically Stored Information

Production should follow the parties’ agreements, court orders, and applicable procedural rules. The producing party generally provides responsive, nonprivileged information in the form in which it is ordinarily maintained or in a reasonably usable form, subject to the governing rules and any specific requests.

Before delivery, the production set should be checked for completeness, privilege, confidentiality, and consistency with agreed formats. Common production formats include searchable PDF files, native files, and images accompanied by extracted text and metadata. The appropriate format depends on the information’s nature and the parties’ agreement or the court’s direction.

A clear production protocol can address:

• File formats, naming conventions, and delivery method
• Metadata fields and any load files
• Redactions, confidentiality designations, and privilege logs

A secure transfer method helps protect sensitive data. Production records should identify what was delivered and when, supporting accountability if questions arise later.

Resolving Disputes About Discovery Procedures

Disputes over electronic discovery procedures may concern the scope of a search, the sources to be examined, collection methods, production format, or the cost of retrieving information. Parties should identify the precise issue and explain how it affects relevant, proportional discovery.

Under applicable procedural rules, counsel generally should confer in good faith before asking the court to resolve a discovery dispute. A focused discussion can clarify technical facts, narrow disagreements, and identify practical solutions, such as staged collection or agreed search terms. Parties should document proposals and responses.

If discussions fail, a party may seek court intervention through the procedures and deadlines set by the court and governing rules. The court may assess relevance, proportionality, accessibility, and any claimed burden. Available remedies depend on the circumstances and applicable law; sanctions are not automatic.

To prepare for a conference or motion, parties should organize:

• The disputed request and the response or objection
• Relevant technical details and burden evidence
• Proposed alternatives and prior efforts to resolve the issue

Meet-and-confer discussions

Before seeking court intervention, parties should confer in good faith to address disagreements about the scope or handling of electronically stored information. Applicable rules and court orders may specify when and how this discussion must occur; requirements can vary by jurisdiction.

Participants should identify the disputed issues and exchange practical proposals, such as:

• Search terms, date ranges, custodians, or data sources
• The format for production and treatment of metadata
• The handling of inaccessible information, privilege claims, and confidentiality concerns

A focused discussion can narrow disagreements and reduce unnecessary expense. Parties should document proposals, responses, and any agreements, including limits on collection or review. These records help clarify what remains unresolved if a motion becomes necessary.

The meet-and-confer process does not replace each party’s discovery obligations. If discussions do not resolve a dispute, the parties may present the remaining issues to the court under the applicable procedures.

Court intervention and sanctions under applicable rules

When parties cannot resolve an e-discovery dispute through meet-and-confer discussions, they may ask the court to decide the issue. A motion should identify the information sought, explain its relevance and proportionality, and describe the efforts made to resolve the disagreement.

Courts apply the governing procedural rules, including rules addressing electronically stored information. Under U.S. Federal Rule of Civil Procedure 37(e), for example, remedies may be considered when information that should have been preserved is lost because reasonable preservation steps were not taken and it cannot be restored or replaced.

The available response depends on the circumstances. A court may order additional discovery or other measures to address prejudice; more severe sanctions generally require a finding of intent to deprive another party of the information. Applicable rules and standards vary by jurisdiction.

Parties should maintain records of preservation efforts, collection decisions, and communications about disputed material. Clear documentation can help the court assess whether the electronic discovery procedures were reasonable and whether any remedy is warranted.

Closing the E-Discovery Process With Defensible Documentation

After production is complete and discovery obligations have been addressed, document how the electronic discovery procedures were carried out. Retain records of preservation notices, custodian and data-source decisions, collection methods, processing steps, review protocols, and production details.

A defensible record should identify who performed key tasks, when they occurred, and any material decisions or deviations. Where appropriate, preserve chain-of-custody information and verification results, such as collection logs or file-integrity checks. Avoid documenting conclusions that the available records cannot support.

Confirm that relevant data sources were addressed and that any agreed or court-ordered actions were completed. If information was withheld, redacted, or unavailable, maintain records explaining the basis, consistent with applicable rules and orders.

Keep documentation securely with the matter file under the organization’s retention policies and any legal hold requirements. Do not destroy records merely because production has ended; preservation duties may continue while the case or related obligations remain unresolved.