What litigation support does, and why the role keeps changing

Litigation support is the people-and-processes function that manages the data and technology side of a dispute. It covers collection, processing, administration of review platforms, production, and the technical preparation of deposition and trial materials. The work connects the legal theory of a case to the systems in which its records exist.

The function is broader than litigation support services offered by outside providers, but it is not the same as legal representation. Litigation support professionals determine how information moves, what technology is applied, how exceptions are recorded, and how the resulting materials can support counsel, witnesses, experts, and the court.

A hybrid legal-technology role#

Litigation support sits between the legal team and the information systems holding the evidence. That position gives the role two characteristics: enough technical depth to understand data and workflows, and enough procedural understanding to recognize why a collection request, processing decision, production protocol, or objection has legal significance.

A load file, for example, is not merely a technical artifact. It records the population of documents processed and the steps applied to them. A production protocol is not merely an export instruction. It defines how a production is created, labeled, organized, and checked. The support professional must understand both the mechanism and its intended legal use.

The role also involves users, custodians, and access controls. Custodians are people whose information may be relevant; legal holds notify them to preserve it. Administrators determine who can access review platforms, what they can do there, and how activity is recorded. Those decisions support confidentiality, privilege, and the defensibility of the review process.

The work, phase by phase#

Litigation support follows the dispute rather than a rigid production checklist. The Electronic Discovery Reference Model, or EDRM, organizes the work into information governance, identification, preservation, collection, processing, review, analysis, production, and presentation. EDRM is a reference model, not a mandatory sequence, and matters often loop between stages as facts, claims, and production issues change.

Scoping and preservation#

The first phase is deciding what exists and what should be preserved. Support professionals work with counsel to identify relevant custodians, data sources, and collection scope. A legal hold may need to cover multiple custodians, business units, or systems, with different handling requirements for email, collaborative platforms, databases, and other electronically stored information.

Scoping requires care. A collection that is too narrow may omit relevant material; one that is too broad may create avoidable processing and review work. The support team documents its sources, methods, and exceptions so that counsel can evaluate the collection and opposing parties can test it without relying on an informal description.

Collection and processing#

Collection acquires data for later examination. Processing prepares that data for review by extracting content and metadata, applying formats, grouping related records, and identifying duplicates. De-duplication removes exact duplicate documents, while near-duplicate detection identifies records that may differ only slightly. Email threading organizes messages into conversations so reviewers can assess them as exchanges rather than isolated items.

Processing rarely proceeds without exceptions. Missing data, unreadable files, unsupported content, corrupted records, or unusual field values may require investigation and a record of the treatment. Those exceptions can affect what reviewers see and what counsel can claim has been searched. The support professional therefore translates a processing decision into an auditable record.

After processing, the team loads the resulting population into a review platform and creates the datasets needed for review, production, or further analysis. The load file provides a technical record of that population. Custodian, date, issue, and other fields support targeted searching and organize the work, but the usefulness of those fields depends on how accurately they were populated.

Review and analysis#

During review, support professionals administer the platform and its users, build searches, test search results, coordinate workflow, and monitor the progress of review. Boolean or keyword search can retrieve documents by terms and relationships defined in the query. A defensible search depends on an understanding of the data, the vocabulary of the matter, and the purpose of the search.

Technology-assisted review, or TAR, applies machine-assisted methods to prioritize and classify documents for human review. Predictive coding is one form of TAR. Continuous active learning, or CAL, is a TAR method that uses reviewer feedback to refine its classifications. Support personnel may also organize issue coding, privilege review, and the preparation of a privilege log, but those activities remain connected to substantive legal judgment.

Privilege log preparation requires more than listing documents. The log records the basis for withholding material so that a court or opposing party can assess the claim. Clawback procedures address documents produced subject to a claimed privilege, while redaction removes or masks content that should not be disclosed. Each measure depends on an established workflow and accurate documentation.

Production and quality control#

Production is the controlled delivery of responsive material in the agreed form. A production format may be native, TIFF, or PDF, with or without load files. The appropriate format depends on the needs of the case and the agreement between the parties. Production preparation may also include privilege screening, redaction, metadata treatment, document numbering, file naming, and assembly into production sets.

Quality control is more than confirming that files open. The team checks the production population, field population, exceptions, privilege treatment, Bates-style identification where used, image quality, redactions, and the relationship between the production and the load file. The production guide on this site provides a closer look at format choices and their consequences.

Errors in a production can require supplemental material, replacement files, explanation, or further review. The support team records the issue, identifies its cause, and implements a corrective step. Counsel evaluates any legal consequence, but the person operating the process often identifies the problem first.

Depositions and trial preparation#

Litigation support also prepares the technical foundation for testimony and courtroom use. For depositions, the team may organize exhibits, maintain exhibit references, prepare demonstratives, convert or tag materials, and make documents accessible to counsel and the witness. The role supports preparation without replacing the lawyer’s questioning or the witness’s personal knowledge.

