Legal departments face three forces that compound. External obligations add complexity, enterprise demand adds volume, and urgency removes the time needed to handle both. These forces become unmanageable when the legal function has no connected system of record and no deliberate operating model. The response starts with a pressure map, agreed ownership and priority rules, and connected records for the evidence the team rebuilds most often.
Ask a General Counsel what consumed their team this year and you’ll hear about work they thought they had already finished.
An assessment is reopened. A clause is renegotiated after sign-off. A register is rebuilt because nobody can prove which version was approved. Around these tasks sit requests that arrive on the day they’re due, regulatory changes that have to be absorbed within weeks, and AI tools that reach the business before legal hears about them.
Some of that pressure comes from new laws and regulations, but much of it comes from inside the organization. The Omnibus Directive, for example, changed sustainability reporting and due-diligence requirements for affected companies, forcing some teams to revisit positions they had already settled.
Complexity, volume and urgency are real, and they aren’t going away. They become unmanageable when the function has no connected system of record and no deliberate operating model. Without the first, every answer is rebuilt from scratch. Without the second, priority goes to whoever escalates loudest. That’s why finished work keeps coming back.
Resolving it means tracing each force to its source, seeing how it shows up in a team’s week, then separating what leadership has to decide from what a connected record has to carry.
Understanding where the pressure comes from
These forces aren’t new. What has changed is how far they exceed the legal function’s ability to absorb them, as the role of legal has expanded, the GC’s remit has grown, and the underlying pain points have become harder to ignore.
Each force affects the team differently. External obligations add complexity, enterprise demand adds volume, and urgency removes the time needed to manage both.
External obligations: the force that adds complexity
Counting obligations doesn’t explain the complexity legal teams face today. The difficulty lies in how those obligations interact and in how many parts of the business each one touches. A single transaction can involve privacy, AI, sector rules, and reporting duties at once, each with its own scope, deadline, and standard of proof. When the rules change mid-program, work that was already signed off becomes rework.
An auditor gives you five days to prove that a control operated eight months ago. The control worked. Finding the evidence is the problem, so three people spend a week rebuilding a record that should already exist. The stakes are clear: recent GDPR enforcement data puts fines at roughly €1.2 billion in 2025, while breach notifications rose 22% to around 443 a day. A control that worked counts for little if the organization can’t prove it.
These answers rarely belong to one lawyer from start to finish. They have to be assembled from information held across teams and systems. When the supporting records aren’t documented, senior lawyers spend their time coordinating and reconstructing instead of exercising judgment. The most experienced person in the room becomes the one who knows where everything is kept.
Enterprise demand: the force that adds volume
Legal used to be consulted at specific moments: a deal, a dispute or a filing. As the role of the legal function has evolved, it has become embedded in more parts of the business. Each expansion created a standing dependency, and those dependencies generate requests over time. The remit grew, but the team didn’t necessarily grow with it.
That makes the existing complexity harder to manage. Legal now handles more requests, and many of them need input from several parts of the organization.
Consider a common situation: a business unit deployed an AI tool months ago, and legal finds out in a renewal thread. Microsoft and LinkedIn research found that 75% of knowledge workers already use generative AI at work and 78% bring their own tools, so that discovery is becoming routine. The tool then raises several questions at once: is it a processing activity, which vendor terms apply, what data-transfer implications exist, and how should the use case be classified?
Requests arrive through every channel, so the team can’t see its own queue because it lacks a legal intake process. Nobody can say what legal is carrying, which turns every prioritization conversation into a debate driven by isolated examples.
Urgency: the force that removes the slack
Legal’s work has become a dependency in someone else’s deadline. Lateness has a visible commercial cost, while carefulness has an invisible one, and that asymmetry shapes how the week gets spent. Urgency removes the buffer that once absorbed complexity and volume. Accountability then closes the last exit: the fast answer still has to be provable later, by a date, with a named owner, and in a form a regulator accepts.
A contract needs three sign-offs across two jurisdictions. It sits for six days, and nobody can say whose desk it’s on without asking. A board pack is assembled by email and versioned in filenames, and the copy that gets circulated turns out not to be the approved one.
Prioritization becomes reactive. Whoever escalates hardest gets served first, even though escalation volume is a poor proxy for risk. Work carrying real exposure and no internal champion waits.
Three multipliers, one team
These pressures compound. Complexity makes each item slower, volume creates more items, and urgency removes the slack needed to handle them. Three multipliers act on one fixed team, which is why the bind is structural rather than seasonal. Recent legal department benchmarking puts the median at 367 employees per lawyer, up from 300, while legal spend as a share of revenue sits at a six-year low. Read together, those numbers describe a function asked to carry more with proportionally less.
Every General Counsel recognizes these forces, and many have recognized them for years. Recognition on its own doesn’t change the operating reality. For anything to move, the pressure has to become a reason to act, and the response has to address more than the loudest symptom.
How technology can ease the pressure points
That is usually the moment a shortlist of tools appears, which is the wrong place to start. Before comparing options, a department has to know which of the three forces is binding it, in what order and at what cost. Many teams can describe their sources of pressure but can’t rank them, and without that ranking the decision gets shaped by a vendor’s narrative instead of the department’s own evidence.
Start with the pressure map
Fixing a lower-priority problem first may produce a gain in an area nobody sees as urgent. Diagnosis doesn’t need a new system: track your legal KPIs, he sources of requests, how long they sit, and how often the team re-establishes information instead of deciding. Then start with what costs most.
Separate managerial problems from technical ones
Technology can’t resolve all of these problems. Urgency is partly managerial, because no system decides which requests deserve priority. Coordination is partly organizational: software that routes work between functions that haven’t agreed who decides only automates the confusion. That part needs leadership and clear ownership, not software. What’s left is technical: evidence gets reconstructed, the queue stays invisible and answers that cross entities, contracts and board records are assembled by hand each time.
The legal operating system as the information layer
Finance has ERP, sales has CRM and HR has HCM. Legal has accumulated point tools that don’t talk to each other, and even a contract lifecycle management system can’t answer questions spanning contracts, entities, board records and matters. A legal operating system proves itself in the team’s week.
- Connected information, so an answer is assembled once instead of tracked down from whoever knows where it’s kept.
- A visible queue, with evidence captured as work happens. This way, priorities are defended with data and the auditor’s question is answered before it’s asked.
- A modular entry point, so the first implementation addresses the department’s highest-priority problem.
- Records that hold up, because structure, security, and data sovereignty decide whether information is trustworthy in an audit. Those factors also determine whether it is safe to use with AI.
Each of those aspects answers a different pressure point, and no department feels them all with the same weight. Which one comes first, and what leadership settles before it goes live, determine how quickly the team feels the difference.
From reconstructing the record to deciding with it
The pressure map is where the work starts, and the order of what follows matters.
- First, rank what each force costs the team today: hours spent hunting for evidence, contracts stalled on an unclear sign-off, requests that never reach a queue.
- Second, settle the questions no software can answer: agree who owns each type of decision and what earns priority. Then write those rules down so they hold when the next deadline lands.
- Third, connect the records the team keeps piecing back together, starting with the ones auditors and boards ask for. These might include proof that a control operated, or the resolution that authorized a contract.
That information layer is most useful once the rules it supports are agreed on.
Done in that order, the change shows up in how the business sees legal. Once legal can answer from its own record, it moves from the team that pieces together what happened to the team that can prove it and decide what comes next.
Frequently asked questions
Why are legal departments under so much pressure?
Three forces act on the legal function at once. External obligations add complexity, enterprise demand adds volume, and urgency removes the time needed to handle both. ACC benchmarking puts the median at 367 employees per lawyer, up from 300, while legal spend as a share of revenue sits at a six-year low.
How can a legal department handle a growing workload without more headcount?
Start by measuring where the workload comes from: which channels send requests, how long each request waits and how often the team rebuilds information it already had. Then fix the most expensive problem first. Agreeing on who owns each type of decision and what earns priority often removes as much friction as any new tool.
What is a legal operating model?
A legal operating model sets how the legal function works: who owns which decisions, how requests come in, how priority is set and which systems hold the record. Without a deliberate model, priority tends to go to whoever escalates loudest rather than to the work carrying the most risk.
What is the difference between a legal operating system and CLM?
A contract lifecycle management (CLM) system manages contracts. A legal operating system connects contracts, legal entities, board records and matters, so an answer that spans them is assembled once instead of tracked down by hand. It plays the same role for legal that ERP plays for finance and CRM plays for sales.
Can legal technology fix prioritization problems?
Only in part. Software can make the queue visible and capture evidence as work happens, but no system decides which requests deserve priority. That decision needs leadership and clear ownership, written down before any tool goes live.
Where should a General Counsel consider before buying legal technology?
Start with a pressure map rather than a vendor shortlist. Rank which force is binding the team and what it costs today, settle ownership and priority rules, then connect the records that are most expensive to reconstruct, such as control evidence for auditors.
