AI CONTENTThis article was authored by AI. We invite you to confirm any important details using credible and reliable sources.
Document review in discovery is the process of evaluating collected materials to determine which are relevant to a case, protected by privilege, or subject to production. Because the volume of electronically stored information can be substantial, a sound review process helps parties meet their legal obligations while managing cost and risk.
Effective review begins with a clearly defined scope and well-prepared documents. It also requires consistent decisions about responsiveness, privilege, redactions, and production—often supported by technology and quality controls to help preserve a defensible process.
What Document Review in Discovery Involves
Document review in discovery is the process of examining information gathered during litigation to identify material that must be produced under applicable discovery rules, court orders, and agreed protocols. The collection may include emails, messages, contracts, reports, spreadsheets, and other electronically stored information or paper records.
Reviewers assess each item for relevance to the claims and defenses, responsiveness to document requests, and potential confidentiality or privilege concerns. They may also identify records that require redaction or special handling. The precise criteria depend on the case and governing rules.
This work helps parties determine what can be produced, what may be withheld, and what requires further consideration. A sound review process also records decisions and supports consistent treatment of documents, particularly when collections are large or involve multiple reviewers.
The review is one stage of discovery, not a substitute for defining the requests or resolving disputes. Its scope and procedures are generally shaped by the parties’ obligations and any applicable court direction.
Defining the Scope of Document Review
Defining the scope of document review means identifying which materials must be examined and the legal questions the review must address. The scope should reflect the claims and defenses, discovery requests, applicable court orders, and any agreements between the parties.
Relevant parameters may include date ranges, custodians, data sources, document types, and agreed search methods. Clear criteria help focus the review on information that is relevant and proportional to the needs of the case, while limiting unnecessary work.
The parties should also address how electronically stored information will be handled, including potentially inaccessible sources and the treatment of duplicates or family groups, such as an email and its attachments. Applicable procedural rules and local requirements should guide these decisions.
Document review in discovery benefits from a scope that is documented and communicated to the review team. Recording assumptions, exclusions, and agreed limitations can support consistent decisions and help explain the process if the scope is later challenged.
Preparing Documents for Review
Before substantive review begins, collected files should be organized into a consistent, searchable format. This may involve extracting text from electronic documents, applying optical character recognition to scanned files, and preserving metadata such as author, creation date, and file path.
The review team should also identify duplicates and maintain family relationships among related items, such as an email and its attachments. Keeping these links intact helps reviewers assess documents in context and reduces the risk of separating relevant material from its accompanying records.
A reliable document-management platform can assign unique identifiers, track processing results, and record each item’s place in the collection. Any conversion, deduplication, or filtering should be documented so the review process remains traceable.
Before release to reviewers, the collection should be checked for unreadable files, missing text, and processing errors. These quality checks help ensure the materials are complete and accessible without making judgments about responsiveness or privilege at this stage.
Reviewing Documents for Responsiveness and Privilege
During document review in discovery, each item is assessed against the requests for production and any applicable court orders. Reviewers determine whether a document is responsive, meaning it falls within the stated scope, and record consistent coding decisions to support later analysis.
Responsiveness may depend on context, not just individual pages. Reviewers should examine related documents, such as email attachments and surrounding message threads, while applying the agreed scope and relevant date, custodian, or subject-matter limits. Unclear documents may require escalation under established review protocols.
Reviewers must also identify material protected by attorney-client privilege or the work-product doctrine. A document should not be withheld solely because it involves a lawyer; the reviewer must assess its content, purpose, and participants under the applicable law. Privilege determinations should be documented for consistent handling.
When a document contains both responsive and privileged information, the team should follow applicable rules and protocols for redaction or withholding. Accurate coding and clear records help inform privilege logs and support a defensible production.
Using Technology in Discovery Review
Technology can help organize large collections of electronically stored information and make document review in discovery more consistent. Review platforms allow teams to apply search terms, filters, and document tags to identify potentially relevant material for closer examination.
Search terms may target names, dates, phrases, or other case-specific concepts. Filtering by metadata, such as file type or creation date, can also narrow the collection. These methods can miss relevant documents or return unrelated results, so teams should test and refine them against the case record.
Technology-assisted review uses machine-learning tools to help prioritize or classify documents based on human coding. Its effectiveness depends on the data, review approach, and quality controls; it does not eliminate the need for appropriate human oversight.
Sampling, validation, and tracking decisions can help assess whether searches and automated classifications are performing as intended. Clear documentation of methods and changes supports a defensible review process and helps explain how materials were identified for further review.
Search terms and other filtering methods
Search terms can narrow a large collection to documents likely to be relevant, but they should be developed from the claims, defenses, key events, and terminology used by the parties. Include likely variations, abbreviations, names, and common misspellings where appropriate. Test terms against sample results and refine them to reduce irrelevant hits without overlooking potentially responsive material.
Other filters may limit the collection by date range, custodian, file type, or data source. These criteria should reflect the agreed or court-ordered scope of discovery and be applied consistently. A filter’s effect should be checked, since overly narrow criteria can exclude relevant documents.
In document review in discovery, search and filtering methods are tools for prioritizing review, not substitutes for assessing responsiveness and privilege. Keep records of the terms and filters used, the reasons for changes, and any validation performed. Common methods include:
- Keyword and phrase searches
- Date, custodian, and file-type filters
- Email threading and near-duplicate identification
Technology-assisted review and quality checks
Technology-assisted review (TAR) uses software to help prioritize or classify documents based on patterns identified from human-reviewed examples. In discovery, reviewers may train a system to identify likely responsive material, then apply its results alongside other review methods. TAR supports legal judgment; it does not determine responsiveness or privilege on its own.
A defensible process begins with a suitable document set and clear review criteria. Qualified reviewers code a representative sample, and the system uses those decisions to rank or categorize remaining documents. The legal team should document the workflow, including training decisions, changes to criteria, and the basis for concluding that review is complete.
Quality checks help assess whether TAR results are reliable for the matter. Teams may examine samples of documents classified as responsive and nonresponsive, investigate disagreements, and refine the process where appropriate. Sampling methods and thresholds should be selected in light of the case, the data, and applicable court rules or agreements.
During document review in discovery, TAR should be used with appropriate human oversight and verification. Counsel should preserve records of validation and key decisions so the process can be explained if challenged.
Resolving Issues Before Production
Before production, the review team should resolve uncertainty about privilege, redactions, and the scope of requested material. Clear procedures help prevent inadvertent disclosure and ensure that withheld documents are accounted for consistently.
For privilege claims, reviewers should confirm the applicable legal basis, apply redactions only to protected portions when appropriate, and record withheld or redacted material in a privilege log if required by the governing rules or court orders. The treatment of confidential information should also follow any protective order.
Disputes about scope or withheld documents may be addressed through meet-and-confer discussions, supplemental searches, or motions, depending on the circumstances and applicable procedure. In document review in discovery, maintain records of decisions and document sets affected.
- Confirm disputed search terms, date ranges, and custodians.
- Reassess documents challenged as privileged or nonresponsive.
- Preserve decision logs and relevant correspondence.
Handling privilege claims and redactions
Privilege claims should be reviewed against the applicable law and the specific facts, since the rules and scope of protection can vary by jurisdiction. Reviewers should identify documents or portions that may be protected, such as confidential communications seeking or providing legal advice, and confirm that the claim is supported before withholding material.
When a document contains both privileged and nonprivileged information, redaction may allow the nonprivileged portions to be produced. Redactions should be limited to protected content, applied consistently, and checked to ensure the concealed text cannot be recovered from the produced file.
The review team should record each withholding or redaction and prepare a privilege log when required by the governing rules, court orders, or agreement. The log generally describes the material without revealing the information claimed as privileged; applicable requirements determine the necessary detail.
Before production, a separate quality check can confirm that redactions are complete and that the privilege log aligns with the withheld documents. In document review in discovery, careful documentation helps parties assess claims and address disputes without unnecessarily exposing protected information.
Addressing disputes over scope and withheld documents
Disputes over the scope of discovery may arise when parties disagree about which documents must be searched, the relevant time period, or the meaning of a request. During document review in discovery, counsel should compare the disputed request with the pleadings, applicable discovery rules, and any prior agreements or court orders.
When documents are withheld as privileged or protected, the producing party should provide information sufficient to assess the claim, often through a privilege log where required. The log should identify withheld material without revealing the protected content. Parties should also explain redactions and distinguish them from documents withheld in full.
Counsel can often narrow disagreements through a focused meet-and-confer, discussing specific requests, search methods, and representative documents. If the dispute remains unresolved, either party may seek guidance from the court under applicable procedures. Clear records of decisions and communications help preserve a defensible process.
Producing Reviewed Documents and Preserving a Defensible Process
After completing review and resolving privilege issues, produce responsive, nonprivileged documents in the format required by the applicable rules, court orders, or parties’ agreement. Confirm that files are complete and readable, and include any agreed metadata or load files. Apply consistent Bates numbering and verify that redactions are permanent and do not reveal underlying content.
A defensible document review in discovery depends on a clear record of how production decisions were made. Preserve the review protocol, search terms and filters, validation results, privilege logs, and records of quality-control checks. Document any changes to the process and the reasons for them.
Before delivery, reconcile the production against the collected and reviewed document sets, check for missing or duplicate files, and confirm that confidential information is handled as required. Securely transmit the production and retain a copy of the final set, together with delivery records, so the process can be explained if questioned.