Author: Onit

How Should In-House Legal Teams Prepare for Rising Consumer Protection Litigation?

A legal operations team standing at a wall-mounted board of case folders and intake forms, sorting incoming matters by type and priority.

An increase in litigation doesn’t just mean more cases for in-house legal teams. It means more matters to manage, more information to preserve, more outside counsel to coordinate, and more costs to track. 

As caseloads grow, processes that work well today can quickly become bottlenecks. Manual intake, disconnected systems, and inconsistent reporting make it harder for legal departments to maintain visibility and control. 

With consumer protection litigation reaching its highest level in a decade, legal operations leaders have an opportunity to evaluate whether their existing processes are ready for what’s ahead. 

In-house legal teams should prepare by testing whether their matter intake, legal hold, outside counsel and spend reporting processes still work at a higher caseload. Lex Machina’s 2026 Consumer Protection Litigation Report, released October 20, 2026, counted 20,353 consumer protection cases filed in federal court in 2025. That is a 31% increase over the prior year and the highest annual total in the ten years the report covers. 

Those figures describe federal dockets across all industries. They do not predict the caseload of any one company. They do raise a practical question for legal operations leaders: if matter volume in a category like this keeps climbing, which of today’s processes would hold up? 

Volume tests process before it tests people. A manual step that a team absorbs at low volume becomes a backlog at higher volume, and the backlog shows up as late holds, uneven outside counsel staffing and spend that is hard to forecast. 

What does rising federal litigation volume mean for in-house legal departments? 

It means more matters entering the department’s workflow faster, often in the same practice areas and with the same repeated steps. Consumer protection claims are a useful example because a single issue can generate many similar matters, each needing intake, a preservation decision, outside counsel assignment and budget tracking. 

The report points to where the growth is concentrated. Telephone Consumer Protection Act filings rose 63% in 2025, from 1,682 to 2,748 cases. Fair Credit Reporting Act filings rose 44% to 7,750, about 38% of all federal consumer protection filings, up from 19% in 2016. Data breach lawsuits rose 21%. The report also counts more than 12,000 new consumer protection suits in the first half of 2026. 

The 2025 filing count is a signal about the market, not a forecast for a specific department. Teams that wait for their own numbers to rise before reviewing their processes are working with a delay. Teams that review early can fix the slowest step first. 

Which legal operations processes come under strain first? 

Four processes tend to show strain first when matter volume grows, because each depends on repeated manual work: 

  • Intake and triage. Requests arrive by email, calls and forms. Without a consistent way to record the matter type, business unit and urgency, assignment depends on whoever sees the request first. 
  • Legal holds. A hold has to reach the right custodians promptly, and the team has to know who has acknowledged it. Tracking this across inboxes and spreadsheets gets harder with every additional matter. 
  • Outside counsel assignment. Matching a matter to a firm, confirming approved rates and applying billing guidelines takes time that multiplies with each new matter. 
  • Spend forecasting. Finance needs a reliable view of expected and actual costs by matter type. Reports assembled by hand lag behind a fast-moving docket. 

Each of these also leaves a record. When regulators, courts or leadership ask what the department did and when, the quality of that record matters as much as the speed of the work. 

Identifying where these processes break down is the first step toward building a legal operation that can handle growing demands without adding unnecessary complexity. 

How can a legal team test its readiness before volume rises? 

Ask five questions and time how long each takes to answer: 

  1. How many matters of a given type are open today, and who owns each one? 
  1. How long does it take to issue a legal hold after a claim arrives, and who has not yet acknowledged an open hold? 
  1. Who approves outside counsel for a new matter, and are rates and billing guidelines applied automatically? 
  1. Can the team produce a spend forecast for a matter type without rebuilding a spreadsheet? 
  1. Which of these answers depend on one person’s knowledge rather than a system? 

Any question that takes more than a few minutes to answer, or that relies on one person, marks a process worth fixing first. Onit’s guidance on where legal hold processes break down covers the second question in more depth, and the questions legal leaders should be able to ask their data covers the first and fourth. 

How can software help legal teams handle a higher caseload? 

Once legal teams understand where their processes are most vulnerable, the next step is identifying opportunities to standardize repetitive work, improve visibility, and reduce manual effort. 

Software helps most where work is repetitive and the record matters. For legal holds, Onit Legal Holds lets teams issue notices, track custodian responses and keep the full record of a hold in one place. It supports reusable templates for different matter types, automated reminders and escalations for custodians who have not responded, and dashboards that show open holds and outstanding acknowledgments. 

Connecting holds to the matter record also reduces re-entry. With Unity ELM, hold activity sits alongside the matter it came from, so the team can report on both without assembling information from separate systems. 

Tools do not replace the decisions a legal team makes, such as when to issue a hold or which firm to retain. They shorten the steps around those decisions, which is where volume creates delay. 

Key takeaways 

  • Federal courts recorded 20,353 consumer protection filings in 2025, up 31% and the highest total in ten years, according to Lex Machina’s 2026 Consumer Protection Litigation Report. Telephone Consumer Protection Act filings rose 63% and Fair Credit Reporting Act filings rose 44%. 
  • Industry-wide filing counts signal market direction. They do not predict any one company’s caseload. 
  • Intake, legal holds, outside counsel assignment and spend forecasting are the processes most likely to strain as matter volume grows. 
  • A simple test of readiness is how long it takes to answer five operational questions, and which answers depend on one person. 
  • Centralizing holds and matter records helps teams act faster and keep a defensible record of what they did. 

To see what a more structured hold process looks like in practice, read how to simplify legal holds with Unity. 

Three Things Legal Ops Won’t Stop Talking About This Year 

A small group of legal operations professionals in an informal discussion around a laptop, in a modern office setting.

Walk into any legal ops conference this year and the agenda looks the same everywhere: AI, all day, every day. But underneath that one broad label, the actual conversations fall into three distinct buckets, operationalizing AI, untangling the tech stack, and a return to fundamentals, and the interesting part isn’t that teams are talking about these. It’s what’s different in how each one is actually being approached.

Is AI adoption still the open question? 

Not anymore. A recent Onit survey found that 70 percent of legal teams now have a mandate to use AI, which means the real question has moved on. It’s no longer whether to use AI. It’s what’s actually real versus hype, and how to turn early experimentation into value that can be measured rather than just felt. 

