Legal operations: what the function actually owns

Legal operations is the business management of a legal department. It covers spending, outside counsel, technology, process, data, knowledge, contracts, and staffing so that lawyers can focus on practicing law. It also gives the business a reliable view of legal cost and risk.

This is different from practice management inside a law firm. Firm practice management supports lawyers who sell and deliver legal services; legal operations typically sits inside the client organization and manages the resources used to obtain those services. The buyers differ, as do the operating priorities.

What legal operations actually owns#

The scope varies by organization, but legal operations commonly owns the administrative and financial machinery around legal work. The function is not simply a contract between lawyers and a procurement department. It connects legal work to the systems, budgets, vendors, and business stakeholders that make the work possible.

That connection typically includes outside counsel management and billing guidelines. Legal operations maintains panel relationships, routes matters to appropriate counsel, coordinates budgets, reviews invoices against guidelines, and analyzes invoice components. Its aim is not simply to reduce spend. It is to make outside spending visible, consistent, and explainable.

Matter management and intake form another core area. An intake process captures the legal team, relevant business unit, matter type, objectives, budget, and key deadlines. It also determines which standard workflows apply. Poor intake creates downstream work: duplicated requests, inconsistent matter names, unclear ownership, and invoices that cannot be connected to the matter they served.

Technology selection and administration place legal operations at the center of legal operations technology decisions. The function identifies requirements, compares alternatives, manages implementation, controls access, and tracks vendor performance. Legal teams also need to account for administration: user provisioning, training, support, data retention, and the ability to retrieve information when a matter requires it.

Knowledge management is another recurring responsibility. A legal department accumulates templates, playbooks, clauses, institutional knowledge, and approved language that can reduce repetitive work. Legal operations determines where that content lives, who can change it, and how employees find and reuse it. The objective is controlled reuse rather than uncontrolled circulation of outdated material.

Contract process ownership sits more closely to business operations. The legal team remains responsible for legal judgment, but legal operations can structure intake, route requests, track approvals and obligations, maintain a contract repository, and connect deadlines to business owners. This division matters because legal risk and process ownership do not always belong to the same role.

Finally, legal operations reports to the business on cost and risk. That reporting can connect legal matters to operating priorities, forecast spending, identify bottlenecks, and show where legal work may affect a business objective. The most useful reports do not reproduce every invoice line. They give decision-makers information they can act on.

The discovery connection#

Discovery is where legal operations often has the greatest operational impact. Legal operations usually manages the relationship with discovery vendors, coordinates preservation tooling and legal hold processes, and maintains the matter data needed to understand what discovery is costing. These activities connect directly to collection, processing, review, production, and presentation.

For many legal departments, discovery can be the largest controllable line in a legal budget. Preservation, collection, processing, review, production, and related vendor services all require resources. The controllable part is not limited to the hourly rate or the number of documents a platform can process. It includes the scope of preservation, the efficiency of the process, the quality of the data supplied to vendors, and whether review results are used effectively.

The legal team and legal operations share responsibility here. The lawyers determine relevance, privilege, preservation obligations, and litigation positions. The operations function can make those decisions executable through controlled intake, defensible data movement, documented workflows, and timely cost reporting. Neither side is well served by treating discovery administration as an unexplained technical expense.

Legal hold management illustrates the connection. A hold identifies custodians, the information they maintain, and the reasons their information may need to be preserved. Legal operations can support that process with systems that track custodians, issue acknowledgments, and record release activity. The system should support legal judgment rather than turn a hold into an indiscriminate preservation command.

Preservation decisions also affect downstream cost. Overbroad collection can increase processing, review, and production burdens before anyone knows whether the additional information is needed. The 2015 amendments to the Federal Rules of Civil Procedure placed proportionality factors within the definition of the scope of discovery and added “the parties’ relative access to relevant information” as a factor. Legal operations can help capture that information by identifying custodians, systems, available data, and known access points.

Vendor administration becomes particularly important when a producing party uses technology-assisted review. TAR, including predictive coding and continuous active learning, can change the economics and administration of review. The technology does not remove the need for a defensible process. Someone still has to define the review population, evaluate performance, manage exceptions, and document the basis for the production decision.

Judicial decisions in the Southern District of New York help frame that risk. 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, a conclusion affirmed by District Judge Andrew Carter. The agreement of the parties mattered. 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.

Hyles v. City of New York took a different practical position: a court would not force a producing party to use TAR when it preferred keyword searching. That is consistent with Sedona Principle 6, which places the responding party in the best position to decide how to search for and produce its ESI. Some language in Rio Tinto and Hyles is dicta rather than holding, so those decisions signal judicial attitude rather than create a binding rule. Legal operations should therefore treat the choice of search method as a documented, matter-specific decision rather than a categorical policy.

Rules governing requests and objections also belong in the workflow design. Rule 34(b)(2)(B) requires specificity when stating grounds for an objection. Rule 34(b)(2)(C) requires the objection to state whether responsive materials are withheld on that basis. Rule 37(e) establishes a two-tier framework for lost ESI that should have been preserved: a finding of prejudice permits measures no greater than necessary to cure the prejudice, while adverse consequences involving a presumption, jury instruction, dismissal, or default require a finding that the party acted with intent to deprive another party of the information.