Federal Rule of Civil Procedure 30 governs depositions by oral examination. An organization may be named as the deponent if the notice describes the matters for examination with reasonable particularity. Under Rule 30(b)(6), the organization designates one or more people to testify on its behalf, and the testimony represents the organization’s position rather than the designee’s personal knowledge.

The 2020 amendment to Rule 30(b)(6), effective 1 December 2020, requires the parties to confer about the matters for examination before the deposition. It also treats each designated person as a separate deposition for the durational limit. The applicable duration should be checked against the current rule and any standing order rather than assumed from an older workflow.

Support personnel also account for the use of deposition testimony. Rule 32 permits an adverse party to use a party’s deposition, or the deposition of a person who was an officer, director, managing agent, or Rule 30(b)(6) designee at the relevant time, for any purpose. That makes accurate designations, clear topic descriptions, organized exhibits, and reliable transcripts operationally important. Rule 45 may compel a non-party to appear by subpoena, but a deposition notice alone does not compel a non-party.

At trial, the same discipline continues. Materials may need to be standardized, labeled, displayed, printed, or checked for demonstrative use. A technology team may also support courtroom displays and the transition between physical and electronic evidence. The objective is not visual polish alone; it is to make the record understandable and usable within the proceeding.

Where the function belongs#

In a law firm, litigation support often supports one matter team or a broader litigation practice. Its members may sit within a discovery group, serve as embedded technical staff, or work across engagements. The principal difference is institutional proximity: the team may see the theory of the case early, participate directly in strategy sessions, and remain accountable to the lawyers handling the matter.

In a legal department, litigation support is usually an internal capability shared across the organization. It may manage recurring discovery workflows, control vendor access, maintain internal procedures, and coordinate records from several business functions. The support lead must also translate outside counsel’s instructions into work that internal custodians and technical owners can execute.

At a provider, the function is organized around delivery to client teams. Personnel may specialize in collection, processing, review-platform administration, production, or trial technology. A provider needs clear matter governance, quality control, and communication because the client may not control the underlying systems or personnel.

These settings share the same core work, but authority and accountability differ. A firm’s support team may influence litigation strategy. A legal department’s team may focus on cost, control, consistency, and institutional risk. A provider’s team must execute an agreed scope while surfacing exceptions. In each setting, the support professional needs authority to pause work when a technical issue may have legal significance.

The skills the role requires#

The essential capability is translation across domains. Technical fluency alone does not establish whether a collection, search, review population, or production method is fit for purpose. Procedural familiarity alone does not ensure that data was collected or processed accurately. Effective litigation support combines both.

Practical skills include understanding file systems, metadata, text extraction, database structures, load files, review-platform controls, search logic, and production assembly. Equally important are communication, documentation, project judgment, and the ability to explain a technical problem without disguising uncertainty.

This is one of the few legal roles that is not a lawyer’s job but carries real procedural consequence. A collection that omits preserved information, an objection that lacks required specificity, or a lost ESI issue may affect how the discovery process is evaluated. The litigation support professional does not make the legal decision, but the quality of the operational record can determine what information is available for that decision.

The Federal Rules also make documentation more than an administrative preference. Rule 34(b)(2)(B) requires a responding party to state grounds for objecting to a request with specificity, and Rule 34(b)(2)(C) requires an objection to state whether responsive material is withheld on that basis. Those requirements depend on accurate collection and review information. Where ESI that should have been preserved is lost, Rule 37(e) supplies distinct remedial standards for prejudice and intent to deprive.

From executing steps to designing and defending the method#

Automation is moving more mechanical review tasks into software, but that does not make the surrounding judgment less necessary. It shifts the center of the role from performing each step toward selecting the method, configuring the workflow, testing the output, documenting exceptions, and explaining why the process was reasonable in context.

TAR illustrates the change. In Da Silva Moore v. Publicis Groupe, Magistrate Judge Andrew Peck held that computer-assisted review was an acceptable way to search for relevant ESI in appropriate cases; the parties’ agreement to use it mattered, and District Judge Andrew Carter affirmed in April 2012. It is widely described as the first judicial opinion approving predictive coding.

In Rio Tinto PLC v. Vale S.A., Judge Peck described judicial willingness to permit technology-assisted review as black-letter law, and Maura Grossman was later appointed special master to resolve TAR disputes. By contrast, in Hyles v. City of New York on 1 August 2016, Judge Peck would not force a producing party to use TAR when it preferred keyword searching. That approach is consistent with Sedona Principle 6, under which the responding party is best situated to decide how to search for and produce its ESI.

Some language in Rio Tinto and Hyles is dicta rather than holding, so it signals judicial attitude rather than binding rule. The practical lesson remains matter-specific: the support team should be prepared to explain the technology, validate its operation, address weaknesses, and connect the method to the production protocol and governing obligations.

That is the enduring value of the role. Automation can execute a classification workflow, but the professional still determines what the workflow should do, what it missed, whether its exceptions are material, and whether another method would serve the case better. The documents and productions produced by litigation support remain the foundation for later legal decisions, depositions, and trial arguments.