Enabling talent for that shift looks different team to team: prompt training, AI literacy assessments, and a genuinely new hiring category, legal engineers, sometimes called legal quants, who exist specifically to bridge legal judgment and technical implementation. Governance is moving just as fast. At a recent Onit App Builder user group, one legal team shared an internal app built to help senior lawyers review, approve, and track AI tool use across the entire company, a practical answer to a question a lot of legal departments are only starting to ask: who actually signs off when a new AI tool shows up inside the business. For a deeper look at how two legal departments are restructuring around this shift in practice, see Evolve or Get Left Behind: Designing the Future-Ready Legal Ops Team. 

Is the answer to AI sprawl just one more platform? 

Not exactly. The average lawyer already navigates somewhere between 30 and 60 applications to get through a normal day, and AI is adding to that list rather than replacing anything on it: frontier models, AI wrappers, MCP connectors, open source tools, and custom-built solutions all competing for a spot in the stack. Some teams are responding by building an orchestration layer that gives lawyers one place to access everything rather than switching between tools, while others are deliberately holding off, on the reasoning that not every problem is actually an AI problem in the first place. 

One rule of thumb making the rounds in Onit’s community cuts through a lot of the noise: review the tools you’re already paying for before buying something new, lean on platforms your team already has real experience with, and skip automating a process that wasn’t actually a problem to begin with. People, Process, Tools: Strategies for Smarter Legal Spend Management goes deeper on what that looks like for spend management specifically, one of the areas where stack sprawl shows up fastest. 

Is “back to fundamentals” just another buzzword? 

It keeps coming up for a reason. Underneath the AI conversation, three plainer questions tend to decide whether any of it actually works. Is the AI being powered by clean, relevant data stored in a unified place, or is it layered on top of the same scattered systems that caused problems before AI entered the picture? Are the underlying workflows actually defined and consistent, or does the result still depend on which person happens to handle a given request? And are the people affected by the change being brought along the journey deliberately, or is adoption just being announced and left to figure itself out? 

None of those three questions are new. Legal ops has been having versions of this conversation for years, long before AI made it urgent again. What’s changed is the cost of skipping them: AI makes good fundamentals pay off faster, and it makes bad ones fail faster and more visibly too, since a tool built on messy data or an undefined process doesn’t quietly underperform, it actively surfaces the mess. 

In practice, that’s rarely one dramatic failure. It’s duplicate vendor records that make a spend report quietly wrong in both directions at once, or two reviewers handling the same type of request two different ways because the workflow was never actually written down, just passed along informally from whoever trained whoever came before them. An AI tool layered on top of either one doesn’t fix it. It just answers questions faster using the same inconsistent underlying picture, which can be worse than not asking at all, since a fast wrong answer gets trusted more than a slow one. And the “bringing people along” piece isn’t a soft add-on to the other two. A workflow that’s technically correct still fails if the people using it don’t understand why it changed, since they’ll quietly route around it the same way they would any other process that wasn’t explained. 

Where this is still being worked out 

Onit’s OnPoint community has already run more than a dozen peer group meetings this year alone, on subjects ranging from international e-billing mandates to AI hallucinations showing up in court filings, whether the industry is in an AI bubble, and what CFOs actually want from legal. None of those have tidy answers yet, which is exactly why they keep coming back around. 

One thread worth watching: an upcoming session on outside counsel AI adoption and billing guidelines. If that’s a question on your mind already, You’re Negotiating Outside Counsel Savings. Can You Actually Prove Them? is a useful place to start now. For everything else, the conversations are ongoing in the OnPoint Community, and the next one is worth being part of rather than reading about after the fact.

Why Legal Ops Teams Are Asking Questions Instead of Running Reports

A legal operations professional typing a question into a chat panel beside a live dashboard with charts, in a clean modern office setting.

A leadership question about legal spend can trigger a reporting project: find the right report, adjust the filters, export the data, and repeat when the follow-up arrives. Ask Unity gives teams another way to get the information they need, directly within Unity ELM. 

Between April and August 2026, users asked Ask Unity approximately 5,000 questions about their own spend, matter, and vendor data. Ask Unity is Onit’s conversational way to work with data across Unity, starting with Unity ELM, and it lets users ask a plain-language question and get an answer, a chart, or a path to drill in deeper, directly inside the product they already use. 

That volume is worth noticing on its own. It points to something more specific than general interest in AI: teams are using conversation to access information that would otherwise require a reporting detour. For legal operations, that can mean less time assembling answers and more time interpreting what they mean for spend, workload, and outside counsel management. 

What are legal teams actually asking it? 

Spend and budget questions make up the largest share, about 30 percent of everything asked, covering what a team is spending and how it breaks down by matter, vendor, budget, or accrual. Status questions come up constantly too: where an invoice or vendor record stands, or how long it took to approve an invoice or close a matter. Other questions cover matter portfolios, vendors, timekeepers, and billing or compliance savings. 

That breadth matters. Legal operations decisions draw on more than invoice totals. Budgets, accruals, purchase orders, and matter information provide context for understanding financial exposure, reviewing outside counsel spend, and explaining results to finance. Ask Unity makes those data available through the same conversation. 

About 20 percent of questions are product how-to questions, the kind that used to mean a trip to the Resource Center or a separate support chat. Those two experiences were combined into Ask Unity in the August release, so the same conversation that answers a spend question can also walk someone through creating a matter or help them create a support ticket without leaving the chat. 

For occasional users, that brings product guidance closer to the task at hand. For legal operations, it can reduce the routine questions that interrupt higher-value work. 

Does this replace the reports teams already build? 

Ask Unity complements established reports by giving teams another way to answer ad hoc questions without building a report by hand. Two patterns show up repeatedly in how people actually use it. The most common is asking for a downloadable version of an answer, usually an Excel file. Close behind is drilling into a result with a follow-up question: adding a column, changing the date range, or breaking a number down by week instead of by quarter, without rebuilding the request from scratch. 

Answers can also take the form of line graphs, bar graphs, and pie charts, with options to download visualizations and export data. Teams can explore a result in conversation, then use the output in a leadership update, budget discussion, or further analysis. 

That flexibility matters when the first answer leads to another question. If finance asks for a different time period or a vendor-level breakdown, legal operations can continue the analysis in the same conversation. 

