Legal Requests by Business Unit: Benchmarks and What They Reveal About Your Company

Legal requests by business unit is a legal KPI that segments incoming legal work by the internal team or function that submitted it, such as sales, product, HR, finance, procurement, or marketing. 

The distribution reveals which parts of the business rely on legal most, which are underserved, and which may be routing around the function entirely. It's one of the most useful business intelligence signals in-house legal produces, and one of the most frequently misread. 

Reading it well starts with knowing what a healthy distribution looks like in your company type, and what an unhealthy one is trying to tell you.

How Requests by Business Unit Are Typically Distributed

Once they can measure legal requests by business unit properly, most in-house legal teams notice the same overall patterns:

• Sales and commercial functions usually lead in raw volume, driven by contract review and negotiation work. 
• HR sits behind sales but tends to be the most consistent contributor, generating a steady stream of employment, benefits, and policy work. 
• Product and engineering typically rank higher in tech companies than in traditional industries, mostly because of IP, licensing, and privacy questions. 
• Procurement is often lower in volume but higher in complexity per request. 
• Marketing is variable and campaign-driven, spiking around launches and quiet in between. 
• Finance and the executive office sit toward the tail, but individual requests from those functions carry disproportionate weight.

The specific ordering shifts with company type and stage. What matters more than the exact ranking is whether the data actually captures every business unit. If your legal request intake system can’t identify which team submitted each request at the time it’s created, any reporting based on it won’t be reliable. A structured legal front door that automatically pulls business unit data from Microsoft Teams, Slack, or other communication channels can help provide clear, useful insights.

Benchmarks by Company Type

Distribution patterns vary predictably by industry, and knowing the pattern for your company type is more useful than a universal benchmark.

SaaS and Technology

Sales and commercial functions dominate, typically making up the largest share of total requests. Product, procurement, and HR follow behind. Legal is heavily involved throughout deal cycles, particularly for enterprise contracts and data protection reviews.

Financial Services

Compliance and regulatory work sits alongside commercial as the top driver, with procurement and HR close behind. The regulatory function is often a large internal client in its own right, separate from the business units it supports.

Healthcare and Life Sciences

Compliance, HR, and procurement typically lead, with clinical operations generating steady vendor, licensing, and privacy work. Commercial volume tends to be lower than in other industries but higher in complexity per request.

Manufacturing and Industrial

Procurement, commercial, and safety or employment work usually lead. Supplier agreements and regulatory matters generate more consistent volume than in tech or professional services.

These patterns are consistent with published legal operations research, including ACC and Bloomberg Law surveys. Industry benchmarks are directional; your own twelve-month historical trend is diagnostic.

‍

What Does High Concentration in One Business Unit Indicate?

A heavily concentrated distribution is not automatically a problem. If sales is 60 percent of your total requests in a SaaS company with a fast-moving commercial motion, that's a reflection of business reality.

The signal to watch for is concentration that doesn't match the business. If sales generates most of your volume but the company is a regulated business with heavy compliance obligations, something may be off. Either the regulatory function has stopped routing work through legal, or the intake system isn't capturing it, or the risk exposure is quietly accumulating outside legal's line of sight.

The other pattern worth flagging is concentration that reflects over-reliance on legal for low-value work. A business unit that generates an unusually high volume of standard NDAs, template contracts, or routine advisory questions is a candidate for self-service, playbook automation, or requester enablement.

What Does Low Demand From a Business Unit Indicate?

Zero or near-zero demand from a business unit rarely means zero legal risk in that unit. Instead, it usually means one of four things.

First, the unit is routing around legal, either using external counsel directly or making risk decisions without legal input. Second, the unit has an embedded lawyer whose work isn't captured in the central intake system, which is a data problem rather than a coverage problem. Third, the unit doesn't recognize the legal implications of what it does, which usually surfaces later as an incident. And fourth, legal has been positioned as slow or unhelpful by that unit's leadership, and requests have gradually stopped.

The business unit that appears “quiet” is often the one carrying the greatest risk. However, any function whose request volume looks abnormally low for the company's size and industry is worth a direct conversation with its leader.

How to Use the Data in Workforce Planning

The business unit view is one of the few legal analytics inputs that ties directly to structural decisions about the team. Three uses come up most often. 

First, align your team with actual demand. If 40 percent of requests come from sales but you only have one commercial lawyer, the workload is unbalanced. That suggests you either need to hire another lawyer or use an alternative legal service provider (ALSP) to handle the extra work. 

Second, choose between embedded and central coverage: if one team has steady, high-volume legal needs, an embedded lawyer makes sense; if demand is inconsistent or seasonal, central support is more suitable.

Third, when negotiating internal services, per-unit volume data provides the foundation for decisions about chargebacks, tiered SLAs, and shared resourcing.

It’s important to note that none of this works without clean, sustained data. A legal analytics dashboard that pulls request data directly from your intake system, tagged by business unit at the point of submission, is the foundation for using this KPI in planning rather than just reporting.

Key Takeaways

Legal requests by business unit is one of the most useful indicators of what’s really happening in the business. The distribution tells you where legal is respected, where it's routed around, and where the business is quietly accumulating risk outside your line of sight. 

Benchmark this measure against your industry pattern, and treat your own historical trend as the more reliable diagnostic. Use the data to plan the team you actually need, rather than the one that matched last year's assumptions. 

Book a demo to see how structured intake and legal analytics dashboards make this KPI reportable in real time.