LoginStart Trial

What is legal transformation?

Andrew Mellett • 7 July 2026

What is legal transformation?

The term gets used loosely, but the shift it describes is specific. A legal function that has not transformed reacts to whatever the business sends over: review this contract, answer this query, sign off on this campaign. A transformed legal function has redesigned its operating model so that routine work is automated or self served, and lawyers spend their time on the advisory and risk work that only they can do.

Plexus's Future-Ready General Counsel 2026 report, based on responses from 150 General Counsel across Australia, the United States, New Zealand and EMEA, found that 58.7% of GCs are actively adopting AI across legal workflows. Only 6.7% have fully operationalised an AI-enabled operating model. That gap is the entire story of legal transformation in 2026: adoption is happening everywhere, but operationalisation, the actual redesign of how work gets done, is rare.

The pressure behind this is structural, not optional. 81% of GCs say their teams lack the staffing to do their jobs effectively, and in Australia that figure rises to 97%. At the same time, AI is currently a workload multiplier rather than a workload reducer for legal, because every AI-generated contract, communication and policy created elsewhere in the business produces a downstream legal obligation. Waiting is not a neutral choice.

Legal operations is the discipline of running the legal function efficiently: process, technology, metrics, and vendor management. Legal transformation is the broader change programme that legal operations sits inside. You can improve legal operations without transforming the function, tightening a workflow here, adding a dashboard there, but legal transformation asks a bigger question: what should this function look like when it is built for how the business actually works today, rather than how it worked ten years ago.

A legal operating model is the explicit definition of what a legal team handles directly, what it hands to self-service or automation, and what it delegates to outside counsel, along with the structure, workflows and technology that support those decisions. Most legal functions do not have one written down. They have a default instead, which is that whatever is most urgent gets done first and everything else waits. An undocumented operating model always defaults to the loudest request, not the highest-value one.

A documented legal operating system extends the operating model concept into a single platform that manages all legal work, contracts, matters, compliance and legal AI, rather than leaving each category in a separate point solution. See how Plexus AI supports this in practice.

Analysis across 340 in-house legal teams in Plexus's legal function diagnostic identifies where transformation actually has to happen. Four components come up consistently.

1.   Operating model redesign. Define explicitly what lawyers do, what self-service handles, and what technology decides. A documented model with published service levels is the single highest-return investment a GC can make.

2.   Automation and AI, starting with contracts. Contracts and procurement account for 38% of lawyer time on their own, and it is the category with the clearest automation potential. Contract review and drafting is the most widely adopted AI application in legal, cited by 94% of active AI users, because it has the lowest implementation risk and the fastest visible return.

3.   Proactive compliance. Moving compliance from an annual review cycle to continuous monitoring closes the gap between when a risk emerges and when someone notices it.

4.   Measurement that speaks the board's language. GCs who track legal function performance in cost and volume terms struggle to get funding. GCs who translate the same data into business outcomes get a different conversation. The full methodology for running this kind of diagnostic on your own team is in Plexus's guide to where lawyer time actually goes.

1.   Run a time audit. Two weeks of time logging, tagged to a small set of categories, is enough to produce usable data. The full methodology is in Plexus's legal time audit guide.

2.   Benchmark the findings. Compare your team's split against the pattern seen across 340 in-house teams: high performing functions keep contracts and procurement under 25% of total time, and strategic advisory over 40%.

3.   Start with the highest-automation category. For most teams that is contracts and procurement. Do not try to transform everything simultaneously; the teams that succeed sequence the work.

4.   Build a board-ready business case. Convert the automatable time percentage into a dollar figure against your legal salary cost, and frame the investment as a reallocation of existing spend rather than new budget. Plexus's guide on how to build a legal AI business case walks through the calculation your CFO will actually engage with.

5.   Redeploy the recovered capacity deliberately. Capacity that automation frees up does not automatically become strategic work. It has to be redirected on purpose, into advisory work, proactive risk management, or faster business partnering, or it simply refills with more of the same reactive work.

Most organisations reach initial operational AI maturity in 12 to 24 months. The typical path starts with contract review and drafting, extends into compliance monitoring and knowledge management, and matures into risk scoring, predictive analytics and eventually agentic AI. The speed depends mainly on data quality, governance clarity and leadership commitment, not on the availability of technology.

The General Counsel or Chief Legal Officer typically owns it, but the distinction between those two roles is itself part of the transformation story. A General Counsel operates reactively, matter by matter, measured by cost, and usually reports to the CFO. A Chief Legal Officer operates proactively, with a portfolio view, measured by business outcomes, and usually reports to the CEO or board. The move from one to the other is not a title change. It requires automating the commodity work, architecting an explicit operating model, and claiming the AI governance agenda that sits unowned in most organisations today. The operating model differences between the two roles, and what the transition actually requires, are covered in full in Plexus's guide on moving from General Counsel to Chief Legal Officer.

The most successful transformation initiatives are not solely legal-owned. Joint sponsorship with finance and operations leadership secures the budget and cross-functional buy-in that a legal-only initiative rarely gets.

For a deeper look at how the General Counsel role itself is changing, see what is a general counsel.

Plexus is a single platform for contracts, matters, compliance and legal AI, built for legal functions redesigning how they work. See Plexus AI in action, or start with your own audit using the legal time audit methodology.