When a question is ambiguous, Ask Unity can ask a clarifying follow-up before answering. Asked something like who their slowest reviewer is, it can clarify which measure to use, such as average review time or the longest single review. Defining the measure helps users interpret the result before drawing conclusions about a potential bottleneck. 

What else do people use it for, beyond reporting? 

Two uses show up often enough to be worth calling out on their own. The first is summarizing key information tied to a matter or invoice, helping users get oriented without reviewing each detail individually. The second is finding data problems: missing fields, outdated entries, or records that should reconcile with each other but don’t, so a team can fix the underlying data instead of working around it. 

Ask Unity also supports an organization’s custom attributes alongside standard fields. That allows teams to explore information specific to how they organize their legal work and combine it with standard matter, vendor, or spend data in their questions. 

The business value is making the data teams already maintain more useful. Custom fields can inform analysis, while questions about missing or outdated information can help teams identify records that need attention. 

Who is this actually for, and what should teams expect today? 

Ask Unity is built into Unity ELM and supports legal operations, GCs, finance partners, procurement, and invoice reviewers. It shows up as a chat widget on every page in Unity, added in the August release, and supports questions across invoices, matters, vendors, timekeepers, budgets, accruals, purchase orders, custom attributes, and invoice reviewer rules. 

The conversation is not restricted to the page a user is viewing. Someone reviewing an invoice can ask about budgets or explore a broader spend question without navigating to a separate reporting page. Product guidance is available through the same chat. 

The clearest signal that a team is a good fit isn’t a title, it’s the behavior: people coming back weekly or monthly for the same kind of spend or matter information, recurring reporting requests, or reporting complex enough that it normally takes real effort to assemble. 

For those teams, Ask Unity provides a more accessible way to investigate day-to-day questions alongside their established reporting processes. Its combination of broad data coverage, custom attributes, conversational follow-ups, and exportable charts can help legal operations respond to business questions with less manual report assembly. 

For a broader look at how Onit is building AI into daily legal work rather than as a separate add-on, see Agentic AI in Legal Operations: What It Is and Why It Matters. To see where conversational access to your own data fits inside a full Enterprise Legal Management setup, visit Onit’s Enterprise Legal Management page. 

The Hardest Part of Legal Tech Modernization Isn’t the New System

Professional working at a desktop computer in an office, reviewing digital information and managing administrative tasks at a workstation.

Legal departments rarely set out to build a fragmented technology stack. It happens one decision at a time: a spend management tool here, a contract system there, each one chosen to solve a specific problem at a specific moment. Years later, those systems are still running, even after the vendors stop investing in them and the workarounds pile up around their limitations.

By the time a legal team decides to modernize, the new technology is usually the easy part to agree on. The hard part is everything that has to happen to the old systems first.

Why Replacing Legacy Legal Systems Is Harder Than Adding New Ones

Buying a new tool is additive. Replacing an old one is subtractive, and subtraction carries risk that addition doesn’t. Live matters, contracts, and historical data all depend on the system being retired. Teams have built years of muscle memory around its quirks. Every integration built on top of it has to be re-pointed or rebuilt.

That’s why legal technology debt accumulates quietly. No one decides to keep an outdated system on purpose. It stays in place because retiring it looks harder than tolerating it, until tolerating it becomes the bigger cost. Legacy systems built for a different era weren’t designed for how legal departments operate now, and the gap between what they can do and what the business needs keeps widening.

Retire First, Expand Second

Teams that modernize successfully tend to resist the urge to rebuild everything at once. Instead, they sequence the work: retire what’s broken, implement the core functionality the business depends on, stabilize the team on the new system, and only then expand into more advanced capabilities.

That sequencing decision extends to deployment strategy. A fully unified, single-instance rollout can be the right long-term goal, but it isn’t always the fastest or lowest-risk path to getting off a failing legacy system. Running parallel deployments on separate instances can let implementation teams move independently, which matters most when the legacy systems are actively degrading and timelines are tight.

Bringing every solution into one connected ecosystem is still the destination. It just doesn’t have to be the first step.

A Real-World Example: Medtronic

Medtronic, a global leader in healthcare technology, needed to retire legacy legal and contract management systems that had become outdated and difficult to maintain. Its long-standing vendors no longer met the organization’s operational needs, which introduced inefficiency, risk, and technical debt without a meaningful return on investment. With pressure to modernize quickly and control spend, Medtronic needed a flexible, cost-effective platform that could support both Enterprise Legal Management (ELM) and Contract Lifecycle Management (CLM) while stabilizing current workflows and leaving room for future expansion.

“We were replacing long-standing existing systems that were basically in a state of disrepair. The blessing was getting modern technology (to replace them) …the curse was you’re really kind of starting at a lower point (in retiring technology debt first),” said a Senior Director of Legal Operations at Medtronic.

After benchmarking competing legal solutions, Medtronic selected Onit as its enterprise partner, launching dual implementations of ELM and CLM on separate, dedicated instances rather than pursuing a single unified instance from the start. That decision let parallel deployment teams move independently, reducing complexity and accelerating value delivery under an aggressive timeline. The rollout itself followed a minimum viable product approach: retire the legacy systems first, implement core functionality, stabilize users, and build a foundation for future expansion.

That foundation delivered:

  • Technology consolidation: Aging legal systems replaced with a scalable, unified, modern platform.
  • Strategic architecture: Separate-instance deployment let parallel teams retire legacy systems faster while preserving ecosystem benefits.
  • Faster IT value delivery: Fewer tools in the legal tech stack, with the full team trained to manage Onit, freeing IT to focus on strategic support.
  • Greater agility: Legal operations can now make post-launch adjustments without large-scale development work.
  • Cost savings: A material reduction in licensing and support costs compared to the legacy tools.

“We appreciate having all capabilities integrated into a single, cohesive platform, which provides a streamlined and comprehensive solution. Additionally, the flexibility to make configuration changes post-implementation and adapt as needed has proved highly valuable for our team,” said a Senior Principal IT Project Lead at Medtronic.

What a Legacy Replacement Actually Requires

A few decisions tend to separate modernization projects that stay on track from ones that stall:

  • Benchmark before committing. Comparing capabilities, licensing, and total cost to implement across vendors surfaces trade-offs that a single demo won’t.
  • Decide sequencing deliberately. A unified single-instance approach and a parallel multi-instance approach both have a place. The right choice depends on how urgently the legacy systems need to come offline.
  • Build for post-launch autonomy. A platform that lets the legal team configure and iterate workflows after go-live reduces the ongoing burden on IT.
  • Measure the full cost of ownership, not just features. Licensing and support costs compound over years, and consolidating a fragmented stack often pays for itself in that line alone.