Legal operations can translate those requirements into controls. A request log can record the objections and their effect. A loss analysis can separate recoverable prejudice from disputed intent. A conferral record can document how the parties addressed search and review. Rule 26(f) requires the parties to confer before the scheduling conference, while Rule 16(b) governs the scheduling order, creating a natural point at which discovery responsibilities can be made explicit.

Other legal teams may overlook the protection mechanism in Federal Rule of Evidence 502(d). A federal court may order that privilege or work-product protection is not waived by disclosure in the proceeding before it. A clawback mechanism in the production workflow can support that protection, although the operational design still needs to account for the court’s order and the handling of privileged or protected material.

The Electronic Discovery Reference Model can help legal operations map ownership without treating discovery as a rigid sequence. EDRM covers information governance, identification, preservation, collection, processing, review, analysis, production, and presentation. It is a reference model, not a mandatory sequence, and real matters often loop between stages. That makes coordination more important than forcing every matter through a one-way checklist.

How capability develops#

A one-person legal operations function can do meaningful work. It can consolidate outside counsel invoices, apply billing guidelines, maintain a matter list, standardize intake, administer priority legal technology, and produce a regular cost report. The advantage is concentration: the person can see where budgets, vendors, and workflows interact. The constraint is capacity. A single operator can become a bottleneck when discovery, contracts, reporting, and technology administration occur at the same time.

A larger function can divide those responsibilities and add data controls, formal intake workflows, knowledge programs, and deeper spend analysis. It can also establish a governance rhythm for vendors and internal stakeholders. Added headcount does not itself create better operations, however. It creates value when the function has reliable data and defined workflows rather than when it has more tools.

The order of development is consequential. Spend visibility usually provides the earliest operational foundation. Legal operations first needs to know what is being spent, on which matters, and which invoices do not match billing guidelines. Without that baseline, process improvement lacks a target and technology purchases lack a business case.

Process comes next. Intake, invoice review, legal hold administration, discovery request tracking, and contract intake can then follow repeatable paths. Technology supports the process, but substituting software for unclear ownership and inconsistent definitions only makes the underlying problem harder to see. A system cannot accurately report the cost of a matter if the organization cannot reliably define what a matter is.

Technology capabilities can then expand. Administration, data movement, workflow support, and reporting may be automated or made more consistent as the underlying data becomes dependable. The sequence is not rigid, and mature legal departments revisit it as their legal portfolio and business needs change. The general point is that visibility, process, and technology reinforce one another when they are built in that order.

The measurement problem#

Legal departments measure many things because legal work affects many dimensions. Finance may focus on invoices and forecasts. Business stakeholders may focus on the progress of a specific dispute or contract. Discovery teams may track preserved data, processing status, review activity, and production volumes. Legal operations may report outside counsel performance, technology adoption, matter throughput, or operational exceptions.

The recurring measurement problem is that many available measures describe activity without improving a decision. A count of open matters shows scale but not whether the matters are staffed appropriately. A total technology-user count shows reach but not whether users can complete the work. A document volume shows the size of a collection but not whether the collection was proportionate. Each measure becomes more useful when connected to a decision about cost, staffing, process, or risk.

Spend visibility is easier to define than many legal metrics. Outside counsel spend can be categorized by matter, practice area, timekeeper, invoice component, and budget status. The resulting analysis can reveal guideline exceptions, budget variances, or patterns that justify changes to staffing or panel decisions. The reliability of that analysis depends on consistent matter coding and invoice data, which makes it as much a process problem as a reporting problem.

Cycle measures can also influence operations when the time window reflects a meaningful business event. Examples include the time from request intake to assignment, from a preservation trigger to hold completion, or from invoice receipt to final review. These measures identify queues and ownership gaps. They are not useful simply because they are faster to produce; they matter when they distinguish a temporary workload issue from a broken handoff.

Discovery metrics require particular care. Data volumes, processing counts, review progress, and production status may be necessary for administration, but none alone shows whether the discovery process is proportionate or effective. Cost data should be viewed alongside the scope of preservation, the search and review method, the treatment of objections, and the status of any disputed production. The result should support a reasoned decision rather than reward a narrow activity target.

Quality measures are also important, but they need a defined denominator and a known use. Privilege review defects, missing productions, and untimely responses can prompt training, workflow changes, or vendor review. A measure becomes useful when it identifies where the corrective action belongs. Counting defects without analyzing their source adds reporting work rather than reducing risk.

The measures most likely to change decisions are therefore linked, even if they are not perfect. Spend and budget data show financial pressure. Cycle data show where work is stuck. Quality data show where the process is unreliable. Risk data show where legal exposure or operational failure could affect the business. When those views are separate, legal operations can produce accurate reports that still fail to support action.

The practical role of the function#

Legal operations adds value by making legal work legible and manageable. It creates a shared view of cost, connects legal work to business activity, coordinates vendors and internal stakeholders, and maintains the systems through which legal work is performed.

That role is especially important in discovery, where technical process, legal judgment, vendor performance, and financial impact meet. The function does not replace lawyers or discovery professionals. It supplies the management structure that allows them to make and execute decisions with better information.

A legal department can use that structure to answer practical questions: which matters account for controllable legal spend, where preservation and review resources are being used, which vendors are delivering against agreed terms, and which process failures can be corrected before they become larger problems. Those are the concrete responsibilities behind the label “legal ops.”