None of this is unique to one department or one pair of systems. The same questions come up whenever a team is deciding what modern ELM software actually needs to deliver or evaluating how contract lifecycle management fits into the broader legal tech stack.

See the Full Results

Medtronic’s legal operations team moved from reactive maintenance of failing systems to a modern, data-driven partner for the broader business. Read the full Medtronic customer story to see how the team sequenced its legacy replacement and what results followed.

Legal Invoice Review Should Optimize for Accuracy, Not Maximum Reductions

Legal invoice review should be measured by whether the department paid the right amount for the right work, not by how much it cut. Reductions are a frequent and legitimate result of review, but a program that treats accuracy as the primary goal rewards the right behavior, produces data that can be trusted and is better received by both inside and outside counsel attorneys.

Ask most legal departments how their invoice review program is performing and the answer is usually a reduction figure: total adjustments, write-down rate or dollars cut last quarter. The number is easy to report upward. It says little about whether invoices were reviewed correctly. 

What is legal invoice review actually for? 

Legal invoice review is the process of checking outside counsel invoices against the terms the company and the firm agreed to, then deciding what is appropriate to pay. Those terms live in outside counsel billing guidelines, approved rate structures and matter engagement letters, all set before the work begins. Both sides commit to something: the firm to bill in an agreed upon way, the department to pay for work billed in alignment with those terms. 

In The Right Invoice: Rethinking Legal Invoice Review, Onit’s Jeff Solomon, VP GTM Strategy, made the point directly: Compliance programs do not exist to save money. They exist to make sure the department pays the right amount for the right work.  

Savings remains a byproduct of compliance. When a firm bills for something the guidelines exclude, the correct invoice tends to be a smaller one. However, the reduction is the result of accurate review, not because it’s the objective. 

Why is the biggest reduction the wrong target for invoice review? 

A program measured on write-downs, rather than compliance, often creates three problems. 

It rewards the wrong finds. Reviewers evaluated on dollars cut have an incentive to pursue the reductions that are easiest to defend, rather than the charges that are actually non-compliant. The volume of adjustments becomes a stand-in for rigor. 

It hides inconsistency. Two reviewers can post similar reduction totals while applying the same guideline in different ways. The headline number looks stable while enforcement varies from reviewer to reviewer. 

It strains the relationship the guidelines were meant to support. Billing guidelines are a communication tool between a department and its firms. Compliance with an agreed upon rule is an easy conversation, aggressively going after savings seems more like a monthly negotiation. 

None of this means overbilling should go unchallenged. It means each challenge should rest on what was agreed, not on a target. 

What does accurate invoice review make possible? 

Accurate invoice review produces a high-confidence approval process and cleaner data to rely on afterward. Reviewers approve an invoice because it reflects the applicable terms, not by default. The benefits extend past the invoice in front of them: 

  • Consistent enforcement. The same term is applied the same way across firms, matters and reviewers, which is what gives a guideline meaning. 
  • Reliable spend data. If the department reports on spend by UTBMS task and activity codes, a misclassified line item distorts every report built on it. 
  • Stronger rate negotiations. Accurate billing history gives the department a defensible view of what each firm charged and delivered. 
  • Comparable matter costs. Total case costs can be compared across matters only when each matter was reviewed against the terms that governed it. 

Why is accurate invoice review harder than applying billing rules? 

Accuracy is difficult because many billing terms are contextual. E-billing rules handle fixed checks well, such as catching a duplicate invoice number. Whether a charge is appropriate, though, often depends on the firm, the type of work and what was negotiated for the matter. Onit’s decision framework for business rules, AI and human review covers which checks belong in each layer. 

The terms governing a single invoice can sit in three places: standard outside counsel guidelines, firm-specific or practice-specific guidelines, and matter-level engagement letters. Consider a common example: the general guidelines exclude computerized research, but the engagement letter for one matter permits it. An accurate review honors the engagement letter. A rule that only knows the general guidelines writes the charge down and creates a dispute the department then has to unwind. Why billing guidelines are not enough for matter-level review explains how to bring those terms into the review. 

Accuracy is also measurable. In research by Onit’s AI Center of Excellence, the top-performing model reached 92% invoice-level accuracy, compared with 72% for experienced lawyers reviewing the same invoices. 

Where does AI-assisted first-pass review fit? 

An AI reviewer is most useful in front of the human reviewer, not in place of one. Instead of starting from scratch, the reviewer receives an invoice already checked against the department’s own guidelines and engagement terms, with each finding explained. The reviewer’s job shifts from finding issues to deciding on them. First-pass review also closes the coverage gap that limits most review programs. Accuracy is what makes that wider coverage worth trusting. 

How much the first pass decides on its own is a governance choice. Spend Agent, available for OnitX ELM and Unity ELM, lets Legal Operations set each vendor to one of three modes: 

  • Sentry: Spend Agent identifies findings and calculates recommended adjustments, and a reviewer decides whether to accept them. Eligible adjustments can be shown as recommendations or pre-applied for review. Either way, the reviewer keeps the final invoice decision. 
  • Auto: Spend Agent automatically acts on invoices based on the department’s own guidelines, allowing the reviewer to receive a clean invoice for their final review. 
  • Off: The vendor’s invoices bypass Spend Agent and follow the standard billing workflow. 

These modes are governance choices, not maturity rankings. A department might use Sentry for high-value or sensitive relationships and Auto for lower-risk invoice populations. Engagement documents uploaded to the matter and associated with the vendor are reviewed alongside the general guidelines, and matter-specific terms take precedence where the two conflict. 

How should legal departments measure invoice review instead? 

Measure the quality of review decisions first and reductions second. Start with questions that describe accuracy rather than volume: 

  • What share of invoices are approved without follow-up disputes? 
  • How consistently is the same guideline applied across reviewers and firms? 
  • How often are matter-level exceptions honored on the first pass? 
  • How much reviewer time goes to judgment rather than to finding issues? 
  • Is billing data clean enough to support rate negotiations and panel decisions? 

Savings still belong in the report, measured carefully. Separate findings, recommended adjustments, accepted adjustments and realized savings. A flagged line is not a saving until the adjustment is applied and accepted. Being able to prove negotiated savings to finance and leadership is its own discipline. In an accuracy-first program, savings sit further down the report, as an outcome of review that works. 

Key takeaways 

  • Legal invoice review exists to confirm the department pays the right amount for the right work. Reductions are a byproduct, not the goal. 
  • Measuring review by write-downs rewards easy cuts, hides inconsistency between reviewers and strains outside counsel relationships. 
  • Accurate review depends on applying general guidelines, firm-specific guidelines and matter-level engagement terms together, with matter terms taking precedence. 
  • Better metrics include dispute-free approvals, consistency across reviewers and correctly honored exceptions, with savings reported as findings, recommended, accepted and realized. 

The goal was never the biggest reduction. It was the right invoice. For a practical model of how to get there, download The First-Pass Framework for Legal Invoice Review, which includes a governance worksheet for mapping one vendor or invoice population. 

Board-Ready Legal Reporting: Why University Legal Teams Still Build Reports by Hand

University legal team reviewing financial reports and charts for legal spend and matter reporting.

The board meeting is two weeks away. Trustees want an update on significant matters. The CFO needs to know how legal spend is tracking against budget before the next forecast. Institutional leadership is asking how many open matters involve a particular campus. 

So the Office of General Counsel does what it always does. Someone pulls matter status from one spreadsheet. Someone else exports invoice data. A third person reconciles the two because the numbers rarely match on the first pass. The final report looks polished. The process behind it is exhausting and has to be repeated next time. 

Why is legal reporting in higher education still so manual? 

Legal reporting in higher education is still manual because the data it depends on lives in separate places. Matters are tracked in spreadsheets or standalone systems, invoices move through email and accounts payable, and campuses or units often track work differently. When systems don’t share context, people become the connective tissue. 

That is a rational response to a fragmented environment. If no system holds the full picture, the only way to produce an accurate report is to assemble it by hand, every time. Each report starts from scratch, and nothing accumulates. 

Who relies on a university legal office’s reporting? 

A university’s Office of General Counsel often reports to several audiences, and each needs something different: 

  • The board: significant matters, legal risk and trends over time. 
  • Finance and the budget office: spend against budget, accruals and forecasts, especially during year-end budget scoping and ahead of a July fiscal year. 
  • Audit: consistent, traceable records. 
  • Procurement: which firms the institution uses and on what terms. 

Each request is reasonable. Together, they turn reporting into a recurring project that competes with the legal work itself. 

What are the hidden costs of building every report by hand? 

The obvious cost is time. Hours spent reconciling spreadsheets are hours not spent advising the institution, managing outside counsel or improving processes. The less visible costs are often more damaging: 

  • Inconsistent definitions. One campus might treat a matter as open until the final invoice while another closes it at resolution. Spend may reflect what has been invoiced rather than what has been committed. 
  • Stale information. Status fields show when someone last updated them, not where a matter actually stands. 
  • Lower confidence. Numbers assembled under deadline pressure are harder to stand behind than the polished report suggests. 
  • Decisions built on incomplete data. Leadership and the board act on these reports. Gaps in the data carry into the decisions. 

Why can’t a better dashboard fix the problem? 

A dashboard can only display the data it receives. Better visualization and filtering improve how information is consumed, but they don’t improve the information itself. 

A dashboard connected to a matter list that hasn’t been updated in two weeks shows a two-week-old picture. Spend data that arrives after invoices are approved, rather than when work is authorized, distorts the budget view. The fix has to happen below the reporting layer, in how matter, spend and vendor data are captured. For a deeper look, see why manual legal reporting effort exceeds the output. 

What happens to legal reporting when leadership changes? 

When reporting depends on individual effort, it is only as durable as the people doing it. A general counsel retires. The staff member who maintained the master spreadsheet moves to another role. A new administration asks for a different view of the same data. 

In a manual environment, each of those moments resets the clock. Historical comparisons become difficult, definitions drift and the context behind the numbers disappears. Durable reporting requires a durable record: matter, vendor and spend history that persists regardless of who is in the role. 

How does connected legal operations change reporting? 

Connected legal operations make reporting a byproduct of the work. When legal matter management, legal eBilling and vendor records share one system of record, the data stays current as work moves forward. 

A new matter carries its owner, campus, budget and outside counsel from the start. Invoices attach to the matter they belong to. Budgets and accruals update as work progresses. Reports can then draw on that record instead of a fresh round of spreadsheets. When the board, finance or an auditor asks, the information is already there and already consistent. 

What makes legal reporting board-ready? 

Board-ready legal reporting is current, consistent, traceable, complete and repeatable: 

  • Current: it reflects where matters and spend stand today. 
  • Consistent: it uses the same definitions across campuses, units and reporting periods. 
  • Traceable: every summary figure can be traced to the underlying matters and invoices. 
  • Complete: it covers the whole institution, not only the units that report most reliably. 
  • Repeatable: next quarter’s report doesn’t require rebuilding this quarter’s. 

Those qualities depend on the same foundation described in The Hidden Cost of Disconnected Legal Operations in Higher Education.

Where should a university legal office start? 

Before investing in another report template, find where the underlying gaps are: matter tracking, spend data, vendor records or consistency across campuses. A few practical first steps: 

  • Inventory your recurring reports. List every report the office produces, who asks for it, how often and how many hours it takes to assemble. The most effort-heavy report is usually the best place to start. 
  • Agree on definitions. Decide what counts as an open matter, when spend is recorded and how campuses categorize work. Consistent definitions make reports comparable from period to period. 
  • Trace one number back to its source. Pick a figure from your last board or budget report and follow it back to the underlying matters and invoices. If that takes more than a few minutes, the gap is in the data, not the report. 
  • Start before the next budget cycle. Aligning with finance ahead of year-end budget scoping and the July fiscal year gives the office time to improve the data before the next round of requests. 

When your office is ready to make reporting a byproduct of the work, Unity ELM is designed to serve as a connected legal system of record for matters, spend, vendors and reporting. 

The Hidden Cost of Disconnected Legal Operations in Higher Education

University legal operations professional reviewing data across multiple screens, illustrating the complexity of disconnected systems and reporting.

Many university legal teams carry enterprise-grade complexity without enterprise-grade legal infrastructure. Matters span multiple campuses and units. Outside counsel is engaged by different parts of the institution. Finance, procurement and leadership all need answers from the Office of General Counsel. 

The tools holding it together are often spreadsheets, shared drives, email and the memory of a few experienced people. That works until it doesn’t: a budget question that takes a week to answer, an invoice approved against the wrong rate, or a matter history that leaves when someone retires. Those moments are the hidden cost of disconnected legal operations. 

What are disconnected legal operations in higher education? 

Disconnected legal operations happen when a university legal office manages matters, outside counsel spend, vendor relationships and reporting in separate tools, so information has to be moved and reconciled by hand. In higher education, the problem grows when campuses and units each track legal work their own way. 

Each tool may handle its own task well enough. The trouble is what happens between them. A matter is opened in one spreadsheet, budgeted in another and invoiced through email. Spend data has to be exported and reshaped before finance can use it. Status updates depend on someone chasing an attorney for the latest information. Every handoff becomes a point where details get missed. 

Why are university legal departments especially exposed? 

Several conditions common in higher education make fragmentation more likely and more costly: 

  • Multiple campuses and units. When different parts of the institution engage counsel, approve invoices and track matters independently, no one has a complete view. 
  • Many stakeholders. Finance, procurement and IT each depend on legal data, and leadership and the board expect consistent reporting. 
  • Institutional memory. Experienced attorneys and staff often hold the history of key matters and firm relationships. When they move on or leadership changes, that history can go with them. 
  • Audit and accountability expectations. Institutional reporting needs to be defensible, which is difficult when the underlying data is scattered. 

How does fragmentation affect visibility into legal matters? 

Fragmentation turns basic questions into research projects. A general counsel should be able to see how many matters are open across the institution, who owns them, where they stand and which are trending over budget. When that information lives in campus spreadsheets and individual inboxes, answering takes a data-gathering exercise, and the result is out of date by the time it is assembled. 

Late visibility also means late action. A matter that is growing in scope or a unit engaging counsel outside established guidelines is easier to address early. Effective legal matter management gives the Office of General Counsel one current view of legal work across matters, campuses, owners and status. 

Where does outside counsel spend lose visibility? 

Outside counsel spend loses visibility in the gaps between invoices, matters and budgets. Invoices arrive by email. Billing guidelines sit in a document reviewers may or may not check. Approvals depend on who is available. Enforcement becomes selective, and over time, firms learn which rules matter. 

For a university, those gaps tend to surface at the worst moments: during budget scoping before year-end, when accruals are needed ahead of a July fiscal year, or when finance asks why spend exceeded forecast. Legal eBilling with budget enforcement, accruals and consistently applied billing guidelines turns those questions into routine reports. 

Why shouldn’t vendor knowledge live in someone’s memory? 

Vendor knowledge shouldn’t live in someone’s memory because the institution loses it when that person moves on. Which firms handle which types of work? What rates were agreed, and by whom? Which relationships have needed repeated invoice adjustments? 

When that information isn’t structured, different units can engage the same firm on different terms, and performance conversations rely on anecdote. Legal vendor management built on connected matter data gives the institution a record of outside counsel relationships, rates, engagements and firm data that lasts beyond any one person. 

“We already have a process.” Why isn’t that enough? 

Most university legal offices do have processes, and many work reasonably well day to day. Individual tools can handle individual tasks. What they can’t do is connect matters, spend, vendors and reporting in a governed system that persists across teams, audits and leadership transitions. 

A spreadsheet can list matters. It can’t enforce a billing guideline, track an accrual against budget, keep rates consistent across units or preserve a reliable history when its owner leaves. Disconnected processes also tend to persist because they grow gradually, with tools adopted at different times by different units to solve immediate problems. The gaps usually stay hidden until a leadership transition, an audit or a major matter exposes them. 

What does a connected legal system of record look like? 

A connected legal system of record brings matter, spend, vendor and reporting information into one governed environment, so an update made once is reflected everywhere it is needed. For a university legal office, that means: 

  • Matter visibility: one current view of legal work across matters, campuses, owners and status. 
  • Spend control: eBilling, budget enforcement, accruals, rate governance and spend reporting. 
  • Vendor governance: structured outside counsel relationships, rates, engagements and firm data. 
  • Reporting and continuity: defensible institutional reporting, plus matter, vendor and spend history that survives leadership change. 

With that foundation, legal, finance and procurement work from the same numbers. Reporting to leadership and the board also becomes far less manual, a topic covered in Board-Ready Legal Reporting: Why University Legal Teams Still Build Reports by Hand. 

How can a university legal office start? 

Start by finding where disconnection creates the most friction. Is it between campuses that track matters differently? Between invoice approval and budget tracking? Between vendor engagement and performance review? Or between the data Legal holds and the reports leadership needs? 

Then take a few practical first steps: 

  • Map the current state. List where matters, invoices, rates and vendor records live today, and who maintains each one. 
  • Set a baseline. Count open matters across campuses, total year-to-date outside counsel spend and note how many firms are engaged and at what rates. If those numbers are hard to pull together, that’s a finding in itself. 
  • Bring finance and procurement in early. They depend on the same data, and aligning before budget scoping and the July fiscal year makes the case for change easier to build. 
  • Fix the biggest gap first. One connected workflow, such as eBilling with consistent billing guidelines, often shows value quickly and builds momentum for the rest. 

When your office is ready to connect that work, Unity ELM is designed to serve as a connected legal system of record for matters, spend, vendors and reporting. 

What Is a Legal Hold, and Why a Defensible Process Matters More Than Ever

Cloud data storage, file management, and cybersecurity technology concept.

 The duty to preserve evidence once litigation is reasonably anticipated is not new. What has changed is the level of scrutiny organizations face regarding whether that obligation was met, and whether they can demonstrate that it was met. 

Much of that scrutiny traces back to a landmark preservation dispute involving Morgan Stanley in the mid-2000s. The case centered on preservation failures that included overwritten emails, missing backup tapes, and searches the company represented as complete but later proved insufficient. The court found spoliation, the improper destruction or alteration of evidence, and shifted the burden of proof against the company before the underlying dispute was even decided on its merits. 

Shortly afterward, preservation obligations became more formally embedded in the Federal Rules of Civil Procedure and, over time, across many state court systems as well. Today, the obligation to preserve evidence generally arises once litigation, a government investigation, or a regulatory inquiry is reasonably anticipated, not when a lawsuit is officially filed. 

What a Legal Hold Actually Is 

A legal hold is the process organizations use to meet their preservation obligations. 

While individual processes vary, legal holds typically involve three core stages: 

1. Identify the Obligation 

Legal teams determine what information may be relevant to a matter and identify the individuals who possess or control that information. 

2. Notify and Preserve 

Those individuals, commonly referred to as custodians, receive preservation instructions, acknowledge their obligations, and take steps to retain relevant materials. 

3. Manage Through Release 

Legal teams track responses, update hold requirements as circumstances evolve, and formally document when preservation obligations end. 

The goal is straightforward: create a consistent, documented record of what actions the organization took, when it took them, and who was involved. If a regulator, court, or opposing party later challenges the preservation effort, that record becomes critical evidence of the organization’s process. 

What Happens Without a Real Process 

Many organizations still administer legal holds using email and spreadsheets. 

In a basic sense, the approach can work. Notices are sent. Responses are collected. Records are maintained. 

However, several operational challenges tend to emerge over time: 

  • Manual notice distribution and follow-up consume legal team resources that could otherwise be dedicated to substantive legal work. 
  • Custodian information becomes outdated as employees change roles, switch managers, or leave the organization. 
  • Matter records and hold records become disconnected, making reconstruction of a complete matter history difficult. 
  • Visibility into acknowledgment status is limited, making it harder to identify non-responsive custodians or missed preservation steps. 
  • Execution varies from team to team, reducing consistency and making governance harder to demonstrate. 

None of these challenges are necessarily catastrophic on their own. Problems arise when a preservation effort is questioned and the organization must reconstruct exactly what occurred, often months or years after the fact. 

What a Defensible Record Needs to Show 

When a legal hold is challenged, organizations generally need to answer a specific set of questions: 

  • Who received the preservation notice? 
  • What information were they instructed to preserve? 
  • Who acknowledged or attested to their obligations? 
  • What follow-up actions occurred when acknowledgments were not received? 
  • When did preservation obligations change, and how were those changes documented? 
  • When was the hold released, and how was that release communicated? 

When those answers are scattered across email inboxes, spreadsheets, and manually maintained records, legal teams often face unnecessary administrative effort and increased organizational risk. 

A defensible process should make these answers accessible, consistent, and well documented. 

This Isn’t Only a Large-Enterprise Problem 

Legal holds are often associated with large enterprises and high-profile litigation. 

In practice, organizations of many sizes face employment disputes, regulatory inquiries, commercial litigation, and other matters that trigger preservation obligations. 

The challenge is not solely the volume of litigation exposure. It is the ability to demonstrate what actions were taken, when they occurred, and who was involved. 

That requirement does not disappear simply because an organization is smaller. 

Building a Defensible Process 

A structured legal hold program built around standardized templates, tracked acknowledgments, documented follow-up, and centralized records creates a stronger foundation for meeting preservation obligations. 

The objective is not simply sending notices. It is creating a repeatable and well-documented process that enables legal teams to answer difficult questions when they arise. 

Onit Legal Holds helps connect hold execution directly to matter management, allowing hold activity and matter records to remain linked throughout the life of a matter rather than existing as separate administrative processes. 

For a deeper look at how a structured approach can improve the legal hold experience, read How Legal Hold Software Supports Litigation Peace of Mind. 

Legal Ops Doesn’t Need an IT Ticket for Every Workflow

Legal operations professional working at a laptop with workflow automation icons and directional arrows illustrating streamlined legal workflow automation and process management.

Most legal departments can name a dozen manual processes they’d automate tomorrow if they had the resources: an intake form that should route itself, an approval that still moves by email, a certification that gets tracked in a spreadsheet instead of a system of record. 

The idea isn’t the hard part. The build is. 

In a lot of organizations, turning a workflow idea into a working process means submitting a request to IT, waiting for it to reach the top of a queue that legal doesn’t control, and hoping the final product matches what the team actually asked for. For a legal department managing a handful of processes, that delay is annoying. For a legal department managing hundreds of processes across multiple regions and business units, it’s a structural limit on how fast the function can operate. 

When Every Workflow Competes for the Same Developer 

IT-dependent workflow building doesn’t scale with legal’s needs, because legal’s needs and IT’s priorities rarely move at the same pace. A new disclosure requirement, a shift in how a business unit handles vendor onboarding, or a spike in a particular request type can all create an immediate need for a new or updated workflow. But IT teams are managing their own backlog, and legal requests are competing with everything else on it. 

The result is familiar to a lot of legal operations teams: workarounds. Processes stay in email and spreadsheets longer than they should, not because anyone prefers it that way, but because building something better isn’t within the team’s control. That’s one of the common manual habits still holding legal departments back, and it tends to persist until legal has a way to build without waiting. 

What Changes When Legal Can Build Its Own Workflows 

Low-code platforms shift where workflow ownership sits. Instead of writing a specification and handing it to a developer, legal operations teams can configure the workflow directly, adjust it based on how people actually use it, and expand it to new use cases without opening a new project with IT every time. 

That doesn’t remove IT from the picture entirely. Integrations, security requirements, and enterprise-scale deployment still benefit from IT’s involvement. What changes is the day-to-day iteration: legal can stand up a new workflow, test it with a small group, and refine it in days rather than months. 

Onit’s App Catalog and Apptitude are built around that model, and the same logic applies to how legal teams handle inbound requests through a Legal Service Request system: routing work to the right resource automatically, rather than triaging it manually. 

A Real-World Example: ADM 

Archer Daniels Midland (ADM), one of the world’s largest agricultural processors and food ingredient providers, faced this challenge at global scale. ADM’s Legal Affairs, Regulatory & Compliance (LARC) department manages a wide portfolio of litigation, regulatory, compliance, and commercial matters across regions, and needed a way to standardize procedures and reduce manual burden without becoming dependent on IT for every change. 

Since adopting Onit in 2015, ADM has continued to expand its use of the platform. Powered by Apptitude, ADM’s low-code, highly configurable model has enabled the LARC team to build hundreds of purpose-built workflows supporting its own function and the broader business. Today, with more than 18,000 users globally, Onit serves as ADM LARC’s system of record and reporting. 

That foundation supports a wide range of use cases: 

  • Contract lifecycle automation: NDA intake and auto-creation, integrated with DocuSign, reduced turnaround from weeks to hours by eliminating manual steps. 
  • Legal Service Request: Increased transparency for business users and routed requests to the right legal resource automatically. 
  • Compliance and risk workflows: Automated processes from conflict-of-interest review to quarterly disclosure certifications. 
  • Attorney management and internal approvals: Custom tools for onboarding, budget approval, law firm RFP and preapproval, and engagement letter execution. 
  • Bond and insurance certificate processes: Centralized, self-service workflows in place of fragmented manual steps involving multiple parties. 
  • Real estate process management: End-to-end tracking from initial need through execution and handoff to lease management. 

ADM also builds in MVP-style iteration, using early usage data to refine each workflow so automation stays aligned with how the business actually works, rather than how it was originally scoped. 

“Having a platform and partnership with Onit has been game-changer for ADM, having the ability to quickly turn ideas into action to eliminate an inefficiency and/or create visibility in a process has allowed us to build credibility with our business partners and other functional colleagues,” said Aaron Van Nice, Vice President, LARC Operational Excellence. 

Building a Workflow Model That Scales 

A few practices separate legal teams that scale automation successfully from those that stall out after the first few workflows: 

  • Start with the processes causing the most friction, not the ones that are easiest to build. High-friction, high-volume processes deliver the clearest return and the strongest case for expanding the program. 
  • Treat the first version as a starting point, not the final product. Usage data reveals what a workflow needs to actually do, which is rarely identical to how it was first scoped. 
  • Keep IT involved where it matters. Integrations, data security, and enterprise rollout still benefit from IT’s expertise, even when day-to-day configuration doesn’t require it. 
  • Measure adoption, not just completion. A workflow that’s technically live but rarely used hasn’t solved the underlying problem. 

None of this requires legal to become a technology function. It requires a platform that lets legal operations build, test, and adjust workflows at the pace the business actually needs, which is a theme that shows up across modern legal operations more broadly, not just in workflow automation. 

See the Full Results 

ADM’s LARC department has moved from addressing isolated workflow challenges to supporting enterprise-wide transformation across a global legal function. Read the full ADM customer story to see how the team built and scaled hundreds of automated workflows, and what results followed. 

Where Legal Hold Processes Break Down and What a Stronger Process Looks Like 

Falling dominoes halted by a gap in the sequence, symbolizing how strong legal hold processes prevent compliance risks, preservation failures, and litigation challenges.

Legal hold problems rarely start with one dramatic failure. More often, risk builds through smaller process gaps: a custodian list that goes stale, a reminder that goes out late, a preservation issue that isn’t surfaced, or a release that isn’t clearly documented. Individually, those gaps may seem manageable. Together, they can make it harder to demonstrate the reasonable, consistent preservation process Legal intended to follow. 

In a recent Onit webinar on closing the gaps in legal hold processes, the throughline was straightforward: legal holds are rarely managed in one place. Most organizations run some mix of specialized technology and manual process across identifying custodians, tracking HR changes, monitoring preservation status, and reporting. Each handoff between those pieces is a place where something can slip. 

A Useful Frame: The Information Governance Reference Model 

Before getting into where things break down, it’s worth grounding the discussion in a framework that already exists for this. EDRM, the organization behind the Electronic Discovery Reference Model, maintains an Information Governance Reference Model that lays out a cross-functional approach to managing information, including stakeholder alignment, retention decisions, and the ongoing processes that connect them. It’s a useful reminder that legal holds don’t exist in isolation. They sit inside a broader information governance structure that touches Legal, IT, HR, and Records Management alike. 

With that frame in mind, here’s where the hold lifecycle itself tends to break down. 

Where the Process Breaks Down, Stage by Stage 

Identifying custodians. This is the first place data goes stale. People change roles, leave the company, or pick up new responsibilities, and a manual process often doesn’t catch it. Without a way to track this in real time, the custodian list on day one of a hold can already be wrong by day thirty. 

Issuing notice. Instructions vary depending on who is writing them and when. Without a defined template covering purpose, scope, suspension of routine deletion, and confidentiality, notices can end up inconsistent across groups handling similar matters. 

Acknowledgment tracking. Once a notice goes out, Legal needs visibility into whether custodians have received and acknowledged it. In a manual process, those acknowledgments often land in an inbox with no structure behind them. In larger matters where a hold notice might go to hundreds of people, identifying exactly who among them hasn’t responded becomes a real burden, not a minor annoyance. 

Follow-up and escalation. Reminder timing tends to be inconsistent without something automated managing it. Instead of a defined cadence, follow-up often depends on someone remembering to check for non-responses, which is exactly the kind of gap that shows up later if a hold gets challenged. 

Preservation. A hold ultimately has to translate into reasonable steps to preserve potentially relevant information. But preservation activity can sit outside the day-to-day hold workflow, leaving Legal and IT to reconcile status across systems. When preservation requests, status, failures, and follow-up aren’t visible alongside the hold itself, identifying exceptions becomes harder. 

Release and reporting. Releasing a custodian from a hold, and documenting that release, is easy to do inconsistently. Reconstructing who is or isn’t currently subject to a hold, at best, means pulling data from multiple systems. At worst, it’s a fully manual exercise every time someone asks. 

What a Stronger Process Looks Like 

A few foundations show up consistently in a process that holds up under scrutiny: 

  • Connection to matter context. The matter explains why a hold exists; the hold addresses what happens next. When hold activity, including notices, acknowledgments, escalations, and releases, stays tied to the matter record, Legal gets a complete view without reconciling separate systems. 
  • Clear custodian accountability. Knowing what each custodian is required to do, whether they’ve acknowledged it, and whether they’re actually following through, rather than assuming a notice sent equals a notice actioned. 
  • Consistency in notices, reminders, and escalations. The same level of detail and the same cadence applied every time, not dependent on who happens to be running a particular matter. 
  • Real visibility into status. Surfacing what’s complete, overdue, or needs attention through alerts, rather than requiring someone to run a report to find out something already went wrong. 

The point of technology in this process is to support it, not replace judgment. Automating notice delivery, acknowledgment tracking, and status alerts doesn’t remove Legal’s role in deciding scope or handling exceptions. It removes the administrative burden that makes those small gaps likely to happen in the first place.